Move this repo to outside spacetelescope repo?

[SaOgaz]

Hey @mdboom, we we're discussing this repo in a meeting, and it came up that it might be more appropriate (given it's common external usage) to move this repo outside the spacetelescope organization. STScI has no plan to maintain it going forward. Do you want to take it? If not, any ideas of who would?

Same could be said for the https://github.com/spacetelescope/yaml-schema-standard repo.

[Relequestual]

Hi there. The JSON Schema team has much appreciated this resource! If Mozilla wanted to take it over, that would be great as long as redirects are set up. It would also be a great opportunity to collaborate with those who have some form of investment in the spec and can drive changes moving forward.

Equally, it may be something we could move within the JSON Schema org repo, and give full repo access to you @mdboom or anyone else who wants to / can work on it officially.

If I don't pick up any replies here in a timly manner, please come join the JSON Schema slack.

[mdboom]

Sorry, just seeing this now. I do think it would make sense to move this under the JSON Schema org, if that's still a possibility, @Relequestual.

[pllim]

Please let us know if anyone needs special permission to make this happen. Thank you!

[Relequestual]

OK.
I think we (JSON Schema) will need to decide what we should do here.
We've just had a big update to our site which inclues a new "learn" section.

I'll flag this for discussion!

[Relequestual]

Feel free to assing myself to this task so I can better keep track that my action is required on this. Thanks.

[mdboom]

Thanks. Unfortunately, I can't assign you since this project is now STScI folks-only. However, I'm happy to coordinate with you to move this if that's still something the json schema org wants to do. If not, just let me know, and I'll just move it to my personal Github account.

FWIW, I've spent some time updating this for Draft 6 on my personal fork, and will add Draft 7 once Python's jsonschema library adds support so it can be validated. I'm eager to push that out to wherever the next location of this is likely to be.

[pllim]

@Relequestual , please accept collaborator invite, then I should be able to assign you. @mdboom , you should still have admin access to this repo, but if that is not the case, I'll be happy to fix the settings for you, so just let me know. Thank you, all!

[mdboom]

OBSOLETE: New steps below

[Relequestual]

@pllim Thanks for the invite. I've noted it, but have not yet been able to action it. Will do shortly.
@mdboom This is all really exciting!
I think a few of these things are out of the order they should be.

I'm going to reach out to github support first, as transfering the repo to a different org WILL effect the live site as it runs on github.io. I think we might actually not need to set up any redirects, but this is something I'll check with Github. They are usually pretty speedy to respond.

I'll be back here once I know more.
I'm on this!

[mdboom]

Cool, thanks for drilling down on those details!

[Relequestual]

Update:

When transfering a repo from one org to another, all github.com URLs will redirect as expected, but github.io aka github pages will NOT redirect.

After the transfer, you COULD create a new repo her with the same name, and add a readme with a redirect notice, and have the github pages site auto redirect, but then the github.com URLs would not redirect.

Any thoughts on how best to proceed anyone?

[mdboom]

I think the redirecting the Github pages, with a README note is probably our best option. Most users of the content will be automatically redirected, and potential contributors (a much smaller and more motivated group) will just have the small hiccup of needing to jump over to the new repo. We can update the "Fork my on Github" banner and any other contributing instructions like that to the new repo as well.

It does seem like we'll need to coordinate this move carefully so minimize downtime at the old URLs, however. Maybe we'll want to set aside some time when myself, someone at STScI and someone on the json-schema org are all available at the same time (which will be a little tricky with timezones)...

[pllim]

I'll be happy to help next week. Please email me to coordinate.

[Relequestual]

I'm in UK, so coordination is possible.
@mdboom Would you like to put together a revised ordered checklist based on these plans? =]

@pllim Sorry, I do not have your email! Maybe @mdboom can provide?