issuetracker-development — IssueTrackerProduct Development

Re: [Issuetracker-development] IssueTracker & CMF/Plone

[Peter B. <ma...@pe...>]

David,

The idea is great news to the future of IssueTracker! CMF is a great 
product and the need is there because people have asked for it.

I know very little about CMF products. What I would Not like to see is a 
modified duplicate called something like CMFIssueTracker which is a copy of 
the IssueTracker with bits changed. That'll make upgrades difficult.
Surely you can create a CMF'ed version that "monkey patches" (let me know 
if you don't know what I mean) the core?
If you feel that this is not possible, but maybe with some new changes then 
I'm happy to try to help you sort things out.

If you want to I can add you as a developer on the sourceforge project page 
with a CVS module just for this.
But first, please tell me what can be done without codying code twice.

Cheers,
Peter


PS. I think someone has already created a product called something like 
CMFSiteTracker back when IssueTracker used to be called SiteTracker. I 
couldn't find it on google or zope.org now though.



At 23:23 2002-09-14 +1000, David Hart wrote:

>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
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.381 / Virus Database: 214 - Release Date: 2002-08-02

[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

[Issuetracker-development] IssueTrackerProduct mailinglist announcement

[Peter B. <ma...@pe...>]

Dear everybody who has shown interest in my IssueTrackerProduct product lately,

I just wanted to let you know that I have set up a mailinglist and a CVS 
repository for the development of the IssueTrackerProduct.
If you want to be informed of any changes to the product I suggest that you 
sign up for this one.

The CVS will be the main thing but I will obviously sometimes pack 
something up and release it as a file. Using CVS is easy and please do not 
hesitate to get started with it if you haven't already.

 From now on I would prefer if people either send emails to the 
issuetracker-development mailinglist or use the bug tracker on the 
sourceforge project page.

Thank you, Peter

LINKS:

Mailinglist:
http://lists.sourceforge.net/lists/listinfo/issuetracker-development

Mailinglist archive:
http://www.geocrawler.com/lists/3/SourceForge/25548/0/

Sourceforge project page:
http://sourceforge.net/projects/issuetracker/

CVS repository:
http://sourceforge.net/cvs/?group_id=60145
To download the latest, go...:

cvs 
-d:pserver:ano...@cv...:/cvsroot/issuetracker 
login

cvs -z3 
-d:pserver:ano...@cv...:/cvsroot/issuetracker 
co IssueTrackerProduct

[Issuetracker-development] The first message to the issuetracker-development list

[Peter B. <ma...@pe...>]

Cool! It works. Let's get going then.