Skip to content

Conversation

gkellogg
Copy link
Member

@gkellogg gkellogg commented Jul 3, 2022

This is a pretty straight forward copy/paste from the issue into the document, which is probably good enough for now.

Addresses #7, #8, #11, #12, #13, #17, #19, #31, and #35.

cc/ @nichtich, @anatoly-scherbakov.

@gkellogg gkellogg added the UCR Issue on Use Case/Recommendation label Jul 3, 2022
@gkellogg
Copy link
Member Author

gkellogg commented Jul 3, 2022

Note, sadly no PR-preview on the UCR document.

@VladimirAlexiev
Copy link
Contributor

@gkellogg thanks for this!
However I'm wondering whether it's a bit early.

@ioggstream @pchampin what do you think?

  • I don't know much about how the editorial process happens
  • Maybe Gregg did the right thing to start the UCR spec, and now we should appoint owners per section/topic, and they take the responsibility of maintaining the section as discussions unfold on github, and as consensus is reached?

@VladimirAlexiev VladimirAlexiev mentioned this pull request Jul 4, 2022
14 tasks
@gkellogg
Copy link
Member Author

gkellogg commented Jul 6, 2022

This PR was discussed in the 2022-07-06 meeting, and it was decided to not merge now, and wait until more use cases have been identified and reconciled.

@gkellogg gkellogg marked this pull request as draft July 6, 2022 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UCR Issue on Use Case/Recommendation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants