public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] my 2014-2015 council manifesto
Date: Tue, 24 Jun 2014 20:08:24 -0500	[thread overview]
Message-ID: <20140625010824.GA3063@linux1> (raw)

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

All,

here is my manifesto; it is similar to my previous manifestos.

1.  I believe the council should only be asked to make a decision on an
issue when the issue cannot be settled by the community itself. As it
has been said by others, the council should do what it can to stay out
of the way of innovations, which should come from the developers.

2. When the council is asked to make a decision, it should be fully
informed about both sides of the issue before it votes. On the other
hand, the council should not block progress by taking an extremely long
time to make a decision.

3. I believe we can learn from the past, and improve upon it. Continuing
to do things like we have in the past is not a bad thing in itself.
However, using what we have done in the past to block innovation can be.
I understand that people are used to doing things a certain way. However,
that alone is not justification for continuing to do things the same way
in the future. if we need to make a change, we should make sure that
change is backward compatible with what we have, or if this is not
possible, provide the smoothest possible transition for our users.
Since the council doesn't maintain all of the packages, the council is
not going to know the technical details of how to make either of these
happen, so I don't feel that the council should mandate specific
implementations.

Thanks,

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2014-06-25  1:08 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=20140625010824.GA3063@linux1 \
    --to=williamh@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