This issue is a follow-up to the weekly Solid CG meeting of 2022-12-14 (cf. minutes).
User Stories serve as the basic input for the UCR's (Use Cases and Requirements) which give direction to TR's (Technical Reports). Currently, anyone can contribute a User Story, and label it as they see fit. This begs the question whether the input is being as useful as it could be.
An individual, with possibly little knowledge about the Solid ecosystem, might have very valuable User Stories to contribute, but does not necessarily know which labels to put on them. On the other hand, someone with at least a certain overview over the Solid ecosystem as a whole, has a much better chance at labelling them usefully. Moreover, if such a person also has an overview of the existing User Stories and Use Cases, they would also be able to distinguish more high-level groups of those. Such categorisation is extremely useful for prioritisation and roadmapping the work that needs to be done by the panels.
Would it therefore be a good idea to have someone keep an eye on this repo, and especially on the labels of new User Stories? And would someone be willing to take up that role?
This issue is a follow-up to the weekly Solid CG meeting of 2022-12-14 (cf. minutes).
User Stories serve as the basic input for the UCR's (Use Cases and Requirements) which give direction to TR's (Technical Reports). Currently, anyone can contribute a User Story, and label it as they see fit. This begs the question whether the input is being as useful as it could be.
An individual, with possibly little knowledge about the Solid ecosystem, might have very valuable User Stories to contribute, but does not necessarily know which labels to put on them. On the other hand, someone with at least a certain overview over the Solid ecosystem as a whole, has a much better chance at labelling them usefully. Moreover, if such a person also has an overview of the existing User Stories and Use Cases, they would also be able to distinguish more high-level groups of those. Such categorisation is extremely useful for prioritisation and roadmapping the work that needs to be done by the panels.
Would it therefore be a good idea to have someone keep an eye on this repo, and especially on the labels of new User Stories? And would someone be willing to take up that role?
Edit: Tagging @timbl and @csarven for input.