1 |
Hi devs, |
2 |
|
3 |
First, I want to apologise, as many of you will get two copiess of this email |
4 |
and some will even see it three, this one time. I, however, wanted to make |
5 |
sure everybody has all the relevant addresses. |
6 |
|
7 |
Second, indeed I think we should move this discussion to the list, rather than |
8 |
sending emails with bunch of CCs. I would like to remind everybody, that |
9 |
there is a mailing list: gentoo-science@l.g.o, which is supposed |
10 |
to be used for more or less general discussions related to our project and |
11 |
especially for stuff like that. Donnie: nice reminder of the sci alias, but I |
12 |
think the list is suited better for this purpose. First, it is free for all |
13 |
to sign up, so we need not take special care of interested/involved nondevs. |
14 |
More importantly, this way the discussion will not interfer with bug reports |
15 |
(and the other way around). |
16 |
|
17 |
Wednesday, 13. May 2009, Andrey Kislyuk Ви написали: |
18 |
> - Current projects. All active developers, please reply to this |
19 |
> message with a list of any major items you're working on, so we can |
20 |
> put them in the status report. For instance, I'm working on the |
21 |
> bioperl-1.6.0 update and a few big troublesome sci-biology packages |
22 |
> including ncbi-tools++, gbench, wgs-assembler and cytoscape. I know |
23 |
> Markus is working on the Octave 3 stuff. What else? |
24 |
Thanks for the reports sent so far. However I would like to expand this |
25 |
request a bit - it would really be nice to get a headcount. Therefore, I |
26 |
would like to ask all devs who are still involved in Scientific Gentoo to |
27 |
respond, shortly outlining the (intended) range of "responsibilities" and |
28 |
expected activity level, - even if not very active at the moment. Please |
29 |
answer to the list, so that we can keep track of the responces in one concise |
30 |
thread. Actually, I'll branch the discussion then and will create a subthread |
31 |
for this in a moment.. |
32 |
|
33 |
After collecting the responce we can update the webpage - I could do it or |
34 |
somebody else willing could step up ;). |
35 |
|
36 |
I'll start with myself: |
37 |
> - Selecting a lead. George Shapovalov is our current lead. George, if |
38 |
> you're active, we'll need your help with the status update, otherwise |
39 |
> we need to select a new lead. Please reply to nominate people or with |
40 |
> any thoughts (we could be anarchists like the python herd and go |
41 |
> without a lead!) |
42 |
Well, I am here, although I am not working on any specific package(s), mostly |
43 |
reacting to organizational issues. I was indeed rather quiet last few month, |
44 |
however we have seen a steady flow of new contributors to science overlay - I |
45 |
had to do mediate one almost montly for the last year or so. Which implies, |
46 |
that we should have a good pool of potential devs, however, as always, this |
47 |
is not guaranteed - people need to stay active, not just show activity once. |
48 |
|
49 |
As for my lead status - either is fine with me. I try to react and organize |
50 |
when something comes up, however, I am afraid, I will not have much time in |
51 |
the coming year or two for more active actions (have to push out a couple of |
52 |
papers and change position). In this regard, you could call what was going on |
53 |
an anarchy - people going about their regular routines and taking care of |
54 |
their areas of interest and organizing when necessary, but I would rather |
55 |
call it "pragmatic handling" ;). If there are some ideas about some projects |
56 |
it would be interesting to discuss them, however, as I mentioned, it has been |
57 |
quiet lately in this regard. I'd say, the real need that we may have is |
58 |
organizing another wave of recruitment. Thus I definitly wellcome the request |
59 |
for recruitment status: |
60 |
> - Recruiting and recruit status. If you're being recruited or are in |
61 |
> charge of a recruit, please reply so we have a head count and let us |
62 |
> know the ETA for becoming a dev if you have one. |
63 |
but again, would like to expand it slightly. As the original message will only |
64 |
reach the people on the original CC list, I'd like to ask anybody who knows a |
65 |
prospective applicant/interested user to forward this rectuitment request |
66 |
correspondingly. Please ask them to subscribe to gentoo-science mailing list |
67 |
as well. Some of the old participants might even still be on the list in |
68 |
fact :). |
69 |
|
70 |
> We need to add a |
71 |
> staffing needs section to the project page. Do we have specific |
72 |
> recruiting requests? |
73 |
On the updating the recruitment page. IIRC we were discussing (somewhat |
74 |
transient discussion I must admit) this some half a year ago (with bicataly |
75 |
and somebody else on irc?). The general feeling was that our staffing needs |
76 |
are a bit different from the general Gentoo populace, as people who make a |
77 |
good fit would be proficient in (or at least familiar with) some or other |
78 |
scientific discipline. Also, such people usually have a crapload of other |
79 |
duties on their hands and/or are somewhat shy in terms of active |
80 |
participation in geek discussions/communities. Therefore we considered the |
81 |
overlay as the most promising recruitment avenue and I think we could try to |
82 |
check if any of its regualrs are ripe enough for joining with a full dev |
83 |
status. |
84 |
|
85 |
Nonetheless, putting the request in the open should not hart. I would, |
86 |
however, urge whoever is going to write recruitment request to be careful |
87 |
about wording. Weer there any specific plans - who and when was going to do |
88 |
this or should I write something up? (perhaps in ~2 weeks, after headcount |
89 |
somewhat settles; nug me if I slip off the radar again - I am almost always |
90 |
there, just silent). |
91 |
|
92 |
> We also need a tracker bug for science |
93 |
> contributors who are potential recruits. |
94 |
There is one such, still open, but did not see much activity for over a year. |
95 |
Perhaps we cpuld create a new one with less text :), although that one is not |
96 |
that long. But it should be better organized - we need a separate bugs |
97 |
branching off - one per recruitment case. In fact, we just need the recruits, |
98 |
as was discussed above, and this is the main problem I'd say. Then we can |
99 |
simply add standard recruitment bugs as dependencies. What may need to go in |
100 |
the bug itself are some org discussions - summaries of which could be |
101 |
attached to keep track of things. |
102 |
|
103 |
Oh, the bug; its #138021: |
104 |
https://bugs.gentoo.org/show_bug.cgi?id=138021 |
105 |
|
106 |
|
107 |
George |