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.

  • tyfi@wirebase.orgOPEnglish
    92·
    1 year ago

    The issue with that approach (too busy to build structure), is that it’s a never ending battle. There is never a good time. It’s an easy trap to fall into.

    The best way to be successful with products like this is to invest time early in building out the team. By doing so, you’re multiplying output and limiting tech debt.

    I would even be happy to help with helping build out the team (identifying gaps, key roles, volunteers) as that’s something I’m experienced with.

    • calr0x@sh.itjust.worksEnglish
      5·
      1 year ago

      None of this should come across as argumentative or being short. My understanding is it’s just two people so I still think this isn’t a time to have ideas. Shoot them a message on GitHub or whatever community they have set up for feedback and help build the ranks to get them to help they need… ;)