On Thursday 18 March 2010 21:09:43 Thomas Sachau wrote: > On 03/18/2010 05:29 PM, Markos Chandras wrote: > > Dear fellow developers, > > > > A new project is about to start so I am requesting your feedback > > > > The primary goal of the Proxy Maintainers[1] project is to create and > > maintain relationships between developers and users in order to ensure > > packages in the > > > Gentoo tree stay up to date. This involves a few main tasks: > Also it is a nice idea, i dont think, it will help Gentoo in the longer > term. As i can see with the Sunrise project, most users only want to get > their ebuild initially into portage/sunrise. They also listen to > suggestions, improve their code and read a document to get access. But in > most cases, they only do the initial commit or initial commit+some version > bumps before they leave again and the ebuild is unmaintained. > I dont think, we want to proxy for those users, since this would result in > either the proxy maintaining the ebuilds or many more maintainer-needed > ebuild in main tree. These users are not our target group. Our target group are highly motivated users who are willing to see their ebuilds on portage tree, they just dont know who to poke or contact us to make that happen. Some of them will be from the Sunrise userbase since we have these kind of Gentoo users there > The next group of users are those, who actively > maintain their ebuild, also help other users and do this for a longer > time. Usually those users get a mentor offer sooner or later and then > become a Gentoo Developer. Not always. I can remember at least 4 different occasions where it took them >1 year becoming a developer. Proxy-maintainer project is a good way to keep them around without pushing them completing their quizzes > So for those users, who are willing to help and > can do this for longer time (requirements for Gentoo devs), sunrise is > already a good starting point and base to get in. Of course. But remember that we target different user group. Through this project, we intend to lower the number of maintainer-wanted packages instead of pushing them into an overlay. The difference is that, when a developer picks a package from sunrise overlay, we maintains it by himself when he puts it to portage tree. What we want to achieve here is to make users responsible for their package in portage tree. > The only case, where > there might be a (minimal) profit are those rare users, who initially > commit their ebuild and maintain exactly and only this ebuild for a longer > time. There might be 2 or 3 users doing it this way, so creating just > another project for this idea is imho a bit too much work for minimal > profit. Proxy-maintainer is not wide spread to users so they dont know this proxying portage ebuilds is an option. > > I think, it might be better to send the interested users so Sunrise, where > they can learn the basics and afterwards you could still offer them to > proxy the ebuild (sunrise has an extra branch for proxy maintainers). > A much better idea is imho to make the idea and way of Sunrise more public > and easier to see without searching (Homepage, FAQ, Forums), so interested > users can find it easier. In addition, every dev, who is interested in > proxy maintaining something can do this via Sunrise. Sunrise is an excellent place to train users. But we still to let them know that they can control their ebuilds on portage through us. We need to let them know what proxy-maintainer is and how to take advantage of it
Are you willing to to adjust the Sunrise page accordingly? Like listing info about proxy maintainer thingie and possibly another column on the developer project table listing our areas of interest? Something like merging the two projects or extending the Sunrise one if you like -- Markos Chandras (hwoarang) Gentoo Linux Developer Web: http://hwoarang.silverarrow.org
signature.asc
Description: This is a digitally signed message part.
