After recent discussions of creating a new repo dedicated to font creation, https://github.com/Khan/KaTeX/pull/632#issuecomment-323603003, I decided to create a github organization for KaTeX.
I was thinking we would start out with the following repos:
To get started we'd do the following:
This is kind of a big deal so I'd love to get everyone's thoughts and concerns before proceeding further.
I'm still new to Github organizations, but this sounds fine to me. I take it that all issues etc. get preserved by the move, which is nice. The main change is that the git repo changes URL? A potential worry is that someone has KaTeX's git link hard-coded (e.g. via NPM -- though not sure if this works), and they need to update. But that's the price of living on the bleeding edge, I suppose...
All of the issues will be preserved with the move. We'll probably want to create a Khan/KaTeX fork from KaTeX/KaTeX after the move that way if someone does have something hardcoded it will still work. We should probably have a message that top of the Khan/KaTeX README.md pointing people to KaTeX/KaTeX. There is link from https://www.npmjs.com/package/katex to Khan/KaTeX but we should be able to update that. We'll need to update gitter as well.
Nice idea to fork/link. The NPM link comes from package.js, so if we update that and do another npm publish (presumably part of the release script), then we'll be all set.
Based on previous experience, the fork/link shouldn't actually be necessary because GH automatically redirects old repo URLs to the new one: https://help.github.com/articles/about-repository-transfers/
Update: we now have https://github.com/KaTeX. The main repo will continue to live at Khan/KaTeX for the time being though.
This repo has been transferred to the KaTeX Github organization.
@kevinbarabash I'm excited to see the new organization is in action!
It seems a Gitter chat room should be manually created and Greenkeeper may not work. Also the screenshotter GitHub app need to be reinstalled.
We'll also have to update the badges in the README.
Most helpful comment
Nice idea to fork/link. The NPM link comes from
package.js, so if we update that and do anothernpm publish(presumably part of the release script), then we'll be all set.