[Sugar-devel] github (was Re: Fwd: Proposal on how to speed up patch reviews)

[Daniel Narvaez]

I would expect the same workflow to be possible in GitHub.

But let's play a bit with it and see if we like it before making too many
plans about a switch :)

On Thursday, 28 March 2013, Chris Leonard wrote:

> On Thu, Mar 28, 2013 at 7:19 AM, Daniel Narvaez <dwnarvaez at gmail.com<javascript:;>>
> wrote:
> > Anyway  I think a github workflow would cover three important things
> > we care about
> >
> > * Patches are visible to anyone.
> > * Patches are trackable.
> > * Integration with issues tracking.
> >
> > Of course it migth introduce other problems :)
> >
>
> So how does this work for Pootle integration and the L10n workflow?
>
> At the present time, all translation-ready (i18n-ized) Sugar packages
> have special gituser "pootle" added as a committer.  Lang admins can
> click "Commit to VCS" in Pootle and the commit is made (on their
> behalf) by the priv'ed pootle gituser.
>
> Simple to manage at set-up time for new Sugar Activities/packages
> (make sure git user "pootle" has commit.)  Simple to manage lang admin
> privs via Pootle admin user interface.
>
> What workflow has the equivalent simplicity in github?  I can tell you
> there is no way that breaking out languages or localizers as
> individual contributors to a repo (eliminating the special poolte
> user) is going to work out well.
>
> cjl
> Sugar Labs Translation Team Coordinator
>


-- 
Daniel Narvaez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130328/b0c4d671/attachment.html>