Piotr Szymaniak posted on Fri, 21 Nov 2014 23:06:30 +0100 as excerpted: > On Wed, Nov 19, 2014 at 08:07:36PM +0800, Patrick Lauer wrote: >> http://packages.gentooexperimental.org/repoman-checks/ >> >> updated per cron job, split by category. Much easier to handle :) >> >> Feel free to work on fixing things - there's enough issues that you >> won't run out of work this decade. > > So, lets assume that a lot of users get their hands on fixing things > ("lets make Gentoo a better distro!"). What's the work path here? Fix, > diff, new bug "I fixed this and that!"? git portage... pull request? > > Just asking, but I know that fixing things that will stay forever on > Bugzilla is killing motivation.
For portage (and portage-related) apps in particular, there's the portage- devel list, gentoo-portage-dev. Portage development has changed recently and is /much/ better in terms of bus-factor now, and that was reflected on the list, so I'd recommend that particularly people with an on-going interest subscribe there and skim a couple months back in the history to get a decent overview of how things work now in terms of patch submission norms, coding style, etc. See gentoo-portage-dev as covered on the main gentoo mailing lists page here: http://www.gentoo.org/main/en/lists.xml Meanwhile, also see the portage-project page, which covers much of the patch rules, etc and has links to both the IRC channel and mailing list, portage git repos and issues like running multiple portage versions on the same system, etc, here: http://wiki.gentoo.org/wiki/Project:Portage -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
