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.

  • oatmilkmaid@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    2
    ·
    edit-2
    1 year ago

    Not to sound rude or anything - but I’m getting big corporate vibes from this post which really isn’t what Lemmy is trying to be. If you want to offer that kind of support, look at getting involved with individual instances. They are probably closer to a product than Lemmy is. The Lemmy project doesn’t need that kind of corporate structure to it. It’s not a charitable organization or Reddit 2.0.

    Furthermore Lemmy users are not customers nor is Lemmy a product and it worries me that you would want to see it in this lens.

    • SomeOtherUsername@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      Might have been written by ChatGPT? lol. He does have a point though, if someone wants to contribute, it’d be nice to know what the devs would actually merge.

      • oatmilkmaid@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        Mind you I’m happy that they seem driven to contribute and want to know more about the process and how to potentially help. It’s really just the vibe of the post that’s off putting.

        For contributing to the project, you can always submit issues to discuss next steps or possible ideas and implementation. It’s not just “here’s code please merge”. Being a contributor to an open source project also involves participating in discussions about the future of the project which you can usually do through mailing lists or issues for most projects.

        For Lemmy specifically there is already a process for feature requests and discussions here

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

      I’m just talking about contributing time to helping develop a platform. Corporations are good at process - so yes, there are definitely lessons to be learned there that should be implemented in any platform that is quickly growing (eg: putting a team of volunteers together to help out)