From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: New project: Licenses
Date: Thu, 21 Nov 2013 16:21:19 +0100 [thread overview]
Message-ID: <21134.9455.662483.27571@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <528E1B11.1040104@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
>>>>> On Thu, 21 Nov 2013, hasufell wrote:
>> For the time being, it will be listed as a top-level project.
>> (There were some ideas that Licenses could be a subproject of
>> another TLP, but so far this hasn't worked out.)
> It should be a subproject of QA.
Indeed, that's one of the two TLPs that were suggested. The past QA
disliked having Licenses as their subproject, though. It depends on
how the role of QA is defined: If it is seen as primarily technical,
then Licenses (which is largely non-technical) doesn't fit so well.
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-11-21 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 14:22 [gentoo-dev] RFC: New project: Licenses Ulrich Mueller
2013-11-21 14:39 ` hasufell
2013-11-21 15:21 ` Ulrich Mueller [this message]
2013-11-21 21:11 ` Roy Bamford
2013-11-22 9:38 ` Ulrich Mueller
2013-11-29 23:04 ` Roy Bamford
2013-11-22 11:04 ` hasufell
2013-11-25 9:14 ` Thomas Kahle
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=21134.9455.662483.27571@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@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