www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Google Summer of Code 2016

reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
The deadline for the Google Summer of Code, 2016 is February 
19th. Which means we have about a month and a half to put 
something together.  For the time being I've recycled last years 
projects (with one dropped so far):

http://wiki.dlang.org/GSOC_2016_Ideas#Ideas

Since we were rejected with, more or less, the same set of 
proposals last year it seems unlikely we would succeed this year 
with the same lineup.  So some new ideas (or some refreshing of 
the existing ideas) would be helpful.

Also if you see a project with yourself proposed as mentor, and 
you can no longer participate, then please let me know so I can 
remove your  project from the existing list.

If you are interested in mentoring a project, in addition to 
adding the project idea to the ideas page, you should add 
yourself to the mentors list at:

http://wiki.dlang.org/GSOC_mentors

If you have and idea for a new project it would be worthwhile to 
post it here so the community has the opportunity for input 
before it gets added to the ideas page.

Happy New Year to everyone.

Craig
Dec 31 2015
next sibling parent reply CraigDillabaugh <craig.dillabaugh gmail.com> writes:
On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh 
wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas

 Since we were rejected with, more or less, the same set of 
 proposals last year it seems unlikely we would succeed this 
 year with the same lineup.  So some new ideas (or some 
 refreshing of the existing ideas) would be helpful.


clip


 Happy New Year to everyone.

 Craig


Just bumping my own thread here.

Is there any interest is doing a GSOC application this year 
within the community? I don't mind doing the admin work, but 
having even a couple of solid new ideas for projects would 
improve the odds of a successful application.
Jan 04 2016
parent reply Laeeth Isharc <laeethnospam nospam.laeeth.com> writes:
On Monday, 4 January 2016 at 22:58:43 UTC, CraigDillabaugh wrote:

 On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh 
 wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas

 Since we were rejected with, more or less, the same set of 
 proposals last year it seems unlikely we would succeed this 
 year with the same lineup.  So some new ideas (or some 
 refreshing of the existing ideas) would be helpful.


 clip


 Happy New Year to everyone.

 Craig


 Just bumping my own thread here.

 Is there any interest is doing a GSOC application this year 
 within the community? I don't mind doing the admin work, but 
 having even a couple of solid new ideas for projects would 
 improve the odds of a successful application.


What do you think about the idea of building higher-level 
bindings for Apple mobile + Android as a project, now that the 
compiler itself is at a useful stage of development?
Jan 05 2016
next sibling parent CraigDillabaugh <craig.dillabaugh gmail.com> writes:
On Tuesday, 5 January 2016 at 22:28:40 UTC, Laeeth Isharc wrote:

 On Monday, 4 January 2016 at 22:58:43 UTC, CraigDillabaugh 
 wrote:

 On Thursday, 31 December 2015 at 23:58:32 UTC, Craig 
 Dillabaugh wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas




 What do you think about the idea of building higher-level 
 bindings for Apple mobile + Android as a project, now that the 
 compiler itself is at a useful stage of development?


I generally don't take a stand one way or the other on the 
projects, but rather let the community chime in, since in many 
cases (like this one) I am not terribly familiar with the problem 
space.

So any opinions on this project idea are welcomed.

Would you be willing to mentor such a project, or put together an 
outline (see the ideas page for some examples) of what the 
project would look like?  If the community likes the project 
idea, but you can't mentor it then perhaps we can find someone 
who would be.
Jan 05 2016
prev sibling next sibling parent reply Rikki Cattermole <alphaglosined gmail.com> writes:
On 06/01/16 11:28 AM, Laeeth Isharc wrote:

 On Monday, 4 January 2016 at 22:58:43 UTC, CraigDillabaugh wrote:

 On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh wrote:

 The deadline for the Google Summer of Code, 2016 is February 19th.
 Which means we have about a month and a half to put something
 together.  For the time being I've recycled last years projects (with
 one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas

 Since we were rejected with, more or less, the same set of proposals
 last year it seems unlikely we would succeed this year with the same
 lineup.  So some new ideas (or some refreshing of the existing ideas)
 would be helpful.


 clip


 Happy New Year to everyone.

 Craig


 Just bumping my own thread here.

 Is there any interest is doing a GSOC application this year within the
 community? I don't mind doing the admin work, but having even a couple
 of solid new ideas for projects would improve the odds of a successful
 application.


 What do you think about the idea of building higher-level bindings for
 Apple mobile + Android as a project, now that the compiler itself is at
 a useful stage of development?


For Android you really need an easy way to interface with JNI.
And that means another library.
There is a library that really isn't complete [0], is my fork.

I made the JNI bindings be derelict style.
If the demand is there I'll move them over to alphaPhobos with my 
updated DerelictUtil loader.

jvm.d is a bit cleaner and has comments.
It is also very magical in loading and will make things 'just work'.
I.e. it patches up stdout ext. on Windows.

I also did some serious clean up regarding to the abstractions around 
fields, classes and methods.

Craig Dillabaugh if you are interested in working on this with me, 
please let me know.

[0] https://github.com/rikkimax/djvm
Jan 05 2016
parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Wednesday, 6 January 2016 at 02:27:05 UTC, Rikki Cattermole 
wrote:

 On 06/01/16 11:28 AM, Laeeth Isharc wrote:

 On Monday, 4 January 2016 at 22:58:43 UTC, CraigDillabaugh




