Be the change you want to see in Lemmy
Be the change you want to see in Lemmy
There have been various posts here in the last days describing how difficult it is for new people to start using Lemmy. In fact they are absolutely correct, it is much easier to get started on Reddit. But what many forget is that Lemmy is not a corporation employing dozens of full-time designers, running A/B-tests and so on. Lemmy is an open source project run by volunteers, with only @dessalines and me working on it full-time. Neither of us is a particularly good designer, and our time is mainly spent working on the backend (database, federation, api), and preparing the upcoming 1.0 release.
If you see anything on join-lemmy.org or in the Lemmy UI itself that could be improved, the best option is to make that improvement yourself. Both of them use standard web technologies (nodejs, tailwindcss, inferno etc). The userbase here is quite technical so there are many of you able to contribute. We rarely reject any pull requests as long as they make a real improvement. Though it usually requires a little back and forth to review the changes and then address the review comments.
You can find the source code for join-lemmy.org here and follow development instructions in the readme. Regarding the default Lemmy UI go here and read the documentation with development instructions. If you are not a developer you can still help, for example by improving the documentation. Additionally you can make changes to the texts for joinlemmy and lemmy-ui.
All this said, there have also been some suggestions to make onboarding easier by directing new users to a hardcoded default instance. This may sound like a good idea at first but won't work well in practice. Running such an instance would take significant time for administration and moderation, but we maintainers are already too busy. Besides it would be impossible to reach an agreement who this default instance should federate with or how exactly it should be moderated. So if you want to get nontechnical users to Lemmy, the solution is to link them directly to a specific instance based on their interests.
You're viewing a single thread.
The userbase here is quite technical so there are many of you able to contribute.
As a project manager, I can help by ballooning the scope and setting the deadline to yesterday! Doing my part!
Oh, I can do project management too!
Your next task is waves hands around ... the thing ... waves hands around some more ... like the other thing ... but different.
I got you guys, lets start with daily standup to get everyone on the same page.
Don't forget about asking how the project is going too!
Didn't be so hard on yourself. You can also pester us about the status of Jira tickets.
Honestly, if my PM never pestered me about the status of my tickets, I would never close them. Some of us need the pestering!
Also, why haven't you closed that low priority ticket and you keep working the high priority tickets that are new.
My old company solved that problem by making everything high priority by default, with efforts directed by the whims of the CTO.
That's a recipe for disaster if I've ever heard of one. Fixing Jane in accounting's monitor or figuring out the routing table for the entire enterprise. All top priority!