You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Users wants a new namespace so they go author a discussion with a title like I want a cool new namespace foobar
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
Acknowledge any known gaps/deficiencies/etc....
...
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.
The text was updated successfully, but these errors were encountered:
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
@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 👍
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
I want a cool new namespace foobar
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.
The text was updated successfully, but these errors were encountered: