Susan Spencer writes ("Re: Voting system for elections"):
> Well, 'recent commits' is useful only as an imperfect indicator of
> whether a project is dead or alive. It isn't an absolute to use as
> a checkbox item for evaluating the appropriateness of a software
> solution. Rather it is good to know in case it stops working due to
> upstream issues or any variety of factors.
It can't stop working due to "upstream issues" if upstream are not
making changes. Looking at the state in Debian, it stopped working
"recently" because of churn in some Python libraries, but this was
fairly easily fixed by a Debian contributor.
> It is part of the 'due diligence' research phase of choosing a software
> solution.
I agree that if the program were obviously in need of major work, and
there was no upstream, then this would be a problem. But this is not
the case here.
Ian.
_______________________________________________
Spi-general mailing list
Spi-general@lists.spi-inc.org
http://lists.spi-inc.org/listinfo/spi-general
