public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: RFC: extending project xml to have stuff that the project is working on and collect them as Gentoo current goals
Date: Wed, 11 Apr 2007 06:37:13 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.04.11.06.37.12@cox.net> (raw)
In-Reply-To: 461BF4D1.6090204@gentoo.org

Petteri Räty <betelgeuse@gentoo.org> posted 461BF4D1.6090204@gentoo.org,
excerpted below, on  Tue, 10 Apr 2007 23:34:25 +0300:

> As the recent thread showed there is a lot going on in Gentoo land
> although it doesn't always seem so. I propose we extend project xml to
> describe current stuff going on in the project in question and their
> estimated completion date. Then we require this file to be updated
> monthly. What do you think?

I think proposals such as this have come up before. (No offense 
intended.  In fact, probably you and enough others it's time to outline 
the reasons again, simply weren't around at the time.)  I think they went 
nowhere, in part because it was thought to be just more bureaucracy 
forced (the term you used was required) on the team leads, to little 
ultimate effect (see kloeri's cron remarks).  

Remember, Gentoo's all volunteers.  You can't force them to do it as part 
of their job (for their paycheck).  What's the penalty going to be?  
Suspension of the team lead, throwing a monkey wrench in the progress 
that was being made?  Dissolving the project?  From what I've observed 
here and elsewhere over the years, a "requirement" that can't be enforced 
is a very unhealthy thing.

Thus, it's not a very practical idea, or at least no one was able to 
figure out how to make it such in previous rounds.

Instead, what tends to happen is somewhat less frequently and more 
informally, but perhaps more effectively as it's not forced. 
Periodically, perhaps twice a year or so, someone starts a thread like 
the one you referred to.  Often it's prompted by year-end or mid-year, 
and someone posts an impromptu summary of where their project is.  Other 
times, it's as this one, started for other reasons.  However, once one 
person posts a summary, another does and another, and pretty soon most of 
the projects have... and everybody did it impromptu, nothing "required" 
about it. =8^)

Of course, in more specific cases, the council notices and ultimately 
meetings often bring about discussion of projects of particular interest 
at the moment.

In any case, it may not get to the project's web page, but anyone (dev, 
user, journalist, or simply curious public) caring enough to follow this 
list ends up seeing the updates as I said, perhaps twice a year or so.  
If one were suitably devious, one could even scheme to generate such a 
thread starter every few months (cron /that/ reminder =8^), just to get 
the pile-on effect and see where everyone was, again without "requiring" 
reports of anyone. =8^)

Of course, often these threads get mentioned in GWN and thus features not 
only there, but as a result on the Gentoo home page and on community 
sites such as LWN as well, so one doesn't even have to follow this list 
to know about it, only make /some/ effort to be keeping up with general 
things Gentoo, and they'll probably see coverage of the thread.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-dev@gentoo.org mailing list



      parent reply	other threads:[~2007-04-11  6:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 20:34 [gentoo-dev] RFC: extending project xml to have stuff that the project is working on and collect them as Gentoo current goals Petteri Räty
2007-04-10 20:38 ` Mike Doty
2007-04-10 20:44   ` Petteri Räty
2007-04-10 21:02     ` Carsten Lohrke
2007-04-10 20:43 ` Ned Ludd
2007-04-10 21:11 ` Chris Gianelloni
2007-04-10 21:17   ` Petteri Räty
2007-04-11 13:54     ` Chris Gianelloni
2007-04-11 14:28       ` Michael Krelin
2007-04-11 18:27       ` Donnie Berkholz
2007-04-10 21:29 ` Bryan Østergaard
2007-04-10 21:37   ` Petteri Räty
2007-04-11 13:50     ` Chris Gianelloni
2007-04-11 15:55       ` Jan Kundrát
2007-04-11 16:07         ` Alec Warner
2007-04-10 21:34 ` Mike Frysinger
2007-04-10 22:08 ` Marius Mauch
2007-04-10 23:19 ` Stephen Bennett
2007-04-11  6:37 ` Duncan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2007.04.11.06.37.12@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox