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

Discussions for namespace inclusion #360

Closed
darakian opened this issue Nov 7, 2024 · 3 comments
Closed

Discussions for namespace inclusion #360

darakian opened this issue Nov 7, 2024 · 3 comments
Labels
Needs Discussion Discuss in a future QWG meeting or on mailing list

Comments

@darakian
Copy link

darakian commented Nov 7, 2024

Related to:
#321
#320
#300

Also related to some synchronous conversation from the QWG meeting. I'd like to suggest that proposals for new namespaces be captured in discussions (the github feature). The model I have in my mind is

  1. Users wants a new namespace so they go author a discussion with a title like I want a cool new namespace foobar
  2. In the discussion they lay out why they want it, where the data is expected to come from, where they think the data will go to/how it will be used
  3. Acknowledge any known gaps/deficiencies/etc....
  4. ...
  5. Profit

The thinking here is that we then have a place to capture synchronous discussion. IMO any decision making should be captured in these discussion. Purl could be the first one to try this with since there seems to be demand for formalized purl strings in the affected block.

@andrewpollock
Copy link

It'd be really good to have a central governance document to cover how the working group operates, then it'd be a case of sending PRs to propose evolution of it

@darakian
Copy link
Author

darakian commented Nov 7, 2024

Ya, also good. PRs could be used instead of discussions as well 👍

@jayjacobs jayjacobs added the Needs Discussion Discuss in a future QWG meeting or on mailing list label Nov 8, 2024
@darakian
Copy link
Author

@andrewpollock after stewing on this for a few days I think you're right. There's no need to add another layer of discussion. I've made a fairly basic PR #361 where we can kick the tires on having discussion in PRs 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Discussion Discuss in a future QWG meeting or on mailing list
Projects
None yet
Development

No branches or pull requests

3 participants