Update description #13

New Issue

Closed

opened 2023-04-01 07:28:01 +00:00 by helge · 3 comments

helge commented

2023-04-01 07:28:01 +00:00

Owner

I think I want to delimit better where fediverse-ideas should fit into a process. For this, I would propose three (possibly) overlapping stages:

Idea Stage: fediverse-ideas
Proposal Stage: FEP
Implementation Stage: Your repository

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.

Thoughts?

I plan to include this in the README.md of this repository.

I think I want to delimit better where fediverse-ideas should fit into a process. For this, I would propose three (possibly) overlapping stages: - Idea Stage: [fediverse-ideas](https://codeberg.org/fediverse/fediverse-ideas/) - Proposal Stage: [FEP](https://codeberg.org/fediverse/fep) - Implementation Stage: Your repository ![Proposed Flow](https://codeberg.org/attachments/3411e4cc-e521-4e28-8d4a-800b6a9e6197) 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. Thoughts? I plan to include this in the README.md of this repository.

idea-flow.png

6.9 KiB

helge added the

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.

## 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.

👍 1

helge referenced this issue

2023-04-02 10:44:01 +00:00

Update to resolve Issue #13 #17

helge commented

2023-04-02 10:46:15 +00:00

Poster

Owner

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.

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

helge closed this issue

2023-04-02 10:46:15 +00:00

helge referenced this issue from a commit

2023-04-02 18:49:00 +00:00

Update to resolve Issue #13

No Label