[Sugar-devel] Moving more modules to github
Daniel Narvaez
dwnarvaez at gmail.com
Mon Apr 7 05:31:04 EDT 2014
Looking at my email, it sounds like Aleksey is offline for a while but
Ignacio is co-maintainer. Adding both.
On Monday, 7 April 2014, Gonzalo Odiard <gonzalo at laptop.org> wrote:
>
> On Sun, Apr 6, 2014 at 7:22 AM, Daniel Narvaez <dwnarvaez at gmail.com<javascript:_e(%7B%7D,'cvml','dwnarvaez at gmail.com');>
> > wrote:
>
>> Gonzalo, can you confirm which of these activities you maintain and if
>> you are fine with the move? So I can try to hunt down the remaining
>> maintainers.
>>
>>
> I maintain:
> write
> read
> log (with Ignacio)
> jukebox
> imageviewer (with Agustin)
> terminal
>
>
> Aleksey maintained
>
> chat
>
> Gonzalo
>
>
>
>
>>
>> On Friday, 4 April 2014, Daniel Narvaez <dwnarvaez at gmail.com<javascript:_e(%7B%7D,'cvml','dwnarvaez at gmail.com');>>
>> wrote:
>>
>>> Hello,
>>>
>>> I think we should move more of our modules to github, at least all the
>>> ones we are currently building in sugar-build.
>>>
>>> That will make it easier for contributors because they won't have to go
>>> through two different processes to submit patches. Also gitorious lacks pr
>>> notifications which is really bad.
>>>
>>> Finally, it would make it easier to detect changes to the modules in
>>> buildbot without having to poll, which is giving issues to our server (you
>>> could probably do the same on gitorious, but I'm not really looking forward
>>> to write and maintain that for two different services). I'm also planning
>>> to add support for triggering builds on pr submission, so that broken ones
>>> can be marked as such in the UI, and it would be good for all the modules
>>> to benefit from this.
>>>
>>> So here are the modules I would like to move
>>>
>>> sugar
>>> sugar-toolkit
>>> browse
>>> write
>>> chat
>>> read
>>> log
>>> terminal
>>> pippy
>>> imageviewer
>>> jukebox
>>> turtleart
>>>
>>> What needs to be done
>>>
>>> 1 Get permission from module maintainers. If you are reading this please
>>> confirm you are fine with this.
>>> 2 Mirror the modules on github. I can take care of that.
>>> 3 Update sugar-build. I can take care of that.
>>> 4 Update pootle. Gonzalo, did you volunteer? :)
>>> 5 Setup a redirect from git.sugarlabs.org to github.com. Anyone knows
>>> who/how did it for the core modules?
>>>
>>> --
>>> Daniel Narvaez
>>>
>>
>>
>> --
>> Daniel Narvaez
>>
>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org<javascript:_e(%7B%7D,'cvml','Sugar-devel at lists.sugarlabs.org');>
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
--
Daniel Narvaez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140407/c1c0e63d/attachment.html>
More information about the Sugar-devel
mailing list