Update description #13
I think I want to delimit better where fediverse-ideas should fit into a process. For this, I would propose three (possibly) overlapping stages:
The basic idea is that in the Idea Stage, we collect the information on "Why we want to implement something?"s, e.g. User Feedback, Technical Improvement, Vision, and the "How can it possible be done?"s, e.g. Technical Proposals, Libraries to use, Existing Implementations, and possibly advantages and disadvantages of it.
Then only in the Proposal Stage, a concrete proposal is decided.
Anything that satisfies a basic requirement such as "a person wants it" should be considered valid for the Idea Stage. Furthermore, one should hold oneself to a higher bar before dismissing an idea than for proposing one. For example, nobody discussing an idea is enough form of a dismissal, that one shouldn't feel the need to explicitly write one.
I plan to include this in the README.md of this repository.
I prefer to use SocialHub for discussing ideas. It was historically used for that, it also has categories/tags, and with upcoming ActivityPub support it will become an even better place.
Perhaps fediverse-ideas can be used to work on FEP drafts? This is where version control and code review features are necessary. But we can do that in the main FEP repository too
The Idea tracker
Given that we use an issue tracker here, for this repo it might be more explicitly used as an "idea tracker". Ideas typically mature in multiple places. On SocialHub multiple topics may branch off, and on the Fediverse there's different people, independently or not, talking about the same idea or variations thereof.
This idea tracker may keep a ToC of all those places, bringing them together. It may track metadata as metrics, may keep lists of people who've shown interest in the past, etc.
The process @helge proposes fits in the Idea issue template, and labels of the issue. I gather that in
Proposal Stage on or more cross-references to FEP process are made, and FEP's may receive feedback, updates, or new FEP's created.
When an idea reaches
Implementation Stage there might be more than one project that takes on the idea. Once again they are references to projects that may live anywhere on the web.
I prefer to use SocialHub for discussing ideas.
I agree and will close this issue to avoid setting too much of a bad precedent. Instead, I've formulated the idea as a pull request. Including some of the comments, I would appreciate feedback before merging.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?