Hi all,
I'd like to propose that we move Conductor and aeolus-configure over to
GitHub. (Bear with me for one second, please.)
"But wait," you're thinking. "Didn't we just have that discussion
the
other week?" Not like this.
What I'd like to propose is that we keep our workflow exactly the same
as it is today, but move the repository from FedoraHosted to GitHub.
We'll still send patches to the list, have someone test them and send an
ACK to the list, and then push the code. It'll just be to the git repo
on GitHub instead of the repo on FedoraHosted.
Why do this? Two reasons, really:
a.) Most of the other Aeolus projects are already on GitHub. This way,
everything will be in one place.
b.) GitHub is a lot more widely-known than FedoraHosted. If we link
people in the community to the GitHub page for Conductor, most will
instinctively know how to clone the source and how to start
contributing. As it is today, I have to cat .git/config to have any idea
where our repo lives.
I think that we should probably do this at the end of this sprint before
starting the next one, since I imagine moving it mid-sprint would be too
disruptive. Does anyone object to this change?
I think the change will look something like this:
1.) Create the Conductor and aeolus-configure repos on GitHub, and give
existing developers commit rights there
2.) Change our .git/config files to point there
3.) Update the
aeolusproject.org site which has documentation pointing
to the FH repos
4.) Update Redmine's repo browser to use the new location
5.) Modify Jenkins to use the GitHub repo
6.) Send out an email explaining the change and telling everyone what
they need to do
7.) Add a logo to the main Aeolus Project organization to replace the
default octocat
Again, I'm happy to take the lead on making this happen, but I want to
make sure there's consensus. (Plus, I don't have rights to the project
right now.)
What do you think?
Best,
Matt