Re: Training points for users interested in helping out with ebuild development (was: Re: [gentoo-dev] Retiring)
Olivier Huber said: > Hi, > > 2009/5/4 Thomas Sachau > > >[snip] > > For those, who can work with IRC and are interested in working with > > ebuilds, there is already an option: > > > > Join #gentoo-dev-help or even better #gentoo-sunrise and read the > > documentation from the topic. The Sunrise Overlay (with the > > #gentoo-sunrise IRC channel) is open for everyone willing to learn > > and contribute to it. Even normal users can get access, learn how to > > create ebuilds, how to improve them and how to maintain them. > > As a starting point, this is a central overlay, where ebuilds are > > maintained, that dont get a developer as maintainer because of > > missing manpower. Additionally, all contributors learn the ebuild > > development work themselves. > > I think these are really good advise but I think we could improve the > way users can help concerning maintainer-needed packages. > dirtyepic made a funny entry on his blog [1] and darkside tried also > to do something [2], but it seems to me that this alias is a black > hole. For instance, the last bugday I tried to close some bugs. Some > one them were assigned to maintainer-needed@, > so I said on #gentoo-bugs that I've updated those bugs. Sometimes, a > dev was watching and the issue was closed, but for others I have still > no comments (Ok. I'm too impatient, but I'm not really confident. But > some devs can still surprise me ;-) ) > > I fully understand that looking at this type of bug is hard and > boring. On the other hand, I know some devs who are willing to help > and check patches. Since I don't think it would be a good practise to > savagely CC' them, I propose to add a bug-with-patch alias or > something like that. many devs go through maintainer-needed bugs from time to time. i think the easy ones will get comitted fairly fast. instead of a bug-with-patch alias, i think a _easyfix_ alias could be more helpful. it could also be used by package maintainers, which dont have the time to do the _easyfix_ (rename version bump etc.) sometimes the issue appears really simple, but it reallly isnt. in that case it would be nice, if it were deduceable from the bug, why no progress is being made. also, i feel voting for bugs is completely underutilized. votes make it apparent to the developers which bugs bug a lot of people. the incentive to fix those first is there... regards Thilo > > Cheers, signature.asc Description: This is a digitally signed message part.
Re: Training points for users interested in helping out with ebuild development (was: Re: [gentoo-dev] Retiring)
Le mardi 05 mai 2009 à 01:59 +0200, Olivier Huber a écrit : > Hi, > [...] > , I propose to add a bug-with-patch alias or > something like that. > > Cheers, > You mean something like the "Inclusion" keyword in bugzilla ? Or maybe a separate keyword that would indicate unreviewed patches. It's sad we don't have the ability to set per attachment status other than obsolete in our bugzie but we can still figure ways to work without it. -- Gilles Dartiguelongue Gentoo
Re: Training points for users interested in helping out with ebuild development (was: Re: [gentoo-dev] Retiring)
On Tue, May 5, 2009 at 5:29 AM, Olivier Huber wrote: [snip] > dirtyepic made a funny entry on his blog [1] and darkside tried also > to do something [2], but it seems to me that this alias is a black [snip] You forgot the references :) Don't postpone putting them till the end! You *will* forget them! Add them when you write the [$num]s ;) -- ~Nirbheek Chauhan
Re: Training points for users interested in helping out with ebuild development (was: Re: [gentoo-dev] Retiring)
Hi, 2009/5/4 Thomas Sachau >[snip] > For those, who can work with IRC and are interested in working with ebuilds, > there is already an option: > > Join #gentoo-dev-help or even better #gentoo-sunrise and read the > documentation from the topic. The > Sunrise Overlay (with the #gentoo-sunrise IRC channel) is open for everyone > willing to learn and > contribute to it. Even normal users can get access, learn how to create > ebuilds, how to improve them > and how to maintain them. > As a starting point, this is a central overlay, where ebuilds are maintained, > that dont get a > developer as maintainer because of missing manpower. Additionally, all > contributors learn the ebuild > development work themselves. I think these are really good advise but I think we could improve the way users can help concerning maintainer-needed packages. dirtyepic made a funny entry on his blog [1] and darkside tried also to do something [2], but it seems to me that this alias is a black hole. For instance, the last bugday I tried to close some bugs. Some one them were assigned to maintainer-needed@, so I said on #gentoo-bugs that I've updated those bugs. Sometimes, a dev was watching and the issue was closed, but for others I have still no comments (Ok. I'm too impatient, but I'm not really confident. But some devs can still surprise me ;-) ) I fully understand that looking at this type of bug is hard and boring. On the other hand, I know some devs who are willing to help and check patches. Since I don't think it would be a good practise to savagely CC' them, I propose to add a bug-with-patch alias or something like that. Cheers, -- Olivier Huber
Training points for users interested in helping out with ebuild development (was: Re: [gentoo-dev] Retiring)
Mario Fetka schrieb: > On Monday, 4. May 2009 19:06:12 George Prowse wrote: >> Peter Faraday Weller wrote: >>> Hi >>> >>> Thanks, >>> welp >> Sad to hear it mate. >> >> As the person who did your first install for you (i think) I think you >> will be missed. >> >> I am quite surprised about what you said about the state of things >> because i've got the distinct impression from others that Gentoo has >> been improving in the past 12 months. >> >> About the lack of the developers, something I proposed about 3 years ago >> might be applicable: has Gentoo ever thought about doing a "Dev Day" in >> much the same way as the "Bug Days"? Advertise a day where people can >> come and have a chat with developers and get coached because there is a >> vast amount of people and knowledge out there and I never see anything >> about Gentoo wanting people. >> >> If you book them, they will come. >> >> G > > and I would be the first to come > > Mario > > > For those, who can work with IRC and are interested in working with ebuilds, there is already an option: Join #gentoo-dev-help or even better #gentoo-sunrise and read the documentation from the topic. The Sunrise Overlay (with the #gentoo-sunrise IRC channel) is open for everyone willing to learn and contribute to it. Even normal users can get access, learn how to create ebuilds, how to improve them and how to maintain them. As a starting point, this is a central overlay, where ebuilds are maintained, that dont get a developer as maintainer because of missing manpower. Additionally, all contributors learn the ebuild development work themselves. And if you are willing to learn and do continuously good work, there is a good chance that you may level up to a developer yourself someday. You want an example? This was my way to become a full Gentoo developer. ;-) So at least for ebuild maintainence, there are good starting points (probably other projects also have training grounds like the java or kde herds), the bigger problem may be the communication between potential new developers and the current developer base and our options to become a new developer. -- Thomas Sachau Gentoo Linux Developer signature.asc Description: OpenPGP digital signature
