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.

You are viewing a single thread.
View all comments View context
6 points

If GitHub is the best way to get in touch for non-dev initiatives, then I’ll do that. Thanks.

permalink
report
parent
reply
5 points

Sincere thanks for your drive help contribute!

permalink
report
parent
reply

Fediverse

!fediverse@lemmy.world

Create post

A community to talk about the Fediverse and all it’s related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

  • Posts must be on topic.
  • Be respectful of others.
  • Cite the sources used for graphs and other statistics.
  • Follow the general Lemmy.world rules.

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

Community stats

  • 3.9K

    Monthly active users

  • 1.8K

    Posts

  • 62K

    Comments