1 |
On 7 April 2010 11:05, Ulrich Mueller <ulm@g.o> wrote: |
2 |
> Next monthly council meeting will be at 19 April 2010, 18:00 UTC |
3 |
> in #gentoo-council. |
4 |
> |
5 |
> If you have any topics you want us to discuss or even vote about, |
6 |
> simply followup to this message. |
7 |
|
8 |
1. reconsider metadata changepolicies proposal |
9 |
============================================== |
10 |
|
11 |
The fact is there is a spectrum from ebuild maintainers' side about |
12 |
how desirable it is for non-maintainers to step in, ranging from |
13 |
"don't touch this ever" to "please do touch this". There may be very |
14 |
valid reasons for this (in some cases intimate knowledge of the |
15 |
package may be required, for example, or on the opposite side someone |
16 |
might not have the time or motivation to do much about that specific |
17 |
package) that have little to do with territoriality. While there is a |
18 |
need for basic policies to be made more explicit, it is also obvious |
19 |
that there is no good "one policy fits all" approach. The metadata |
20 |
changepolicies proposal beautifully captured this spectrum and has |
21 |
wide support from developers. While this information isn't directly |
22 |
useful to users, the argument that it "would bloat the file for no |
23 |
good reason" is false, because there are very good reasons: to |
24 |
facilitate cooperation between devs as well as a better overall |
25 |
quality of the tree. This benefits users, so I'm quite sure they don't |
26 |
mind we use metadata.xml for that. Can council please decide to honor |
27 |
the wish from developers to implement this? |
28 |
|
29 |
|
30 |
2. website redesign |
31 |
=================== |
32 |
|
33 |
This is a recurring theme in discussions about Gentoo's shortcomings. |
34 |
While there have been some minor improvements in recent years, the |
35 |
resign project itself failed miserably, but is still as needed as |
36 |
ever. We should have one elegant design that will be consistently |
37 |
applied to all official Gentoo websites. A look at znurt.org should |
38 |
convince anyone of what can be done. Also our frontpage needs to be |
39 |
more focussed on communicating the things users and new visitors are |
40 |
looking for. Can council assure that a team will be assembled that can |
41 |
effectively tackle this issue? |
42 |
|
43 |
|
44 |
3. manpower and recruitment issues |
45 |
================================== |
46 |
|
47 |
Another recurring theme is the lack of manpower in certain areas, the |
48 |
recruitment bottleneck and the quizzes. There are some initiatives but |
49 |
more decisive leadership is needed. Can council decide to actively |
50 |
pursue solutions for these structural problems? |
51 |
|
52 |
|
53 |
4. devrel ineffectiveness |
54 |
========================= |
55 |
|
56 |
What can be done to assure that conflicts are addressed in a timely |
57 |
and effective manner by DevRel? What can be done to remove poisonous |
58 |
people from Gentoo and its communication channels more decisively and |
59 |
effectively? The fact that many people indicate they do not want to |
60 |
become a developer for this exact reason, should be cause for concern. |
61 |
Can council make a statement that they share these concerns and are |
62 |
actively looking to address them? |
63 |
|
64 |
|
65 |
5. centralize developer documentation |
66 |
===================================== |
67 |
|
68 |
Currently the documentation a developer needs to effectively write |
69 |
ebuilds and maintain packages is scattered all over the place. We have |
70 |
the (incomplete) devmanual, the developer handbook, various guides and |
71 |
policies in individual projects, the GLEPs, council decisions, and a |
72 |
legacy of unwritten rules or poorly documented policies. It would be |
73 |
very helpful to centralize all that information, and work on properly |
74 |
documenting our policies. At the very least there should be one page |
75 |
that funtions as a portal to all existing relevant information. Even |
76 |
better would be to have as much of that relevant information as |
77 |
possible consolidated into one place, so that everyone knows where to |
78 |
go to look that up. Can council decide to see this implemented? |
79 |
|
80 |
Thanks, |
81 |
-- |
82 |
Ben de Groot |
83 |
Gentoo Qt project lead developer |
84 |
Gentoo Wiki project lead |