We are beginning our journey of defining our Code Collaboration Data (CoCoDa). Some initial discussions have been going on in Radicle Collaboration Tools.
In this discussion we want to guide the process of defining the data involved with issues that
radicle-link will store and
radicle-upstream will store. This initial discussion should be a back and forth as to what user needs we expect, what kind of use stories we expect, and ultimately should lead to a more canonical definition of how we expect issues to look in the radicle ecosystem; likely to be specified in a spec document.
Taking a look at how GitHub models issues an issue is made up of the following components:
- Sequence of Comments
Comments are composed of:
And then inside a Body we have interesting artifacts such as URLs, links to other artifacts, links to other projects. These will be on the more difficult end of things to present.
Some of the stories that can come to mind:
- Create an Issue
- Edit an Issue’s Title
- Edit an Issue’s Body
- Add a comment to the Issue
- User edits Comment
I think it would be useful to visit the above as denotations since that will show us what types need to be used and these user stories are functions. But lemme know what you think @xla @rudolfs @garbados (I would tag Sarah but it seems her discourse isn’t set up yet ;)) is there things that I may be missing here? Is there anything I can elaborate, or you would like to elaborate on?
Peace my fellow Radicles