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 > -- > [EMAIL PROTECTED] mailing list > -- [EMAIL PROTECTED] mailing list
