Thanks for answering my questions Petko & Chris! That helps a lot :)
On Mon, Feb 18, 2013 at 4:51 AM, Chris Wilson <[email protected]> wrote: > Hi Kate, > > Thanks a lot for volunteering to help out :) > > In answer to each of your questions: > > 1. For issue relating to Gnome applications such as Nautilus, design > decisions are made by the upstream developers, who can be contacted either > on their mailing > list<https://mail.gnome.org/mailman/listinfo/nautilus-list> or > in their IRC channel (#nautilus at irc.gnome.org). This is true for > all software packages in Ubuntu - the upstream developer will make the > design decisions. If you ever need help figuring out who to contact, then > just drop us an email here or in #ubuntu-desktop on Freenode IRC, where we > hang out. > 2. Except in exceptional circumstances, all patches should be > submitted upstream. In the case of Nautilus, that means getting the source > code from the Gnome repository <http://git.gnome.org/browse/nautilus/>, > developing and committing your patch their, exporting it to a *.patch file, > which is a feature their version control system offers, and attaching it to > the relevant bug report. > > As for keeping track of who's working on what, I think assigning bugs on > upstream bug trackers to yourself is an action reserved > for privileged users. I would suggest reaching out to the developers on the > relevant communication channel and taking 5 or ten minutes to talk to them > about the bug before you start - there may be a reason it's not fixed. If > they're cool with you working on it, then you can ask them to assign it to > you. > > Thanks again for volunteering to help out here. If you ever have any > questions, then please don't hesitate to ask them here. > > Chris > > > On 11 February 2013 23:21, Katherine Cox-Buday > <[email protected]>wrote: > >> Hi all! >> >> I'm dipping my toe into contributing to the development of Ubuntu. I read >> that this was the best team to join for interested developers, so here I am! >> >> It's a bit overwhelming for someone new to OSS development, so I have a >> few questions. Per a previous email, I'm trying to pick out a bug to fix in >> Nautilus from this list <https://launchpad.net/hundredpapercuts/raring>. >> However, upon reading through some of these, it appears that: >> >> 1. A lot of these require some sort of design decision to be made. >> E.g.: Here's a >> bug<https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/48671> where >> the user is requesting for the ability to rename a file by clicking on the >> name 2x. Who makes that decision? >> 2. How does the whole upstream process work? Do we write a patch and >> then submit it to the corresponding project? Since I'm going off of >> Ubuntu's bug tracker, how do I know I'm not working on something that >> someone else upstream is working on? >> >> Other than that, go team papercuts! :) >> >> - Kate >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~papercuts-ninja >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~papercuts-ninja >> More help : https://help.launchpad.net/ListHelp >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~papercuts-ninja Post to : [email protected] Unsubscribe : https://launchpad.net/~papercuts-ninja More help : https://help.launchpad.net/ListHelp
