Status report, milestones, quality improvements?

[Steven Schveighoffer]

On Wed, 16 Mar 2011 11:27:03 -0400, Mike James <foo at bar.com> wrote:

> "Regan Heath" <regan at netmail.co.nz> wrote in message  
> news:op.vsfy88k954xghj at puck.auriga.bhead.co.uk...
>> On Wed, 16 Mar 2011 01:13:33 -0000, jasonw <user at webmails.org> wrote:
>>
>>> One problem is the large amount of obsolete data (  
>>> http://www.dsource.org/projects/dmdfe )
>>>
>>> Dsource is The place for D projects. The problem with dsource is if  
>>> you're a serious professional and need professional quality libraries  
>>> and tools, dsource does nothing in the way of supporting these types  
>>> of users. The sections are filled with small hobby projects such as  
>>> http://www.dsource.org/projects/libcalc. What I'm looking for is  
>>> somehing that emphasizes the names of "important" projects. For  
>>> example standard parallel/concurrency/server/socket/vfs libraries are  
>>> a first class priority. It takes a day to browse through the list of  
>>> mediocre crap.
>>
>> I was browsing dsource the other day and I wanted to be able to sort  
>> projects by last update date or something, to find the ones which were  
>> being currently maintained.  It would certainly be useful to sort by a  
>> category like [alpha] [beta] [stable] etc as well.  I think dsource is  
>> the correct place to put any/all of our 'crap' but it just needs to be  
>> easier to sort and find the things you're interested in, at any one  
>> time.  i.e. what if you were looking for a project to lend a hand to,  
>> no use finding one which is pretty much [stable] and complete.
>>
>> R
>
> The front page of dsource should have 5-10 useful, complete and tested  
> projects highlighted. All the dross and projects never completed (or the  
> 'wishful thinking' projects that were never even started) should be  
> relegated deep.
>
> The front page should be there to introduce, and intice, the prospective  
> D user to some useful libraries...
>

I think it would be good enough to make projects that have not had a  
change in the last year get dropped to an "older projects" page.

Anyone who has a still-maintained but seldom-changing project could just  
make a change in the home page once a year or something to prevent this  
 from happening.

For my project dcollections, there have been long periods with no change  
because I haven't been using it, and nobody is reporting bugs.  But that  
doesn't mean it's not a robust project ready for use.  I wouldn't mind  
just having to ping it every once in a while to make sure it stays "fresh".

-Steve