Of the open source projects I am familiar with, none of them have a
central administrative council that is fully elected by the userbase.
For example, the LLVM Foundation Foundation was appointed effectively by
itself (consisting of core developers of the project), Firefox is
managed by a corporation, and Debian by a council that appoints itself
but is subject to effectively a public recall. Python and Linux (and
pretty much every tiny software project, too) are effectively
dictatorships. This process is already far on the democratic side of the
spectrum merely by subjecting the council election to a wider vote. In
my experience, given the tendency I've seen for a lot of apathy on this
list, I don't think a more open nomination process would be any more
effective.
If you disagree with the process, you could simply just vote against the
slate of nominees regardless of whether or not you agree with them.
--
Joshua Cranmer
Thunderbird and DXR developer
Source code archæologist
I'm sorry that you disagree with it, but that is what's going to happen.
This was explained in the email last year, and in person by me to both
you and Volker.
In a few months, Thunderbird is quite likely to move to a new
organizational home (or have a very different relationship with Mozilla)
and depending on what that organizational home is, they will require a
governance reform to match the way that projects in that organization
are governed. There is no point in having two major governance
reorganizations in the space of a few months. I believe this process is
a good compromise between continuing with an expired council, and a full
immediate governance reform.
I am satisfied that the Council has canvassed an appropriate set of
current core Thunderbird contributors to see who is willing to serve. I
don't believe that anyone in that set who wanted to serve has been denied.
> council? In my opinion, what you are proposing does not match the
> definition of an open, democratic and transparent election.
I very much hope the process is open and transparent (I will be posting
the exact process soon). As for democratic, well, Mozilla is not a
democracy and never has been; while there are many things about
democractic processes which are good and useful, being "as democratic as
possible" is not a goal.
Hi.
In the current state of the project, it is often better to do
something quick, than to architect it overly broadly and "too
perfect". In the latter case, nothing gets done in the end.
Anyway, IF the community does not like the "Current process", it can
vote NO for the presented council. In that case I expect there is a
plan B, which probably is something like your "Fully transparent and
open process". But your assumption that this plan only takes 15
minutes more effort is completely unfounded and does not account for
the behaviour of our current community.
So as long as there is the way to reject the first proposed process
(by voting No), I see no problem with it.
aceman
- -------- Original Message --------
Subject: Upcoming Council vote
From: BA <b...@pep-project.org>
To: tb-pl...@mozilla.org
Date: Mon, 15 Feb 2016 22:05:34 +0100
> <mailto:b...@pep-project.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlbCSOMACgkQbqmMCC19m/UldgCeOBj32fcuwP9IL4JEr4yWWD5V
gFAAn3Sj92rhBxT2FBpOxU9x5CmWc0/Q
=pb6E
-----END PGP SIGNATURE-----
Current process:
a. Current council selects individuals to form the new council.
b. This group is presented as an all OR nothing election.
c. Everyone votes YES/NO
versus
Fully transparent and open process:
a. Post a call for nominations and volunteers on TB planning
b. Present a list of X candidates for an election of 9 positions
c. Everyone votes for 9 people of their choice
I think the only difference in effort between the 2 processes is about 15 more minutes in vote counting for the second process, and that would give the new TB council full transparency and legitimacy going forward and not allow any room for criticism.
-- Nathan Tuggy [:tuggyne] nat...@tuggycomputer.com