clip

 For Android you really need an easy way to interface with JNI.
 And that means another library.
 There is a library that really isn't complete [0], is my fork.

 I made the JNI bindings be derelict style.
 If the demand is there I'll move them over to alphaPhobos with 
 my updated DerelictUtil loader.

 jvm.d is a bit cleaner and has comments.
 It is also very magical in loading and will make things 'just 
 work'.
 I.e. it patches up stdout ext. on Windows.

 I also did some serious clean up regarding to the abstractions 
 around fields, classes and methods.

 Craig Dillabaugh if you are interested in working on this with 
 me, please let me know.

 [0] https://github.com/rikkimax/djvm


Do you mean me, or Laeeth Isharc?  The only Android/Apple device 
I have is a second hand iPhone that I've only ever used to take a 
few pictures and listen to the music left on it by the guy who 
gave it to me.  So I am likely not a good candidate to get 
involved in work on such bindings.  Heck, I don't even know what 
JNI is!
Jan 05 2016
parent Rikki Cattermole <alphaglosined gmail.com> writes:
On 06/01/16 3:56 PM, Craig Dillabaugh wrote:

 On Wednesday, 6 January 2016 at 02:27:05 UTC, Rikki Cattermole wrote:

 On 06/01/16 11:28 AM, Laeeth Isharc wrote:

 On Monday, 4 January 2016 at 22:58:43 UTC, CraigDillabaugh




 clip

 For Android you really need an easy way to interface with JNI.
 And that means another library.
 There is a library that really isn't complete [0], is my fork.

 I made the JNI bindings be derelict style.
 If the demand is there I'll move them over to alphaPhobos with my
 updated DerelictUtil loader.

 jvm.d is a bit cleaner and has comments.
 It is also very magical in loading and will make things 'just work'.
 I.e. it patches up stdout ext. on Windows.

 I also did some serious clean up regarding to the abstractions around
 fields, classes and methods.

 Craig Dillabaugh if you are interested in working on this with me,
 please let me know.

 [0] https://github.com/rikkimax/djvm


 Do you mean me, or Laeeth Isharc?  The only Android/Apple device I have
 is a second hand iPhone that I've only ever used to take a few pictures
 and listen to the music left on it by the guy who gave it to me.  So I
 am likely not a good candidate to get involved in work on such
 bindings.  Heck, I don't even know what JNI is!


Okay Laeeth then, I sometimes mix people up :p
Jan 05 2016
prev sibling parent reply Jacob Carlborg <doob me.com> writes:
On 2016-01-05 23:28, Laeeth Isharc wrote:


 What do you think about the idea of building higher-level bindings for
 Apple mobile + Android as a project, now that the compiler itself is at
 a useful stage of development?


D has only basic support for interfacing with Objective-C, there's more 
in the works.

-- 
/Jacob Carlborg
Jan 06 2016
parent reply CraigDillabaugh <craig.dillabaugh gmail.com> writes:
On Wednesday, 6 January 2016 at 13:28:56 UTC, Jacob Carlborg 
wrote:

 On 2016-01-05 23:28, Laeeth Isharc wrote:


 What do you think about the idea of building higher-level 
 bindings for
 Apple mobile + Android as a project, now that the compiler 
 itself is at
 a useful stage of development?


 D has only basic support for interfacing with Objective-C, 
 there's more in the works.


I assume, based on my limited knowledge, that this would likely
be two separate projects then:

- bindings for Android
- bindings for Apple Mobile

Would a GSOC project be helpful in moving the Objective-C work 
forward.
Jan 06 2016
parent Jacob Carlborg <doob me.com> writes:
On 2016-01-06 15:49, CraigDillabaugh wrote:


 Would a GSOC project be helpful in moving the Objective-C work forward.


I'm not sure if it's a good fit for a GSOC project. The implementation 
is basically done, it just needs to be upstreamed.

-- 
/Jacob Carlborg
Jan 06 2016
prev sibling next sibling parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh 
wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 [...]


Deadline is getting closer, any new project ideas are welcome. 
Starting to get some contact from students now.
Jan 14 2016
next sibling parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 01/14/2016 01:56 PM, Craig Dillabaugh wrote:

 Deadline is getting closer, any new project ideas are welcome. Starting
 to get some contact from students now.


A few quick ideas:

* Bringing a parser generator library into phobos, either based on 
pegged or independent

* SQL parser, binder, validator

* Anything building on the strengths on D: introspection, compile-time 
stuff, DSL, etc.

* Improving the GC

* Theoretical work - core language semantics, proving immutable provides 
guarantees etc.


Andrei
Jan 14 2016
next sibling parent Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu 
wrote:

 On 01/14/2016 01:56 PM, Craig Dillabaugh wrote:

 Deadline is getting closer, any new project ideas are welcome. 
 Starting
 to get some contact from students now.


 A few quick ideas:

 * Bringing a parser generator library into phobos, either based 
 on pegged or independent

 * SQL parser, binder, validator

 * Anything building on the strengths on D: introspection, 
 compile-time stuff, DSL, etc.

 * Improving the GC

 * Theoretical work - core language semantics, proving immutable 
 provides guarantees etc.


 Andrei


Thanks.
Jan 14 2016
prev sibling next sibling parent reply Marc =?UTF-8?B?U2Now7x0eg==?= <schuetzm gmx.net> writes:
On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu 
wrote:

 A few quick ideas:

 * Bringing a parser generator library into phobos, either based 
 on pegged or independent

 * SQL parser, binder, validator

 * Anything building on the strengths on D: introspection, 
 compile-time stuff, DSL, etc.

 * Improving the GC

 * Theoretical work - core language semantics, proving immutable 
 provides guarantees etc.


