Fediverse Futures
Social Media Reimagined
This is a companion to Fediverse Futures on Social Coding to elaborate the Fediverse from high-level, non-technical perspectives, brainstorming our visions and dreams.
We need a more holistic approach to fedi development and evolution. We need product designers, graphics artists, UX / UI / Interaction designers, futurists and visionaries to join the dev folks. Everyone is encouraged to join here and enrich our views on what Fediverse can be with diverse and different viewpoints, and to stimulate brainstorming, creativity, thinking out-of-the-box and crazy, wild ideas.
Some guidelines
- Choose a descriptive title that speaks for itself.
- Be substantive in your comments and stay on-topic.
- Treat others as you want to be treated, respectful.
- Don't be overly critical, we are just brainstorming.
Please read the Social Coding Community Participation Guidelines for more information.
Our fedi hashtags
#Peopleverse #FediverseFutures #Web0 #SocialNetworkingReimagined #UnitedInDiversity #Fedivolution2022 #SocialCoding #ActivityPub
view the rest of the comments
I have been a developer for over 10 years now.
I don't see why an issue must be assigned to a milestone, so I don't see how an issue can break any lifecycle.
@musicmatze @poVoq
The Github Discusions is relatively new feature they added. I did not see many projects yet that are very actively using it.
How an issue is used in a development project is "it depends". Whatever the chosen and preferred method of the maintainers is. If you really want a concise backlog with concrete stuff, and no "pie in the sky" musings on future major extensions, then Discussion section can be very handy. If you don't use discussions, you may end in a situation where off-topic'ish issues sit in the backlog like forever, and pile up.