[Issuetracker-development] IssueTracker & CMF/Plone

[David H. <dh...@at...>]

Hi List,

I've begun making changes to add CMF/Plone compatibility to
IssueTracker. The first changes simply allow the two to co-exist
(IssueTracker folderish objects within a Plone Site folderish object),
but not really to interoperate. For full interoperation, it will be
necessary to make Issue Tracker Issues registered CMF portal content
types, after which time they could reside in any CMF Folder.

What's the best way to contribute IssueTracker changes back to the
community?



The CMF offers terrific tools to accomplish portal-like tasks including
user join/login/memberdata management, workflow, documents with
selectable HTML/STX/TXT format, discussions, news posting with news
board, event posting with calendar, etc. All portal objects are catalog
aware and searchable. With most or all parts of the CMF slated to go
into Zope 3.0. With this in mind, it's a good idea to at least be
compatible with the CMF, and an even better idea to interoperate with
CMF. 

Both the CMFDefault and Plone implementations of the CMF tools are busy,
feature-packed and suitable only for very tech savvy users. This is not
however necessary. the IssueTracker could exist in forms including both
a CMF instance for stand-alone operation (as clean looking as it is
today, hiding much of the complexity of the CMF), and as an add-on to an
existing CMF site, with both options taking full advantage of all the
tools offered by the CMF.

-- 
David Hart