Zope Integration

[alecmunro]

I'm a big Trac fan, and we really want to use it for our projects, but we are currently in need to better workflow support and better permissions. I noticed these two items are planned, but seem like they will be delayed until 0.12. Has any thought been given to trying to make Trac into a Zope product, or some other variety of integration? There are decent workflow libraries already available, and their permission system is quite excellent.

I would be willing to contribute some quantity of time on this, as I have a fair amount of Zope experience. It's also possible that my employer would be willing to pay me to contribute, if it meant we were likely to get the functionality we need.

(Perhaps an enhancement ticket is not the best way to suggest this, but it was the best way I was able to find).

[Christian Boos]

better workflow support and better permissions

That sounds like 0.11, no?

make Trac into a Zope product, or some other variety of integration?

That's a long term idea, we could use this ticket to discuss what this would actually mean and the changes that would be required at the Trac level.

[Matthew Good]

If there are ways people can tie Trac into parts of the Zope applications via a plugin that would be fine, but using Zope in the Trac core would almost certainly lead to forking of the project. Zope is a pretty heavy dependency and would require extensive changes to use it effectively, and I think there's sufficient resistance to Zope amongst the TracTeam that this would lead to a split. I think this should be closed as wontfix.

[anonymous]

I am a heavy Trac user, and I would fork the project, personally if necessary, if it became a Zope. App.

[Noah Kantrowitz]

+1 on the wontfix. I really see no long-term benefits to such a move, and there are plenty of downsides.

[Christian Boos]

Has any thought been given to trying to make Trac into a Zope product, or some other variety of integration?

Sorry if I wasn't clear, but I intended that ticket to be about the other kind of integration, not at all about Trac using Zope.

So you have to consider this from the Zope centric point-of-view: you already have your Zope environment, and want to graft (parts of) Trac inside. I've no idea how easy that could be, and if there are actually no changes in Trac that are needed to make that possible, then I think we can close as worksforme.

If there are actually a few changes needed in Trac so that it can more easily be integrated in other frameworks (those could be Zope, Django, Pocoo, etc.), I see no reason why we shouldn't do it.

[vs..]

hi, i am gr8 fan of ZOPE as well as trac, i want to know the reason why we cannt implement trac in zope. Please help

[antont]

there is ZopeTrac which is a trac-wrapping Zope product, ​http://www.zope.org/Members/TheJester/ZopeTrac/ZopeTrac/

i just installed it yesterday, haven't still figured out everything of how permissions go. but it certainly feels kinda nice having trac there as a product in the zope list, with the icon and all :)

~Toni

[Christopher Lenz]

This kind of integration should (and apparently is) being done externally to Trac itself. If there's any kind of specific problem with this integration that would be possible to fix on the Trac side without bending over backwards, that should go in separate specific tickets.

So I'm closing this as wontfix as previously suggested.