public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
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:50:29 +0100	[thread overview]
Message-ID: <1192528229.5412.61.camel@zeca> (raw)
In-Reply-To: <20071015210227.GA21110@zealot>

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

On Tue, 2007-10-16 at 00:02 +0300, Jukka Ruohonen wrote:
> 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? 

Becoming an arch tester is (I think) still possible, and a sci tester is
definitely possible. You need to answer the ebuild development quiz.
People interested should read the pointers mentioned in a previous email
of this thread, and mail me or sci@g.o. so we can gather all requests.

> 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? 

Possible ways to have some tests procedures:
- bugzilla: add the test procedure to an existing new package bug, or
file a new bug properly assigned to the herd mentioned in the ebuild
metadata.xml.
- overlay: write test procedures, just as the emacs project did [1]

I will see with overlay.g.o staff if we can open our overlay wiki to the
gentoo science community and make it a more general wiki.

--
Sébastien

[1] http://overlays.gentoo.org/proj/emacs

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-10-16 10:01 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 [this message]
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=1192528229.5412.61.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