vc-use-cases

vc-use-cases copied to clipboard

1.7. Review Editor/Author section (issue vc-use-cases#107)

See github issue vc-use-cases#107.

Kristina Yasuda: Is this outdated?.
… need to review editor author section?.

Joe Andrieu: I don't think it is. As opposed to how we handle the normative specs, who should be an editor or author, this is somewhat leftover. I don't have a good sense of how we should change this..
… the new version editors is just Kevin and me.
… I defer toManu for how to clean it up.

Manu Sporny: we have people on here who haven't been involved in years. We can add the version they worked on next to their names..
… I need to change the respec so we can list all the people who have been involved without it taking up a whole page..
… It is important to acknowledge all of the people who have contributed, but it should be easier to read..

Kristina Yasuda: can I assign you?.

Manu Sporny: yes, I have a similar action on vc data model.

Kristina Yasuda: Joe, can you give a quick look to see if any of these should be discussed, or we can shift to other doc?.

Kristina Yasuda: https://github.com/w3c/vc-use-cases/issues.

Kristina Yasuda: people, take a look at the issues to see if there's anything folks want to talk about.

Manu Sporny: we have a number of VC systems going into production, it would be good to list them in the use cases doc..
… whatever public gossip we can talk about.

Joe Andrieu: we are going to put out a call for input, new short use cases, extant use cases.
… we do want to have a section that is current uses of VCs. It will be short. a way to look at signals of market adoption for the technology.

Kristina Yasuda: that sounds like a great next step.

Joe Andrieu: not sure how much time is set aside in the F2F, but the call will probably go out after that..

Kristina Yasuda: we can take some time during F2F.
… and mark some issues as pending close if they are outdated.