GSoC 2017 Ideas!

[Adam D. Ruppe via Digitalmars-d]

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.