Official bug tracker?

Hi all.

I think it is time to decide on a new official bug tracker for the 
Archetypes project itself.

Currently we have issues in various places:

AT trac: https://trac.plone.org/archetypes/ (disabled)
Poi: http://plone.org/products/archetypes/issues (2 issues)
sf.net tracker: 
http://sourceforge.net/tracker/?group_id=75272&atid=543430 (~150 issues)
Plone trac, category infrastructure/content types 
https://trac.plone.org/plone/ (some issues)

As I assume nobody likes the sf.net tracker, I think we have three 
options here:

1. Use POI.
2. Use Plone's trac.
3. Use the seperate trac instance.

Personally I love trac and I would consider AT big enough to have its 
own trac instance. Mixing all pure AT related issues into the Plone trac 
instance isn't optimal as AT has a different version numbering and might 
have a distinct release schedule.

While I think POI is great for small products which have a dedicated 
maintainer who approves issues, I think this model doesn't suite AT well.

One advantage of using trac is the availability of an import script for 
sourceforge.net trackers. If we agree on using trac I would volunteer to 
do this import (with some help of wiggy ;) and clean up the existing issues.

What do you all think?

Hanno



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642