Dear Boost developers, organization applications for the Google Summer of Code 2023 will start next year in January, that is in about 2 months from now. In order to prepare the application for Boost C++, I would like to have a list of interested mentors and the topics they would like to propose to their students. The Google Summer of Code is a good opportunity for Boost to try ideas or improve existing libraries. Contact me now if you have any questions and are interested in mentoring next summer. Cheers, David
Hi David,
I've never participated in GSoC before but may be interested in mentoring.
I was thinking in an Asio-based postgres connection (as we've done with
MySQL). how does GSoC work? How much time does it take for mentors? Is a
new project like this adequate for the event?
Thanks,
Ruben.
On Tue, 15 Nov 2022, 02:24 David Bellot via Boost,
Dear Boost developers,
organization applications for the Google Summer of Code 2023 will start next year in January, that is in about 2 months from now.
In order to prepare the application for Boost C++, I would like to have a list of interested mentors and the topics they would like to propose to their students.
The Google Summer of Code is a good opportunity for Boost to try ideas or improve existing libraries. Contact me now if you have any questions and are interested in mentoring next summer.
Cheers, David
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi future mentors,
and hi to those who already answered by email (Hans, Ruben, etc...).
The way it works is quite simple:
1. Boost will be a candidate organization for the GSoC. I take care of
this part. If we are selected by Google, then we will ask for "slots", that
is a financing for each student. On average we get between 5 to 10 slots
per year, which is a nice contribution from Google to Boost.
2. Mentors can contact me with a project and also write their project on
our wiki page. We will advertise it to the potential students with the
description of each project. Ideally a mentor will briefly describe the
project and also ask for a programming test. We want the best students.
3. When we know how many slots we get from Google, the students will
submit their project. Each year we get roughly 80-100 candidates. I usually
"clean up" the list, removing the obviously bad projects and usually we're
down to 20 projects max.
4. Then either each mentor has a student and we're ready to announce the
winners, or we have to rank the students. So far, we never had the problem
of not having enough students or not having enough mentors, ... or too many
thinking of that. But if the numbers don't match, we will have to vote to
select students.
5. Finally, on the GSoC website, our winners are selected and Google
will start the process.
6. Then there is a bonding period during which the students will get in
touch with the Boost GSoC community, introduce themselves and work can
start.
7. The main core of the project is, of course, the coding period, during
which students work closely with their mentor. Usually there is a mid-term
evaluation and a final evaluation. If a student doesn't pass the mid-term,
then they will have to leave GSoC and will not get paid for the second term.
It's a very cool program, with many interesting students from all our the
world and I really encourage potential mentors to try this great
experience. The quality of the contributions can be very high and it helps
Boost a lot too.
Best,
David
-
On Mon, Nov 21, 2022 at 7:15 AM Ruben Perez via Boost
Hi David,
I've never participated in GSoC before but may be interested in mentoring. I was thinking in an Asio-based postgres connection (as we've done with MySQL). how does GSoC work? How much time does it take for mentors? Is a new project like this adequate for the event?
Thanks, Ruben.
On Tue, 15 Nov 2022, 02:24 David Bellot via Boost,
wrote: Dear Boost developers,
organization applications for the Google Summer of Code 2023 will start next year in January, that is in about 2 months from now.
In order to prepare the application for Boost C++, I would like to have a list of interested mentors and the topics they would like to propose to their students.
The Google Summer of Code is a good opportunity for Boost to try ideas or improve existing libraries. Contact me now if you have any questions and are interested in mentoring next summer.
Cheers, David
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Sun, 20 Nov 2022 at 21:15, Ruben Perez via Boost
I've never participated in GSoC before but may be interested in mentoring. I was thinking in an Asio-based postgres connection (as we've done with MySQL). how does GSoC work?
Well, Boost participation does not differ to a regular GSoC one, we follow all the rules and timeline https://summerofcode.withgoogle.com/how-it-works https://developers.google.com/open-source/gsoc/timeline https://github.com/boostorg/wiki/wiki/Google-Summer-of-Code%3A-Overview
How much time does it take for mentors?
It varies, it depends on a project and a student, https://google.github.io/gsocguides/mentor/setting-expectations#project-size... I recommend skimming through all the official guides https://google.github.io/gsocguides/mentor/
Is a new project like this adequate for the event?
AFAIR, we have agreed within Boost that a new library is not a good project for GSoS, and for variety of reasons. It may be a success, but you may also shoot yourself in a foot mentoring a student who you likely don't know professionally. GSoC is not a trivial work for both, mentors and students. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
On Mon, 21 Nov 2022 at 13:25, Mateusz Loskot via Boost < boost@lists.boost.org> wrote:
Is a new project like this adequate for the event?
AFAIR, we have agreed within Boost that a new library is not a good project for GSoS, and for variety of reasons.
It may be a success, but you may also shoot yourself in a foot mentoring a student who you likely don't know professionally. GSoC is not a trivial work for both, mentors and students.
I agree with this. I have been a GSoC student who tried to introduce a new library and have also been a mentor of that library and an existing library. A new library requires a lot of work beyond GSoC and due to lack of time and other various reasons students may be unable to finish it. A student may complete the target of GSoC and make it a successful GSoC project but after that, the progress maybe be stalled and it may be a failed library. So a project which can be finished completely inside the GSoC window is a good choice IMHO. -- Thank you, Pranam Lashkari, https://lpranam.github.io/
participants (4)
-
David Bellot
-
Mateusz Loskot
-
Pranam Lashkari
-
Ruben Perez