From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-project] [GLEP] GLEP Purpose and Guidelines
Date: Tue, 17 Jun 2008 09:48:04 +0200 [thread overview]
Message-ID: <g37q7l$gmu$1@ger.gmane.org> (raw)
Hi there
Since GLEP 1 is outdated (it still mentions project managers, etc.) and I
think that current GLEP workflow is too undefined and not well suited for
changing organizational policies I wrote a new one:
http://dev.gentoo.org/~dev-zero/glep/glep-glep.html
http://dev.gentoo.org/~dev-zero/glep/glep-glep.txt
One big change is that GLEPs shouldn't be used anymore implicitly (as in: we
have some council policies in proj/en/council but no reference to GLEP 39
which states additional policies), but they must either be linked to or the
content of the GLEP must be added to the corresponding policy documents.
Cheers,
Tiziano
--
gentoo-project@lists.gentoo.org mailing list
next reply other threads:[~2008-06-17 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 7:48 Tiziano Müller [this message]
2008-06-19 13:54 ` [gentoo-project] Re: [gentoo-dev] [GLEP] GLEP Purpose and Guidelines Peter Volkov
2008-06-19 14:22 ` Tiziano Müller
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='g37q7l$gmu$1@ger.gmane.org' \
--to=dev-zero@gentoo.org \
--cc=gentoo-dev@lists.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