Hi all,

Google Summer of Code (GSoC) 2018 is about to start soon [1] (the application period for organizations is in January 2018).
Hence, I would very happy about any project ideas you have or projects which are important to you.
And, of course, if you would be willing to mentor a student, please don't forget to tell me.
You can always reach me via mail (seb [at] wilzba [dot] ch) or on Slack (dlang.slack.com). There's also a special #gsoc channel.

I have also started to work over the ideas from last year [2], but this page is currently WIP.

@Students: if you have any questions or maybe have an idea for a project yourself, please feel free to contact me. I'm more than happy to help!

I am looking forward to hearing (1) what you think can be done in three months by a student and (2) will have a huge impact on the D ecosystem.

Cheers,

Seb

[1] https://developers.google.com/open-source/gsoc/timeline
[2] https://wiki.dlang.org/GSOC_2018_Ideas

On Tuesday, 5 December 2017 at 18:20:40 UTC, Seb wrote:
> I am looking forward to hearing (1) what you think can be done in three months by a student and (2) will have a huge impact on the D ecosystem.
>
> [2] https://wiki.dlang.org/GSOC_2018_Ideas

I see there is a dub section in [2]. Maybe another issue that has been brought up repeatedly fits in that category, namely extending code.dlang.org in various ways?

On Thursday, 7 December 2017 at 22:26:08 UTC, Bastiaan Veelo wrote:
>
> I see there is a dub section in [2]. Maybe another issue that has been brought up repeatedly fits in that category, namely extending code.dlang.org in various ways?

I had thought I had followed one of the links somewhere and it mentioned it, but it probably should be listed on that GSOC page.

It might be worthwhile to add some more structure to this page. Right now the outline is grouped broadly by project. It might be a little clearer to group the different projects by category (e.g. compiler, phobos [already there], tooling, library).

Also, it might be useful to add some information on expected difficulty or time intensiveness. I recall from the last time some of the students maybe bit off more than they could chew (i.e., there's no reason taking std.experimental.xml to the finish line or work on a precise garbage collector couldn't be GSOC projects for 2018). For instance, I imagine improvements to code.dlang.org require less knowledge than Lowerer.

Something I would add:
Jupyter kernel (could depend on either d-repl or dabble, not sure which is better)

On 12/5/17 10:20, Seb wrote:
> Hi all,
>
> Google Summer of Code (GSoC) 2018 is about to start soon [1] (the
> application period for organizations is in January 2018).
> Hence, I would very happy about any project ideas you have or projects
> which are important to you.
> And, of course, if you would be willing to mentor a student, please
> don't forget to tell me.
> You can always reach me via mail (seb [at] wilzba [dot] ch) or on Slack
> (dlang.slack.com). There's also a special #gsoc channel.
>
> I have also started to work over the ideas from last year [2], but this
> page is currently WIP.
>
> @Students: if you have any questions or maybe have an idea for a project
> yourself, please feel free to contact me. I'm more than happy to help!
>
> I am looking forward to hearing (1) what you think can be done in three
> months by a student and (2) will have a huge impact on the D ecosystem.
>
> Cheers,
>
> Seb
>
> [1] https://developers.google.com/open-source/gsoc/timeline
> [2] https://wiki.dlang.org/GSOC_2018_Ideas
>

I am absolutely up for mentoring this year and there are some fantastic projects on this list. The ones I'd be willing to mentor are:

std.database - I've done a significant amount of work on this (not on github yet). And I have almost two decades of experience with various SQL interface libraries. I've seen the good, the bad, and the ugly, and would be able to work very closely with the student. :)

std.eventloop - This will be needed if I am ever going to get Async/Await off the ground.

std.decimal - I need this for some personal projects.

