[Zope-PTK] FYI: Issue tracking

[Brian Lenihan]

I have to say I beg to differ.   Part of the open source model is to 
release early and often.  I personally don't care if early releases are 
incomplete or buggy, I just want to see if there is something there which 
interests me enough do something about helping to make it work in my mostly 
non-existent spare time.

As for documentation, python tends to be self-documenting. One could argue 
that Zope is an exception to this rule, but then one would have to be 
somewhat lazy to do so.

There has been plenty if interest expressed in getting access to the 
various iterations of DC's problem tracking code.  How is the Zope 
community going to scratch that itch unless you make the code accessible ?

I'll bet you cash money the tracker will be ready for general use quicker 
if you just throw it out and see what happens.

At 09:51 PM 02/16/2000 -0500, you wrote:
>Bill Anderson wrote:
> >
> > Paul Everitt wrote:
> > >
> > > The PTK project now has a Tracker setup for report:
> > >
> > >   http://www.zope.org/Products/PTK/Tracker
> >
> > This looks _really_ sweet.
> > Any chance at getting the code? ;)
>
>It is pretty damn suite.  The next step for us to use it a little more
>widely and make sure we get the kinks out of it.  The next step after
>that might be to make it something you can add to a folder on Zope.org.
>After that we might make it widely available.
>
>The problem for us, obviously, is time.  It costs a lot to give things
>away for free. :^(  Moreover, the Zope community would probably kill us
>if we kept throwing over new software without documenting the old.
>
>--Paul
>
>_______________________________________________
>Zope-PTK maillist  -  Zope-PTK@zope.org
>http://lists.zope.org/mailman/listinfo/zope-ptk