1 |
Chris Gianelloni wrote: |
2 |
>>> - Project status reports once a month for every project |
3 |
>> Totally agree on this one! |
4 |
> |
5 |
> OK. |
6 |
> |
7 |
> I'll give you Release Engineering's "status reports" for September, |
8 |
> October, and November: |
9 |
> |
10 |
> September: taking a well-deserved break |
11 |
> October: taking a well-deserved break |
12 |
> November: taking a well-deserved break |
13 |
> |
14 |
> How about other projects that rely on things like upstream's release |
15 |
> cycle? What about projects that just maintain ebuilds? |
16 |
> |
17 |
> Here's the games team's "status reports" for every month: |
18 |
> |
19 |
> "Fixed more bugs, added more packages, cleaned up some ebuilds." |
20 |
> |
21 |
> Now, perhaps what everyone would like, instead, would be status reports |
22 |
> *where necessary* from certain projects? |
23 |
> |
24 |
> In fact, the council has been discussing asking a few projects about the |
25 |
> status on some of their tasks. The main reason for this is for |
26 |
> communications purposes. Basically, we'd just get a "Hey, where are you |
27 |
> at on $x?" response from the teams. |
28 |
> |
29 |
> I don't *want* to drown projects in bureaucracy and paperwork. I want |
30 |
> them to *accomplish* things, instead. |
31 |
> |
32 |
|
33 |
I think the problem with reports is "how often would they be posted?" , |
34 |
and exactly "what kind of info would they contain?". |
35 |
|
36 |
I propose the following: |
37 |
|
38 |
To post a Gentoo Project report every six months, (yes, accompanying |
39 |
every Gentoo release, *be careful*, i am not saying you releng guys |
40 |
should take care of this). |
41 |
|
42 |
This report would be like a way of ChangeLog for our Gentoo project, |
43 |
which could contain the following: |
44 |
|
45 |
- Herds news: Each herd could write a 1-2 page report about the main |
46 |
changes they have done in these last 6 months. Including news about |
47 |
interesting packages added, new eclasses for sustaining the herd |
48 |
packages, any useful comment for the users of the herds, etc etc. |
49 |
|
50 |
- Project news: This could include projects like releng, pr, userel. |
51 |
Which could post general news about the main things happening for these |
52 |
last 6 months too. For example, releng could post about some new |
53 |
techniques involved to release this new Gentoo release; which packages |
54 |
were more problematic for building it and why? , in other words, the |
55 |
kind of info our users (and devel too) would be interested on. |
56 |
|
57 |
Now, this kind of report could be very very useful, both for users as |
58 |
for our developers. And making its release every 6 months, i think the |
59 |
time and what-to-comment problem shouldn't be a concern at all. |
60 |
|
61 |
I already can hear some of you saying "No, i don't want to write |
62 |
anything for X or Y!" ; fine, just don't do it. Nobody would be forced |
63 |
to do it. This would be a paper for those herds/projects/developers |
64 |
willing to communicate their work during the past 6 months to our |
65 |
community, and which could become in a very informative source to give a |
66 |
general overview of what it is going on in Gentoo land. |
67 |
|
68 |
"Fine , i won't write anything .. but .. mm .. Who would read this |
69 |
anyway?" , i hear this question too ... Sorry, i can't give you names of |
70 |
who are going to read this. But i think a big portion of our community |
71 |
would do it, if we post it on gentoo.org every 6 months surely someone |
72 |
would pick it and read it, don't doubt it. (myself included.) |
73 |
|
74 |
"Ok .. mmm fine .. mm.. wait, this is the same than GWN, isnt this?"; no |
75 |
it isn't ; i don't see a common pattern of Herds/Projects reports |
76 |
(check, it is report, *not* news) released every week on GWN; and that's |
77 |
because, GWN is for general weekly news .. mmmm that is very evidently |
78 |
on its name indeed. |
79 |
|
80 |
Suggestions and constructive criticisms are welcome. |
81 |
|
82 |
Regards, |
83 |
|
84 |
|
85 |
-- |
86 |
|
87 |
|
88 |
Luis F. Araujo "araujo at gentoo.org" |
89 |
Gentoo Linux |
90 |
|
91 |
|
92 |
-- |
93 |
gentoo-dev@g.o mailing list |