Gentoo Archives: gentoo-dev

From: AllenJB <gentoo-lists@××××××××××.uk>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: Project proposal -- maintainer-wanted
Date: Thu, 14 May 2009 01:27:49
Message-Id: 4A0B738F.3030000@allenjb.me.uk
In Reply to: [gentoo-dev] RFC: Project proposal -- maintainer-wanted by Mart Raudsepp
1 Mart Raudsepp wrote:
2 > Hello,
3 >
4 > I have had this project in my mind for a while, so it's about time to
5 > get it out there, as to see if feedback finds it a good one - and if
6 > that is so, if there are people who want to make it happen.
7 > It is worded as a hypothetical project description for the purpose of
8 > the text perhaps being a draft for the projects official description. So
9 > in the following text instead of terms like "this project would be" I'm
10 > purposely using terms like "this project is", as while writing it, it
11 > got quickly very awkward writing "would be" and such all the time.
12 > Please take it still as a proposal to be judged, commented, improved,
13 > etc etc. And well, do that commenting and improving and volunteering ;)
14 >
15 >
16 > Project maintainer-wanted
17 > =========================
18 >
19 > Abstract:
20 > There are currently quite some package requests (over 3000) languishing
21 > on bugzilla waiting for a developer or team to get interested and
22 > package it in the official gentoo-x86 portage tree. However in quite
23 > some cases that might not happen for quite a while even with very
24 > popular packages desired by users. The purpose of the maintainer-wanted
25 > project is to get as many of such packages to the official tree as
26 > possible as a stopgap solution.
27 >
28 > <SNIP>
29 >
30 > ----
31 >
32 > Discuss! :)
33 >
34 > Mart Raudsepp
35 > Gentoo Developer
36 > Mail: leio@g.o
37 > Weblog: http://planet.gentoo.org/developers/leio
38
39 So, to solve the problem of lack of manpower / interest causing packages
40 not to be added to the tree, Gentoo will create a dedicated project to
41 shove as many of these packages into the tree as possible?
42
43 In my opinion, you've failed to solve the real problem:
44 Where is the manpower and interest for this project going to come from?
45
46 All that's going to happen is Gentoo will have many many buggy and out
47 of date packages in the MAIN TREE. Exactly where they shouldn't be. You
48 claim quality won't be sacrificed, but I simply can't see this without
49 any attempt to solve the manpower issues first.
50
51 Isn't the purpose of this project already somewhat covered by Sunrise?
52 If developers are interested in shoving packages without a maintainer
53 into a tree (while not retaining quite the same level of responsibility
54 for them), can't they already do it there? A dedicated overlay which is
55 already monitored, but packages are not guaranteed to be as highly
56 maintained as those in the main tree (from my point of view of what
57 Sunrise is)
58
59 Proxy maintenance is already available via going directly to interested
60 developers / projects or via the Sunrise overlay.
61
62 As a user I would not like to see Gentoo pursue this policy. It's going
63 to create a situation where I can't trust that the packages in the main
64 tree are maintained to the level I expect.
65
66 To my knowledge, a list of maintainer-wanted bugs can already be easily
67 generated using Bugzilla's search feature. While some sort of more
68 organized format may possibly increase uptake of maintainer-wanted
69 packages, I'm dubious as to how much compared to the amount of effort
70 required to create it.
71
72 Summary: I believe that this project will create problems, not solve them.
73
74 Gentoo should be looking at ways to encourage user contributions to
75 Sunrise and proxy maintainership. In my opinion this would include more
76 publicizing of these avenues - for example, bring back the newsletter
77 and start features on Gentoo projects (who they are, what they do,
78 roadmap, help needed - basically the same as the status reports that
79 occasionally go to -devel), new developer profiles (again, instead of
80 these only going to -devel) and proxy maintainership / Sunrise (latest
81 additions, moves to main tree).
82
83 While the existing docs are quite good, perhaps look at how the
84 documentation on creating packages can be improved (perhaps start with a
85 basic "how to" on creating a simple ebuild, putting it in a local
86 overlay and manifesting it).
87
88 (Side note: I've started a very small project of putting up the Project
89 Status summaries on to the wiki[1], linked from the forums[4] and a
90 blog[2] post on Planet Larry[3] - it's not much, but it's a start that I
91 hope to build on in the future)
92
93 [1] http://en.gentoo-wiki.com/wiki/Projects_Status
94 [2] http://allenjb.me.uk
95 [3] http://planet.larrythecow.org
96 [4] http://forums.gentoo.org/viewtopic-t-763205.html
97
98 I think Gentoo could be doing more to reach out to users who may wish to
99 contribute rather than just waiting for them to come to them. While many
100 probably do read Planet Gentoo and some will sign up to -devel if they
101 are so inclined, I don't think these methods are as good as actively
102 reaching out to users on the forums and newsletter.
103
104 With regards to the forums, I realize many developer choose not to spend
105 time there because of their lack of free time, but is there anything
106 that could be done to improve this situation? Perhaps creating a
107 dedicated forum for package development (and splitting up "Portage &
108 Programming" generally - I personally think it's too much of a
109 catch-all). What about a forum setup that better resembles the project
110 setup so that individual projects can more easily find queries that are
111 likely to affect them?
112
113
114 AllenJB

Replies

Subject Author
Re: [gentoo-dev] RFC: Project proposal -- maintainer-wanted Richard Freeman <rich0@g.o>