| 1 |
Hi, |
| 2 |
|
| 3 |
On Sun, 18 Mar 2018 20:29:49 +0100 Federico Lodovici wrote: |
| 4 |
> Hi, |
| 5 |
> during this week I've updated my gsoc proposal document, you can find it |
| 6 |
> here: |
| 7 |
> https://docs.google.com/document/d/1bN3ZiEGweg1t2SmPztIu6aveE5jQIZFGm722L31_tiM/edit?usp=sharing |
| 8 |
> What do you think? How can I improve it? |
| 9 |
|
| 10 |
Most important: provide detailed per-week plan of your work. This |
| 11 |
is very important. Listing deliverables is good, but we must see |
| 12 |
per-week progress on how you are going to obtain them. In case on |
| 13 |
unexpected problems the plan may be amended later if mutual mentors |
| 14 |
and student agreement is reached. |
| 15 |
|
| 16 |
The detailed plan is not just formality: it help a lot to see how |
| 17 |
student understands their task and how realistic are objectives |
| 18 |
within given time frame. Of course it should be reasonable without |
| 19 |
extremes: not too simple to be reasonable for 3 months of work and |
| 20 |
not overcomplicated, because student should do work timely. |
| 21 |
|
| 22 |
Please note that according to the GSoC program rules, mentors must |
| 23 |
evaluated student based on the final submitted application. |
| 24 |
Amendments after the deadline are not possible. |
| 25 |
|
| 26 |
> TF needs a lot of python dependencies and also optional cuda |
| 27 |
> toolkit and cuda libraries |
| 28 |
|
| 29 |
We already have CUDA toolkit and libraries in the sci overlay. They |
| 30 |
may need some update, but it shouldn't be a problem. |
| 31 |
|
| 32 |
> I’ll then start the most challenge part, porting and packaging |
| 33 |
> Intel Tools. |
| 34 |
|
| 35 |
While Intel stuff may rightfully be a part of your project, I do not |
| 36 |
recommend to focus on them too much, since this is a proprietary |
| 37 |
software and GSoC is all about Free/Libre software. |
| 38 |
|
| 39 |
> I’m also interested to port Intel’s python distribution |
| 40 |
|
| 41 |
I've discussed this project with Intel devs on one of the |
| 42 |
conferences. There is nothing special about it: it is a normal |
| 43 |
Python linked with Intel libraries and with some math libs replaced |
| 44 |
with more optimized free software solutions. So everyone can do the |
| 45 |
same with Intel MKL without need to obtain Intel Python. They |
| 46 |
created this project mostly due to marketing issues, since python |
| 47 |
is a popular language and management want to establish Intel's |
| 48 |
presence in this area. |
| 49 |
|
| 50 |
If you want to pursue this task, I recommend to build on FLOSS |
| 51 |
solutions as described above, packaging Intel Python itself is |
| 52 |
quite useless. |
| 53 |
|
| 54 |
> I’d like if it is possible to bring into the sci-gentoo overlay |
| 55 |
> an “official” matlab ebuild |
| 56 |
|
| 57 |
Devoting a whole month to the proprietary piece of software is |
| 58 |
questionable again. Devoting some time to improve |
| 59 |
proprietary software packaging in Gentoo is OK, but devoting half of |
| 60 |
your time for them is questionable at least. |
| 61 |
|
| 62 |
> I’ve fixed a compilation bug on sci-physics/rivet and I’m |
| 63 |
> finding the best strategy to fix sci-lib/scipy. |
| 64 |
|
| 65 |
Please provide a links or bug numbers for bugs you have fixed in |
| 66 |
the main repo. I found only your version bump of rivet (commit |
| 67 |
23ff9c6da1eb892b12e7a0b1edbf4d87ae4f6b26). If you have made other |
| 68 |
changes, please provide all the links in your proposal. |
| 69 |
|
| 70 |
Do not forget to run repoman on your packages or changes, your |
| 71 |
overlay clearly have some QA issues right now (e.g. packages lack |
| 72 |
metadata.xml). |
| 73 |
|
| 74 |
Bottom notes: |
| 75 |
|
| 76 |
1. Please provide your scheduled absence during the coding period if |
| 77 |
any: you may have exams or other events when your availability will |
| 78 |
be limited |
| 79 |
|
| 80 |
2. We need to know your availability hours and time zone. |
| 81 |
|
| 82 |
3. You must provide more contact information, see top of the |
| 83 |
https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2018/Ideas |
| 84 |
page for the list of our requirements: |
| 85 |
|
| 86 |
«Give us your contact info and working hours. Please provide your |
| 87 |
email address, home mailing address, and phone number. This is a |
| 88 |
requirement and provides for accountability on both your side and |
| 89 |
ours. Also, please tell us what hours you will be working and |
| 90 |
responsive to contact via email and IRC; these should sum to at |
| 91 |
least 35 hours a week.» |
| 92 |
|
| 93 |
There is no need to provide your personal data in publicly visible |
| 94 |
draft, however be sure to include it in the final proposal. |
| 95 |
|
| 96 |
Thanks and good luck! |
| 97 |
|
| 98 |
P.S. Please, do not top-post. |
| 99 |
|
| 100 |
Best regards, |
| 101 |
Andrew Savchenko |
Archives