public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Tee <johnmtee@fastmail.fm>
To: gentoo-science@lists.gentoo.org
Subject: [gentoo-science] unsubscribe
Date: Tue, 23 Aug 2005 09:19:32 +1000	[thread overview]
Message-ID: <430A5D84.7040304@fastmail.fm> (raw)
In-Reply-To: <200508221005.24280.cryos@gentoo.org>

Marcus D. Hanwell wrote:
> On Monday 22 August 2005 08:48, C Y wrote:
> 
>>Perhaps we could have a "support team" behind someone with official
>>Gentoo developer status - people could point out significant ebuilds
>>with most logic in place to the developer, help work out quirks in the
>>programs/ebuilds, and generally speed things up?  Certainly the
>>developer would bear final responsibility but this way those of us with
>>five hours every month or so could help out too, particularly for
>>specialty packages.  (BTY, if some genius could figure out brl-cad I
>>would be grateful - it's going to take me a year at this point :-/.)
> 
> 
> I was wondering myself if some people in here might be receptive to the idea 
> of a support team, much like the arch testers we have for the amd64 porting 
> team. It often leads on to people becoming devs, but is a great way to help 
> out when you can.
> 
> Tony Murray is filling that kind of role unofficially with all the work he 
> puts into the boinc and setiathome ebuilds, whilst I review, test, improve 
> and commit them once they are up to standard. I also have good contact with 
> the quickplot developer who has integrated my patches upstream and helped 
> significantly with the ebuilds for that package.
> 
> I think these relationships are important, and I personally nurture them as 
> much as possible. Many scientific packages are very involved and having 
> people help test and work out problems can significantly increase our 
> efficiency as a team.
> 
>>There are a fair number of at least partial ebuilds for useful
>>scientific software stuck in bugzilla - brl-cad and acl2 come
>>immediately to mind, and I know there are others.  Plus a fair number
>>that don't have ebuilds where it would be useful to have them.  Gentoo
>>is alreay one of the best for scientific software, due to compiling
>>things being easy and our ebuild pool, but we could definitely do
>>better.
> 
> 
> The problem comes down to manpower and a need to recruit some more people to 
> the team. Having a support team similar to the arch testers could certainly 
> help in our case if those people were not ready to become devs/didn't have 
> the time. Once a package has been committed they would also need to help with 
> version bumps and fixing bugs with the new packages ideally.
> 
>>My machine is probably a poor test machine - what gentoo environment
>>would we need to maintain?
> 
> 
> Just an up to date Gentoo install is fine. If you are testing some more 
> experimental stuff (I test new baselayout, glibc, gcc and other core stuff 
> sometimes) then a chroot might also be adviseable. Scientific apps just 
> require an up to date system.
> 
> Thanks,
> 
> Marcus

-- 
gentoo-science@gentoo.org mailing list



  parent reply	other threads:[~2005-08-22 23:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200508161807.14897.cryos@gentoo.org>
     [not found] ` <200508172024.42323.ribosome@gentoo.org>
2005-08-18  9:52   ` [gentoo-science] Re: Scientific herd leadership George Shapovalov
2005-08-18 15:03     ` Olivier Fisette
2005-08-18 16:03       ` Donnie Berkholz
2005-08-18 20:35       ` Jordan Dawe
2005-08-21 19:58         ` Olivier Fisette
2005-08-21 23:15           ` M. Edward (Ed) Borasky
2005-08-22 16:12             ` Marcus D. Hanwell
2005-08-22  7:48           ` C Y
2005-08-22  9:05             ` Marcus D. Hanwell
2005-08-22 14:56               ` M. Edward (Ed) Borasky
2005-08-22 23:19               ` John Tee [this message]
2005-08-23  7:09                 ` [gentoo-science] unsubscribe Patrick Kursawe
2005-08-22 14:34             ` [gentoo-science] Re: Scientific herd leadership M. Edward (Ed) Borasky
2005-08-22 16:28               ` C Y
2005-08-21 13:47     ` Marcus D. Hanwell
     [not found] <200508251800.j7PI06kF008710@robin.gentoo.org>
2005-08-29  3:21 ` [gentoo-science] unsubscribe askclark
2006-09-16 12:24 askclark
     [not found] <20080319140015.B9107E0817@pigeon.gentoo.org>
2008-03-19 20:25 ` asclark
  -- strict thread matches above, loose matches on Subject: below --
2012-05-31 16:40 John Lips
2018-09-12 12:41 Frederico Moraes Ferreira

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=430A5D84.7040304@fastmail.fm \
    --to=johnmtee@fastmail.fm \
    --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