[MeeGo-touch-dev] INFO: Speeding up merge requests

[Jörgen Scheibengruber]

Am Dienstag, den 07.09.2010, 17:02 +0200 schrieb ext Foster, Dawn M:

[...]

> I've been working on documenting our contribution process for MeeGo.
> Here's what we have so far:
> General: http://meego.com/about/contribution-guidelines
> Kernel: http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors
> 
> Having something clearly documented along with the rest of the contribution
> guidelines would probably help avoid some confusion. I'm happy to help 
> draft the guidelines and get them added to our existing ones. I know that 
> we've been needing to add details about merge requests, and this is a good
> excuse to get it started. 
> 
> A couple of questions first:
> * I assume people can also submit patches (using the existing guidelines)
> above?

I would say that merge-requests are the preferred way, at least for
meegotouch. At least every change that needs a thorough review should go
that way. That said, it all depends on the maintainers, i.e. the ones
with write-access. For trivial and/or straight-forward patches, I
wouldn't see why a maintainer wouldn't commit it directly.

And it does not necessarily mean that the person who contributes the
patch needs to create the merge-request, that can also be done by
someone who is an active contributor to meegotouch.

> * Can / should anyone make merge requests or is this limited to existing or 
> established contributors?

I think everyone can and should do it.

> * Other thoughts on what else should / should not be included in the contribution
> guidelines?

These are just my 2¢, if someone disagrees with me, please speak up! :-)

Br,
Jörge