Attn: We need GSoC 2014 mentors for Boost!
Dear Boost community, We are now just five days away from the closing date for Google Summer of Code 2014 registration. Last year's GSoC was a huge success, with Google funding work on Boost to the tune of $35,000 and paying over $8,000 in costs for three representatives of Boost to attend the GSoC mentor's summit at Google HQ. As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! At the time of writing, we have just *eight* prospective mentors, and we need more to be sure of being approved by Google! Therefore, if you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list at https://svn.boost.org/trac/boost/wiki/SoC2014. If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost@lists.boost.org. Thank you in advance for your time. Niall Douglas (Boost Google Summer of Code admin) Boris Schäling (Boost Google Summer of Code backup admin)
On 02/07/2014 10:15 PM, Niall Douglas wrote:
As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! At the time of writing, we have just *eight* prospective mentors, and we need more to be sure of being approved by Google!
I would suggest not to read too much into previous approvals / rejections. I seriously doubt there to be a strong correlation between number of potential mentors / projects and the likelihood of acceptance of the organization. (The number of slots we may be awarded is an entirely different question, but that comes much later in the process.) FWIW, Stefan -- ...ich hab' noch einen Koffer in Berlin...
On 7 Feb 2014 at 22:23, Stefan Seefeld wrote:
for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! At the time of writing, we have just *eight* prospective mentors, and we need more to be sure of being approved by Google!
I would suggest not to read too much into previous approvals / rejections. I seriously doubt there to be a strong correlation between number of potential mentors / projects and the likelihood of acceptance of the organization. (The number of slots we may be awarded is an entirely different question, but that comes much later in the process.)
In the org registration form they explicitly ask for the number of mentors you already have ready and willing. That suggests it is an important criterion for approval. Niall -- Currently unemployed and looking for work in Ireland. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/
As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects!
Thanks for the reminder Niall and Boris, and for cultivating
intrerest here.
I was thinking of two ideas to improve the clarity and robustness
of our project list.
1) Remove the question marks (?) from the potential projects
and move most of these to the "ideas" section.
2) I could potentially offer to participate as dual-mentor with
Vicente on the fixed-point class. Boost really needs to make
progress here. And we can still decline to do the project
unless the realy, really, really, super candidate knocks on
the door. I recall that we failed to find the *right* candidate
for this challenging project last year.
What do you think about these? Vicente? Anyone else?
Cheers, Chris.
On Saturday, February 8, 2014 4:16 AM, Niall Douglas
Le 08/02/14 11:35, Christopher Kormanyos a écrit :
As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! Thanks for the reminder Niall and Boris, and for cultivating intrerest here.
I was thinking of two ideas to improve the clarity and robustness of our project list.
1) Remove the question marks (?) from the potential projects and move most of these to the "ideas" section. I will try to do it today.
2) I could potentially offer to participate as dual-mentor with Vicente on the fixed-point class. Boost really needs to make progress here. And we can still decline to do the project unless the realy, really, really, super candidate knocks on the door. I recall that we failed to find the *right* candidate for this challenging project last year.
What do you think about these? Vicente? Anyone else?
I don't know if Google accepts dual mentors. If not, you could mentor this project that is very close to the domain you are working with Boost.Multiprecission. I would be happy to help as much as possible. Please be free to add you name as possible mentor. Best, Vicente
Le 08/02/14 14:43, Vicente J. Botet Escriba a écrit :
Le 08/02/14 11:35, Christopher Kormanyos a écrit :
As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! Thanks for the reminder Niall and Boris, and for cultivating intrerest here.
I was thinking of two ideas to improve the clarity and robustness of our project list.
1) Remove the question marks (?) from the potential projects and move most of these to the "ideas" section. I will try to do it today. Humm, why do you want to move this to the "ideas" section?
Vicente
1) Remove the question marks (?) from the potential projects and move most of these to the "ideas" section.
I will try to do it today.
Humm, why do you want to move this to the "ideas" section?
Really just remove the question marks. With the question
marks on the topics, I was not sure if you wanted to make
the time commitment for mentoring.
I guess maybe if you are sure about potentially mentoring a topic,
then leave it in the projects. If you are uncertain, maybe the ideas
section might be better.
Sorry about bothering you.
Cheers, Chris.
On Saturday, February 8, 2014 3:03 PM, Vicente J. Botet Escriba
Le 08/02/14 11:35, Christopher Kormanyos a écrit :
As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! Thanks for the reminder Niall and Boris, and for cultivating intrerest here.
I was thinking of two ideas to improve the clarity and robustness of our project list.
1) Remove the question marks (?) from the potential projects and move most of these to the "ideas" section. I will try to do it today. Humm, why do you want to move this to the "ideas" section?
Vicente _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
What do you think about these? Vicente? Anyone else?
I don't know if Google accepts dual mentors. If not, you could mentor this project that is very close to the domain you are working with Boost.Multiprecission. I would be happy to help as much as possible. Please be free to add you name as possible mentor.
Thanks, Vicente. I'll think about it. I am aware of a young programmer
we recently worked with who would be technically capable of going
far in this project.
But I don't know if I should mentor two projects. I might not have
enough time for that.
I'll let you know soon.
Cheers, Chris.
On Saturday, February 8, 2014 2:43 PM, Vicente J. Botet Escriba
As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! Thanks for the reminder Niall and Boris, and for cultivating intrerest here.
I was thinking of two ideas to improve the clarity and robustness of our project list.
1) Remove the question marks (?) from the potential projects and move most of these to the "ideas" section. I will try to do it today.
2) I could potentially offer to participate as dual-mentor with Vicente on the fixed-point class. Boost really needs to make progress here. And we can still decline to do the project unless the realy, really, really, super candidate knocks on the door. I recall that we failed to find the *right* candidate for this challenging project last year.
What do you think about these? Vicente? Anyone else?
I don't know if Google accepts dual mentors. If not, you could mentor this project that is very close to the domain you are working with Boost.Multiprecission. I would be happy to help as much as possible. Please be free to add you name as possible mentor. Best, Vicente _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On 8 Feb 2014 at 14:43, Vicente J. Botet Escriba wrote:
2) I could potentially offer to participate as dual-mentor with Vicente on the fixed-point class. Boost really needs to make
I don't know if Google accepts dual mentors. If not, you could mentor this project that is very close to the domain you are working with Boost.Multiprecission. I would be happy to help as much as possible. Please be free to add you name as possible mentor.
Actually Google absolutely loves to see a second/backup mentor. In fact we have to fill in a question on the registration form about how we plan for and organise backup mentors. You do need a "primary" mentor though, and there can be only one of those. You can have as many secondary/backup mentors as you like. Indeed, last year the Trie project had three mentors! All mentors get T-shirts and can be funded to attend the GSoC mentors conference! :) Niall -- Currently unemployed and looking for work in Ireland. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/
On 8 Feb 2014 at 10:35, Christopher Kormanyos wrote:
2) I could potentially offer to participate as dual-mentor with Vicente on the fixed-point class. Boost really needs to make progress here. And we can still decline to do the project unless the realy, really, really, super candidate knocks on the door. I recall that we failed to find the *right* candidate for this challenging project last year.
It's always a challenge to find good students. Last year we lost our top rated candidate and proposal because Google refused to fund them for Boost. In the end, you make do with what you get. Niall -- Currently unemployed and looking for work in Ireland. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/
We are now just five days away from the closing date for Google Summer of Code 2014 registration. Last year's GSoC was a huge success, with Google funding work on Boost to the tune of $35,000 and paying over $8,000 in costs for three representatives of Boost to attend the GSoC mentor's summit at Google HQ.
As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! At the time of writing, we have just *eight* prospective mentors, and we need more to be sure of being approved by Google!
Therefore, if you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list at https://svn.boost.org/trac/boost/wiki/SoC2014.
If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost@lists.boost.org. Thank you in advance for your time.
Niall, I'd be happy to help with mentoring one student if the topic fits. Thanks! Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu
Dear Mr. Kaiser , I'd like to be a part of this project considering my deep
interest in algorithms and parallel computing. I am currently working on a
study project involving the use of OpenMP/MPI to solve boundary value
problems. Could you please specify the pre requisites(if any) etc. ?
On Sat, Feb 8, 2014 at 8:38 PM, Hartmut Kaiser
We are now just five days away from the closing date for Google Summer of Code 2014 registration. Last year's GSoC was a huge success, with Google funding work on Boost to the tune of $35,000 and paying over $8,000 in costs for three representatives of Boost to attend the GSoC mentor's summit at Google HQ.
As part of filling in our application for 2014, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2014. We do NOT want a repeat of 2012 when our application was rejected due to an insufficiently long list of prospective mentors and projects! At the time of writing, we have just *eight* prospective mentors, and we need more to be sure of being approved by Google!
Therefore, if you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list at https://svn.boost.org/trac/boost/wiki/SoC2014.
If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost@lists.boost.org. Thank you in advance for your time.
Niall, I'd be happy to help with mentoring one student if the topic fits.
Thanks! Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On 8 Feb 2014 at 9:08, Hartmut Kaiser wrote:
If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost@lists.boost.org. Thank you in advance for your time.
Niall, I'd be happy to help with mentoring one student if the topic fits.
Do any of the work items listed on https://svn.boost.org/trac/boost/wiki/SoC2014 interest you? For those that do, if you could add your name as a "potential mentor" under their description that would be great. If none suit you, would you have a GSoC project proposal to mind? Niall -- Currently unemployed and looking for work in Ireland. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/
If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost@lists.boost.org. Thank you in advance for your time.
Niall, I'd be happy to help with mentoring one student if the topic fits.
Do any of the work items listed on https://svn.boost.org/trac/boost/wiki/SoC2014 interest you? For those that do, if you could add your name as a "potential mentor" under their description that would be great.
If none suit you, would you have a GSoC project proposal to mind?
I'd be happy to mentor any of the projects related to parallelism or concurrency. Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu
On 8 Feb 2014 at 20:47, Hartmut Kaiser wrote:
If none suit you, would you have a GSoC project proposal to mind?
I'd be happy to mentor any of the projects related to parallelism or concurrency.
Ok, I'll add you as a potential mentor to any project I think relates to parallelism or concurrency. Be aware you may be surprised at what I think you interested in :) Niall --- Boost C++ Libraries Google Summer of Code 2014 admin https://svn.boost.org/trac/boost/wiki/SoC2014
If none suit you, would you have a GSoC project proposal to mind?
I'd be happy to mentor any of the projects related to parallelism or concurrency.
Ok, I'll add you as a potential mentor to any project I think relates to parallelism or concurrency. Be aware you may be surprised at what I think you interested in :)
Thanks Niall. Some comments: Boost.Functional / Invoke: This has already been fully implemented by Agustin Berge here: https://github.com/STEllAR-GROUP/hpx/blob/master/hpx/util/invoke.hpp. Feel free to use. Boost.Thread / Work-Stealing-Thread-Pool: This is something already implemented as part of HPX (https://github.com/STEllAR-GROUP/hpx), we have several work-stealing implementations, FWIW. Feel free to use. Boost.Thread / Scheduler-Executor: Note that there is a newer document (D3904, sorry I have no direct link), which will be discussed next week in Issaquah and I expect for it to be changed significantly. Boost.Thread / Parallel algorithms: Should that include N3554: http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n3554.pdf? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu
If none suit you, would you have a GSoC project proposal to mind? I'd be happy to mentor any of the projects related to parallelism or concurrency. Ok, I'll add you as a potential mentor to any project I think relates to parallelism or concurrency. Be aware you may be surprised at what I think you interested in :) Thanks Niall.
Some comments:
Boost.Functional / Invoke: This has already been fully implemented by Agustin Berge here: https://github.com/STEllAR-GROUP/hpx/blob/master/hpx/util/invoke.hpp. Feel free to use. There are some implementations of invoke by there, even one in Boost.Thread. My intention is that the project result in a new library in Boost that can be used by the user and other libraries in Boost. I want also that an invoker class be added and take in account a possible invocation_trait in Boost.Thread. Thanks for the offer. Boost.Thread / Work-Stealing-Thread-Pool: This is something already implemented as part of HPX (https://github.com/STEllAR-GROUP/hpx), we have several work-stealing implementations, FWIW. Feel free to use. Again thanks. The intent is to have this in Boost.
Boost.Thread / Scheduler-Executor: Note that there is a newer document (D3904, sorry I have no direct link), which will be discussed next week in Issaquah and I expect for it to be changed significantly. I'm aware of it. I have proposed on the std-proposal ML to turn the dynamic polymorphism on a static polymorphism, but I have not received any comments from the authors. IMO, the time scheduled operations are orthogonal to the executor and so I propose to have an adaptor that adds
Le 09/02/14 16:47, Hartmut Kaiser a écrit : these operations to any model of Executor.
Boost.Thread / Parallel algorithms: Should that include N3554: http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n3554.pdf?
It could, of course. At least the std::par functions, but I prefer to replace the execution_policy by an Executor. Specializations for a specific executor would always be possible. I've added the reference on the wiki project. Best, Vicente
On 9 Feb 2014 at 17:24, Vicente J. Botet Escriba wrote:
Boost.Thread / Work-Stealing-Thread-Pool: This is something already implemented as part of HPX (https://github.com/STEllAR-GROUP/hpx), we have several work-stealing implementations, FWIW. Feel free to use.
Again thanks. The intent is to have this in Boost.
Would HPX's implementation be easily portable to Boost do you think?
Boost.Thread / Scheduler-Executor: Note that there is a newer document (D3904, sorry I have no direct link), which will be discussed next week in Issaquah and I expect for it to be changed significantly.
I'm aware of it. I have proposed on the std-proposal ML to turn the dynamic polymorphism on a static polymorphism, but I have not received any comments from the authors. IMO, the time scheduled operations are orthogonal to the executor and so I propose to have an adaptor that adds these operations to any model of Executor.
FYI Vicente some time ago I wrote to the relevant team at Microsoft behind the "Improvements to std::future<>" paper giving my support for your idea. You should also be aware that my next work item for AFIO is to add metaprogramming to enable a .then(callable) way of specifying completions to operations in the same style as futures or any other async object. I intend this to be a stop gap temporary implementation to tide me over until your fully featured implementaton for Boost.Thread is under way. Niall --- Boost C++ Libraries Google Summer of Code 2014 admin https://svn.boost.org/trac/boost/wiki/SoC2014
Boost.Thread / Work-Stealing-Thread-Pool: This is something already implemented as part of HPX (https://github.com/STEllAR-GROUP/hpx), we have several work-stealing implementations, FWIW. Feel free to use.
Again thanks. The intent is to have this in Boost.
Would HPX's implementation be easily portable to Boost do you think?
There are many things in HPX which could be extracted to be part of Boost. All of it is Boost licensed and very much aligned with Boost coding style and quality requirements. Thus I wouldn't see any formal problems. Things which come to mind (in no particular order) are: - Fully move-enabled and serializable implementations of tuple, any, bind, protect, function - Highly efficient binary portable serialization archives (including array and zero copy optimizations) - Small utilities such as invoke, void_guard, deferred_call, one_shot_bind, high_resolution_timer, decay, etc. - Adaptation of other proposed Boost code like a portable stack-backtrace, a plugin library, a generic cache library, etc. - A (user level) thread scheduling subsystem allowing to mix and match different policies, like different work-stealing mechanisms (or none at all), lifo/fifo queues, flat/hierarchical schedulers, etc. At the same time, the parts of HPX have been developed together and might be interlined and it might not be trivial (albeit not impossible) to rip out only part of it without pulling in half of other things. Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu
On 2/7/2014 9:15 PM, Niall Douglas wrote:
Therefore, if you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list at https://svn.boost.org/trac/boost/wiki/SoC2014.
If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost@lists.boost.org. Thank you in advance for your time.
I'm interested in mentoring students with C++ work. I'm not sure what I'm supposed to do based on your announcement: I'm not proposing a new project/idea, and I'm not sure if we are invited to add our names to the "could be mentored by" on existing descriptions, or what.
Le 08/02/14 22:27, John M. Dlugosz a écrit :
On 2/7/2014 9:15 PM, Niall Douglas wrote:
Therefore, if you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list at https://svn.boost.org/trac/boost/wiki/SoC2014.
If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost@lists.boost.org. Thank you in advance for your time.
I'm interested in mentoring students with C++ work. I'm not sure what I'm supposed to do based on your announcement: I'm not proposing a new project/idea, and I'm not sure if we are invited to add our names to the "could be mentored by" on existing descriptions, or what.
Hi, of course. I couldn't mentor all the projects I added to the projects ideas. The could is the more associated to this constraint. These are projects that I want to see in Boost as libraries or part of libraries.. If a student helps to achieve a part, this is great. If a mentor (you for example) is interested on some of the projects please add your name. Best, Vicente
On 8 Feb 2014 at 15:27, John M. Dlugosz wrote:
I'm interested in mentoring students with C++ work. I'm not sure what I'm supposed to do based on your announcement: I'm not proposing a new project/idea, and I'm not sure if we are invited to add our names to the "could be mentored by" on existing descriptions, or what.
If you have nothing specific in mind, please do feel absolutely free to add yourself to "could be mentored by" where you feel yourself competent. And thanks for volunteering! Niall --- Boost C++ Libraries Google Summer of Code 2014 admin https://svn.boost.org/trac/boost/wiki/SoC2014
On 8 February 2014 04:15, Niall Douglas
Dear Boost community,
<snip>
If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost@lists.boost.org. Thank you in advance for your time.
Niall Douglas (Boost Google Summer of Code admin) Boris Schäling (Boost Google Summer of Code backup admin)
As a previous GSoC student I'd be more than happy to mentor a project, consider me ready and willing. I'll have a look over the proposed projects tomorrow and add to them where possible. Jeroen Habraken
participants (8)
-
Christopher Kormanyos -
Hartmut Kaiser -
Jeroen Habraken -
John M. Dlugosz -
Niall Douglas -
Stefan Seefeld -
Utsav Tiwary -
Vicente J. Botet Escriba