Relationship between UCRs and Solid user-stories
Closed this issue · 2 comments
On proposal
ACP, WAC, WAC+...
Details
What is the relationship between the UCRs defined by the authorization panel and the Solid user stories on authorization?
Acceptance criteria
- Understand how UCR and user stories overlap and what form of reuse or linking should be adopted
- Agree on an adequate plan of action
The user stories, from my side, are intended as a extremely low threshold thing for the community to contribute their needs in a structured manner that can potentially be useful.
We learned very soon that it is actually very hard for people to come up with use cases that can inform spec in a useful way, the response is usually "yes, Solid can do that, just write some client code". We shouldn't have people wasting their time writing stuff that can be dismissed that easily, and we shouldn't spend time having to go through them and dismiss them either, it isn't nice and good use of time for anyone.
Therefore, we created the user-stories repo so that people can submit these one-liners, without making a huge effort, and yet, structure them better. This makes it more likely that a small effort can make something that is actually useful.
My idea is then that the user stories can be closed once we can point people to an implementation that does what they wanted.
The UCRs should be a more elaborate thing done by experts. They should be encouraged to review the user stories, but also other sources of information. The UCR are what is the immediate motivator for spec work, user stories a mere help to experts.
But then, I also hope that user stories can be a broader view, so that experts also find it useful to submit user stories.
Thank you for the clarification @kjetilk.
I guess the adequate plan of action would then be, when time allows, to go through the Solid user stories on authorization and link them back to existing answers. I would propose that this plan of action is generic to all user-stories issues as opposed to tightly coupled to the authorization panel and therefore, that this issue should be closed.