* A flexible serialization framework in Phobos. std.csv could be 
changed to use it, and vibe.d as well as various serialization 
related libraries (e.g. Protocol Buffers, capnproto) would also 
benefit from standardization here.
Jan 15 2016
parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:

 On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu 
 wrote:

 A few quick ideas:

 * Bringing a parser generator library into phobos, either 
 based on pegged or independent

 * SQL parser, binder, validator

 * Anything building on the strengths on D: introspection, 
 compile-time stuff, DSL, etc.

 * Improving the GC

 * Theoretical work - core language semantics, proving 
 immutable provides guarantees etc.


 * A flexible serialization framework in Phobos. std.csv could 
 be changed to use it, and vibe.d as well as various 
 serialization related libraries (e.g. Protocol Buffers, 
 capnproto) would also benefit from standardization here.


What about Orange?  What is preventing it from becoming part of 
Phobos?

https://github.com/jacob-carlborg/orange
Jan 15 2016
parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 1/15/16 6:58 AM, Craig Dillabaugh wrote:

 On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:

 On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu wrote:

 A few quick ideas:

 * Bringing a parser generator library into phobos, either based on
 pegged or independent

 * SQL parser, binder, validator

 * Anything building on the strengths on D: introspection,
 compile-time stuff, DSL, etc.

 * Improving the GC

 * Theoretical work - core language semantics, proving immutable
 provides guarantees etc.


 * A flexible serialization framework in Phobos. std.csv could be
 changed to use it, and vibe.d as well as various serialization related
 libraries (e.g. Protocol Buffers, capnproto) would also benefit from
 standardization here.


 What about Orange?  What is preventing it from becoming part of Phobos?

 https://github.com/jacob-carlborg/orange


I recall there has been one (or two?) unsuccessful attempts. -- Andrei
Jan 15 2016
next sibling parent reply Marc =?UTF-8?B?U2Now7x0eg==?= <schuetzm gmx.net> writes:
On Friday, 15 January 2016 at 12:36:32 UTC, Andrei Alexandrescu 
wrote:

 On 1/15/16 6:58 AM, Craig Dillabaugh wrote:

 On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:

 * A flexible serialization framework in Phobos. std.csv could 
 be
 changed to use it, and vibe.d as well as various 
 serialization related
 libraries (e.g. Protocol Buffers, capnproto) would also 
 benefit from
 standardization here.


 What about Orange?  What is preventing it from becoming part 
 of Phobos?

 https://github.com/jacob-carlborg/orange


 I recall there has been one (or two?) unsuccessful attempts. -- 
 Andrei


Right, but it needs someone to take another stab at it. Part of 
the job is to gather all the requirements and look at the 
previous discussions as well as existing solutions.
Jan 15 2016
parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 01/15/2016 08:11 AM, Marc Schütz wrote:

 On Friday, 15 January 2016 at 12:36:32 UTC, Andrei Alexandrescu wrote:

 On 1/15/16 6:58 AM, Craig Dillabaugh wrote:

 On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz wrote:

 * A flexible serialization framework in Phobos. std.csv could be
 changed to use it, and vibe.d as well as various serialization related
 libraries (e.g. Protocol Buffers, capnproto) would also benefit from
 standardization here.


 What about Orange?  What is preventing it from becoming part of Phobos?

 https://github.com/jacob-carlborg/orange


 I recall there has been one (or two?) unsuccessful attempts. -- Andrei


 Right, but it needs someone to take another stab at it. Part of the job
 is to gather all the requirements and look at the previous discussions
 as well as existing solutions.


It would be terrific if Jacob wanted to mentor a student to work on a 
Phobos package starting from Orange. -- Andrei
Jan 15 2016
parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Friday, 15 January 2016 at 13:43:07 UTC, Andrei Alexandrescu 
wrote:

 On 01/15/2016 08:11 AM, Marc Schütz wrote:

 On Friday, 15 January 2016 at 12:36:32 UTC, Andrei 
 Alexandrescu wrote:

 On 1/15/16 6:58 AM, Craig Dillabaugh wrote:

 On Friday, 15 January 2016 at 10:02:14 UTC, Marc Schütz 
 wrote:

 [...]


 What about Orange?  What is preventing it from becoming part 
 of Phobos?

 https://github.com/jacob-carlborg/orange


 I recall there has been one (or two?) unsuccessful attempts. 
 -- Andrei


 Right, but it needs someone to take another stab at it. Part 
 of the job
 is to gather all the requirements and look at the previous 
 discussions
 as well as existing solutions.


 It would be terrific if Jacob wanted to mentor a student to 
 work on a Phobos package starting from Orange. -- Andrei


Agreed ... Jacob?
Jan 15 2016
parent Jacob Carlborg <doob me.com> writes:
On 2016-01-15 14:56, Craig Dillabaugh wrote:


 Agreed ... Jacob?


I could help, but I have no interest in being an official mentor.

-- 
/Jacob Carlborg
Jan 15 2016
prev sibling parent reply Jacob Carlborg <doob me.com> writes:
On 2016-01-15 13:36, Andrei Alexandrescu wrote:


 I recall there has been one (or two?) unsuccessful attempts. -- Andrei


Yes, twice. It mainly needs to be rangified.

