Vision for the first semester of 2016

[Chris Wright via Digitalmars-d-announce]

On Wed, 27 Jan 2016 21:01:47 +0000, Martin Nowak wrote:

> On Monday, 25 January 2016 at 16:26:36 UTC, Russel Winder wrote:
>> PyPI has is an highly opinionated metric that helps you decide what is
>> good and what is dross.
> 
> Could you help us on designing one for code.dlang.org as well?

I'd want to use the number of releases, how recent the most recent 
release was, the longevity of the project, and the number of other 
projects that depend on it. If people are willing to let dub submit 
anonymous usage information, the number of builds depending on a project 
is also an indicator of its value.

Longevity is an awkward one. If I create a project, do nothing with it 
for four years, then make a release, will that count as well as making a 
release once a month for four years? But the other metrics should account 
for that.

If possible, I'd include when the project last compiled and whether it 
passes its unittests. This requires setting up a continuous integration 
service for untrusted code. I've seen other people's designs for that, 
and I think I could replicate it without too much trouble.