| 1 |
Patrick Lauer wrote: |
| 2 |
> So - as GWN monkey - I'm offering my services as aggregator for project |
| 3 |
> updates. |
| 4 |
|
| 5 |
I'd rather see the project managers/bosses/dedicated_members doing that |
| 6 |
themselves. Fine example might be GDP updates which work quite well, IMHO. |
| 7 |
|
| 8 |
> Maybe someone from the doc project wants to help to get this |
| 9 |
> information put on the website so that it's visible? |
| 10 |
|
| 11 |
I'm not sure about what permissions are required to post to the |
| 12 |
mainpage, but if the respective people are sane enough, they could get |
| 13 |
them, imho. |
| 14 |
|
| 15 |
> I suggest project updates every 6 months (which roughly is the same |
| 16 |
> timeframe as releases) |
| 17 |
|
| 18 |
Would those updates be mandatory or just recommended? |
| 19 |
|
| 20 |
> Any feedback appreciated :-) |
| 21 |
|
| 22 |
Well, as I said, we (the GDP) are already doing that. |
| 23 |
|
| 24 |
I'm not sure if it's a good idea to make such updates compulsory, but |
| 25 |
I'm sure we should at least recommend them. Let's make a deal - one |
| 26 |
lollipop/cookie for one status report, paid from the foundation funds, |
| 27 |
okay? :-) |
| 28 |
|
| 29 |
Cheers, |
| 30 |
-jkt |
| 31 |
|
| 32 |
-- |
| 33 |
cd /local/pub && more beer > /dev/mouth |
Archives