-- 
/Jacob Carlborg
Jan 15 2016
parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Friday, 15 January 2016 at 20:20:29 UTC, Jacob Carlborg wrote:

 On 2016-01-15 13:36, Andrei Alexandrescu wrote:


 I recall there has been one (or two?) unsuccessful attempts. 
 -- Andrei


 Yes, twice. It mainly needs to be rangified.


How much work do you think that would involve? Would it be enough 
to qualify as a project (I am guessing something in the range of 
150-300 hours of total work, including getting up to speed, 
design, implementation, testing, would be suitable).
Jan 15 2016
parent Jacob Carlborg <doob me.com> writes:
On 2016-01-15 23:25, Craig Dillabaugh wrote:


 How much work do you think that would involve? Would it be enough to
 qualify as a project (I am guessing something in the range of 150-300
 hours of total work, including getting up to speed, design,
 implementation, testing, would be suitable).


It's hard to say. It depends on how much time it takes to get up to 
speed. If the student already knows D it will be a lot quicker. But for 
me that's already working on this, I really hope it wouldn't take that 
long time.

I think it's a bigger chance that it's too small than too large. But if 
it's possible to be flexible we could add more archive types if the 
project turns out to be too small.

-- 
/Jacob Carlborg
Jan 16 2016
prev sibling parent Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Friday, 15 January 2016 at 03:33:23 UTC, Andrei Alexandrescu 
wrote:

 On 01/14/2016 01:56 PM, Craig Dillabaugh wrote:

 Deadline is getting closer, any new project ideas are welcome. 
 Starting
 to get some contact from students now.


 A few quick ideas:

 * Bringing a parser generator library into phobos, either based 
 on pegged or independent

 * SQL parser, binder, validator

 * Improving the GC

 clip

 Andrei


I wanted to follow up on a few of Andrei's ideas.

Is there any work ongoing on the GC, I know there has been lots 
of talk from time to time, but are there any concrete efforts out 
there that a student could start from?

Also I've seen lots of discussion on improving SQL support, and 
good starting points.

For the parser generator there is currently Pegged, that could be 
integrated into Phobos.  Would that be enough work for a full 
project.

https://github.com/PhilippeSigaud/Pegged

Also, anyone interested in mentoring projects related to these 
topics.
Feb 02 2016
prev sibling next sibling parent tchaloupka <chalucha gmail.com> writes:
On Thursday, 14 January 2016 at 18:56:21 UTC, Craig Dillabaugh 
wrote:

 On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh 
 wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 [...]


 Deadline is getting closer, any new project ideas are welcome. 
 Starting to get some contact from students now.


It might be helpfull if they can help with:

* proper fast JSON parser (this is already worked on I think 
here: https://github.com/s-ludwig/std_data_json, but it seems to 
need a help with to finally get it to Phobos as we are constantly 
bit by it on public: https://github.com/kostya/benchmarks)

* same with the XML parser

* one probably crazy idea - WCF[1] interoperability for vibe.d 
(it might be helpfull in commercial field if one can use vibe.d 
as a backend server with WCF capability so .Net clients can call 
it directly with autogenerated protocol). But it will be a lot of 
work to implement all features..

[1] 
https://msdn.microsoft.com/en-us/library/ms731082%28v=vs.110%29.aspx
Jan 14 2016
prev sibling parent reply Tavi <octavian.cacina outlook.com> writes:
On Thursday, 14 January 2016 at 18:56:21 UTC, Craig Dillabaugh 
wrote:

 Deadline is getting closer, any new project ideas are welcome. 
 Starting to get some contact from students now.



FlatBuffers for DLang - http://google.github.io/flatbuffers/
Jan 15 2016
parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Friday, 15 January 2016 at 15:11:39 UTC, Tavi wrote:

 On Thursday, 14 January 2016 at 18:56:21 UTC, Craig Dillabaugh 
 wrote:

 Deadline is getting closer, any new project ideas are welcome. 
 Starting to get some contact from students now.



 FlatBuffers for DLang - http://google.github.io/flatbuffers/


Are you volunteering as a potential mentor :o)
Jan 15 2016
parent reply Tavi <octavian.cacina outlook.com> writes:
On Friday, 15 January 2016 at 16:06:00 UTC, Craig Dillabaugh 
wrote:

 On Friday, 15 January 2016 at 15:11:39 UTC, Tavi wrote:

 On Thursday, 14 January 2016 at 18:56:21 UTC, Craig Dillabaugh 
 wrote:

 Deadline is getting closer, any new project ideas are 
 welcome. Starting to get some contact from students now.



 FlatBuffers for DLang - http://google.github.io/flatbuffers/


 Are you volunteering as a potential mentor :o)


I haven't started anything seriously in D yet, so I would not be 
qualified for such mentoring.
Being an efficient cross platform serialization library started 

JavaScript), may be a good candidate for GSOC.
Jan 15 2016
next sibling parent Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Friday, 15 January 2016 at 20:46:59 UTC, Tavi wrote:

 On Friday, 15 January 2016 at 16:06:00 UTC, Craig Dillabaugh 
 wrote:

 On Friday, 15 January 2016 at 15:11:39 UTC, Tavi wrote:

 On Thursday, 14 January 2016 at 18:56:21 UTC, Craig 
 Dillabaugh wrote:

 Deadline is getting closer, any new project ideas are 
 welcome. Starting to get some contact from students now.



 FlatBuffers for DLang - http://google.github.io/flatbuffers/


 Are you volunteering as a potential mentor :o)


 I haven't started anything seriously in D yet, so I would not 
 be qualified for such mentoring.
 Being an efficient cross platform serialization library started 

 JavaScript), may be a good candidate for GSOC.


