git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GSoC 2016: applications open, deadline = Fri, 19/2

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Feb 13, 2016, 11:21 UTC
Message-ID
<vpqd1s04zzs.fsf@anie.imag.fr>
In-Reply-To
<20160212130446.GB10858@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 11 quoted lines
> On Fri, Feb 12, 2016 at 08:10:34AM +0100, Matthieu Moy wrote:
>
>> So, that makes it 4 possible co-mentors, i.e. 2 potential slots. Not
>> much, but it starts looking like last year ... ;-).
>> 
>> Peff, would you be willing to co-admin with me (that would be cool, you
>> are the one with most experience here and you know the SFC stuff for
>> payment)? Are there any other co-admin volunteer?
>
> Yes, I'm willing to co-admin (though I'm also happy to step aside for
> somebody else if they would like to do it).
Cool!
Show 25 quoted lines
> The biggest task there is getting the application together. I went
> through the account creation steps at the site (which is different this
> year), and the application questions are:
>
>  - Why does your org want to participate in Google Summer of Code?
>
>  - How many potential mentors have agreed to mentor this year?
>
>  - How will you keep mentors engaged with their students?
>
>  - How will you help your students stay on schedule to complete their projects?
>
>  - How will you get your students involved in your community during GSoC?
>
>  - How will you keep students involved with your community after GSoC?
>
>  - Has your org been accepted as a mentoring org in Google Summer of Code before?
>
>  - Are you part of a foundation/umbrella organization?
>
>  - What year was your project started? 
>
> I think we can pull most of these answers from previous-year
> applications, but I haven't looked yet. In years past we collaborated
> on the answers via the git.github.io site, and I pasted them in place.
I started working on it.

http://git.github.io/SoC-2015-Org-Application/ => the application itself. Mostly cut-and-paste from last year, but the questions have changed a bit. There's a "Remarks on the current state of the application" section at the end for stuff I wasn't sure about.

This is the urgent part, we won't have an opportunity to modify it after the deadline.

Less urgent, but we need to add more stuff to be credible:

http://git.github.io/SoC-2016-Ideas/ => Ideas page. I removed the completed project, and updated some other to reflect the current state of Git. I think "Convert scripts to builtins" is still feasible this year, but probably harder (we can't say "start with git-pull.sh" anymore ...). Johannes: you're still interested I guess?

http://git.github.io/SoC-2016-Microprojects/ => I just did s/2015/2016/. I think most projects are not valid anymore, and we need new ones.

To all: please contribute to these pages, either by sending patches here (CC: me and peff), pushing directly if you have access, or submitting pull-requests. The repo is https://github.com/git/git.github.io/.

Thanks,
-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Jeff KingNext: Stefan Beller
Message 10 of 67 in “GSoC 2016: applications open, deadline = Fri, 19/2”
  1. Matthieu MoyFeb 10, 2016
  2. Johannes SchindelinFeb 10, 2016
  3. Stefan BellerFeb 10, 2016
  4. Christian CouderFeb 11, 2016
  5. Matthieu MoyFeb 12, 2016
  6. Lars SchneiderFeb 12, 2016
  7. Matthieu MoyFeb 12, 2016
  8. Jeff KingFeb 12, 2016
  9. Jeff KingFeb 12, 2016
  10. Matthieu MoyFeb 13, 2016
  11. Stefan BellerFeb 16, 2016
  12. Matthieu MoyFeb 17, 2016
  13. Duy NguyenFeb 17, 2016
  14. 0/3 Turn git-rebase--*.sh to external helpersNguyễn Thái Ngọc Duy, Feb 17, 2016
  15. 1/3 rebase: move common functions to rebase--lib.shNguyễn Thái Ngọc Duy, Feb 17, 2016
  16. 2/3 rebase: move cleanup code to exit_rebase()Nguyễn Thái Ngọc Duy, Feb 17, 2016
  17. Matthieu MoyFeb 17, 2016
  18. 3/3 rebase: turn git-rebase--*.sh into separate programsNguyễn Thái Ngọc Duy, Feb 17, 2016
  19. Matthieu MoyFeb 17, 2016
  20. Johannes SchindelinFeb 17, 2016
  21. Duy NguyenFeb 17, 2016
  22. Johannes SchindelinFeb 17, 2016
  23. Christian CouderFeb 17, 2016
  24. Duy NguyenFeb 22, 2016
  25. Matthieu MoyFeb 22, 2016
  26. Jeff KingFeb 22, 2016
  27. Junio C HamanoFeb 22, 2016
  28. Jeff KingFeb 22, 2016
  29. Matthieu MoyFeb 23, 2016
  30. Jeff KingFeb 24, 2016
  31. Thomas GummererFeb 17, 2016
  32. Lars SchneiderFeb 17, 2016
  33. Matthieu MoyFeb 17, 2016
  34. Junio C HamanoFeb 17, 2016
  35. Matthieu MoyFeb 17, 2016
  36. Jeff KingFeb 17, 2016
  37. Junio C HamanoFeb 17, 2016
  38. Carlos Martín NietoFeb 18, 2016
  39. Matthieu MoyFeb 19, 2016
  40. Carlos Martín NietoFeb 19, 2016
  41. Git has been accepted as a GSoC 2016 mentor organization!Matthieu Moy, Feb 29, 2016
  42. Jeff KingMar 8, 2016
  43. Junio C HamanoMar 8, 2016
  44. Jeff KingMar 8, 2016
  45. Matthieu MoyMar 9, 2016
  46. Jeff KingMar 9, 2016
  47. Johannes SchindelinMar 9, 2016
  48. Jeff KingMar 9, 2016
  49. Matthieu MoyFeb 19, 2016
  50. Jeff KingFeb 19, 2016
  51. Matthieu MoyFeb 19, 2016
  52. Jeff KingFeb 19, 2016
  53. Lars SchneiderFeb 18, 2016
  54. Stefan BellerFeb 18, 2016
  55. Junio C HamanoFeb 18, 2016
  56. Matthieu MoyFeb 19, 2016
  57. Junio C HamanoFeb 19, 2016
  58. Johannes SchindelinFeb 20, 2016
  59. Lars SchneiderFeb 19, 2016
  60. Matthieu MoyFeb 19, 2016
  61. Junio C HamanoFeb 19, 2016
  62. Thomas GummererFeb 19, 2016
  63. Duy NguyenFeb 19, 2016
  64. Junio C HamanoFeb 19, 2016
  65. Duy NguyenFeb 19, 2016
  66. Matthieu MoyFeb 19, 2016
  67. Duy NguyenFeb 19, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.