Re: Elitists v's popularists (was Re: [RFC] Making NM 'by recommendation')
I support Martin's proposal.
on Sun, 28 Jan 2001 02:25:53 +0100,
Jordi Mallach <firstname.lastname@example.org> wrote:
> On Sun, Jan 28, 2001 at 12:10:22PM +1100, Glenn McGrath wrote:
> > ><snip> If someone comes by and nobody has seen him either on the
> > > lists, BTS or whatever, it's not very probable he has a lot of interest in
> > > Debian.
> > Well if you recognise this as a problem you should also recognise that
> > debian developers can become inactive as well but still be considered a
> > debian developer.
> This is "-newmaint-admin", we're involved in people coming in, not going
> out. I believe there's a group of people preparing a proposal to regulate
> extremely inactive maintainers, etc. But that belongs to -oldmaint-killing.
I agree. And we need some plan to focus on "already prepaired and skilled"
in order to speed up the process of fully qualified and deadly needed people.
We AM currently have to "ask the innocent people to learn more and to skill
up themselves before they can pass the required stages" sometimes, and this
may not be welcomed by that innocent people temslves.
We had taken our effort to note the requirements conditions to pass the stages
on our web pages (New Maintainer's Corner) but it does not seem to be enough.
So we may need more clear message to ask people to help us by preparing well
before sending the application.
Surely we need help, and currently we can't afford to be counselors or
instructors for those who wish to learn the required things.
If we could do it without any cost, it might be desirable. But we can't.
> > This proposal to filter out new members only covers part of the problem,
> > it doesnt attempt to filter out existing developers who wouldnt get in
> > by todays standards.
> > For those reasons i see this proposal as a way to reduce the growth of
> > membership not as a means of controling quality of membership.
> When you get a decent AM and get into Debian, please write a proposal that
> looks after this quality.
And it might need some extra cost. But it has nothing to do with this topic.
Taketoshi Sano: <email@example.com>,<firstname.lastname@example.org>,<email@example.com>