Thanks then for the suggestion.  It is my policy to always ask if 
someone wants to mentor!
Jan 15 2016
prev sibling parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Friday, 15 January 2016 at 20:46:59 UTC, Tavi wrote:

 On Friday, 15 January 2016 at 16:06:00 UTC, Craig Dillabaugh 
 wrote:

 On Friday, 15 January 2016 at 15:11:39 UTC, Tavi wrote:

 On Thursday, 14 January 2016 at 18:56:21 UTC, Craig 
 Dillabaugh wrote:

 Deadline is getting closer, any new project ideas are 
 welcome. Starting to get some contact from students now.



 FlatBuffers for DLang - http://google.github.io/flatbuffers/


 Are you volunteering as a potential mentor :o)


 I haven't started anything seriously in D yet, so I would not 
 be qualified for such mentoring.
 Being an efficient cross platform serialization library started 

 JavaScript), may be a good candidate for GSOC.


Anyone interested and capable of mentor a student interested in 
doing FlatBuffers for D.
Feb 06 2016
parent reply Dragos Carp <dragoscarp gmail.com> writes:
On Saturday, 6 February 2016 at 20:18:57 UTC, Craig Dillabaugh 
wrote:

 Anyone interested and capable of mentor a student interested in 
 doing FlatBuffers for D.


I could do that. Currently, as a side project, I'm working on 
adding D support for Protocol Buffers v3 [1].

Main goals of the new design:
- integration in the upstream project
- simple readable generated code
- range based solution

Of course, the same can be applied for the FlatBuffers.

[1] https://github.com/dcarp/protobuf/tree/dlang_support
Feb 07 2016
parent reply CraigDillabaugh <craig.dillabaugh gmail.com> writes:
On Sunday, 7 February 2016 at 12:14:24 UTC, Dragos Carp wrote:

 On Saturday, 6 February 2016 at 20:18:57 UTC, Craig Dillabaugh 
 wrote:

 Anyone interested and capable of mentor a student interested 
 in doing FlatBuffers for D.


 I could do that. Currently, as a side project, I'm working on 
 adding D support for Protocol Buffers v3 [1].

 Main goals of the new design:
 - integration in the upstream project
 - simple readable generated code
 - range based solution

 Of course, the same can be applied for the FlatBuffers.

 [1] https://github.com/dcarp/protobuf/tree/dlang_support


Awesome! Thanks.  I will write up something on the idea's page in 
the next day or two (which you are welcome to edit of course).  
Also, if a student were interested in working on Protocol 
Buffers, would there be opportunities there too?

I also ask Mentor's to write a little bit about themselves on the 
mentor's page:

http://wiki.dlang.org/GSOC_mentors
Feb 08 2016
parent Dragos Carp <dragoscarp gmail.com> writes:
On Monday, 8 February 2016 at 13:25:38 UTC, CraigDillabaugh wrote:

 Awesome! Thanks.  I will write up something on the idea's page 
 in the next day or two (which you are welcome to edit of 
 course).  Also, if a student were interested in working on 
 Protocol Buffers, would there be opportunities there too?


There is still some pending work regarding Protocol Buffers:
- native support for the so called "well known" types
- optimization of non-recursive messages
- comments and deprecate field handling
- benchmarking
- json support
Feb 08 2016
prev sibling next sibling parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh 
wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas



 Craig


Just trying to keep GSOC on the front page ...

If you have your name attached to a project currently on our list 
please let me know if you can't mentor this year.  I am starting 
to get some inquires for students about projects (just had one 
about DDT), and it would be bad is some project that is currently 
on the list disappeared between now and mid-February.  So I would 
rather clean up any projects that we can't go ahead with now.
Jan 18 2016
next sibling parent reply CraigDillabaugh <craig.dillabaugh gmail.com> writes:
On Monday, 18 January 2016 at 16:16:01 UTC, Craig Dillabaugh 
wrote:

 On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh 
 wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas



 Craig


 Just trying to keep GSOC on the front page ...

 If you have your name attached to a project currently on our 
 list please let me know if you can't mentor this year.  I am 
 starting to get some inquires for students about projects (just 
 had one about DDT), and it would be bad is some project that is 
 currently on the list disappeared between now and mid-February.
  So I would rather clean up any projects that we can't go ahead 
 with now.


I can't believe I let this slip all the way to page 4 :o)

GSOC organization deadline is 3.5 weeks away, and while there 
have been a few ideas proposed here, we don't have too much that 
is concrete.

I will try and get to work on filling in the idea's page with 
what we have so far, but still need more ideas from the 
community.  Note, if you have an idea you also need to either be 
able to mentor, or even better, volunteer someone else.

For the time being the following people are listed as potential 
mentors for projects already on the idea's page (from last year):

Andrei Alexandrescu
Iain Buclaw
Bruno Medeiros
Jens Mueller
Martin Nowak
Jacob Ovrum
Amaury Sechet
Russel Winder

I would like to get confirmation from each of you if you can 
mentor this year (and if your name is attached to a project, can 
that still be a go).  If I don't have confirmation I will have to 
drop the mentor/project, as it would look really bad if students 
submit proposals and we end up saying "Oh, sorry that individual 
can't really mentor you ... maybe you should try something Rust 
related."

Cheers

Craig
Jan 26 2016
next sibling parent Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 01/26/2016 01:45 PM, CraigDillabaugh wrote:

 I would like to get confirmation from each of you if you can mentor this
 year (and if your name is attached to a project, can that still be a go).


