From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-project] Re: [gentoo-dev] [GLEP] GLEP Purpose and Guidelines
Date: Thu, 19 Jun 2008 16:22:54 +0200 [thread overview]
Message-ID: <g3dq3v$5j0$1@ger.gmane.org> (raw)
In-Reply-To: 1213883654.5167.87.camel@camobap
Peter Volkov wrote:
> ? ???, 17/06/2008 ? 09:48 +0200, Tiziano Müller ?????:
>> http://dev.gentoo.org/~dev-zero/glep/glep-glep.txt
>
> ?Your GLEP describes only two possible types: Technical and
> Organizational.
Yes.
> At the same time type of your GLEP is informational.
I can't use the new types since I have to write the GLEP in terms of the
current GLEP system/types.
> How
> this could be? What happens with informational GLEPs?
The current ones remain as they are. New ones should be one of the mentioned
types.
>
> Why did you dropped motivation from the body while mentioning it in
> workflow?
There must be a motivation. But the motivation could also be made clear in
the abstract. In other words: There must not be a separate
section "motivation" to make the motivation clear.
> ?What about previous copyright claim?
What do you mean? (yes, in my proposal a "Credits" section is needed)
>
> Actually this is just a beginning of questions and generally it feels
> this glep is not finished
true, by intention. Just keep them coming.
> and should borrow more ideas from the current
> GLEP 1. It's even better to update GLEP 1 instead for writing new one...
No. A GLEP should not be updated (besides trivial updates). That's one of
the things I'm trying to make clear here. It's not good at all to have the
GLEPs describing policies, they should only be used to propose/describe
changes to our policies (example: even if some country's law system is
based on the roman right you also don't get a copy of the roman right and a
book with changes made to it if you want to look at the current right).
In other words: GLEPs should only be patches or changesets.
--
gentoo-project@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-06-19 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 7:48 [gentoo-project] [GLEP] GLEP Purpose and Guidelines Tiziano Müller
2008-06-19 13:54 ` [gentoo-project] Re: [gentoo-dev] " Peter Volkov
2008-06-19 14:22 ` Tiziano Müller [this message]
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='g3dq3v$5j0$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