From: Jukka Ruohonen <drear@iki.fi>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci team help
Date: Tue, 16 Oct 2007 00:02:27 +0300 [thread overview]
Message-ID: <20071015210227.GA21110@zealot> (raw)
In-Reply-To: <20071015201410.GJ23990@supernova>
While I too might have some interest in developing particularly the scientific
packages, Donnie's comment made me to wonder whether the idea of "support teams"
(cf. arch testers) was buried?
I think this idea that was mentioned in the previous thread would be especially
suitable for the sci-team and its packages that often require, besides the normal
ebuild practices, some special expertise to carry out full runtime testing. Or would
these teams just mean extra work for the actual developers? Will a presumably small
community using the scientific packages need this kind of an extra layer?
Perhaps these "support teams" would also narrow the (assumed) threshold of
participating in the overlay. (I see that "herd testers" are mentioned in the
overlay, but as a long-time Gentoo user I have no knowledge what these testers are;
this also demonstrates the little obscurity that surrounds all overlays from an
end-user perspective.)
Regards,
Jukka Ruohonen.
> > So what could we do to get more help: call for new recruits, convince
> > more devs to join the sci herd, get proxied packages, more overlay
> > maintainers? (in the past, there was a similar thread [1]). I could
> > train a new dev in anyone interested, I would have more time in 2 weeks.
>
> Just a cautionary note:
>
> However much we might be able to use the extra help, we need to make
> sure to keep our developer standards high.
>
> I think a good way to start is to make the overlay an "accepted"
> solution for where to keep packages. Get more people participating in
> the overlay, and even be willing to move packages from the main tree to
> the overlay if there's non-devs willing to help with things that are
> poorly maintained.
>
> The overlay worked great to get you to join. =)
>
> Thanks,
> Donnie
> --
> gentoo-science@gentoo.org mailing list
>
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-15 21:14 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 [this message]
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
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=20071015210227.GA21110@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