Affirmative. -- Andrei
Jan 26 2016
prev sibling parent Russel Winder via Digitalmars-d <digitalmars-d puremagic.com> writes:
On Tue, 2016-01-26 at 18:45 +0000, CraigDillabaugh via Digitalmars-d
wrote:

 [=E2=80=A6]
=C2=A0
 I would like to get confirmation from each of you if you can=C2=A0
 mentor this year (and if your name is attached to a project, can=C2=A0
 that still be a go).=C2=A0=C2=A0If I don't have confirmation I will have =


to=C2=A0

I believe I will be able to.

I haven't been able to check the projects and propose new ones, sorry.
Mayhap at the end of next week. Sorry for the delay=E2=80=A6 things.
--=20
Russel.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder ekiga.n=
et
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
Jan 28 2016
prev sibling parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Monday, 18 January 2016 at 16:16:01 UTC, Craig Dillabaugh 
wrote:

 On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh 
 wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas



 Craig


 Just trying to keep GSOC on the front page ...

 If you have your name attached to a project currently on our 
 list please let me know if you can't mentor this year.  I am 
 starting to get some inquires for students about projects (just 
 had one about DDT), and it would be bad is some project that is 
 currently on the list disappeared between now and mid-February.
  So I would rather clean up any projects that we can't go ahead 
 with now.


I would like confirmation from the following individuals if they 
can mentor GSOC this summer.

Iain Buclaw
Bruno Medeiros
Martin Nowak (and as backup Admin)
Jacob Ovrum

And as backup mentors
  Adam D. Ruppe
  Dmitry Olshansky

I will continue to polish the Ideas page until the deadline (Feb 
18th)

http://wiki.dlang.org/GSOC_2016_Ideas

but improvements by the community are welcome.
Feb 09 2016
parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Wednesday, 10 February 2016 at 03:28:55 UTC, Craig Dillabaugh 
wrote:
clip

 I would like confirmation from the following individuals if 
 they can mentor GSOC this summer.

 Iain Buclaw
 Bruno Medeiros
 Martin Nowak (and as backup Admin)
 Jacob Ovrum

 And as backup mentors
  Adam D. Ruppe
  Dmitry Olshansky

 I will continue to polish the Ideas page until the deadline 
 (Feb 18th)

 http://wiki.dlang.org/GSOC_2016_Ideas

 but improvements by the community are welcome.


GSOC deadline is Friday.  Would be great if I could get 
confirmation from the above individuals if they can still mentor. 
  Also, if you have an interest in being a mentor please let me 
know, and I can add you to the list.

Also improvements to the Idea's page are welcome.  I've added a 
few things (and subtracted one or two), but it still looks a lot 
like last year's losing effort.
Feb 15 2016
parent reply Johannes Pfau <nospam example.com> writes:
Am Tue, 16 Feb 2016 00:28:29 +0000
schrieb Craig Dillabaugh <craig.dillabaugh gmail.com>:


 On Wednesday, 10 February 2016 at 03:28:55 UTC, Craig Dillabaugh 
 wrote:
 clip

 I would like confirmation from the following individuals if 
 they can mentor GSOC this summer.

 Iain Buclaw
 Bruno Medeiros
 Martin Nowak (and as backup Admin)
 Jacob Ovrum

 And as backup mentors
  Adam D. Ruppe
  Dmitry Olshansky

 I will continue to polish the Ideas page until the deadline 
 (Feb 18th)

 http://wiki.dlang.org/GSOC_2016_Ideas

 but improvements by the community are welcome.  


 
 GSOC deadline is Friday.  Would be great if I could get 
 confirmation from the above individuals if they can still mentor. 
   Also, if you have an interest in being a mentor please let me 
 know, and I can add you to the list.
 
 Also improvements to the Idea's page are welcome.  I've added a 
 few things (and subtracted one or two), but it still looks a lot 
 like last year's losing effort.
 
 


I'd suggest posting this to D.announce, people often don't read these
old threads.
Feb 16 2016
parent Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Tuesday, 16 February 2016 at 11:20:13 UTC, Johannes Pfau wrote:

 Am Tue, 16 Feb 2016 00:28:29 +0000
 schrieb Craig Dillabaugh <craig.dillabaugh gmail.com>:


clip

 
 


 I'd suggest posting this to D.announce, people often don't read 
 these old threads.


