# Google Summer of Code 2021

**URL:** <https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691>\
**Category:** Request Feedback\
**Created:** [January 3, 2021, 10:54am UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691 "2021-01-03T10:54:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![razze](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/razze/32/1650_2.png) [@razze](https://discourse.elm-lang.org/u/razze)\
**Post date:** [January 3, 2021, 10:54am UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/1 "2021-01-03T10:54:53Z")

</div>

Hey everybody,

google summer of code (GSOC) 2021 is comming up, they changed the format a bit, to smaller projects, but that shouldn’t be a problem.

**What is GSOC?**  
Basically students pitch projects to open source orgas that take part and if they get choosen they can work on that over the summer and get paid by google.

> **[Google Summer of Code](https://summerofcode.withgoogle.com/how-it-works/#timeline)**

**Here’s what I’m proposing:**  
I would like to take part in gsoc this year under the umbrella of `elm-tooling` and focus on stuff outside of the compiler. Evan made it very clear, that he thinks it’s to much work for him with too little return. That’s fine, but I think we can still do it for other parts of the eco system.

**What do we need?**  
I need help, both organizing it and mentoring it.  
Organization can be as simple as keeping everybody in the loop or handling some paperwork.  
Mentoring basically means to talk with a (your) student on a regular basis. It depends on the student, but usually it’s a few minutes a day and maybe three hours a week.  
If your interested, please let me know either here or in slack (maybe we should get a channel there)

**We also need projects:**  
We need to generate some ideas, what we could have a student work on (they can still pitch whatever they want, but just a few do). So I’ve created a git repo with a template, please feel free to add some projects you like to see or even just add an issue to discuss it.

> <https://github.com/elm-tooling/gsoc-projects/blob/master/readme.md>

If there are any questions left, feel free to reach out.

---

<div class="post-metadata">

**Author:** ![jfmengels](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/jfmengels/32/3124_2.png) [@jfmengels](https://discourse.elm-lang.org/u/jfmengels)\
**Post date:** [January 13, 2021, 10:17am UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/2 "2021-01-13T10:17:49Z")

</div>

I’m not great at organizing things nor with paperwork, but I would definitely be interested in having someone work on `elm-review`.

I’ll try and come up with ideas. Do you know whether we should ideally come up with a single large task for the ten weeks or if multiple smaller projects is fine? 🤔

Also, for `elm-review` to be a part of this, would it need to be moved to under `elm-tooling` or is GSOC not that regarding?

---

<div class="post-metadata">

**Author:** ![razze](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/razze/32/1650_2.png) [@razze](https://discourse.elm-lang.org/u/razze)\
**Post date:** [January 13, 2021, 3:37pm UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/3 "2021-01-13T15:37:05Z")

</div>

> [@jfmengels](#):
>
> I’ll try and come up with ideas. Do you know whether we should ideally come up with a single large task for the ten weeks or if multiple smaller projects is fine?

Multiple should be fine, as long as they have a common direction (common headline). I think you will struggle a bit more in finding a student for that, but I might be wrong. One thing gsoc is strict on, is that it should be features, not cleanup behind you or bugfix for you 🙂

> [@jfmengels](#):
>
> Also, for `elm-review` to be a part of this, would it need to be moved to under `elm-tooling` or is GSOC not that regarding?

No, GSOC doesn’t care afaik. Just say `elm-tooling` is the umbrella organization in this case. One thing google expects, is that whatever get’s worked on is available somewhere when it’s done, it doesn’t even have to be git (but I would recommend git)

---

<div class="post-metadata">

**Author:** ![georgesboris](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/georgesboris/32/3598_2.png) [@georgesboris](https://discourse.elm-lang.org/u/georgesboris)\
**Post date:** [January 14, 2021, 11:12am UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/4 "2021-01-14T11:12:24Z")

</div>

While reading this [Elm | Voters | Repl.it](https://replit.canny.io/languages-requests/p/elm-1) I’ve seen it was mentioned that if Elm had C-bindings it would be easier to integrate with prybar (making it available on repl.it). I don’t know if having C-bindings would also enable other things to happen. I don’t know if this is feaseable or interesting but thought it would be useful to add to the pile of ideas here.

---

<div class="post-metadata">

**Author:** ![razze](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/razze/32/1650_2.png) [@razze](https://discourse.elm-lang.org/u/razze)\
**Post date:** [January 14, 2021, 12:00pm UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/5 "2021-01-14T12:00:53Z")

</div>

I think doing that in a sane way, would need a repl api / c-bindings. Those would both be compiler changes, which are not a part of this proposal (see above “Here’s what I’m proposing:”).

---

<div class="post-metadata">

**Author:** ![galanggg](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/galanggg/32/3696_2.png) [@galanggg](https://discourse.elm-lang.org/u/galanggg)\
**Post date:** [January 20, 2021, 8:32am UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/6 "2021-01-20T08:32:59Z")

</div>

Hi, I just saw the project ideas on github. Does each project have an explanation of the level of difficulty?

---

<div class="post-metadata">

**Author:** ![razze](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/razze/32/1650_2.png) [@razze](https://discourse.elm-lang.org/u/razze)\
**Post date:** [January 20, 2021, 11:27am UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/7 "2021-01-20T11:27:33Z")

</div>

No, not yet but it’s usually what we do. I just forgot about that when I created the template I think. Good catch.

---

<div class="post-metadata">

**Author:** ![razze](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/razze/32/1650_2.png) [@razze](https://discourse.elm-lang.org/u/razze)\
**Post date:** [January 26, 2021, 10:41am UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/8 "2021-01-26T10:41:31Z")

</div>

I also think doing elm packages that the community is missing would be a possible project. As long as the scope is roughly a month of work. It’s a bit surprising given the org name, so I wanted to mention it.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/elm_lang/original/1X/50a05e53677a2c3b47776d7abd0f113eb50193a1.png) [@system](https://discourse.elm-lang.org/u/system)\
**Post date:** [February 5, 2021, 10:41am UTC](https://discourse.elm-lang.org/t/google-summer-of-code-2021/6691/9 "2021-02-05T10:41:57Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.