From: "Sébastien Fabbro" <bicatali@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci team help
Date: Tue, 16 Oct 2007 10:54:11 +0100 [thread overview]
Message-ID: <1192528451.5412.63.camel@zeca> (raw)
In-Reply-To: <20071016072030.GS23990@supernova>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
On Tue, 2007-10-16 at 00:20 -0700, Donnie Berkholz wrote:
> On 12:01 Tue 16 Oct , Andrey G. Grozin wrote:
> > The original cryos' idea when he created the science overlay was a place to
> > develop ebuilds until they become mature enough to be moved to the main
> > tree (I can dig his original post about this subject). He suggested that
> > ebuilds whould, in most cases, be moved to the main tree quickly enough.
>
> OK, sure, but historic reasons are not future reasons. If things should
> change, this is not a reason to hold it back.
>
These days, the overlay is more of a sandbox for devs and a place to
ease package transition from bugzilla to the tree. Why some packages are
still in the overlay rather than in the main tree to me is only a matter
of manpower. Hopefully some day Gentoo will get more modular- right now
our cvs repository is gigantic and as you all know this means more
inertia.
> > 1. Inform users *prominently* that some interesting packages don't live in
> > the main portage tree (currently, not many users know this).
>
> Yep.
>
Well anyone who has commit access to the overlay is welcome to add
anything relevant to the wiki trac page.
> - Is it expected to be fairly popular, or is it extremely specific?
It's hard to judge this. We have the CC and votes at bugs.gentoo.org,
but as useful as bugzilla could be, it is not the zen-est interface.
Many times I feel that our tendency to resolve all issues with bugzilla
reduces productivity both for bugs reporters and bugs resolvers.
Anyway it is nice to see the science project is generating interest.
--
Sébastien
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-16 10:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:39 [gentoo-science] sci team help Sébastien Fabbro
2007-10-15 19:09 ` C Y
2007-10-15 19:11 ` Yuriy Rusinov
2007-10-15 20:26 ` Sébastien Fabbro
2007-10-23 15:16 ` Redouane Boumghar
2007-10-15 20:14 ` Donnie Berkholz
2007-10-15 21:02 ` Jukka Ruohonen
2007-10-16 1:19 ` Markus Luisser
2007-10-16 9:50 ` Sébastien Fabbro
2007-10-16 10:18 ` Sébastien Fabbro
2007-10-16 5:01 ` Andrey G. Grozin
2007-10-16 7:20 ` Donnie Berkholz
2007-10-16 9:54 ` Sébastien Fabbro [this message]
2007-10-16 10:04 ` Jukka Ruohonen
2007-10-16 10:15 ` Donnie Berkholz
2007-10-16 2:41 ` Nuno Sucena Almeida
2007-10-16 13:57 ` M. Edward (Ed) Borasky
2007-10-16 15:03 ` Sébastien Fabbro
2007-10-16 19:11 ` Nuno Sucena Almeida
2007-10-16 22:51 ` Donnie Berkholz
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=1192528451.5412.63.camel@zeca \
--to=bicatali@gentoo.org \
--cc=gentoo-science@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