From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1M4WtM-0002Vm-BL for garchives@archives.gentoo.org; Thu, 14 May 2009 09:06:17 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9051BE04D6; Thu, 14 May 2009 09:06:15 +0000 (UTC) Received: from mbox.unige.ch (mbox.unige.ch [129.194.9.209]) by pigeon.gentoo.org (Postfix) with ESMTP id 4AB99E04D6 for ; Thu, 14 May 2009 09:06:15 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-science@lists.gentoo.org Reply-to: gentoo-science@lists.gentoo.org MIME-version: 1.0 Content-disposition: inline Content-type: text/plain; charset=utf-8 Received: from deleron ([129.194.54.121]) by mbox.unige.ch (Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007; 32bit)) with ESMTPS id <0KJM004O3MLSG280@mbox.unige.ch> for gentoo-science@lists.gentoo.org; Thu, 14 May 2009 11:05:52 +0200 (CEST) From: George Shapovalov Organization: Gentoo Linux To: gentoo-science@lists.gentoo.org Subject: [gentoo-science] Re: Gentoo Science project status Date: Thu, 14 May 2009 11:05:26 +0200 User-Agent: KMail/1.9.10 Cc: sci@gentoo.org, bicatali@gentoo.org, calchan@gentoo.org, cryos@gentoo.org, dberkholz@gentoo.org, djay@gentoo.org, fordfrog@gentoo.org, grozin@gentoo.org, hanno@gentoo.org, je_fro@gentoo.org, jsbronder@gentoo.org, markusle@gentoo.org, nerdboy@gentoo.org, phosphan@gentoo.org, ribosome@gentoo.org, spock@gentoo.org, weaver@gentoo.org, A.G.Grozin@inp.nsk.su, lucas.chiesa@gmail.com, gentoofan23@gentoo.org, jlec@j-schmitz.net, jcdemay@gmail.com, tom111@gmx.de, f.r.bissey@massey.ac.nz, marcus@cryos.org, rei4dan@gmail.com, oli.borm@web.de, scarabeus@gentoo.org, Andrey Kislyuk , alexxy@gentoo.org References: <17e1a1290905131226i75476536t7bb473506ccaee4@mail.gmail.com> In-reply-to: <17e1a1290905131226i75476536t7bb473506ccaee4@mail.gmail.com> Content-transfer-encoding: quoted-printable Message-id: <200905141105.31841.george@gentoo.org> X-Archives-Salt: 749dd938-18ab-42c0-84f8-9890110196aa X-Archives-Hash: b7f59a723f314982dab85bccaaa88fac Hi devs, =46irst, I want to apologise, as many of you will get two copiess of this e= mail=20 and some will even see it three, this one time. I, however, wanted to make= =20 sure everybody has all the relevant addresses. Second, indeed I think we should move this discussion to the list, rather t= han=20 sending emails with bunch of CCs. I would like to remind everybody, that=20 there is a mailing list: gentoo-science@lists.gentoo.org, which is supposed= =20 to be used for more or less general discussions related to our project and= =20 especially for stuff like that. Donnie: nice reminder of the sci alias, but= I=20 think the list is suited better for this purpose. First, it is free for all= =20 to sign up, so we need not take special care of interested/involved nondevs= =2E=20 More importantly, this way the discussion will not interfer with bug report= s=20 (and the other way around). Wednesday, 13. May 2009, Andrey Kislyuk =D0=92=D0=B8 =D0=BD=D0=B0=D0=BF=D0= =B8=D1=81=D0=B0=D0=BB=D0=B8: > - Current projects. All active developers, please reply to this > message with a list of any major items you're working on, so we can > put them in the status report. For instance, I'm working on the > bioperl-1.6.0 update and a few big troublesome sci-biology packages > including ncbi-tools++, gbench, wgs-assembler and cytoscape. I know > Markus is working on the Octave 3 stuff. What else? Thanks for the reports sent so far. However I would like to expand this=20 request a bit - it would really be nice to get a headcount. Therefore, I=20 would like to ask all devs who are still involved in Scientific Gentoo to=20 respond, shortly outlining the (intended) range of "responsibilities" and=20 expected activity level, - even if not very active at the moment. Please=20 answer to the list, so that we can keep track of the responces in one conci= se=20 thread. Actually, I'll branch the discussion then and will create a subthre= ad=20 for this in a moment.. After collecting the responce we can update the webpage - I could do it or= =20 somebody else willing could step up ;). I'll start with myself: > - Selecting a lead. George Shapovalov is our current lead. George, if > you're active, we'll need your help with the status update, otherwise > we need to select a new lead. Please reply to nominate people or with > any thoughts (we could be anarchists like the python herd and go > without a lead!) Well, I am here, although I am not working on any specific package(s), most= ly=20 reacting to organizational issues. I was indeed rather quiet last few month= ,=20 however we have seen a steady flow of new contributors to science overlay -= I=20 had to do mediate one almost montly for the last year or so. Which implies,= =20 that we should have a good pool of potential devs, however, as always, this= =20 is not guaranteed - people need to stay active, not just show activity once. As for my lead status - either is fine with me. I try to react and organize= =20 when something comes up, however, I am afraid, I will not have much time in= =20 the coming year or two for more active actions (have to push out a couple o= f=20 papers and change position). In this regard, you could call what was going = on=20 an anarchy - people going about their regular routines and taking care of=20 their areas of interest and organizing when necessary, but I would rather=20 call it "pragmatic handling" ;). If there are some ideas about some project= s=20 it would be interesting to discuss them, however, as I mentioned, it has be= en=20 quiet lately in this regard. I'd say, the real need that we may have is=20 organizing another wave of recruitment. Thus I definitly wellcome the reque= st=20 for recruitment status: > - Recruiting and recruit status. If you're being recruited or are in > charge of a recruit, please reply so we have a head count and let us > know the ETA for becoming a dev if you have one.=20 but again, would like to expand it slightly. As the original message will o= nly=20 reach the people on the original CC list, I'd like to ask anybody who knows= a=20 prospective applicant/interested user to forward this rectuitment request=20 correspondingly. Please ask them to subscribe to gentoo-science mailing lis= t=20 as well. Some of the old participants might even still be on the list in=20 fact :). > We need to add a=20 > staffing needs section to the project page. Do we have specific > recruiting requests?=20 On the updating the recruitment page. IIRC we were discussing (somewhat=20 transient discussion I must admit) this some half a year ago (with bicataly= =20 and somebody else on irc?). The general feeling was that our staffing needs= =20 are a bit different from the general Gentoo populace, as people who make a= =20 good fit would be proficient in (or at least familiar with) some or other=20 scientific discipline. Also, such people usually have a crapload of other=20 duties on their hands and/or are somewhat shy in terms of active=20 participation in geek discussions/communities. Therefore we considered the= =20 overlay as the most promising recruitment avenue and I think we could try t= o=20 check if any of its regualrs are ripe enough for joining with a full dev=20 status.=20 Nonetheless, putting the request in the open should not hart. I would,=20 however, urge whoever is going to write recruitment request to be careful=20 about wording. Weer there any specific plans - who and when was going to do= =20 this or should I write something up? (perhaps in ~2 weeks, after headcount= =20 somewhat settles; nug me if I slip off the radar again - I am almost always= =20 there, just silent). > We also need a tracker bug for science=20 > contributors who are potential recruits.=20 There is one such, still open, but did not see much activity for over a yea= r.=20 Perhaps we cpuld create a new one with less text :), although that one is n= ot=20 that long. But it should be better organized - we need a separate bugs=20 branching off - one per recruitment case. In fact, we just need the recruit= s,=20 as was discussed above, and this is the main problem I'd say. Then we can=20 simply add standard recruitment bugs as dependencies. What may need to go i= n=20 the bug itself are some org discussions - summaries of which could be=20 attached to keep track of things. Oh, the bug; its #138021: https://bugs.gentoo.org/show_bug.cgi?id=3D138021 George