Hi all, I was thinking about putting in a few project ideas for yt with either the OpenAstronomy or NumFOCUS google summer of code orgs. Would anyone else be interested in mentoring a google summer of code student this summer? To do so you will need to come up with a project idea in the following format: a) a project title b) more detailed description of the project (2-5 sentences) c) expected outcomes d) skills required/preferred e) possible mentors. And if possible, an easy, medium or hard rating of each project. (from the google summer of code mentor's guide <https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list>, which includes a number of other suggestions for appropriately scoping a summer of code project idea) The due date for summer of code orgs is January 26th. Ideally I'd like to contact the org we're working with a few weeks before that. In the past we've had trouble attracting students so we need to be careful to appropriately scope projects while still making them seem interesting. We should also decide which org to work with. We went with OpenAstronomy in the past but I think it makes sense to associate with NumFOCUS this year given our efforts to expose yt to fields outside of astrophysics. -Nathan
Hi Nathan, Thanks for putting this together. Some of the other orgs compile ideas on a wiki or a GH repo -- do you think that'd work for us? If not, where should we brainstorm? I would also suggest going with NumFOCUS, but both are good options. -Matt On Mon, Jan 8, 2018 at 9:57 AM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Hi all,
I was thinking about putting in a few project ideas for yt with either the OpenAstronomy or NumFOCUS google summer of code orgs.
Would anyone else be interested in mentoring a google summer of code student this summer? To do so you will need to come up with a project idea in the following format:
a) a project title b) more detailed description of the project (2-5 sentences) c) expected outcomes d) skills required/preferred e) possible mentors. And if possible, an easy, medium or hard rating of each project.
(from the google summer of code mentor's guide <https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list>, which includes a number of other suggestions for appropriately scoping a summer of code project idea)
The due date for summer of code orgs is January 26th. Ideally I'd like to contact the org we're working with a few weeks before that.
In the past we've had trouble attracting students so we need to be careful to appropriately scope projects while still making them seem interesting.
We should also decide which org to work with. We went with OpenAstronomy in the past but I think it makes sense to associate with NumFOCUS this year given our efforts to expose yt to fields outside of astrophysics.
-Nathan
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Good idea. I've gone ahead and created a repo: https://github.com/yt-project/gsoc-2018 If anyone would like to add a project please open a pull request and add an idea following the template. I've contacted NumFOCUS to see what we need to do to get included into their org application. On Tue, Jan 9, 2018 at 2:19 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Nathan,
Thanks for putting this together. Some of the other orgs compile ideas on a wiki or a GH repo -- do you think that'd work for us? If not, where should we brainstorm?
I would also suggest going with NumFOCUS, but both are good options.
-Matt
On Mon, Jan 8, 2018 at 9:57 AM, Nathan Goldbaum <nathan12343@gmail.com> wrote:
Hi all,
I was thinking about putting in a few project ideas for yt with either the OpenAstronomy or NumFOCUS google summer of code orgs.
Would anyone else be interested in mentoring a google summer of code student this summer? To do so you will need to come up with a project idea in the following format:
a) a project title b) more detailed description of the project (2-5 sentences) c) expected outcomes d) skills required/preferred e) possible mentors. And if possible, an easy, medium or hard rating of each project.
(from the google summer of code mentor's guide <https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list>, which includes a number of other suggestions for appropriately scoping a summer of code project idea)
The due date for summer of code orgs is January 26th. Ideally I'd like to contact the org we're working with a few weeks before that.
In the past we've had trouble attracting students so we need to be careful to appropriately scope projects while still making them seem interesting.
We should also decide which org to work with. We went with OpenAstronomy in the past but I think it makes sense to associate with NumFOCUS this year given our efforts to expose yt to fields outside of astrophysics.
-Nathan
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (2)
-
Matthew Turk -
Nathan Goldbaum