[Spice-devel] Development process?

[Alon Levy]

On Mon, Jun 11, 2012 at 07:58:24PM +0200, Hans de Goede wrote:
> Hi,
> 
> On 06/11/2012 04:45 PM, Jeremy White wrote:
> >Forgive me if this is FAQ'd elsewhere, but I did not find it in a short
> >hunt, and I'm curious.
> 
> Documentation is not our strong point, help with that is greatly
> appreciated :)
> 
> >Who has commit access to the main trees,
> 
> For all the repositories under http://cgit.freedesktop.org/spice/
> anyone who has a proven track record of being a team player and making
> regular code contributions so far has been given direct commit / push
> access. That currently means the entire Spice team @ Red Hat, and
> Daniel P. Berrange have access (not sure if I'm missing someone ...)
> 
> Note that since access is managed through a unix group, access to one
> of them means access to all of them.
> 
> > and how is the decision to
> >commit made?
> 
> For the above repositories in general the rule is send patches to
> spice-devel, wait for review and revise on comments, or push on ack.
> 
> I must admit that for the linux agent and usbredir I break the rules,
> since the code is 99% mine, so I my own stuff I just push without
> reviews...
> 
> >But I also saw several patches appear in the xf86-video-qxl master
> >branch, and I didn't see them show up anywhere in a mailing list.
> 
> That falls under the xorg umbrella, so it has different rules /
> a different mailinglist. Alon can probably fill you in on this.

Soren has commit access to that, and I do too, and it's mostly review by
subjecting it to the open air. If no one objects after a week, push it.
Soren seems to push things directly without posting patches though.

> 
> Regards,
> 
> Hans
> _______________________________________________
> Spice-devel mailing list
> Spice-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel