Hi all. Very happy to see Lemmy’s success so far. I’m interested in contributing to Lemmy’s growth.
At this stage, the engineering team should consider bringing some additional public-facing structure, such as:
1. Published roadmap
2. Performance metrics and reporting
3. Community outreach - keeping user base in the loop on roadmap, launches, metrics, growing pains
Lemmy will continue to grow regardless, however bringing some structure will onboard new users faster and add trust to Lemmy’s image. Trust factor is important - Reddit refugees are evaluating alternatives to Reddit, and are ultimately choosing off relatively little information.
What is the best way to get involved in new initiatives for Lemmy? I have experience with this type of work (engineering manager at a large tech company), focused on building teams, product roadmaps, and continually improving customer experiences through engineering.
Are you talking about all of the Lemmy instances, or just Lemmy.world?
I’m talking about Lemmy as a product - not specific to any instance
Gotcha, then the comments delirium@lemmy.world and drunemeton@lemmy.world left are going to be your best answer. You seem to be thinking there’s a corporate hierarchy to Lemmy when it’s all a bunch of hobbyists on both the software and server host levels. And like drunemeton said, by the thousands.
Would the same apply to something like creation of a new website? Or a weekly newsletter, or similar? I was assuming that non-dev work would be coordinated outside of GitHub, but could be wrong!