search

w3c / rdf-star-wg

RDF-star Working Group
Other
25 stars 8 forks source link

Editor assignments - Add here which spec you would like to work on #11

Closed ghurlbot closed 9 months ago

ghurlbot commented 1 year ago

Based on the list of #10, we want to track who volunteers to work on what spec(s). If you work on a spec, please add your name in the form of - @username so we have it properly indented

pfps commented 1 year ago

I don't seem to have edit permission here.

ktk commented 1 year ago

@pchampin could you check if @pfps is in the proper groups?

afs commented 1 year ago

Editor and contributor are not the same.

Surely anyone can contribute?

hartig commented 1 year ago

I also don't seem to be able to edit the entry above.

kasei commented 1 year ago

If the intention is to edit the issue text in-place, then I also seem to need the right permissions.

ktk commented 1 year ago

It was but maybe that doesn't work with the permissions set up. In worst case comment here and I will update the list.

@afs can you clarify the roles?

gkellogg commented 1 year ago

@pfps said:

I don't seem to have edit permission here.

Only users with update access to the repo can edit comments of other people,, so this might not be the best way for people to add. I'd suggest they sign up in a comment, and someone with the appropriate access can update the list.

Ideally, each spec should have at least two editors, but anyone/everyone is encouraged to contribute either directly, or by reviewing and commenting on PRs. Having update access to the repo isn't really necessary to contribute, but it simplifies things for frequent contributors, as branches can be made directly on the repo, and not through a clone, which makes it easier for other contributors to directly build on that.

kasei commented 1 year ago

sparql-query sparql-service-description sparql-protocol sparql-federated-query sparql-results-json sparql-results-csv-tsv

pfps commented 1 year ago

rdf-semantics

afs commented 1 year ago

@afs can you clarify the roles?

Without wishing to prejudge the chairs views:

A contributor

They don't need write access but it does make it easier for frequent contributors or when working on a large PR because the branch can be in the doc repo and others can PR that.

An editor is taking responsibility for a document as a whole.

hartig commented 1 year ago

rdf-concepts sparql-query sparql-federated-query

domel commented 1 year ago

rdf-n-quads rdf-n-triples rdf-trig rdf-turtle rdf-schema sparql-results-xml

rubensworks commented 1 year ago

sparql-query sparql-update sparql-service-description sparql-results-json sparql-results-csv-tsv sparql-results-xml sparql-protocol

doerthe commented 1 year ago

rdf-semantics

ktk commented 1 year ago

@afs I clarified the title, "contribute" is no longer part of it. Hope this is a bit clearer that way, thanks for your comment.

timothee-haudebourg commented 1 year ago

rdf-schema rdf-semantics

gkellogg commented 1 year ago

I did look up information on each assigned editor, and here are individual records that can be added, as appropriate. I'll do this for all the RDF specs as part of the preparation. Ordering isn't significant right now, and can be worked out by management and the editors later.

[
  { name: "Gregg Kellogg", w3cid: "44770" },
  { name: "Ora Lassila", w3cid: "9656"},
  { name: "Olaf Hartig", w3cid: "112469"},
  { name: "Pierre-Antoine Champin", w3cid: "42931"},
  { name: "Dominik Tomaszuk", w3cid: "44239"},
  { name: "Timothée Haudebourg", w3cid: "138654"},
  { name: "Dörthe Arndt", w3cid: "111308"},
  { name: "Peter Patel-Schneider", w3cid: "13382"},
  { name: "Andy Seaborne", w3cid: "29909"},
  { name: "Gregory Williams", w3cid: "38870"},
  { name: "Ruben Taelman", w3cid: "84199"},
]

Note that the Person record allows more fields. I'd suggest limiting additional records to the following:

There is a url field to link to the editor's personal page, but these have sometimes proved to be a problem when it comes to validating the document, but can certainly be used if there's a good reason.

franconi commented 1 year ago

rdf-semantics

Tpt commented 1 year ago

sparql-query sparql-update sparql-results-csv-tsv sparql-results-json sparql-results-xml sparql-protocol sparql-graph-store-protocol

pfps commented 9 months ago

I think this issue has passed its expiry date.

afs commented 9 months ago

The editors on the doc themselves is definitive so no real need for this issue that I can see. The issue was a quick way to progress at the start.