Done!  Thanks for the suggestion.
Feb 16 2016
prev sibling parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh 
wrote:

 The deadline for the Google Summer of Code, 2016 is February 
 19th. Which means we have about a month and a half to put 
 something together.  For the time being I've recycled last 
 years projects (with one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas


clip

 http://wiki.dlang.org/GSOC_mentors


We have had another student inquiry on the GSOC front.  I am 
going from memory, which is always a bit sketchy, but it seems 
that there is a bit of an increase in student interest this year.

Would there be any interest in a project to automate binding 
generation from C files (or perhaps even a full conversion tool)? 
  This could be done either as a new project, or possibly building 
on dstep - if there is meaningful work that can still be done to 
improve that project.  Alternately, the student suggested using  
pycparser (https://github.com/eliben/pycparse) as the basis for 
such a tool?

Jacob, are you sure you don't want to Mentor?  It seems like you 
are involved in all the interesting projects from a student 
perspective :o)

Is there work that can be done to improve dstep?
Jan 28 2016
next sibling parent reply Rikki Cattermole <alphaglosined gmail.com> writes:
On 29/01/16 2:53 AM, Craig Dillabaugh wrote:

 On Thursday, 31 December 2015 at 23:58:32 UTC, Craig Dillabaugh wrote:

 The deadline for the Google Summer of Code, 2016 is February 19th.
 Which means we have about a month and a half to put something
 together.  For the time being I've recycled last years projects (with
 one dropped so far):

 http://wiki.dlang.org/GSOC_2016_Ideas#Ideas


 clip

 http://wiki.dlang.org/GSOC_mentors


 We have had another student inquiry on the GSOC front.  I am going from
 memory, which is always a bit sketchy, but it seems that there is a bit
 of an increase in student interest this year.

 Would there be any interest in a project to automate binding generation
 from C files (or perhaps even a full conversion tool)?  This could be
 done either as a new project, or possibly building on dstep - if there
 is meaningful work that can still be done to improve that project.
 Alternately, the student suggested using pycparser
 (https://github.com/eliben/pycparse) as the basis for such a tool?

 Jacob, are you sure you don't want to Mentor?  It seems like you are
 involved in all the interesting projects from a student perspective :o)

 Is there work that can be done to improve dstep?


I have a c phase 1-3 implemented in D.
I would be willing to give up the source if I keep the rights (but code 
can be open just not an open source license).
Could be used to fully translate c code to D without too much work I 
would think.

http://en.cppreference.com/w/c/language/translation_phases
Jan 28 2016
parent Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Thursday, 28 January 2016 at 13:57:06 UTC, Rikki Cattermole 
wrote:

 On 29/01/16 2:53 AM, Craig Dillabaugh wrote:

 [...]


 I have a c phase 1-3 implemented in D.
 I would be willing to give up the source if I keep the rights 
 (but code can be open just not an open source license).
 Could be used to fully translate c code to D without too much 
 work I would think.

 http://en.cppreference.com/w/c/language/translation_phases


Rikki, how would this improve upon what we have with Dstep (apart 
from it being fun since it is in D).
Feb 03 2016
prev sibling next sibling parent reply Dicebot <public dicebot.lv> writes:
On Thursday, 28 January 2016 at 13:53:30 UTC, Craig Dillabaugh 
wrote:

 Would there be any interest in a project to automate binding 
 generation from C files (or perhaps even a full conversion 
 tool)?
  This could be done either as a new project, or possibly 
 building on dstep - if there is meaningful work that can still 
 be done to improve that project.  Alternately, the student 
 suggested using  pycparser (https://github.com/eliben/pycparse) 
 as the basis for such a tool?


I think it is very important to focus on polishing dstep instead 
of creating more and more imperfect tools. In the end any 
approach which doesn't use existing mature C compiler frontend is 
doomed to make binding mistakes.

Random suggestions for improving dstep:
- implement support for C++ clang API using new shiny dmd 
features (it tends to have more features than C one)
- implement automatic generation of idiomatic D code for raw 
bindings (i.e. stripping redundant namespace prefixes)
- remove/minimize dependencies apart from Phobos/libclang (will 
make much easier including it into standard tools)
Jan 28 2016
next sibling parent reply Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Thursday, 28 January 2016 at 15:20:12 UTC, Dicebot wrote:

 On Thursday, 28 January 2016 at 13:53:30 UTC, Craig Dillabaugh 
 wrote:

 Would there be any interest in a project to automate binding 
 generation from C files (or perhaps even a full conversion 
 tool)?
  This could be done either as a new project, or possibly 
 building on dstep - if there is meaningful work that can still 
 be done to improve that project.  Alternately, the student 
 suggested using  pycparser 
 (https://github.com/eliben/pycparse) as the basis for such a 
 tool?


 I think it is very important to focus on polishing dstep 
 instead of creating more and more imperfect tools. In the end 
 any approach which doesn't use existing mature C compiler 
 frontend is doomed to make binding mistakes.

 Random suggestions for improving dstep:
 - implement support for C++ clang API using new shiny dmd 
 features (it tends to have more features than C one)
 - implement automatic generation of idiomatic D code for raw 
 bindings (i.e. stripping redundant namespace prefixes)
 - remove/minimize dependencies apart from Phobos/libclang (will 
 make much easier including it into standard tools)


Seems like there should be enough there for a project. Also 
looking at:

https://github.com/jacob-carlborg/dstep

in the list of limitations is, 'Doesn't translate preprocessor 
macros of any kind", that seems like a good challenge.

So if Jacob can't mentor this, is there anyone who would be 
comfortable with that type of project?
Jan 28 2016
parent reply Dicebot <public dicebot.lv> writes:
On Thursday, 28 January 2016 at 17:15:17 UTC, Craig Dillabaugh 
wrote:

 Seems like there should be enough there for a project. Also 
 looking at:

 https://github.com/jacob-carlborg/dstep

 in the list of limitations is, 'Doesn't translate preprocessor 
 macros of any kind", that seems like a good challenge.


AFAIK this is blocked on having C++ API bindings because 
preprocessor isn't exposed to plain C ones (this is exactly why I 
have mentioned it in list).


 So if Jacob can't mentor this, is there anyone who would be 
 comfortable with that type of project?


I may volunteer but need to check my availability and mentor 
duties :) Will respond shortly. But of course it should be Jacob.
Jan 28 2016
next sibling parent Jacob Carlborg <doob me.com> writes:
On 2016-01-28 18:19, Dicebot wrote:


 AFAIK this is blocked on having C++ API bindings because preprocessor
 isn't exposed to plain C ones (this is exactly why I have mentioned it
 in list).