Garbage Collector - It's not on the list but somebody mentioned it. There are actually two PR's outstanding for a precise GC from the 2016 GSoC I mentored; here: https://github.com/dlang/druntime/pull/1603 and here: https://github.com/dlang/druntime/pull/1977. But there is still a ton of room for improvement. There are more areas that precision could be expanded too. The 2016 student started playing around with a type-based pooling collector. There are a number of ideas we could explore. Note that I'm not a big fan of the fork()-based GC idea since it's limited to *nix based systems

-- 
Adam Wilson
IRC: LightBender
import quiet.dlang.dev;

On Thursday, 7 December 2017 at 22:26:08 UTC, Bastiaan Veelo wrote:
> On Tuesday, 5 December 2017 at 18:20:40 UTC, Seb wrote:
>> I am looking forward to hearing (1) what you think can be done in three months by a student and (2) will have a huge impact on the D ecosystem.
>>
>> [2] https://wiki.dlang.org/GSOC_2018_Ideas
>
> I see there is a dub section in [2]. Maybe another issue that has been brought up repeatedly fits in that category, namely extending code.dlang.org in various ways?

+1111

Indeed enhancing user experience of code.dlang.org such as showing github stars and e.g. downloads per month would be way more important then build tool itself.

On Friday, 8 December 2017 at 00:28:11 UTC, Adam Wilson wrote:
> The 2016 student started playing around with a type-based pooling collector.

I actually ran with this idea and wrote a garbage collector from scratch for an independent study at my university. I haven't made much noise about it since I didn't have time to get it to pass all tests, but it had performance about on par with the current GC and it has a precise heap like in the open PR's.

I'm going to continue working on it in the spring, so who knows what'll happen? I would submit a proposal to continue working on it during the summer, but I don't think I can participate in another GSoC (I graduate as the summer starts).

On Tuesday, 5 December 2017 at 18:20:40 UTC, Seb wrote:
> Hi all,
>
> Google Summer of Code (GSoC) 2018 is about to start soon [1] (the application period for organizations is in January 2018).
> Hence, I would very happy about any project ideas you have or projects which are important to you.
> And, of course, if you would be willing to mentor a student, please don't forget to tell me.
> You can always reach me via mail (seb [at] wilzba [dot] ch) or on Slack (dlang.slack.com). There's also a special #gsoc channel.
>
> [...]

do i have to be an actual student in order to participate?

On Sunday, 10 December 2017 at 13:01:43 UTC, Mengu wrote:
> On Tuesday, 5 December 2017 at 18:20:40 UTC, Seb wrote:
>> Hi all,
>>
>> Google Summer of Code (GSoC) 2018 is about to start soon [1] (the application period for organizations is in January 2018).
>> Hence, I would very happy about any project ideas you have or projects which are important to you.
>> And, of course, if you would be willing to mentor a student, please don't forget to tell me.
>> You can always reach me via mail (seb [at] wilzba [dot] ch) or on Slack (dlang.slack.com). There's also a special #gsoc channel.
>>
>> [...]
>
> do i have to be an actual student in order to participate?

I redirect your question to Google's official FAQ: https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation

I hope this answers your question.

On Sunday, 10 December 2017 at 19:04:54 UTC, Seb wrote:
> On Sunday, 10 December 2017 at 13:01:43 UTC, Mengu wrote:
>> On Tuesday, 5 December 2017 at 18:20:40 UTC, Seb wrote:
>>> [...]
>>
>> do i have to be an actual student in order to participate?
>
> I redirect your question to Google's official FAQ: https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation
>
> I hope this answers your question.

indeed it did, thanks.

On Tuesday, 5 December 2017 at 18:20:40 UTC, Seb wrote:
> Hi all,
>
> Google Summer of Code (GSoC) 2018 is about to start soon [1] (the application period for organizations is in January 2018).
> Hence, I would very happy about any project ideas you have or projects which are important to you.
> And, of course, if you would be willing to mentor a student, please don't forget to tell me.
> You can always reach me via mail (seb [at] wilzba [dot] ch) or on Slack (dlang.slack.com). There's also a special #gsoc channel.
>
> [...]

working, unrestricted DLL's for windows