From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: ion license
Date: Sun, 13 May 2007 09:12:08 +0100 [thread overview]
Message-ID: <20070513091208.470b4cc1@snowflake> (raw)
In-Reply-To: <20070513075705.GA6546@pluto.local>
[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]
On Sun, 13 May 2007 09:57:05 +0200
Matti Bickel <mabi@gentoo.org> wrote:
> Ciaran McCreesh <ciaranm@ciaranm.org> wrote:
> > Supporting this would be a huge policy violation, and not so merely
> > as a technicality.
>
> How's that? I agree that this timely response clause will mean ion-3
> will never go stable. That's the only thing i could envision to be a
> policy violation.
Right, and packages that aren't aiming for stable eventually shouldn't
really be in the tree at all.
A larger issue, though... It requires some way of pushing updates to a
user who hasn't synced for >28 days.
> > I suggest simply removing ion support from the main
> > tree, and sticking it in an overlay that comes with a big warning
> > telling users that they cannot expect any level of QA for those
> > packages.
>
> Care to expand on "no QA"? Tuomo fixed several QA warnings upstream
> (missing strlen, etc. includes) when i told him (there will be
> patches on our side until the next _rc).
If upstream release a new version that has a serious bug, Gentoo would
be required to include it as the most visible package within 28 days,
even if it is completely unusable.
> Additionally i'd like to point out the bit where he says he don't
> want this license to hinder distributions who just stick with
> upstream, which our policy explicitly recommends. That's why i'm
> trying to reach a compromise on those USE patches we apply. That's
> why the next build will tell ppl to bug me first.
If he doesn't want to hinder distributions, get him to fix his licence.
The way it is now makes it impossible for distributions to do their job.
> In general: i don't think forking is an option. I won't be
> maintaining a fork myself to begin with.
Probably true, from a Gentoo perspective. If there's a significant ion
userbase, someone else will do the work.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-13 8:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 22:13 [gentoo-dev] RFC: ion license Matti Bickel
2007-05-12 22:31 ` Jan Kundrát
2007-05-12 22:40 ` Donnie Berkholz
2007-05-13 21:41 ` Mike Frysinger
2007-05-14 7:18 ` [gentoo-dev] " Steve Long
2007-05-14 7:51 ` Rob C
2007-05-15 8:40 ` [gentoo-dev] " Steve Long
2007-05-12 22:41 ` [gentoo-dev] " Jakub Moc
2007-05-12 22:50 ` Peter Gordon
2007-05-12 22:56 ` Jakub Moc
2007-05-13 0:19 ` Ciaran McCreesh
2007-05-13 1:22 ` Peter Gordon
2007-05-13 1:35 ` Ciaran McCreesh
2007-05-13 1:42 ` Josh Saddler
2007-05-13 7:57 ` Matti Bickel
2007-05-13 8:12 ` Ciaran McCreesh [this message]
2007-05-13 8:34 ` Matti Bickel
2007-05-13 8:42 ` Ciaran McCreesh
2007-05-13 8:20 ` Wulf C. Krueger
2007-05-13 8:41 ` Matti Bickel
2007-05-13 8:36 ` Ulrich Mueller
2007-05-13 9:18 ` Jakub Moc
2007-05-13 12:28 ` Rob C
2007-05-13 13:08 ` Rémi Cardona
2007-05-13 21:43 ` Mike Frysinger
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=20070513091208.470b4cc1@snowflake \
--to=ciaranm@ciaranm.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