[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Freedombox-discuss] need for concensus or not



Hi,

This is my last mail in this subject, if I'm the only one to push some
kind of organization, I'll stop bother everyone with this. But...

On Sat, Oct 09, 2010 at 03:23:23PM +0200, Jonas Smedegaard wrote:
> If we were hired in a company to reach a common goal, then yes, it
> really would make sense for us to agree ahead on what that common
> goal was.

Well, compare with the debian project : it's not a company, but its dev do
have common goals.

> We are volunteer hackers, however.  It makes good sense to
> understand the individual goals of each other so as to not step on
> each others toes, have a common language when sharing ideas, and
> most importantly to avoid duplicated work.

That's why this mailing list is important.

> But as I see it, if we restrict ourselves not only to a common
> direction but a (too specific) common goal, then what will most
> likely happen is that we loose valuable contributions, as we take
> the steam out of passionate hackers wanting to scratch their own
> personal itch, not the itch of a consensus team.

I didn't speak about a "consensus team".

So if we continue on comparing with the debian project, you would think
that like they have tons of documents describing their common goals, and
you have to read them before applying, hackers don't join the project?


> Specifically about hack vs. debconf (or sysadmin "dirty" hacks vs.
> distro style "clean" hacks, as I feel more accurately frame it), I
> believe I succeeded in raising my concerns (unlike some of my
> previous attempts at other teams). If some of us still favor
> sysadmin-style dirty hacks on top of Debian instead of distro-style
> clean hacks integrated with Debian, then let them do that - the rest
> of us can cherry-pick from their work in our slower pace. :-)

But I'm not sure to see how we'll be able to merge and maintain a project
with different hack types. Sounds like a hell of a work for the debian
people here to try to maintain that.

Actually I'm not telling we have to decide *everything*, nor make those
decisions unchangeable. But it seems to me that some of the direction of
this project have to be stated. Like what type of configuration method it
would adopt. Actually I'm not sure how to begin to dev. I see a lot of
people joining the list, wanting to contribute, but the only thing they
can do is to dig into the mailing list archive, which won't bring them
the beginning of an answer. So noone starts nothing.

I'm not sure the "let's do evything like everyone wants" will bring any
cohesion in this project, nor help people getting involved, finding a
place, etc...

Not that we should decide now, I think stuffs need to be discussed still.

But that's my opinion, and if I'm the only one to push that, I'll shut up
:)

bert.



Reply to: