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.orgOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I was thinking in terms of helping build out a team to work on non-dev related work, as opposed to pulling away time from the devs, who I’m sure are heads down. Fair points though!

    • Phegan@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Thanks for the positive response. I still expect Reddit style responses where I get eviscerated for raising counter points.

      • tyfi@wirebase.orgOP
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        It’s so toxic most of the time. Same to you!

        I’m hopeful that the federated approach results in better discussion overall. Seems like it could!