Migrate Registry to xRegistry org

[duglin]

Migrate Registry to xRegistry org

[duglin]

If you can't make the call this week, or if you just can't wait to comment ;-) , feel free to speak-up here so we can gather as much input as possible. I'd like to create a PR to do the migration after this week's call (and then approve it on next week's call).

[jskeet]

Side-note: we should discuss the impact on https://github.com/cloudevents/spec as well. Will it still make sense to have a toplevel "cloudevents" directory when most of the other specs have been moved? (I'm assuming pagination will go as well.) There's still cesql of course - not sure where that belongs, to be honest.

I'm okay with keeping it where it is (aside from anything else, that avoids more work and breaking links), but I think it's just worth thinking about.

[duglin]

@jskeet yep we may want to redo our dir structure afterwards. And thanks for mentioning "pagination", I forgot to add that to the list (just edited the issue).

[duglin]

Add text about the relationship between the specs...e.g. how are dependencies expressed and dealt with as thing are versioned.

[matzew]

I like the idea of the mono-repo here!

One comment/question: Regarding Message Registry spec, isn't that more a Message (Group) Definition Registry spec? Since we group them, and it provides their structure?

[duglin]

@matzew I guess message (and maybe endpoint) are different from schema in that schema IS the resource of interest, while the other two registries defines the shape of the thing of interest. Is it worth being more verbose when it seems like it should be obvious that the exact messages being sent are not in the registry, rather just their shape? What do others think? @clemensv @deissnerk @jessemenning

[duglin]

See: xregistry/spec#1