[Tilecache] Issue tracking

[Christopher Schmidt]

On Fri, Feb 06, 2009 at 05:01:15PM +0100, Tibor Arpas wrote:
> Hi Christopher, Hi Everybody,
> 
> I would like to express my thank to Christopher and everybody who
> worked on Tilecache. It has surprisingly lot of functionality and I
> like it a lot. But I think there is still space to grow. Some of the
> obstacles for development in mid term I can see is a lack of issue
> tracking system and a lack of unit tests. What's your opinion about
> the issue tracking? Does anybody think it's not necessary at all? Or
> the obstacle is the overhead of setting it up and maintaining? The
> administration of issues and patches should actually become less time
> consuming then through mailing list..

Explain in what ways you think that tracking issues through the mailing
list isn't working? There is currently one outstanding set of
functionality -- the AWS buckets patch -- that I'm aware of. I've seen
no evidence that using Trac or anything else is useful given the size of
the project.

There was a TileCache trac for a year. It was never used, got filled up
with spam, and I turned it off. I haven't regretted it.

Unit tests are welcome, and a number already exist, as doctests in the
modules themeselves and in docstrings of the various modules. Generally
speaking, 'nose' is a handy utility to run these tests.

I have no reason to believe that more unit tests or Trac help with
increasing development or decreasing pain. I'd be interested in
understanding why you think it would.  

Best Regards,
-- 
Christopher Schmidt
MetaCarta