1 |
Hi guys. |
2 |
|
3 |
Sorry that I did not reply yesterday, I had a presentation to prepare for |
4 |
today :). |
5 |
|
6 |
I actually moved to a new place already. I am in Switzerland at the moment |
7 |
(Geneva/Lausanne, anybody around?), starting a new postdoc position (somebody |
8 |
might remember my email to -core or -dev some time ago). I am getting back up |
9 |
to speed, however I am still in much flux and everything official takes soo |
10 |
long in Swiss :(. Pluss the stress of starting new work (and getting all the |
11 |
equipment together :))... |
12 |
|
13 |
There are a few points to address, so I'll structure my reply: |
14 |
|
15 |
1. |
16 |
Anyway, as far as the leadership goes, I have been a lead of the sci herd ever |
17 |
since I created it (few eyars already, was that really that long ago? :)). |
18 |
Unfortunately things were rather quiet lately and, as I am not completely |
19 |
"on" yet, I am willing to give the leadership off to somebody who will have |
20 |
enough time on his hands. That, or at least I think we should have an active |
21 |
co-lead or may be even some more involved structure. Well, lets start with a |
22 |
co-lead first, so that we get at least somehting done :). |
23 |
|
24 |
2. |
25 |
It would be good to have more devs involved in Scientific Gentoo. I can |
26 |
honestly say, that it surpassed my original expectations (it started out as a |
27 |
single category with a herd attached) and seems to have attained a status of |
28 |
an important project at the intersection of science and Linux. Looks like we |
29 |
have people recommending others to run Gentoo because of science apps we |
30 |
carry. Well, at least I saw few reports to that effect some time ago :). |
31 |
|
32 |
I used to put out calls for new/interested devs to help Scientific Gentoo, |
33 |
when I was more active, and the responce was rather positive. However |
34 |
recently I did not have enough time to devote to training of new devs, so |
35 |
that slipped by. I think it would be usefull to reinstate that initiative, |
36 |
but first we need to get a head-count of who feels like doing the training. |
37 |
Should we have a 1 year as a dev requirement for the trainers? (not the |
38 |
trainees of course! They are even better picked up from science than from |
39 |
Linux althogether :)) I would think so, given complexity of Gentoo nowadays |
40 |
and that last thing we want to do is to screw our comprehension by scientific |
41 |
community :). |
42 |
|
43 |
3. Blas/lapack move. |
44 |
Large part of it has been performed, new ebuild are in portage like for ages |
45 |
now. In fact so long, that I no longer feel we can just pick up from the |
46 |
point it was left at, but rather do another round of retesting (or even |
47 |
rethinking the concept) first. The part it staled at was to move all the |
48 |
dependant packages to a new blas/lapack system. I started adjusting some of |
49 |
the ebuilds a year or so ago, but I did not have that much time back then and |
50 |
did not want to step on the toyes of maintainers of these packages. |
51 |
I'll try to check the situation with blas/lapack ebuilds soon and then issue |
52 |
another call for adjustments (for dependant packages). Can we please get |
53 |
those adjustment done this time? Pretty please ;). |
54 |
Then (and only after that) the old versionf of blas/lapack will be masked and, |
55 |
eventually, removed. The bug tracing the status of blas/lapack move is |
56 |
#30453. Should we may be start a new, clean tracker bug? The mentioned one is |
57 |
pretty long, but it has a lot of essential info. |
58 |
|
59 |
4. |
60 |
I am for the regular meetings. It is probably good to try to settle on some |
61 |
time (may be easier if we go through with the "more involved unfrastructure", |
62 |
but the real need for it will only be there if we get 2x more devs than we |
63 |
have now (I mean in Scientific Gentoo)). However I agree, that reviving |
64 |
gentoo-science@l.g.o mailing list is a more realistic (and less |
65 |
stressful) option. In fact, everything is setup, lets just use it! |
66 |
(To give an example, I am CC'ng this message to that list. Sorry for dups, if |
67 |
you receive it twice). |
68 |
|
69 |
5. |
70 |
Anything else? |
71 |
|
72 |
George |
73 |
-- |
74 |
gentoo-science@g.o mailing list |