[Sugar-devel] g.sl.o issues for Karma and perhaps other activities

[Wade Brainerd]

How badly do you need a user friendly repository creator like Gitorious?

If it's not important, you can just use GitWeb which is trivial to set up.

I guess the important thing to consider is that Git can handle
distributing and merging *code* changes across as many servers as you
want.  But if you want the metadata like project descriptions updated,
you'll have to setup cron or a manual process like that.

Honestly, 60 projects doesn't sound like too much work to set up by
hand on both servers, compared with the amount of work to actually
develop the lessons...  Setting up a project on g.sl.o only takes a
minute or so.

-Wade

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