So the ideas page is up for the 2017 GSoC.  Its a bit light on content.  Please feel free to use this forum thread to discuss any ideas you might have for appropriate projects.

https://wiki.dlang.org/GSOC_2017_Ideas

Cheers

Craig

On 15/01/2017 4:19 AM, Craig Dillabaugh wrote:
> So the ideas page is up for the 2017 GSoC.  Its a bit light on content.
> Please feel free to use this forum thread to discuss any ideas you might
> have for appropriate projects.
>
> https://wiki.dlang.org/GSOC_2017_Ideas
>
> Cheers
>
> Craig

This year perhaps we should have something for dub.

On Saturday, 14 January 2017 at 15:23:19 UTC, rikki cattermole wrote:
> On 15/01/2017 4:19 AM, Craig Dillabaugh wrote:
>> So the ideas page is up for the 2017 GSoC.  Its a bit light on content.
>> Please feel free to use this forum thread to discuss any ideas you might
>> have for appropriate projects.
>>
>> https://wiki.dlang.org/GSOC_2017_Ideas
>>
>> Cheers
>>
>> Craig
>
> This year perhaps we should have something for dub.

What did you have in mind, new default language for the config file perhaps :o)?

On Saturday, 14 January 2017 at 15:54:46 UTC, Craig Dillabaugh wrote:
> What did you have in mind, new default language for the config file perhaps :o)?

The website could use some work. Things that would make me hate it less (fyi, I don't actually use dub, but I sometimes try to keep packages up for other people):

* search including subpackages

* subpackage navigation (currently we can list them as dependencies but that's kinda hideous)

* some kind of documentation scanning or linking, including for subpackages. (see, I subpackage everything because I mostly work with modules, not repos.)


Things I've seen other people ask for:

* download count

* rating system (btw I think stars aren't that good, I'd rank on "did this work for you?" multiple choice: "perfect!", "yes", "no it sucked", and "it wasn't what I thought it was". or something like that. 1 star might mean the code was awful, or it might mean the description was awful. Separating "sucked" with "not what i expected" would try to handle that.)



On the program rather than the website:

* integration with external stuff better

* way to install and describe things for offline



So there's a decent amount of low hanging fruit here - I haven't looked at the code, but I can't imagine any of this is all that difficult to do. The hard part might be an innovative design to actually get people to where they need to go more than the code; like keeping ratings is easy, just CRUD that number, but sorting by rating in search so you enter "website scraping" and it gives you back my dom.d (or whatever superior competitor is out there) as a high confidence, popular solution front and center instead of a list of 0 or 100 things that all look the same to the newbie, that's tricky.

On Saturday, 14 January 2017 at 16:12:43 UTC, Adam D. Ruppe wrote:
> but sorting by rating in search

I'm sorry, that was a run on sentence.

The big picture goal I'd like to see is that the package manager, or even a tutorial author for some topic, just take the choice away.

Sure, you can ignore its recommendation and look down the list, but it would be nice if you didn't have to; if there was one solid way to do what they want that is easy to find. End analysis paralysis.

Like on Amazon, where there's hundreds of options, but there's one with the five stars listed as #1 best seller at the top of the list, it is nice to stop evaluation and just hit buy. It kinda sucks to be the new competitor when the system is promoting the existing #1.... but meh.

You also want to avoid cheating the system and manipulating the results, by either established slumlords or new guys wanting a leg up.


If the student can solve the design problem, the implementation might be easy. idk how Google would feel about trivial code with painful design, but that's the way a lot of software work is in the real world sooo I feel it is an applicable project.

On Saturday, 14 January 2017 at 15:54:46 UTC, Craig Dillabaugh wrote:
> What did you have in mind, new default language for the config file perhaps :o)?

Here's a list of issues that are considered blocking by the guy who's in charge of getting D into Debian's package manager:

https://gist.github.com/ximion/77dda83a9926f892c9a4fa0074d6bf2b#dub

On Saturday, 14 January 2017 at 15:19:23 UTC, Craig Dillabaugh wrote:
> So the ideas page is up for the 2017 GSoC.  Its a bit light on content.  Please feel free to use this forum thread to discuss any ideas you might have for appropriate projects.
>
> https://wiki.dlang.org/GSOC_2017_Ideas
>
> Cheers
>
> Craig

This isn't enough for GSoC, but maybe it can be rolled into other website ideas:

It's a pain in the ass to use GDC or LDC when the website only shows the current Phobos documentation. It gives no way to go back a version, or three.

Currently I have to use archive.org.

On 14 January 2017 at 19:44, Jack Stouffer via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
> On Saturday, 14 January 2017 at 15:19:23 UTC, Craig Dillabaugh wrote:
>>
>> So the ideas page is up for the 2017 GSoC.  Its a bit light on content. Please feel free to use this forum thread to discuss any ideas you might have for appropriate projects.
>>
>> https://wiki.dlang.org/GSOC_2017_Ideas
>>
>> Cheers
>>
>> Craig
>
>
> This isn't enough for GSoC, but maybe it can be rolled into other website ideas:
>
> It's a pain in the ass to use GDC or LDC when the website only shows the current Phobos documentation. It gives no way to go back a version, or three.
>
> Currently I have to use archive.org.

Yeah, this is something that readthedocs.org does a lot better at here.

On Saturday, 14 January 2017 at 16:20:06 UTC, Adam D. Ruppe wrote:
> On Saturday, 14 January 2017 at 16:12:43 UTC, Adam D. Ruppe wrote:
>> but sorting by rating in search
>
> I'm sorry, that was a run on sentence.
>
> The big picture goal I'd like to see is that the package manager, or even a tutorial author for some topic, just take the choice away.
>
> Sure, you can ignore its recommendation and look down the list, but it would be nice if you didn't have to; if there was one solid way to do what they want that is easy to find. End analysis paralysis.
>
> Like on Amazon, where there's hundreds of options, but there's one with the five stars listed as #1 best seller at the top of the list, it is nice to stop evaluation and just hit buy. It kinda sucks to be the new competitor when the system is promoting the existing #1.... but meh.
>
> You also want to avoid cheating the system and manipulating the results, by either established slumlords or new guys wanting a leg up.
>
>
> If the student can solve the design problem, the implementation might be easy. idk how Google would feel about trivial code with painful design, but that's the way a lot of software work is in the real world sooo I feel it is an applicable project.

I've been trying to find something on this, but haven't yet, but I am not sure if website work would be considered appropriate.  I know pure documentation is not acceptable, and seem to think the websites might fall in the same category - but I am not sure. I will keep looking.

On 15/01/2017 4:54 AM, Craig Dillabaugh wrote:
> On Saturday, 14 January 2017 at 15:23:19 UTC, rikki cattermole wrote:
>> On 15/01/2017 4:19 AM, Craig Dillabaugh wrote:
>>> So the ideas page is up for the 2017 GSoC.  Its a bit light on content.
>>> Please feel free to use this forum thread to discuss any ideas you might
>>> have for appropriate projects.
>>>
>>> https://wiki.dlang.org/GSOC_2017_Ideas
>>>
>>> Cheers
>>>
>>> Craig
>>
>> This year perhaps we should have something for dub.
>
> What did you have in mind, new default language for the config file
> perhaps :o)?

One thing I'd like code.dlang.org to support is other services. E.g. arbitrary git and mercurial servers. Sub directory dub files ext.