Dear Andreas et al,

The Problem with the PloneCollectorNG is the compatibility with Plone 3 
(we use plone 3.2.3)
On the PloneCollectorNG website 
(http://www.zopyx.com/projects/plonecollectorng) you find the following 
status description:
 >>>>
Status

    * PloneCollectorNG requires Plone 2.1 or Plone 2.5. It won't run on
      Plone 3.X.
    * Making PloneCollectorNG compatible with Plone 3 will require a
      substantial amount of work. This will only happen if there is a
      substantial third-party funding available.

<<<<

If we only want to use an issue tracker, we can use POI (a plone issue 
tracker http://plone.org/products/poi). We have one under 
http://www.opentox.org/partners/issues (It still needs some finetuning). 
You all may have a look if it will solve our needs.
If we want to use a "real" bug-tracking system we have to use non-plone 
solutions like Bugzilla (http://www.bugzilla.org/) or Mantis 
(http://www.mantisbt.org/).
Anyway we have to think about our needs and possibilities: Who shall be 
able to post bugs, who is responsible, who solves the bug, 
mailing-workflow and so on.

Greetings,

Micha





Andreas Maunz schrieb:
> Dear all,
>
> I think we opted for individual bugtracking systems for partner software 
> contributions.
> For the code released by OpenTox project itself (e.g. the API and 
> perhaps an SDK), we should however consider using a bugtracking system 
> that can be integrated into the plone website.
> One I have found and which looks quite stable is "PloneCollectorNG", see 
> http://www.zopyx.com/projects/plonecollectorng and (for downloading) 
> http://sourceforge.net/projects/collective/files/PloneCollectorNG/.
>
> Greetings
> Andreas
> _______________________________________________
> Development mailing list
> Development at opentox.org
> http://www.opentox.org/mailman/listinfo/development
>
>