From: Jukka Ruohonen <drear@iki.fi>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci team help
Date: Tue, 16 Oct 2007 13:04:38 +0300 [thread overview]
Message-ID: <20071016100438.GA4220@zealot> (raw)
In-Reply-To: <20071016072030.GS23990@supernova>
> > Who will decide which packages are first-class citizens and which are not?
> > What are the criteria?
>
> I suggested a few.
> - Is a developer willing to commit to maintaining it?
> - Is it expected to be fairly popular, or is it extremely specific?
> - (for apps already in the tree) Is it unmaintained? Should it be
> moved to an overlay?
The first criteria is naturally a prerequisite for any package. But I also share the
concerns raised by Andrey.
Somehow, I feel, personally, that the sci-packages should constitute an exception
from the general rules regarding overlays. I mean that when a person chooses to use
something from, say, Xfce overlay, the use of an overlay is rather natural and
pleasant, but when a person is "forced" to use an overlay in order to write a Ph.D
thesis, the use of an overlay can be far from pleasant. In my opinion overlays can
not escape additional concerns regarding quality and trust, and these concerns are
much more strongly felt when we are dealing with scientific packages. Again the
keyword may just be the perception.
And as Sébastien mentioned, this is an area in which the build process and runtime
behavior should be rock solid, the former preferably being accompanied by as many
tests as is possible. Do not get me wrong: all packages that I have used from the
sci-overlay have been high-quality ones, but for the mentioned reasons I see no
point in having an overlay that possibly (would? will?) contain unmaintained ebuilds
with little or no testing. Again I see this as an issue specifically related to the
scientific packages.
Also, given that we are dealing with scientific software, the minority of the
packages will fall under the "generic and popular" category, while the rest will
surely be more or less specific. I see that we have eleven sci-categories in the
main tree. Most likely packages in sci-electronics will be extremely specific for
people doing work with packages in the sci-geosciences category. I doubt that
popularity is such a good criteria in choosing which scientific packages deserve to
be in the main tree. I would rather like to ask what kind of internal representation
the sci team has? Are the staffing needs especially bad in some areas?
Again these were just small and perhaps irrelevant opinions from an user of the
scientific packages.
Thanks,
Jukka Ruohonen.
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-16 10:15 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
2007-10-16 10:04 ` Jukka Ruohonen [this message]
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=20071016100438.GA4220@zealot \
--to=drear@iki.fi \
--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