From: Simon Strandgaard <neoneye@...>
Date: 2004-03-31T07:39:22+09:00
Subject: Re: Dormant projects (was Status of AOP in Ruby)

On Wed, 31 Mar 2004 08:17:26 +0900, Tom Copeland wrote:
> On Sun, 2004-03-28 at 06:04, Gawnsoft wrote:
[snip] 
>> Perhaps the sites could send an e-mail to the nominal project manager
>> after a period of dormancy*, and if they hear nothing back, could put
>> up an ad saying 'new PM wanted for this project'?
>> 
>> * and this could be defined by the PM, up to a maximum of, say, 9
>> months.
> 
> The tricky part might be defining what "dormant" means - no commits?  No
> downloads?
> 

Maybe one could calculate a 'dormant' value, so that visitors easily
can distinguish alive and kicking projects from the dead ones:
*  no upload via scp to the homepage.
*  no commits.
*  no file releases
*  no downloads
*  no closed tracker items.

How could such index be calculated?

1=dead
....
5=healthy

A small testsuite

server> ruby test_dormant.rb 
Loaded suite TestDormant
Started
..
Finished in 0.001374 seconds.

1 tests, 1 assertions, 0 failures, 0 errors
server> expand -t2 test_dormant.rb 
require 'test/unit'

class TestDormant < Test::Unit::TestCase
  def calc(days_since_last_commit, days_since_last_release)
    1
  end
  def test_healty1
    assert_equal(true, true)
  end
end

require 'test/unit/ui/console/testrunner'
Test::Unit::UI::Console::TestRunner.run(TestDormant)
server>


ok.. just realized that this isn't easy.

--
Simon Strandgaard