From: "M. Edward (Ed) Borasky" <znmeb@cesmail.net>
To: gentoo-science@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-science] Scientific Gentoo reorg
Date: Sat, 17 Jun 2006 17:30:53 -0700 [thread overview]
Message-ID: <44949EBD.8000404@cesmail.net> (raw)
In-Reply-To: <200606171925.20119.george@gentoo.org>
George Shapovalov wrote:
> So, right now I would like to ask for the feedback on the following:
>
> Q1) I would like to hear about the reasons why people are afraid to join the
> sci team. You may respond to me personally or raise it on the list, but
> please let me/us know about the problems in any case, so that we may address
> them!
>
Not so much afraid as spread too thin between my day job and hobby
computing. I just wouldn't be able to fill a role beyond tester without
giving up something else I really love to do. :)
> Q2) Please let me know if you are supporting or occasionally touching some
> package under sci-* and, assuming we create more herds, which herd it should
> belong to (just make it up as you see fit right now) and whether you would be
> willing to add yourself to the alias of that herd or join some subteam if we
> create one. I will collect the responces and then compile a proposal for the
> new structure.
>
I have some ideas for breaking up the larger chunks. For example,
"sci-mathematics" could be broken into symbolic and numeric, the latter
picking up "blas-atlas" and "lapack-atlas". I'd move everything from
sci-libs into its functional area ... blas-atlas and lapack-atlas to
math/numeric, , the graphics libraries to sci-visualization, etc.
> Q3) Not relevant to this restructuring, but always usefull: if you know of
> some package that you think should really go under sci-something, please let
> us know!
>
Everything I use actively is there already, plus a lot of stuff I have
no interest in. There are a couple of Markov modeling packages I'd like
to see that are in pretty good shape -- PRISM from
http://www.cs.bham.ac.uk/~dxp/prism/ and PEPA Workbench from
ttp://homepages.inf.ed.ac.uk/s9905941/jPEPA/. Neil Gunther's "PDQ"
(http://www.perfdynamics.com/Tools/PDQcode.html) would be a nice
addition. A good open-source discrete event simulator would be nice. The
most popular seems to be C++SIM (http://cxxsim.ncl.ac.uk/)
> And to finish it all up :)
> Q4) If you are a user but would like to be involved more actively, or you have
> to run that particular package for your work but it sits in bugzilla for ages
> and no developer seems sensible enough to take it up, please let us know too.
>
Yeah, but see Q1 :).
--
M. Edward (Ed) Borasky
http://linuxcapacityplanning.com
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-18 0:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 17:25 [gentoo-science] Scientific Gentoo reorg George Shapovalov
2006-06-18 0:30 ` M. Edward (Ed) Borasky [this message]
2006-06-18 0:40 ` Donnie Berkholz
2006-06-18 2:57 ` C Y
2006-06-18 6:03 ` Justin R Findlay
2006-06-19 11:07 ` Jan Marten Simons
2006-06-19 13:52 ` [gentoo-science] Re: [gentoo-dev] " Flammie Pirinen
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=44949EBD.8000404@cesmail.net \
--to=znmeb@cesmail.net \
--cc=gentoo-dev@lists.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