Closed DamienIrving closed 9 years ago
Yes - this will definitely migrate to a more agnostic location; it's only under my account right now as we develop things.
(Speaking of, one day this weekend is blocked off for me to respond to all outstanding issues so we can ship by Monday as agreed - get all comments in!)
My current plan is for the site to remain hosted on GitHub Pages (pull-requests FTW!) and to have CloudFlare manage the DNS & HTTPS support. I'll do email redirection using Mailgun, so after that we can fill in the (currently blank) email link.
This approach will also be good if we want to put a link shortener on the same domain, as CloudFlare can cache redirects to reduce traffic, so it shouldn't require a particularly powerful server/hosting environment.
@BillMills I've just invited you to be an owner of the resbaz github repo so that you can do the necessary git-fu to migrate the site across to a new repo called https://github.com/resbaz/resbaz-2016-02-01 (once that repo is up we can add the key people from Melbourne, Auckland, etc as collaborators so they can hack their own pages). @tjdett can then do his thing so that https://resbaz.info (or whatever we decide for the URL) points at http://resbaz.github.io/resbaz-2016-02-01/.
@DamienIrving great! I think the easiest thing to do here, will be for @pkaroly to PR me with her recent changes, get that settled, then transfer my repo to resbaz-2016-02-01
as you suggest.
alright, we're ready to transfer - but I can't transfer this repo while the resbaz org still has a fork of it (not allowed to have two forks of the same repo in the same account). @DamienIrving @pkaroly please make sure everything you want to keep from resbaz-site is merged back into my fork, then delete your fork so I can transfer ownership to resbaz.
I've deleted it
Ok, all done - @DamienIrving, would recommend against giving everyone with a site commit access to this repo; people should be forking & PRing, so that we don't have to spend time cleaning up engineering oopsies. A core team (you me @pkaroly @tjdett) should do fine - I'm happy to be on deck for reviewing all PRs.
Should this repo actually be hosted on the resbaz github account?
e.g. we could have something like http://resbaz.github.io/resbaz-2016-02-01 / github.com/resbaz/resbaz-2016-02-01 to distinguish from future events
I think Flanders is going to purchase resbaz.org or something like that, so then we could have that URL point to the latest github.io site (instructions on how to do that here)