[haiku-development] Re: Testing the poll

Hello,

2008/8/26 Jorge Mare <kokitomare@xxxxxxxxx>:
>> The poll is designed with the idea that the developers would be the
>> decision making body after the leadership transition from the admins
>> to Haiku inc and the development team. Naturally, since things are
>> still developing in that area, I understand the confusion.
>
> I don't think there is any confusion, nor has this anything to do with
> being admins, part of Haiku Inc. or the development team. This was not
> meant to be an us and/or them situation, nor should we make it one;
> admins, developers, non-developers, Haiku Inc. etc.: we are all the
> same.
>
> I raised the issue because, in general, I think that the "you have to
> be a Haiku developer" criteria to vote (or to edit the wiki, for that
> matter) is both flawed and exclusionary, as it includes a lot of
> people that may have not been involved with Haiku for many years and
> leaves out of the process developers and non-developers who are
> currently contributing, some quite substantially, as well as people
> who will be doing work for the alpha 1 release out of the process.

First of all, to make things clear, the 'you have to be a developer to
vote' criterium was meant more descriptive than prescriptive,
currently you really have to be a developer - meaning you need to be a
member of the developers group in Trac - to vote. That's a setting,
not a final selection of everybody who could vote.

Secondly, whether the developer criterium is too exclusionary and
unfair, that's a hard debate. It goes back to leadership, community
and those discussions have been inconclusive, and in my opinion, can
be considered a failure.

So what we have here is a list of proposals. Initially, Axel said (and I quote):

"The aim of this thread should be to compile a complete list of things
we want to have in the first alpha release, be it feature or software."

My interpretation is that this has to do with the software, which is a
domain exclusive to developers. That is not my interpretation, but
rather something that has been asserted by various community members
time and time again. It has been confirmed (on-list and off-list) that
the decision making body of the Haiku software would become the
developer group - which is everyone with SVN access - after the
dismantling of the admin team and the creation of a new governing body
for the non-profit. Whether that criterium is too exclusionary or not,
that should be debated in a different thread and not in context of
this alpha 1 release.

Now there is a thing which makes this selection of voters more
complex. Some of the proposals are beyond the reach of the technical
side. For example, the marketing proposals (such as #70 through #73),
or #2 - to name the release Developer Release, or one might even argue
whether to select a release coordinator (#6) is beyond the reach of
software. In the latter case I would argue it isn't, but that is not
the point of this message.

The fact that this list is now so broad makes it less effective (in my
opinion), but let's continue and evaluate later.

I feel like I came over as the guy with the veto on who gets to vote
and who doesn't. Let me make it perfectly clear that I don't have this
power (other people can administrate Trac), nor do I want to.

To that extend, send me the list of all the people who - according to
the 'consensus' - should be included, including Trac usernames, and I
will make sure they can edit the page and vote. Since I have to
investigate the Firefox 2 issue, I propose to hold of the actual
voting until I find out what causes the problem, which should give the
list enough time.

N.

Other related posts: