It needs a lot of work to make it functional. 

Logged In: YES 
user_id=1632

I'm working on it, do you want a path when/if I make it work?

Logged In: YES 
user_id=1632

explanation: I didn't know it was broken, so I installed it,
and got frustrated, and started to fix ;-) I will probably
make it work, since it's so much better than the
CMFCollector, and after that I'll want it to behave better
inside a Plone site, perhaps passing down authentication or
whatnot.

Logged In: YES 
user_id=6405

Please join the roundup-devel mailing list so we can discuss it :) 
 

Logged In: YES 
user_id=108053

Will this use the latest Roundup UI (current cvs)?

We are running Zope, but using a cgi roundup interface 
because of the lack of integrated authentication with CMF.  If 
you need some early-stage testing on plone-less Zope/CMF, 
let me know.  We run it on Red Hat 8.0.  <salivating>BTW 
plone is very cool.</salivating>  I haven't used collector, but 
Roundup is the best option we've run across, even in its early 
stages.

Travis

Logged In: YES 
user_id=6405

Roundup's use of ":name" for special variables breaks because Zope 
automagically strips those out of the form submission. 
 
Thus the cgi.client module would need replacing to remove the use of 
":name" variables. The HTML templates would also need editing to change 
their use of the ":name" variables. 
 
Or, Zope could be "fixed" to not strip those variables out, I suppose. 
 

Logged In: YES 
user_id=1632

about the mailing list: I think I'm in too many mailing
lists ;-) and I want to *use* this product, not become a
developer (after all, if I need a tracker, it means I
already have at least one project). But I can spare a few
days and even justify that as "work", as the company where I
work is using Collector and not very happy about it.

On implementation: IMO it's pretty much BBR, or even BBD.
Zope is not a CGI server, and any design that tries to use
it as such will fail, or, in the best case, succeed
marginally with absolutely no advantages compared to running
it in its own port. To save time, what I'm planning to do is
not ZRoundup, but CMFRoundup. It needs to use a CMF-based
skin instead of the template system used by the CGI
front-end (which already uses TAL anyway, so it shouldn't be
that hard), and it could, if practical, integrate with
Zope's authentication.

Oh, well. Guess I'd better join the list anyway ;-) but wait
one more day, my wife is in hospital today and I'd better
start this after the baby is home.

Logged In: YES 
user_id=6405

Sorry, BBR and BBD mean nothing to me. 
 
Hooking into Zope's auth will be a problem due to the requirements that 
Roundup has of its user database - there must be a unique id (currently 
numeric), the users must never be deleted (Roundup has a system of user 
_retirement_ where users are marked as no longer listable, but may still be 
referenced) and the users "folder" must support the full Roundup hyperdb 
Class interface. We can discuss this in more detail on the mailing list 
though. 
 

Logged In: YES 
user_id=113859

I'd think this bug has a high priority, because I roundup
really needs
a Zope frondend. There are new issue trackers coming up for
Zope and roundup might miss the opportunity to grow a zope
community.

As for the problem of mapping zope users to roundup user,
one idea I have is that you could just map each zope user
that actually
accesses contents of roundup to the roundup user database
when that happens the first time.  Thus it will always exist
even when the user does not exist for zope anymore.
~                                                         

Logged In: YES 
user_id=6405

ZRoundup looks only in certain places for its home directory. 
In  
fact, Zope has a method for contructing an arbitrary list of  
directories that it searches for Products (the environment 
variable  
PRODUCTS_PATH). So to find itself, ZRoundup needs to 
search that  
path. Fortunately, that path is available from the __path__ 
property  
of the Products object. The attached diff shows code that 
works for me 

Logged In: YES 
user_id=6405

It's been pointed out that the _file stuff is b0rken too (Zope 
automatically blocks accesses to leading-_ path elements).

Logged In: YES 
user_id=6405

ZRoundup interface un-b0rked.