From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] GLEP 39, metastructure and elections
Date: Tue, 20 May 2008 10:42:11 +0000 [thread overview]
Message-ID: <4832AB03.7010308@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In the fallout of last council's meeting, I've been looking at our
policies and I have a few thoughts.
I've been looking at
http://www.gentoo.org/proj/en/metastructure/index.xml and I think that
the decision that lead to the creation of the council should probably
have been documented there, together with some provisions about
meta-structure changes.
One point that has been raising some arguments and that people don't
seem to agree about is what is required to change GLEP39. As a GLEP,
although an Informational GLEP, it should probably follow the rules of
the GLEPs.
However, I think the decision that lead to the GLEP and that created the
council, should be set as a policy under the meta-structure project and
that it should include a provision stating that "any change to the
meta-structure of the Gentoo project will require a discussion by and a
global vote of the developer community".
I think the meta-structure project is the best place to document the
overall organization of the Gentoo management structure and to define
its policies.
This would allow us to have a GLEP describing the process by which a
certain change to the meta-structure was decided and the provisions of
such a proposal, without having special rules for such GLEPs. Obviously
any change to the policy would need to be discussed under the rules
defined on the meta-structure project and if and when it was approved,
it would be possible to update / add a new Informational GLEP following
the standard procedure for GLEPs. Thus, such a GLEP would reflect
current policy and not define it.
Since the last election for the Foundation, I've been entertaining the
idea to create an elections project for Gentoo. The purpose of such a
project would be to hold a list of people willing to serve as officials
for elections, to document the procedures to run an election and to
discuss / maintain any scripts for conducting an election.
The project would include a "pool" of potential officers for an election
and before any election, the number of required officers would be
selected to run that specific election.
The elections project would be responsible to organize the elections for
the council and the Foundation and could also help organize any other
project's election - if asked to do so.
To anyone thinking that to have a project to run elections is overkill,
I would like to present my experience as an election officer that
running an election is not that simple, in particular if past officers
are not around and the documentation about the procedures is scarce. My
hope is that having such a project would help gather documentation on
the procedures and promote a better understanding on the process, making
it simpler to new persons to run an election. I also hope that it will
help streamline elections by eliminating the wait for finding officers
for an election.
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / SPARC / KDE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgyqwIACgkQcAWygvVEyALqQQCePtlEF/NfwizLobAX8JyjKVEP
+FsAoJ0lHihGRHZNuMPWm0B9HhFv+u7G
=bb4c
-----END PGP SIGNATURE-----
--
gentoo-project@lists.gentoo.org mailing list
reply other threads:[~2008-05-20 10:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4832AB03.7010308@gentoo.org \
--to=jmbsvicetto@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox