On Mon, 2015-01-12 at 15:16 +0000, CraigDillabaugh via Digitalmars-d wrote:
> […]
> 
> Sounds good.  I will see if filcuc is interested in being a Mentor.

I am happy to be the backup mentor for this one.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 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

On Monday, 12 January 2015 at 15:28:01 UTC, Russel Winder via Digitalmars-d wrote:
>
> On Mon, 2015-01-12 at 15:16 +0000, CraigDillabaugh via Digitalmars-d wrote:
>> […]
>> 
>> Sounds good.  I will see if filcuc is interested in being a Mentor.
>
> I am happy to be the backup mentor for this one.

Great.  Thank you.

On 31/12/2014 03:25, Craig Dillabaugh wrote:
>
> 7) Bruno Medeiros - you suggested a DDT project. I've added it. Can you
> provide me with a few more details, and a bio.   Also, under what
> license is DDT released, I couldn't access any code on your GitHub page
> to check this.

Bio:
Lead developer of DDT - the Eclipse D IDE - on and off from as far back as 2008. Has an interest in toolchain development for upcoming languages such as D, particularly the development of IDEs and IDE semantic functionality. Professionally, works mainly with core Java and Eclipse RCP technologies - currently on R&D projects.


DDT is released under the Eclipse Public License. (one tiny component is Apache License)  And yup, several source files still need to be cleaned up to include the license info, I've been a bit lax with that in the past.


DDT core engine ideas (only core Java knowledge needed):
* Make the DDT semantic engine available as a command-line daemon tool (similar to DCD).
* Add support for source formatting (with formatting options).
* Add support for semantic search in the semantic engine (search symbols by name and type (for example: "where in my code is the function std.stdio.writeln called?", or "which classes in my code subclass this given class?") .
* Improve semantic engine / code completion capabilities (for example, understand template instantiation, function overloads, etc.)


DDT Eclipse specific ideas:
* Improve/add UI support for DUB multiple build configurations + launch.
* Reduce usages of DLTK code, possibly refactoring or rewriting DLTK functionality into an IDE-neutral layer (LangEclipseIDE).
* Add support for continuous build mode (build and report errors on the fly).

Some of the items in both lists are a bit small for GSoC, so they might have to be combined with others.

The good news is that this year with DDT there is a lot more opportunities with core Java tasks only, which should make it easier for a newbie to join in and contribute. But realistically, it's a long shot that we'll get a candidate of quality for this proposal - Java interest doesn't rank high in the D community... ^_^'

-- 
Bruno Medeiros
https://twitter.com/brunodomedeiros

On Tuesday, 13 January 2015 at 12:23:16 UTC, Bruno Medeiros wrote:
> On 31/12/2014 03:25, Craig Dillabaugh wrote:
>>
>> 7) Bruno Medeiros - you suggested a DDT project. I've added it. Can you
>> provide me with a few more details, and a bio.   Also, under what
>> license is DDT released, I couldn't access any code on your GitHub page
>> to check this.
>
> Bio:
> Lead developer of DDT - the Eclipse D IDE - on and off from as far back as 2008. Has an interest in toolchain development for upcoming languages such as D, particularly the development of IDEs and IDE semantic functionality. Professionally, works mainly with core Java and Eclipse RCP technologies - currently on R&D projects.
>
>
> DDT is released under the Eclipse Public License. (one tiny component is Apache License)  And yup, several source files still need to be cleaned up to include the license info, I've been a bit lax with that in the past.
>
>
> DDT core engine ideas (only core Java knowledge needed):
> * Make the DDT semantic engine available as a command-line daemon tool (similar to DCD).
> * Add support for source formatting (with formatting options).
> * Add support for semantic search in the semantic engine (search symbols by name and type (for example: "where in my code is the function std.stdio.writeln called?", or "which classes in my code subclass this given class?") .
> * Improve semantic engine / code completion capabilities (for example, understand template instantiation, function overloads, etc.)
>
>
> DDT Eclipse specific ideas:
> * Improve/add UI support for DUB multiple build configurations + launch.
> * Reduce usages of DLTK code, possibly refactoring or rewriting DLTK functionality into an IDE-neutral layer (LangEclipseIDE).
> * Add support for continuous build mode (build and report errors on the fly).
>
> Some of the items in both lists are a bit small for GSoC, so they might have to be combined with others.
>
> The good news is that this year with DDT there is a lot more opportunities with core Java tasks only, which should make it easier for a newbie to join in and contribute. But realistically, it's a long shot that we'll get a candidate of quality for this proposal - Java interest doesn't rank high in the D community... ^_^'

Thank you very much.

On Tuesday, 13 January 2015 at 12:23:16 UTC, Bruno Medeiros wrote:
> On 31/12/2014 03:25, Craig Dillabaugh wrote:
>>
>> 7) Bruno Medeiros - you suggested a DDT project. I've added it. Can you
>> provide me with a few more details, and a bio.   Also, under what
>> license is DDT released, I couldn't access any code on your GitHub page
>> to check this.
>
> The good news is that this year with DDT there is a lot more opportunities with core Java tasks only, which should make it easier for a newbie to join in and contribute. But realistically, it's a long shot that we'll get a candidate of quality for this proposal - Java interest doesn't rank high in the D community... ^_^'

Hey, but if you are a glass half full type, then you would say that we have a much better chance of getting a good candidate for this project because there are so many Java programmers out there.

On Saturday, 3 January 2015 at 03:33:29 UTC, Rikki Cattermole wrote:
> On 3/01/2015 3:59 p.m., Craig Dillabaugh wrote:
>> On Saturday, 3 January 2015 at 00:15:42 UTC, Rikki Cattermole wrote:
>>> On 3/01/2015 4:30 a.m., Craig Dillabaugh wrote:
>>>> On Thursday, 1 January 2015 at 06:19:14 UTC, Rikki Cattermole wrote:
>>>> clip
>>>>
>>>>>> 10) Rikki had mentioned a 'Web Development' project, but I don't have
>>>>>> enough to post on the project ideas page.  Are you still interested in
>>>>>> doing this.
>>>>>
>>>>> Yes I am.
>>>>> I don't know what I'm doing in the near future (need a job) so I can't
>>>>> explore this too much.
>>>>> But I know I will be able to mentor for it.
>>>>>
>>>>>> Hope that everyone has a great 2015, and I look forward to your
>>>>>> feedback.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Craig
>>>>
>>>> It would be great to have you as a mentor, but we definitely need fairly
>>>> solidly defined projects.  Any chance you can come up with something by
>>>> the end of January.
>>>>
>>>> Craig
>>>
>>> Indeed.
>>> I created a list for Cmsed
>>> https://github.com/rikkimax/Cmsed/wiki/Road-map#what-does-other-web-service-frameworks-offer
>>>
>>> Right now it basically comes down to e.g. QR code, bar code, PDF.
>>> QR and bar code isn't that hard. Not really a GSOC project.
>>> PDF definitely is worthy.
>>>
>>> PDF is an interesting case, it needs e.g. PostScript support. And
>>> preferably image and font loading/exporting.
>>> So it might be a good worth while project. As it expands out into
>>> numerous other projects.
>>
>> Thanks.  Would you like to add something to the Wiki, or would you
>> prefer if I did so.  Also, what license are you using?
>>
>> Cheers,
>> Craig
>
> When it comes to my open source code bases I have two rules.
> - If you use it commercially at the very least donate what its worth to you.
> - For non commercial, as long as I'm not held liable you are free to use it in any way you want. At the very least, get involved e.g. PR's, issues.
> So liberal licenses like MIT, BSD. Which are compatible with e.g. BOOST.
>
> Please do write up a skeleton for me on the wiki. I can pad it out. Will help to keep things consistent.

Rikki.  I've updated the Wiki to include a Cmsed entry:

http://wiki.dlang.org/GSOC_2015_Ideas#Cmsed

Please have a look and fill it out a bit more.  Also, I added a stub for your bio - you may want to update (and possibly correct) it :o)

On 18/01/2015 3:57 p.m., Craig Dillabaugh wrote:
> On Saturday, 3 January 2015 at 03:33:29 UTC, Rikki Cattermole wrote:
>> On 3/01/2015 3:59 p.m., Craig Dillabaugh wrote:
>>> On Saturday, 3 January 2015 at 00:15:42 UTC, Rikki Cattermole wrote:
>>>> On 3/01/2015 4:30 a.m., Craig Dillabaugh wrote:
>>>>> On Thursday, 1 January 2015 at 06:19:14 UTC, Rikki Cattermole wrote:
>>>>> clip
>>>>>
>>>>>>> 10) Rikki had mentioned a 'Web Development' project, but I don't
>>>>>>> have
>>>>>>> enough to post on the project ideas page.  Are you still
>>>>>>> interested in
>>>>>>> doing this.
>>>>>>
>>>>>> Yes I am.
>>>>>> I don't know what I'm doing in the near future (need a job) so I
>>>>>> can't
>>>>>> explore this too much.
>>>>>> But I know I will be able to mentor for it.
>>>>>>
>>>>>>> Hope that everyone has a great 2015, and I look forward to your
>>>>>>> feedback.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Craig
>>>>>
>>>>> It would be great to have you as a mentor, but we definitely need
>>>>> fairly
>>>>> solidly defined projects.  Any chance you can come up with
>>>>> something by
>>>>> the end of January.
>>>>>
>>>>> Craig
>>>>
>>>> Indeed.
>>>> I created a list for Cmsed
>>>> https://github.com/rikkimax/Cmsed/wiki/Road-map#what-does-other-web-service-frameworks-offer
>>>>
>>>>
>>>> Right now it basically comes down to e.g. QR code, bar code, PDF.
>>>> QR and bar code isn't that hard. Not really a GSOC project.
>>>> PDF definitely is worthy.
>>>>
>>>> PDF is an interesting case, it needs e.g. PostScript support. And
>>>> preferably image and font loading/exporting.
>>>> So it might be a good worth while project. As it expands out into
>>>> numerous other projects.
>>>
>>> Thanks.  Would you like to add something to the Wiki, or would you
>>> prefer if I did so.  Also, what license are you using?
>>>
>>> Cheers,
>>> Craig
>>
>> When it comes to my open source code bases I have two rules.
>> - If you use it commercially at the very least donate what its worth
>> to you.
>> - For non commercial, as long as I'm not held liable you are free to
>> use it in any way you want. At the very least, get involved e.g. PR's,
>> issues.
>> So liberal licenses like MIT, BSD. Which are compatible with e.g. BOOST.
>>
>> Please do write up a skeleton for me on the wiki. I can pad it out.
>> Will help to keep things consistent.
>
> Rikki.  I've updated the Wiki to include a Cmsed entry:
>
> http://wiki.dlang.org/GSOC_2015_Ideas#Cmsed
>
> Please have a look and fill it out a bit more.  Also, I added a stub for
> your bio - you may want to update (and possibly correct) it :o)

Fun fact, we have more cows now then sheep.
Sorry to disappoint.

On Sunday, 18 January 2015 at 09:09:19 UTC, Rikki Cattermole
wrote:
>>
>> Rikki.  I've updated the Wiki to include a Cmsed entry:
>>
>> http://wiki.dlang.org/GSOC_2015_Ideas#Cmsed
>>
>> Please have a look and fill it out a bit more.  Also, I added a stub for
>> your bio - you may want to update (and possibly correct) it :o)
>
> Fun fact, we have more cows now then sheep.
> Sorry to disappoint.

No way!  Well, I learned something new.  You will have to work
that into your Bio.

Thanks.
Craig

On 19/01/2015 12:29 p.m., CraigDillabaugh wrote:
> On Sunday, 18 January 2015 at 09:09:19 UTC, Rikki Cattermole
> wrote:
>>>
>>> Rikki.  I've updated the Wiki to include a Cmsed entry:
>>>
>>> http://wiki.dlang.org/GSOC_2015_Ideas#Cmsed
>>>
>>> Please have a look and fill it out a bit more.  Also, I added a stub for
>>> your bio - you may want to update (and possibly correct) it :o)
>>
>> Fun fact, we have more cows now then sheep.
>> Sorry to disappoint.
>
> No way!  Well, I learned something new.  You will have to work
> that into your Bio.
>
> Thanks.
> Craig

I think I did pretty good with how it is right now.
So I think I'll leave that part out.