Re: [gentoo-dev] GSoC 2020: Call for mentors and project ideas
Am Sonntag, 2. Februar 2020, 12:47:55 CET schrieb Benda Xu: > Dear Fellows, > > alicef writes: > > > As always, Gentoo plans to participate in the Google Summer of Code > > 2020. We are looking for new project ideas and are always open for > > new mentors. > > Google Summer of Code is a big opportunity for making Gentoo project more > > visible and get more people interested to join Gentoo and helping out. > > > > [...] > > This year's GSoC organization application deadline is on Feb 5. The > more project ideas, the better Gentoo will show itself to be prepared. > If you have been thinking of adding projects to our GSoC 2020 list, this > is a good chance to do so. > > Cheers, > Benda > Hi, I saw the idea „Big Data Infrastructure by Gentoo“ and found it kind of interesting. However, I have a little bit the fear that a full automation won't be possible and the whole project becomes a little bit like g-sorcery (gs-pypi, gs-elpa) or g-octave: a really cool project but not used at a large scale. What do you think of the idea to not do this fully automated but supervised by a maintainer? With that I mean an ebuild generator that generates only the parts of the ebuild that it can easily parse and then present the ebuild draft to a maintainer who completes it to an full ebuild. As far a I know no tool like this exists. I think the focus shift helps a lot: Developing a tool for the Gentoo maintainer not the Gentoo user. I'm only "maintaining" an overlay so maybe I'm missing experience but I often have wished a tool that automatically parses the language specific packaging files and is able to generate a primitive ebuild out of that. Maybe it even can do this in an interactive way: "Hey, upstream needs the dependency 'foo'. In the Gentoo packages I have found 'dev-bar/foo' and 'dev-util/foo'. What is the correct one?" With a not fully automatic tool also packages can be parsed that are not in a complete closed ecosystem, like a 'meson.build' file or cmake files for C++/C programs. But of course package databases like Maven/Cargo/Pypi are also candidates. Unfortunately, I have no time currently to participate in the GSOC. I just want to mention this here as an idea. Please comment or correct me, if such a tool already exists. Best, Gerion signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] GSoC 2020: Call for mentors and project ideas
Dear Fellows, alicef writes: > As always, Gentoo plans to participate in the Google Summer of Code > 2020. We are looking for new project ideas and are always open for > new mentors. > Google Summer of Code is a big opportunity for making Gentoo project more > visible and get more people interested to join Gentoo and helping out. > > [...] This year's GSoC organization application deadline is on Feb 5. The more project ideas, the better Gentoo will show itself to be prepared. If you have been thinking of adding projects to our GSoC 2020 list, this is a good chance to do so. Cheers, Benda signature.asc Description: PGP signature
Re: [gentoo-dev] GSoC 2020: Call for mentors and project ideas
Thank you Alice! alicef writes: > As always, Gentoo plans to participate in the Google Summer of Code > 2020. We are looking for new project ideas and are always open for > new mentors. > Google Summer of Code is a big opportunity for making Gentoo project more > visible and get more people interested to join Gentoo and helping out. > > [...] Gentoo has receive high quality contributions in the past. I hope this year we could have attract more talented Google Summer of Code students to work with us. Cheers, Benda signature.asc Description: PGP signature
[gentoo-dev] GSoC 2020: Call for mentors and project ideas
Hello, As always, Gentoo plans to participate in the Google Summer of Code 2020. We are looking for new project ideas and are always open for new mentors. Google Summer of Code is a big opportunity for making Gentoo project more visible and get more people interested to join Gentoo and helping out. 1. Project ideas GSoC projects should be suitable for 3 months worth of work for a student, taking into account time required for students to get in touch with the project, to learn some details, to fix mistakes and make improvements. Most students are not yet seasoned developers, so their coding rate will be likely slower than yours. Usually projects are something more complicated than just writing some ebuilds, however if non-trivial ebuild related work is required, e.g. to write new eclasses and adapt existing packages to use them (or add new ones), this should do too. Ideas from previous years may be reused, but this should not be abused, since Gentoo moves forward and we have new stuff to do. If you have an idea, but can't be a mentor, please still tell us about it, we'll try to find a mentor later. Ideas should be put to our wiki: [1]. The page contains ideas adding howto. 2. Mentors If you want to be a mentor, welcome! It is not necessary to be a Gentoo developer in order to be a mentor, but project must be Gentoo related. Mentoring requires some time. It depends much on a student, but is usually within 4-10 hours per week. If you don't have that much time, but still want to help, you may become a backup mentor. Students often have 2 mentors to eliminate bus factor and to improve expertise in a project. Please keep in mind that GSoC is not just about new code, but about bringing new people to community and we have developers which where GSoC students in the past. So time invested in students will result not only in some problems solved, but into bringing new people to our community and strengthening ties with existing participants. Mentors should enlist themselves on the wiki: [2]. If you have any questions or proposals, feel free to reply to this e-mail, or contact us via #gentoo-soc IRC channel on FreeNode[3], or by writing to project's alias[4]. [1] https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2020/Ideas [2] https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2020/Mentors [3] http://webchat.freenode.net/?channels=gentoo-soc [4] mailto:soc-ment...@gentoo.org Thanks, Alice -- == Thanks, Alice Ferrazzi Gentoo Kernel Project Leader PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A == 0x5621A6B28638781A.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
