Re: [gentoo-science] sci team help

[Markus Luisser]

I could also sacrify some time to help - I'm not much of a programmer I fear, 
but testing or writing a small script every know and then is certainly not 
beyond me.

On Tuesday 16 October 2007, Jukka Ruohonen wrote:
> 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.)

Full ack to that, that's what things look like for me. I admit that I'm not 
following developments on gentoo so closely anymore, since I simply do not 
have the time, but even so, it can be a bit confusing to find one's way 
around the numerous overlays, official and not-so-official homepages and 
whatnot.

As Jukka expresses it, maybe that is just perceived but that doesn't make it 
less real.

On Tuesday 16 October 2007, Sébastien Fabbro wrote:
> 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?

For me personally, I'd like to see something like a ToDo or AdoptAnEbuild list 
somewhere, perhaps sorted by complexity, so that people that are interested 
can more easily try their hands on it. Just pointing people to bugs.g.o feels 
a little bit like Augeias' stable cleaning with no idea where to begin.

Moreover I guess there are plenty of things that do not have a bug report 
attached to them - stuff like hunting down the changed dependencies of a new 
software release or testing the stability of a simple version bump and things 
the like.

That might create a bit more overhead for 'real' developers but it might also 
lower the treshhold for new people.

Just my two cents.

Cheers

Markus