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.

  • maegul (he/they)@lemmy.mlEnglish
    1·
    1 year ago

    So lots of talk in here ATM of it being a small project with a small and busy team etc, which is all totally fair.

    I’d just like to add:

    1. You’re awesome for wanting to get involved and to do some of the “other work” that is often easily and problematically neglected!!
    2. The fediverse, as you’ve been told here, is FOSS and voluntary, which means that if something doesn’t exist it’s just because someone hasn’t done it yet! Which means just getting involved and doing things isn’t only possible but kinda the whole point!

    As for contacting devs and contributors, yes, the GitHub repos for both lemmy and lemmyui and the issues sections there.

    But they are also on matrix and AFAICT a good amount of chat happens there, so that’s probably where you want to go. I believe there’s a link to their matrix space here: https://join-lemmy.org/docs/contributors/01-overview.html#contributing