Re: [gentoo-dev] Democracy: No silver bullet

[Chris Gianelloni <wolf31o2@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 2913 bytes --]

On Thu, 2006-08-24 at 22:36 -0700, Donnie Berkholz wrote:
> Chris Gianelloni wrote:
> > On Thu, 2006-08-24 at 14:00 -0700, Donnie Berkholz wrote:
> >> Oh, gimme a break. Screaming about it on -dev for hundreds of posts 
> >> isn't just equivalent to a vote, it's better. It makes people think 
> >> there's more than 2 developers opposed to it.
> > 
> > Really?  Even you didn't remember that *I* was opposed to Sunrise and
> > probably accounted for at least a good 50 responses.  Yes, good came
> > from it.  Yes, it could have been done much, much better.
> 
> Sunrise is a poor example for me, because I ignored all the discussion
> on it past a certain point. It was just rehashing the same points over,
> and over, and over...

Yes, because we were asked for the same thing over and over, which is
also why I ended up no longer responding.  You can only say the same
thing so many ways before it gets tiring.

> > Hopefully, to streamline processes and give power back to individual
> > projects to govern themselves in internal matters and let people get
> > back to doing development.  That's a goal I would love to see us strive
> > to achieve in the next year.
> 
> From what I see, projects are pretty free to govern themselves. How do
> you see it differently?

How do you kick someone out of a project?  Currently, I know of no way
to do so.

What process is required for someone to join a project?  Currently,
anyone can add themselves to any project without any consent from the
project itself.  The only real counter-examples to this are projects
which require some kind of specific authorization to join, such as
devrel or infra, since they have access controls.

Who is responsible for an individual developer's work, aside from the
developer?  If a developer joins a project and doesn't do what he's
promised, nothing happens to him.  If he doesn't work his bugs, nothing
happens.  Why not?

What if the developer does poor work?  This really ties into the above,
but what happens if someone is found to not really possess the skills
necessary to be in a project?  Right now, we cannot do anything about
this person but hope that they either magically gain the skills, or
leave the project on their own accord.

> As Weeve said, he's still trying to get people to stop breaking SPARC
> keywords, just like 3 years ago. It's just when trying to do anything
> larger than a single project that you run into issues.

People that do this sort of thing should have some sort of consequences.
The occasional accident is one thing, but there are people that become
"repeat offenders" with many of these sorts of issues, yet nothing is
done to them.  If there's no consequences, why should they bother
changing their behavior?

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]