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

Turn the WG into a maintenance WG #110

Merged
merged 20 commits into from
Aug 15, 2024
Merged

Turn the WG into a maintenance WG #110

merged 20 commits into from
Aug 15, 2024

Conversation

pchampin
Copy link
Collaborator

@pchampin pchampin commented Mar 5, 2024

@iherman
Copy link
Member

iherman commented Jul 5, 2024

  • Having been on the receiving end of such comments no later than yesterday: you should sync the charter text with the latest charter template, otherwise this will be rejected. The new charter draft includes a bunch of small changes (e.g., all pointers to the process document are now different, there is a reference to the TAG principles, etc...), which is a pain in the back side to sync with, but there you go (the comment I got is that it is better to start with the template rather than the old charter text...)
  • In particular, the charter should now begin with a separate section on "motivation and background", which should probably absorb most of what is in the scope section now. The scope is supposed to be very short now, some sort of legal text...
  • I am not sure that the mission statement should stay as is. The mission of the WG is to "maintain" and not to "define".
  • Similarly, the scope should say that we maintain and not do anything more new development. This is not the way it reads right now...
  • It is probably a good idea to add a note that the WG is authorized to do class 4 changes on the spec.

@msporny
Copy link
Member

msporny commented Jul 5, 2024

Supportive of the charter, with @iherman's changes applied.

Copy link
Collaborator

@dlongley dlongley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 with @iherman's changes applied.

Copy link
Collaborator

@philarcher philarcher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks PA

@pchampin
Copy link
Collaborator Author

pchampin commented Jul 9, 2024

All of @iherman's suggestions should now be addressed.

Copy link
Member

@iherman iherman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left one comment; approving once that is taken in consideration (it is just an editorial change).

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
clarification suggested by @iherman

Co-authored-by: Ivan Herman <ivan@w3.org>
Copy link
Member

@gkellogg gkellogg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the RDF-DEV CG should be replaced with the RDF-star WG for coordination. I wouldn’t be adverse to listing both, but the RDF-DEV CG isn’t working on RDF-star at this point.

Copy link
Collaborator

@philarcher philarcher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've committed a couple of changes to the scope section to refer to the published explainer doc (https://www.w3.org/TR/rch-explainer/) rather than the local copy which seems broken anyway. Ignore that commit if you disagree.

Copy link
Contributor

@yamdan yamdan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @pchampin. I approve it with a few editorial suggestions similar to those made by @philarcher.

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
@pchampin
Copy link
Collaborator Author

@peacekeeper I need you to approve the PR before I can merge it

Copy link
Member

@TallTed TallTed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor, editorial

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
@pchampin pchampin removed the request for review from peacekeeper August 13, 2024 10:13
@pchampin
Copy link
Collaborator Author

I still am unable to merge. Probably because @TallTed requested changes, which I just accepted. @TallTed can you now approve the PR?

@pchampin pchampin merged commit 864b74c into main Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants