META: merging projects into organization

Hello, picking up the conversation from https://github.com/Cacodaimon/GhostText-for-Chrome/issues/43 I want to suggest to merge the 4 repos as much as possible to avoid diluting our efforts and simplify issue creation.

I created a GH organization that would include the necessary repos: https://github.com/GhostText

It’s currently filled with placeholders to better illustrate it

https://github.com/GhostText/GhostText https://github.com/GhostText/GhostText-for-Atom https://github.com/GhostText/GhostText-for-SublimeText

Unfortunately the editors require direct access to the repos so we have to keep them separated, but we can still benefit this merge by disabling issues on both.

Here’s the suggested order of operations and the suggested operator (me: 💙; @Cacodaimon: 💚)

• 💙Push a copy of both GT-ST and GT-A to the temp repos
• 💙 Point packagecontrol.io to the new repo (https://github.com/wbond/package_control_channel/pull/5408)
• 💚After packagecontrol move is verified to work, do this:
  • 💙delete GhostText/GhostText
  • 💚rename repo GhostText-for-SublimeText to GhostText
  • 💚transfer Cacodaimon/GhostText to the org GhostText this will let us keep the existing link Cacodaimon/GhostText-for-SublimeText point to GhostText/GhostText (main repo changes name, in short, while GH keeps a redirect. I just verified it to work) even though this repo won’t actually contain GT-ST
• 💚 Point apm (Atom) to the new repo
• 💚After apm’s move is verified to work, do this as fast as possible
  • 💚delete GhostText/GhostText-for-Atom
  • 💚transfer Cacodaimon/GhostText-for-Atom to the org
• 💙Manually merge GT-Ch and GT-FF into GhostText/GhostText, fully replacing its contents
• 💙Empty your existing GT-Ch + GT-FF repos and keep a notice that they moved
• 💙Move all issues to GhostText/GhostText (which will already have existing GT-ST issues) and tag them appropriately (Chrome/Firefox/Atom/SublimeText)
• 💙Leave only one issue open in remaining Cacodaimon/GhostText-… repos open in each: “DON’T OPEN ISSUES HERE”
• 💙💚 Review, close this issue, get beer

By following this:

• package managers will keep working
• all existing internet links will be kept or redirected
• issues will live in a single repo, tagged appropriately
• browsers will share similar code effortlessly

[FichteFoll]

FYI, renaming repos requires the Package Control Channel to be updated because it uses the API to fetch data and github does not set up redirects for the API endpoints.

You both should also publicly declare your membership in the org, so that users can see who the maintainers are. 😉

[fregante]

Thanks for the all the info @FichteFoll!

I saw the org appear on my profile but I didn’t realize that only I could see that. 😃 I’m public now!