I would first try the translation unit option 
"CXTranslationUnit_DetailedPreprocessingRecord". The documentation says:

"Used to indicate that the parser should construct a "detailed" 
preprocessing record, including all macro definitions and instantiations"

If that doesn't work I would prefer improving the C bindings to add 
functionality for working with the preprocessor. But perhaps no one is 
interested in doing that.

One huge advantage is that C API for libclang is a stable API.

-- 
/Jacob Carlborg
Jan 28 2016
prev sibling parent Jacob Carlborg <doob me.com> writes:
On 2016-01-28 18:19, Dicebot wrote:


 AFAIK this is blocked on having C++ API bindings because preprocessor
 isn't exposed to plain C ones (this is exactly why I have mentioned it
 in list).


I'm not sure what you have in mind but handling something like #if seems 
very complicated. Example:

#if __APPLE__
// some declarations
#elif linux
// some declarations
#endif

The problems I see with the above:

1. It's not possible to enable/disable these preprocessor symbols. For 
example enabling both

2. If the above would be possible the compiler would need to have access 
to the SDK of the other platform. Is this what cross-compilers do?

3. Even if the above two points work the compiler would still need to 
choose one of the two paths. I guess it would need to at least lex the 
other path. But just lexing the other path would not need to be enough. 
It need to parse and to the semantic analysis as well to be useful

Just thinking about this brings up new problems and gives me a headache :)

-- 
/Jacob Carlborg
Jan 28 2016
prev sibling parent reply Jacob Carlborg <doob me.com> writes:
On 2016-01-28 16:20, Dicebot wrote:


 I think it is very important to focus on polishing dstep instead of
 creating more and more imperfect tools. In the end any approach which
 doesn't use existing mature C compiler frontend is doomed to make
 binding mistakes.

 Random suggestions for improving dstep:
 - implement support for C++ clang API using new shiny dmd features (it
 tends to have more features than C one)


I would like to avoid this until there's absolutely no other way to do it.

A couple of other ideas:

* Getting the D code more looking like the C code. For example, the same 
order for the symbols as the C code has. Currently it outputs all 
variables first, then all types and all functions last

* Add support for comments

* Generated libclang bindings. These are now manually created, mostly 
for the above two reasons. Ideally it would be possible to generate 
bindings almost exactly like the manually created ones [1]

[1] https://github.com/jacob-carlborg/dstep/blob/master/clang/c/Index.d

-- 
/Jacob Carlborg
Jan 28 2016
parent Dicebot <public dicebot.lv> writes:
On Thursday, 28 January 2016 at 21:07:58 UTC, Jacob Carlborg 
wrote:

 * Generated libclang bindings. These are now manually created, 
 mostly for the above two reasons. Ideally it would be possible 
 to generate bindings almost exactly like the manually created 
 ones [1]

 [1] 
 https://github.com/jacob-carlborg/dstep/blob/master/clang/c/Index.d


Could be cool project to make dstep compilable with clang 
bindings converted with dstep - and run tests with both.
Jan 28 2016
prev sibling parent reply Jacob Carlborg <doob me.com> writes:
On 2016-01-28 14:53, Craig Dillabaugh wrote:



 Jacob, are you sure you don't want to Mentor?  It seems like you are
 involved in all the interesting projects from a student perspective :o)


I can absolutely help out with all of my projects and projects I'm 
involved in. But I have no interested in being an official mentor.

-- 
/Jacob Carlborg
Jan 28 2016
parent reply Russel Winder via Digitalmars-d <digitalmars-d puremagic.com> writes:
On Thu, 2016-01-28 at 22:01 +0100, Jacob Carlborg via Digitalmars-d
wrote:

 On 2016-01-28 14:53, Craig Dillabaugh wrote:
=20
=20

 Jacob, are you sure you don't want to Mentor?=C2=A0=C2=A0It seems like =




you

 are
 involved in all the interesting projects from a student perspective
 :o)


=20
 I can absolutely help out with all of my projects and projects I'm=C2=A0
 involved in. But I have no interested in being an official mentor.


Given I have an interest in making DStep better (so as to wrap the
Linux DVB API and libdvbv5) and Jacob is not wanting to be formal
mentor, and yet can support, I can offer myself as mentor so as to try
and ensure the project moves.

--=20
Russel.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder ekiga.n=
et
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
Jan 28 2016
parent Craig Dillabaugh <craig.dillabaugh gmail.com> writes:
On Thursday, 28 January 2016 at 22:26:44 UTC, Russel Winder wrote:

 On Thu, 2016-01-28 at 22:01 +0100, Jacob Carlborg via 
 Digitalmars-d wrote:

 On 2016-01-28 14:53, Craig Dillabaugh wrote:
 
 

 Jacob, are you sure you don't want to Mentor?  It seems like 
 you
 are
 involved in all the interesting projects from a student 
 perspective
 :o)


 
 I can absolutely help out with all of my projects and projects 
 I'm involved in. But I have no interested in being an official 
 mentor.


 Given I have an interest in making DStep better (so as to wrap 
 the Linux DVB API and libdvbv5) and Jacob is not wanting to be 
 formal mentor, and yet can support, I can offer myself as 
 mentor so as to try and ensure the project moves.


Thanks Russel, Jacob, and Dicebot for your suggestions. I will 
add DStep to our list of projects with Russel as Mentor.
Jan 28 2016