public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jan Marten Simons <marten@xtal.rwth-aachen.de>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] website python error
Date: Mon, 18 Sep 2006 10:40:48 +0200	[thread overview]
Message-ID: <450E5B90.6030400@xtal.rwth-aachen.de> (raw)
In-Reply-To: <200609180843.12369.cryos@gentoo.org>

Marcus D. Hanwell wrote:
> I never tried to keep the overlay secret, but why should users have to 
> set up a myriad of overlays if they just want to run a system? May be you 
> would be better off becoming a developer and adding stuff to the tree? If we 
> follow a trend of keeping more and more stuff in various overlays then Gentoo 
> just becomes more of a pain to run IMHO.
>
> I am hoping to get more proactive in moving suitable ebuilds from the overlay 
> to the main tree in the near future. I will also be encouraging other devs to 
> do the same if they are not already. So the overlay will get smaller as stuff 
> is moved. Hopefully some of our active herd testers will go on to become 
> developers and maintain some of this stuff themselves too.
>
> May be the aims of the overlay should be more clearly defined through debate 
> and documented on the overlay site. I am away for the week starting in about 
> one hour anyway... I will catch up on discussions when I get back. It would 
> be good to hear what more people think about this subject - may be I am on my 
> own with my opinions?
>   

I think it would be a good thing if some interested users do some 
additionally testing of "in work" ebuilds, so that the applications are 
tested on a wider range of hardware and configurations. As a move to 
o.g.o would reduce maintainance as well, I'm in favour of this. 
gentooscience.org could then redirect there.


Jan

-- 
gentoo-science@gentoo.org mailing list



  parent reply	other threads:[~2006-09-18  8:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 13:35 [gentoo-science] website python error Nuno Sucena Almeida
2006-09-13 14:07 ` Andrey G. Grozin
2006-09-14 10:24   ` Marcus D. Hanwell
2006-09-14 10:49     ` Andrey G. Grozin
2006-09-14 11:19       ` Marcus D. Hanwell
2006-09-15  4:22     ` Donnie Berkholz
2006-09-15  7:50       ` Andrey G. Grozin
2006-09-15 11:57         ` Marcus D. Hanwell
2006-09-16  8:51           ` Andrey G. Grozin
2006-09-18  7:43             ` Marcus D. Hanwell
2006-09-18  7:24               ` Donnie Berkholz
2006-09-18  7:27                 ` Donnie Berkholz
2006-09-18  8:40               ` Jan Marten Simons [this message]
2006-09-21 13:53               ` Andrey G. Grozin
2006-09-15  9:05       ` Sebastien Fabbro
2006-09-15 11:51       ` Marcus D. Hanwell

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=450E5B90.6030400@xtal.rwth-aachen.de \
    --to=marten@xtal.rwth-aachen.de \
    --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