Fediverse

28480 readers

707 users here now

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 [email protected]!

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

founded 2 years ago

MODERATORS

[email protected]

How to get involved in new initiatives for Lemmy (wirebase.org)

submitted 1 year ago by [email protected] to c/[email protected]

29 comments fedilink hide all child comments

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 comment's thread
view the rest of the comments

[–] [email protected] 10 points 1 year ago (7 children)

The GitHub repo will be focused on software-level initiatives, whereas I’m talking more about product-level.

If the team is that small, then they need more people involved in product ownership, which is what I’m interesting in contributing towards (as others are too, I assume)

[–] calr0x 9 points 1 year ago (4 children)

I think it's just too early for that level of formality. Basically they're swamped just actually executing changes versus the type of planning you're talking about. Maybe you can offer to help them in some way with that?

[–] [email protected] 8 points 1 year ago (3 children)

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 5 points 1 year ago (1 children)

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.. ;)

[–] [email protected] 4 points 1 year ago (1 children)

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

[–] calr0x 4 points 1 year ago

Sincere thanks for your drive help contribute!

load more comments (1 replies)

load more comments (3 replies)