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.

  • Drunemeton@lemmy.worldEnglish
    51·
    1 year ago

    Welcome to the Fediverse. I don’t think what you’re looking for can exist here. (And that’s by design…)

    Lemmy is the software that ties the instances together. GitHub link was already provided.

    Instances are run independently. Each has “product ownership” in just their own instance. There are over 10,0000 instances, and that number grows daily.

    So you’re going to be trying to get 10,000+ cats to sit still for a group photo. Good luck!

    • tyfi@wirebase.orgOPEnglish
      52·
      1 year ago

      That would be true for metrics/performance reporting, yes. It would make sense to build something that was opt-in for instance owners to submit data.

      Regardless of the mechanism – there will need to be some way to evaluate the performance impacts of changes that are continually being rolled out.

      Thanks :)