Hi Lumin and Andreas, Le jeudi 12 décembre 2019 à 11:11 +0100, Andreas Tille a écrit : > since I need to admit that I have no idea about BLAS/LAPACK and I'm just > a happy user of these packages as dependencies of several of my own > packages, I'm volunteering to co-mentor this project since I regard it > really important and would love to see it happen. A real mentor who can > give some advise and set directions (which I really can not!) would be > very welcome. My time for Debian is currently rather limited, so I was hesitating to be a mentor for this, though my position as long-time maintainer of BLAS/LAPACK (and suitesparse) makes me a natural candidate. On the other hand, Lumin has been doing a very valuable work on those packages, and we should make everything possible to allow him to continue and get all the support he needs. So, if this is possible, having Andreas and myself as co-mentors could be a workable solution. I should be able to give guidance and feedback from time to time. And Lumin is already quite familiar with the issues at hand, so I’m sure he can be autonomous to a large extent. What I’m much less motivated to do however is the “administrative” part, such as wrapping up the proposal or writing reports (though I don’t exactly what a mentor is supposed to do in that area). Maybe someone with more experience with GSoC could comment on that. Best, > On Wed, Dec 11, 2019 at 03:15:13PM +0000, Mo Zhou wrote: > > Hi science team, > > > > I'm proposing the following project for GSoC 2020: > > "Enhancement to Debian's BLAS/LAPACK Ecosys" > > To some extent this is basically making some portion of my > > todo-list well-funded by Google :-) > > > > I cannot "mentor" myself as I'm the participating student... > > So I think I need a GSoC mentor at this point. > > Please tell me if you are willing to be the mentor for this > > proposed project. > > > > Content of Proposal > > ------------------- > > > > 1. write down the formal (science team) policies about BLAS/LAPACK > > linkage and add corresponding lintian warnings. (Partially > > discussed on -devel before.) > > 2. help BLAS/LAPACK reverse dependencies get rid of the > > libcblas.so linkage. (confirmed in the previous MBF) > > 3. remove libcblas.so from src:atlas (confirmed by Sébastien) > > 4. integrate libflame into our ecosys (preliminary packaging > > already available on salsa. may need to work with upstream > > and solve some remaining problems. when the package is ready > > for debian, I'll also port it to Gentoo) > > 5. a fine documentation about debian's BLAS/LAPACK ecosys > > (some of you have already seen a private copy of this) > > > > Optional targets (if there will be enough time for me) > > ------------------------------------------------------ > > > > 1. update src:openblas and src:suitesparse and remove the vendored > > openblas/suitesparse from src:julia. > > 2. patch src:lapack and add 64bit-indexing support for CBLAS. > > > > Background/Who am I > > ------------------- > > > > I'm confident about acceptance ... as long as Debian will not fall > > out > > from the hosting organization list this year... > > > > 1. I'm currently a master student. > > 2. During GSoC2019, I introduced a blas/lapack runtime switch > > mechanism > > to Gentoo ( > > https://wiki.gentoo.org/wiki/Blas-lapack-switch > > ) > > which is to some extent similar to our update-alternatives. > > 3. currently I co-maintain a portion of blas/lapack packages for > > both Gentoo and Debian. > > 4. I have sufficient skill set (as a DD) to finish the proposal > > (that has been dragged for long time due to my slacking off) > > > > > > -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part