[MeeGo-dev] Guidelines for contributing code to MeeGo

[Teemu Tuominen]

  Hi,

Some basic questions from OBS & RPM newbie, regarding linking to 
upstream projects.

- Can we rely that upstream VCS for Meego package is the one available 
through rpm's (URL tag) ?
- Is there a way to identify upstream VCS location, base version and the 
origin of patches without disturbing  package maintainers ?
- At least kernels seem to contain patches that are awaiting review or 
not at all in upstream-process. Is such allowed to all projects and how 
to deal with maintaining such processes long-term ?
- N900 kernel might be a bad example, but the idea maintaining gitorious 
repo that holds the rpmbuild project felt reasonable. But can OBS/OSC 
alone provide similar visibility to everyone ?


Its nice to allow all kind of exceptions, but some general guideline 
might help contributors to join and lease their questions for a start.

regards,
Teemu

On 08/20/2010 07:55 PM, Digioia, MichaelX wrote:
> This is a good start and much better than nothing, currently online. My recommendation would be to add some more on the upstream projects with a link. Also, maybe a list of hot projects that need help to funnel energy in the direction most needed (will become stale quickly so link is better).
>
> /mpd
>
> -----Original Message-----
> From: meego-dev-bounces at meego.com [mailto:meego-dev-bounces at meego.com] On Behalf Of Foster, Dawn M
> Sent: Friday, August 20, 2010 9:30 AM
> To: Development for the MeeGo Project (discussion list)
> Subject: [MeeGo-dev] Guidelines for contributing code to MeeGo
>
> Someone recently pointed out the we have a mostly empty contribution guidelines page on the website: http://meego.com/about/contribution-guidelines
>
> I've also had several people recently tell me that they were confused about the process for contributing code to MeeGo and another person who has submitted several patches into bugzilla, but no one has responded to them.
>
> So, I thought it was time to put together better guidelines for how to contribute code to MeeGo, and I've added an escalation process that I will monitor for when patches slip through the cracks to make sure that someone responds when a community member takes the time to write a patch.
>
> The draft guidelines are here on this wiki page: http://wiki.meego.com/Contributing_code_to_MeeGo
>
> Please feel free to discuss any issues or ask questions here. If you have minor changes, you can make those changes directly to the wiki page.
>
> Since this is really just a written summary of what we seem to be doing now and not really a policy change, if I don't hear any big objections, I'll post this as an official policy on the MeeGo website on Monday.
>
> Regards,
> Dawn
>
>
> _______________________________________________
> MeeGo-dev mailing list
> MeeGo-dev at meego.com
> http://lists.meego.com/listinfo/meego-dev
> _______________________________________________
> MeeGo-dev mailing list
> MeeGo-dev at meego.com
> http://lists.meego.com/listinfo/meego-dev