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.

  • MentalEdge@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    3
    ·
    edit-2
    1 year ago

    You seem to be new to open source projects. This isn’t really how any of these things go.

    Some idividual instances might end up being run the way you seem to think the whole thing should be, but the whole project?

    Just take a look at Jellyfin, it work really well with very little of the structure you’re suggesting. Meanwhile, Emby went to complete shit the more they did that type of thing.

    Anyway, you’ll probably like these: fedidb.org and the-federation.info