<div class="gmail_quote">On Sat, Jan 2, 2010 at 6:16 AM, Wade Brainerd <span dir="ltr"><<a href="mailto:wadetb@gmail.com">wadetb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This sounds like the ideal conditions for Git.<br>
<br>
Just set up a server at your office using any Git related software you<br>
want, like Gitorious or even GitWeb. Developers set their projects up<br>
on your local server, and when they reach some level of stability they<br>
create public repositories on <a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a>.<br></blockquote><div><br></div><div>I would like to set up gitorious but not sure how difficult this would be</div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Do all your development on your local server, and every once a while<br>
push the changes over to SL.<br>
<br>
git push gitorious@git.sugarlabs.org:myproject/mainline.git<br>
<br>
If SL people want to make changes, they clone the repository on<br>
<a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a> and push to it.<br></blockquote><div><br></div><div>We will have about 60 individual repos by April and hopefully several hundred by the end of 2010. It will be impractical and error-prone is we have to create each repo twice, once on our local server and once on the SL server. Is there a way to automate this?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
git push gitorious@git.sugarlabs.org:myproject/wadebs-clone.git<br>
<br>
The SL person lets the author know by email, and the author pulls the<br>
changes to their local repository, merges them, and pushes them to<br>
your internal server.<br>
<br>
git pull gitorious@git.sugarlabs.org:myproject/wadebs-clone.git<br>
.. do merge work<br>
git push username@local-git-server:myproject.git<br>
<br>
Does this help at all?<br>
<br>
-Wade<br>
<div><div></div><div class="h5"><br>
<br>
On Thu, Dec 31, 2009 at 10:37 PM, Bryan Berry <<a href="mailto:bryan@olenepal.org">bryan@olenepal.org</a>> wrote:<br>
> I want to discuss some issues for managing Karma lessons on glso. Please let<br>
> it be clear that I am not criticizing the infrastructure team __at_all__. I<br>
> think they are doing a great job. The issues I am encountering have to do<br>
> with underlying tools and some issues specific to developers working in<br>
> countries w/ crappy bandwidth, such as Nepal.<br>
> Some of the main goals of the Karma Project are to get more developers in<br>
> general involved in creating content for Sugar and to make OLE Nepal's<br>
> content development more accessible and open to developers inside and<br>
> outside Nepal. We have a full-time team of 7 sw engineers, 3 graphic<br>
> designers, and 3 teachers working on content. It would be a crying shame if<br>
> we can't work with the larger community.<br>
> One big problem for devs here in Nepal is that international bandwidth is<br>
> both lousy and expensive. Conversely, w/in Kathmandu bandwidth is relatively<br>
> high-speed and cheap. I have up to 2 Mbps w/in Nepal but get around 30 kbps<br>
> for a site hosted outside Nepal.<br>
> The Karma repos are big and there will soon be many. The main Karma repo<br>
> will be 10-15 MB and each individual lesson will be in its own repo, usually<br>
> 2-4 MB. I hope to have about 60 individual karma activities under source<br>
> control. That will be easily 200 MB. Transferring files of that size over<br>
> slow international links will really cramp our development cycle. At the<br>
> same time we need for the Karma lessons to be easily accessible<br>
> internationally.<br>
> A working solution will have to start with a server inside Nepal hosting the<br>
> Karma content. OLE Nepal can likely provide the server space. Would it be<br>
> possible for us to set up our own instance of gitorious? My impression is<br>
> that everyone is waiting to move to the gitorious instance but something is<br>
> holding it up. Even if g.sl.o migrates to<br>
> <a href="http://gitorious.org" target="_blank">gitorious.org</a> how difficult would it be to set up an instance in Nepal. Or<br>
> will it be too hard to set up a gitorious instance and we should just use<br>
> something simple for Karma like cgit?<br>
> So say we do set up an instance of gitorious here in Nepal. How could we<br>
> make it easy for others outside Nepal to access the code and contribute<br>
> back? If you are outside Nepal, downloading from a server in Nepal also<br>
> sucks due to the bandwidth issue. Would it be feasible to set up a read-only<br>
> mirror of Nepal's repositories on the Sugar infrastructure?<br>
> I would like there to be a writable set of repositories on an international<br>
> server but I can't imagine how the this mirror would sync w/ the Nepal<br>
> server without lots of nasty conflicts.<br>
> Sugaristas, please let me know what you think<br>
</div></div>> _______________________________________________<br>
> Sugar-devel mailing list<br>
> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
><br>
><br>
</blockquote></div><br>