Hello, I'm interested in participating on this year's GSoC and more specifically with the "dnf pip plugin" idea. I'm Ilias, but in order not to repeat myself I've already written a few things about me here: https://fedoraproject.org/wiki/GSOC_2017/Student_Application_Ilias95 Up to this point, I have gone through the python API of dnf, the documentation of pip, and I also took a glance on code of other dnf plugins. I will very soon start to prepare a potential schedule, but first I would like to ask a few things please: 1. Will the plugin take into consideration requirement specifications on requirement.txt files or it will just ignore them? What should we do when we find a line like "X == 4.0" or "X > 4.1" but there's a different version available in Fedora? 2. What should we do if a package is already installed in the system through pip, but it is also available in Fedora? 1. Ignore it 2. Remove pip version and install the Fedora one. 3. Ask the user. 4. Other ? 3. What should we do if a package is already installed in the system through pip AND it's not available in Fedora? 4. There's this section of "other commands" in the project's description. Will I have to make the decisions for these? Should I just provide proposals in my application? Will we openly discuss it in the lists? 5. Do you believe that this specific project is "big" enough in order to get accepted by Google? I'm not referring to its importance that much (personally I like this idea a lot, and I'm sure it will be useful for a lot of people). I mostly refer about the time needed for its implementation. I mean, do you think it is enough to fill the whole 3-month full-time work period? I'm very keen on contributing to the Fedora project. I look forward to having a great cooperation with you, whether I finally make it to the program or not. Thank you very much for your time. Best regards, Ilias Stamatis _______________________________________________ summer-coding mailing list -- summer-coding@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to summer-coding-leave@xxxxxxxxxxxxxxxxxxxxxxx
