-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add content about GSoC (google summer of code) #30
Comments
Who would they work for, though? Is there a central OCaml project that can act as to GSoC sponsor? |
Yeah you really don't need much. Just having them work for the OCaml organization is good enough. I've done this in the past with a different open source organization. The only things you need are:
The intern gets paid for the summer by Google, and hopefully contributes something worthwhile to the community. |
I'm still quite fuzzy on what the OCaml organization actually is. 😃 |
The OCaml github organization: https://github.com/ocaml |
A github organization isn't the same as a formal group of people. |
I don't think there's any more than that. There's no legal entity here AFAIK, since which country's laws would it be under? |
Oh also, to check that a participant is serious, organizations usually require something first. The participant needs to propose something good, but they also need to contribute to the organization in some minor way e.g. fixing a bug or something. |
Out of curiosity, is there any progress on this one? |
One of the very big things OCaml is constantly missing out on is google summer of code participants. In order to get the ball rolling, we need a place to organize a list of projects or ideas that could be contributed to. We also need to have a template ready for our GSoC application.
There was some work done in the past on the ocaml.org wiki. It should be imported and embellished.
The part about ideas for projects could also be generalized -- it doesn't just need to be for GSoC.
The text was updated successfully, but these errors were encountered: