this post was submitted on 02 Jul 2022
8 points (100.0% liked)

Fediverse Futures

982 readers
1 users here now

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

Please read the Social Coding Community Participation Guidelines for more information.

Our fedi hashtags

#Peopleverse #FediverseFutures #Web0 #SocialNetworkingReimagined #UnitedInDiversity #Fedivolution2022 #SocialCoding #ActivityPub

founded 3 years ago
MODERATORS
 

Forge Federation Needs Your Help 🤗

🚀 Join the forge federation matrix chatroom, or the (less active) gitea federation room.

you are viewing a single comment's thread
view the rest of the comments
[–] musicmatze@lemmy.ml 1 points 2 years ago (1 children)

An issues is usually a bug report or similar

Usually? And when it is not?

See, I don't see any reasons why a feature discussion shouldn't be an issue. "Issue" is just a fancy name for "Discussion", isn't it? So basically, these are all some kind of linear or tree-style discussion of some specific topic. There's nothing more to it, is there?

So I don't see why they should be seperate at all. Differentiation can be done via tags, labels, ... or whatever you'd like to call it. That's there already of course.