JellyFin
Booru-style Image Boards like rule34
ArchiveOfOurOwn
The problem is that there are so many different ideas to do that that I doubt they are anywhere close to reaching a consensus. There was the user created multi-communities idea, another about moderators being able to subscribe a community to another, and a few others.
Here is the main discussion:
Account migration similar to Mastodon
That isn’t in the works. @nutomic@lemmy.ml decided to close the issue on GitHub without waiting for community input:
Idk if its in the works but really want transportable profiles, and the ability to add a licence to content i post like pixelfed and peertube.
That isn’t in the works. @nutomic@lemmy.ml decided to close the issue on GitHub without waiting for community input.
Would also be nice to have tags hopefully they federate with mastodon.
The problem is that there are so many different ideas to do that that I doubt they are anywhere close to reaching a consensus. There was the user created multi-communities idea, another about moderators being able to subscribe a community to another, and a few others.
Here is the main discussion:
Those issues seem to be closed without completion.
An Initial Public Offering (IPO) is the process through which shares of a private company are made available to the public for the first time, allowing the company to raise equity capital from public investors. This transition from private to public enables private investors to realize gains and allows public investors to participate in the offering.
I don’t want this to become a rant thread, but the devs have frequently told contributors “No one is forcing you to develop for Lemmy”. That’s but one example.
having a less toxic development community
What exactly do you mean by “toxic development community”? I’ve heard some critique of Lemmy developers for being tankies but I’ve never heard something like this about Lemmy.
Yeah keyword, tag or regex blocking would be nice. Something like this:
Why in the world did you enclose the readme in a code fence, though? It would be so much better to let the markdown do its job. My eyes are burning.
I wanted to use a quote to differentiate it a bit from the post but Lemmy-ui only quotes the first line.
I agree, but the post is pretty much a copy/paste from the comment where I learned about the project, so blame @ptz@dubvee.org
Controversial was added on 0.19 release. This is the pull request.
Love the milestones it’s what I think Lemmy is missing most that makes me excited about other projects.
That’s already came in the latest 0.19 release.
I was really looking forward to scaled sorting on Lemmy, but it didn’t quite live up to my expectations. I thought it would be like the “top” sort but with more diversity, but it ended up feeling more like the “new” sort with most posts having just a single vote.
Right now I’m not particularly excited about any upcoming features. The last release had some great additions.
I wish there was a roadmap for Lemmy so I could anticipate future releases like I do with other projects.
It would also be great to have nightly builds for testing new features before they’re officially released on most instances.
Building and Sustaining Vibrant FOSS Communities
Free and open-source software (FOSS) projects live and breathe through the strength of their communities. From Linux to MongoDB, some of the most widely used software today has been built through the collaborative efforts of contributors across the globe.
Here are some of the factors that can help FOSS projects cultivate an active, engaged community that drives development and innovation over the long run.
Funding Models That Sustain Open Source Work
Funding is oxygen for open source software. Platforms like Open Collective have pioneered issue bounties that incentivize contributions to FOSS projects. Although Open Collective itself is shutting down, other models like monthly subscriptions, bug bounties, and crowdfunding campaigns can help support ongoing development.
Building a Supportive Community Platform
An active Discord server, discussion forum or mailing list fosters closer collaboration within the user and contributor community. It facilitates conversations about new features, issues, and direction for the project. A vibrant community platform keeps engagement high even when development slows down.
Roadmaps and Transparency Around Development
A public roadmap on GitHub that outlines feature requests, bug fixes and other issues being tracked for the project is invaluable. It informs both users and contributors on what’s next for the software and when they can expect key updates. Over time, it builds trust and transparency.
The Takeaway
Vibrant FOSS communities don’t happen by accident. They require planning, communication and most importantly, nurturing contributors and users. By taking the time to build funding models, community platforms and development roadmaps, FOSS projects can sustain themselves for the long haul and continue innovating.
deleted by creator