Move to GitHub org?

[zpnk]

Opening this up to start a discussion about the benefits/logistics of moving this project to it's own GitHub org.

Ideally, the org could also house the deploy.now project.

While we're at it, it's probably worth merging stage.now (website/docs) and stage-ci (server) projects into a single repo.

Tagging in folks who have been active in the project: @jimthedev @paulirish @amccloud @mxstbr @hugomd

What are everyone's thoughts on this?

[paulirish]

Of particular note is that Github handles redirects really well: git URLs and all that should redirect fine so we should have a lot of flexibility here.

I'm a big +1 on github org in general for coordinating work on a project. The permissions model is just so nice.

In this case I don't think its absolutely necessary that there's a "stage.now" org, though that may be nice. If you wanted to put it under the changepane org, that seems reasonable, too, though that may communicate certain expectations about maintenance and ownership you want to avoid.

If i were to do it, I think i'd go with:

• github.com/stage-n-deploy/stage.now
• github.com/stage-n-deploy/deploy.now

Naming the org is pretty tricky. :) shrug

[jimthedev]

Generally I'd recommend keeping the org separate from your company org since it easier to hand off the org if you ever wanted to. It also allows you to maintain private forks of repos for your business if you ever needed to. Lastly, you two will likely work together for a long time, but in the event that one of you parted ways and was removed from the company, you'd still be able to collaborate in the separate org.

Then again, premature optimization is a thing. I guess I figure that since you're making the change, might as well have a clean break. This is what I did with commitizen and it has worked out well even when I've gone between jobs and had contributors come and go.

stage-n-deploy is actually pretty good. +1 on that @paulirish (PS. Thanks for everything you've done for our community. You made me a better developer. I remember watching some crazy video where you were wandering around your parking lot while doing some sort of webperf or grunt q&a back in the day). Keep it up! 👍

[hugomd]

I agree with the above.

Moving the repositories to an organisation would make it easier to handover maintenance to someone else, or to increase the size of the team maintaining.

It also depends on whether you think more repositories might come out of the organisation as well. It's just as easy to add more maintainers to the current repositories as it is (I think), but if the number of repos is likely to grow, then it would be reasonable to group them all up for easier permissions handling.

🚀