Re: Fear the new maintainer process
As I have wrote before, may major concern is to get more
new members into our project NOW. I have worked for this.
I don't wish to be a clitic who does not work using his own
time and resources for what he try to criticize.
In <20000726203144.H9271@tardis.ed.ac.uk>, on Wed, 26 Jul 2000 20:31:44 +0100,
Mark Brown <firstname.lastname@example.org> wrote:
> [1 <text/plain; us-ascii (quoted-printable)>]
> On Wed, Jul 26, 2000 at 03:06:21PM -0400, Clint Adams wrote:
> > This entire thread seems to presume diligence on the part of the AM
> > and lackadaisy on the part of the applicant, not mentioning cases
> > where the reverse is true.
If you suspect that a member in the AM team is blocking the process,
then you can apply yourself as a replacement for that person.
It is not my duty as a member of the Debian to work as an AM,
and I could retire from that position whenever I wish to do so.
(That means the "rejection" on my side for all of applications
currently I have. Do you force me to work against my will ?)
The reason why I work in the NM team now, is just I think it is
important thing. If you wish to help applicants to be registered,
then the best thing you can do is not to cliticize things others do
on the list, but to make yourself work in the given situation.
> > FWIW, if I would have had to have experienced the current bureaucracy
> > to become a maintainer, I'm not certain I would have joined.
If you wish to reduce what you describe "the current bureaucracy",
then go and talk to the person in charge. But please do not
impede the current running queue. Now the registration started
after the long blank, and many new members has entered into the
Debian project. There are also many many people who waiting to
enter the queue.
Do you wish to take away their hope to enter into our project
after the very long waiting again ?
If we insist to trash the current running scheme, then the gate
will be closed again, I am afraid.
If you know a specific applicant who would decide not to join
the Debian because of "the current bureaucracy", then do support
him and persuade the delegates of the importance of his membership.
You can do it whenever you wish to do so, while I can't make
assure the result.
> It's really not that bad. The only thing that didn't feature at all
> in the previous NM process is the tasks and skills bit, and that's
> something that would have to be faced anyway.
In the previous scheme, we don't know how many people wish to enter
our project, we don't know why and how an application is rejected,
we can't track the status (where in the various stages) of the specific
application, we can't know whether the mails to the NM team is lost or
not until the reply comes,
Do you really think those are better than the current status ?
Now we have the database and can track the specific application,
and applicants can know if their mail is lost or not, and more,
they can check their status in the queue by themself.
I think that the current scheme is far better in these points
even if the additional required stuff is considered.
Again, if you have some proposals to improve the current situation,
then do work by yourself to implement that idea. We don't have
much resources (even the mailing list for the new NM team has
not been provided on the Debian's server. Maybe it will be done
after the release of the potato) and we must concentrate on the
processing itself to handle the huge pipeline in front of us.
Taketoshi Sano: <email@example.com>,<firstname.lastname@example.org>,<email@example.com>