<p dir="ltr">I've used Github in the past, it works well. I'm not sure if gitorious has it or not but github allows you to use https and avoid the whole ssh issue. The merge feature is pretty handy and allows for one or two control the main codebase easily.</p>
<div class="gmail_quote">On Sep 17, 2012 11:15 PM, "David L. Anselmi" <<a href="mailto:anselmi@anselmi.us">anselmi@anselmi.us</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
tl;dr: git is cool and the CLUE web site could go up on gitorious soon. Linus is funny and I'd like<br>
to hear about your experience.<br>
<br>
So I started playing with git. Finally.<br>
<br>
I saw <a href="http://blogs.gnome.org/woody/2012/09/15/manage-your-website-through-git/" target="_blank">http://blogs.gnome.org/woody/2012/09/15/manage-your-website-through-git/</a> and thought, "yeah, I<br>
want to do something like that." Of course there are lots of posts like that and what I want isn't<br>
terribly close to what that guy did.<br>
<br>
I've copied the CLUE CVS repository and put it in git. cvs2git worked pretty well once you get past<br>
the command line you need.<br>
<br>
I also set up a gitorious account for CLUE. I probably could have set up my own account, and<br>
perhaps a team for CLUE, but I didn't find a page to tell me what all the options were ahead of<br>
time. But it seems flexible enough that we can redo anything we care to.<br>
<br>
I didn't enable the wiki. I'd like a wiki for this but I don't want to make content that's locked<br>
up somewhere. Anyone know how easy it is to pull all your wiki data out of gitorious? (It should<br>
be based on git so it should just be a clone away. That's how joey did it <a href="http://ikiwiki.info/" target="_blank">http://ikiwiki.info/</a>)<br>
<br>
So pretty quickly now I could upload the code and you all could have it. Then I could set the<br>
server's publish script to pull from gitorious rather than CVS. Then updates could all be done with<br>
pulls.<br>
<br>
The current process is:<br>
<br>
log in to CLUE, edit, commit, publish (requires sudo or admin access)<br>
<br>
The new process would be:<br>
<br>
edit (in your git), commit, push changes to gitorious (requires permission), pull changes to CLUE<br>
(requires permission)<br>
<br>
There are 2 big wins even though it looks like the new process is harder. First, you can have the<br>
code without having to log in to CLUE. Second, the permissions required are simply putting your ssh<br>
key in the right place (then we'll get monkeysphere and you'll wonder what kind of crack we were<br>
on). ;-)<br>
<br>
There is one hold up. I've changed the one password that's in the repository. The code is under a<br>
suitable license, although we might want to add copyright statements to the files eventually. But<br>
there are some pages with contact info for people and I want to ask them before I publish their<br>
(years old) phone numbers where you can get them. But I should get to that eventually.<br>
<br>
It's been fun to get into git and gitorious. And I watched Linus's Google talk on git. It cracks<br>
me up how blunt he is.<br>
<br>
I'd like to hear any thoughts you have about this project or experiences doing similar things.<br>
<br>
Thanks!<br>
Dave<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</blockquote></div>