
Hi, My name is Sumol. I'm a 3rd year Computer Science student. I am new to Open Source Development and want to explore and experience it. I am interested to work for Boost in GSoC 2014. Seeing last year GSoC projects of BOOST I would be really interested in working projects related to maths and computing. Any pointers on how should I go about it ? Thanks, Sumol

First off, you need to wait for the project announcement and the application period. But watch out, as it really does come up pretty early, and it goes by really fast, such as March or April. In general it helps to identify a project early in the application phase and try to write the best application you can. It is beneficial to discuss the project, your application and some trivial technical details on the board. For project specifics, it is better to engage in private e-mails with the potential mentor(s). Almost all successful candidates have represented themselves well on the board and also communicated the project details in depth with the project mentor(s). We had a good GSoC 2013, and I expect nothing less from GSoC 2014. So good luck next year.
Sincerely, Chris.
From: Sumol Lodha

Well, you need to wait for the project announcement to start officially working. But until then you can take a look around: take a glance at the ideas for GSOC2013 https://svn.boost.org/trac/boost/wiki/SoC2013 and previous GSOCs, came up with your own ideas, ask around for a mentor interested in your idea/project. This year we had much more interested students, than the GSOC organizers could fund. Only 10 students were accepted. Finding mentors/people interested in your idea at the very early stage will give you a huge bonus. -- Best regards, Antony Polukhin

Hi, On Wednesday, October 16, 2013 01:45:08 AM Sumol Lodha wrote:
Hi, My name is Sumol. I'm a 3rd year Computer Science student. I am new to Open Source Development and want to explore and experience it. I am interested to work for Boost in GSoC 2014. Seeing last year GSoC projects of BOOST I would be really interested in working projects related to maths and computing. Any pointers on how should I go about it ?
I'd say the best strategy is to get already involved with a bost library that you find particularly interesting. Play around, maybe find a bug, provide a patch, get involved with the authors. With such insights (and connections) you will have a clear advantage writing a GSoC proposal next year. Best, Mario
Thanks, Sumol
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

@Christopher, Antony and Mario Thanks for your replies :) @Christopher First off, you need to wait for the project announcement and the application period. -> Before project announcement and application period, I am interested in exploring the projects in advance. Also as I am newbie to "open source" it will take time for me to get acquainted with git, irc etc and how to use and get acquainted with boost style of c++ coding. So any help in advance before GSoC would be greatly appreciated. Any material(links,books etc) that I should know would be helpful. Also given any task, I would be happy to solve them and I would be able to ask doubts to the community while solving them. @Antony But until then you can take a look around: take a glance at the ideas for GSOC2013 https://svn.boost.org/trac/boost/wiki/SoC2013 and previous GSOCs, came up with your own ideas, ask around for a mentor interested in your idea/project. -> I glanced at the ideas given in the link and after seeing their description I am interested in Math and Algorithms topics. Can you give me more insights on how to come up with our own idea(on existing projects, like report bug etc) and work upon it. As I am total newbie to open source, any suggestions keeping that in view would be helpful. If I know how all the process runs, I could suggest an idea. @Mario Play around, maybe find a bug, provide a patch, get involved with the authors -> As I new to open source, can you give me more insights on 1.how to play around the code? 2.if found some bug how to report it ? 3.How to write a patch and how to submit it ? Any links or material would be helpful. Thanks
participants (4)
-
Antony Polukhin
-
Christopher Kormanyos
-
Mario Mulansky
-
Sumol Lodha