Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review Editor/Author section #107

Open
stonematt opened this issue Aug 2, 2019 · 4 comments
Open

Review Editor/Author section #107

stonematt opened this issue Aug 2, 2019 · 4 comments
Assignees

Comments

@stonematt
Copy link
Contributor

Need to review and Update Editor/Author section to verify it's correct.

@iherman
Copy link
Member

iherman commented Feb 8, 2023

The issue was discussed in a meeting on 2023-02-07

  • no resolutions were taken
View the transcript

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.

@jandrieu
Copy link
Collaborator

jandrieu commented Feb 9, 2024

This latest version has been edited by myself and @KDean-GS1. I think the right thing to do is to acknowledge the other currently listed editors as authors and keep the existing author list (as we have not removed contributions that might remove an author's work).

@brentzundel
Copy link
Member

@jandrieu I support that adjustment

@TallTed
Copy link
Member

TallTed commented Feb 9, 2024

Better to move formerEditors from Editors. Authors is a different kind of contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants