On Saturday, April 20, 2013 07:16:08 PM Vicente J. Botet Escriba wrote:

Le 20/04/13 18:54, Mario Mulansky a écrit :

...

On Saturday, April 20, 2013 06:43:58 PM Vicente J. Botet Escriba wrote:

...

Hi,

would all the GSoC projects be stored under SVN?

well i hope, and don't think, this is mandatory?

odeint is developed in github, and a possible gsoc project would most likely be developed in a branch or a forked repository.

I understand your concern if you are developing already on Git and the possible gsoc project needs to be developen with the same SCM.

But, what about gsoc projects that are new or based on sources included in SVN? Could the student use a different SCM?

I think this is up to the mentor in the end. Google surely doesn't care. What should keep mentor/student agreeing on whatever they want? Best, Mario

Note that I'm not requesting nothing to be mandatory, just I want to know.

Best, Vicente

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Le 20/04/13 20:24, Daniel James a écrit :

On 20 April 2013 18:32, Mario Mulansky wrote:

...

On Saturday, April 20, 2013 07:16:08 PM Vicente J. Botet Escriba wrote:

...

But, what about gsoc projects that are new or based on sources included in SVN? Could the student use a different SCM? I think this is up to the mentor in the end. Google surely doesn't care. What should keep mentor/student agreeing on whatever they want? I think Vicente wants to know if we care, not google. The boost subversion repo is problematic because it's going to be made read-only at some point in the future, so I'd suggest using git, unless there are strong feelings otherwise. I'd also suggest setting up somewhere to store all the GSOC projects (perhaps a github organisation).

Thanks Daniel, this was the kind of informations I was looking for. Vicente