We have been having the following conversation via email regarding setting up issue tracking for community projects (sorry, bad practice to not have it here in the forum):

-----Original Message-----
From: Jeffrey Peters
Sent: Friday, July 18, 2008 11:32 AM
To: Paul Richards; Kirstan Vandersluis; Bill Miller; XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

Hi Paul,

To differentiate from release numbers, you would leave the default for group to none. (IE - not in a release) If we incorporate a project into the main project, you would then associate it to a release.

Search issues - Core issues are associated to a release. That would be the differentiator. You can also search using any combination of the fields in tracker to include words.



Jeff Peters
Software Quality Assurance Manager

-----Original Message-----
From: Paul Richards
Sent: Friday, July 18, 2008 11:14 AM
To: Kirstan Vandersluis; Jeffrey Peters; Bill Miller; XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

Shouldn't we still have a separate Group ("Community Projects") to differentiate from the release numbers.

i.e. if you pick cat="Designer" you pick group=5.0 or group=5.1, but if you pick cat="EDIFact", 5.0 and 5.1 do not make sense. If you have group="community" (or something) then it is not tied to a particular release (unless that is the intention - to tie community projects to releases?) Does the group have to be a decimal format number?

The big issue I see using one tracker, is that there is no way to filter (Search) just core issues and ignore the community stuff. You would have to search 4 times(each core category) or x times for each release (x releases). (With a "community" group you can search all of the community issues in one search.) Not a huge deal, but a lot of noise if a lot of "community" issues are logged.

-----Original Message-----
From: Kirstan Vandersluis
Sent: Friday, July 18, 2008 11:07 AM
To: Jeffrey Peters; Bill Miller; XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

Using categories sounds good to me. The name just needs to reflect the subproject name, like that on the forum and wiki.

-Kirstan

-----Original Message-----
From: Jeffrey Peters
Sent: Friday, July 18, 2008 11:01 AM
To: Bill Miller; XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

Hi Bill,

We are using group for Release numbers. This isn't very intuitive, but that's the way other SF projects use that field. Adding 4 categories will work. Does anyone have any preference on the naming? I can add these to SF today. I can also update the wiki.


Jeff Peters
Software Quality Assurance Manager

-----Original Message-----
From: Bill Miller
Sent: Friday, July 18, 2008 10:09 AM
To: Bill Miller; XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

Maybe I have the hierarchy backwards. Should it be Category: Community Extension Projects / Group: (one for each project)?

-----Original Message-----
From: Bill Miller
Sent: Friday, July 18, 2008 9:31 AM
To: XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

Along with category, should we also use Group? We could have a Community Sandbox Projects group.

-----Original Message-----
From: Bill Miller
Sent: Friday, July 18, 2008 9:30 AM
To: XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

I agree. Does everyone else agree with this approach? Should we create a category for each project? I think that would be best. If everyone agrees, I will update what I wrote to reflect this. We should probably also have information in the wiki on use of categories in the tracker.

-----Original Message-----
From: Jeffrey Peters
Sent: Thursday, July 17, 2008 2:19 PM
To: Paul Richards; Bill Miller
Cc: XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

Hi All,

I would recommend that we add another category(s) for each project using the same issue tracker.


Jeff Peters
Software Quality Assurance Manager

-----Original Message-----
From: Paul Richards
Sent: Thursday, July 17, 2008 1:55 PM
To: Bill Miller
Cc: XAware Development
Subject: RE: Draft of copy to be added to Contribute to the Project

There are five projects listed on the wiki and forum, but only three exist in source forge (CVS).

Where are the issue tracker(s), item 4, for sandbox projects? Are these separate from the issue tracker for all XAware core product bugs? (Could we just use the forums for each project and not have to maintain multiple issue trackers?)

Might add verbiage and instructions (or link to instructions) for joining a project (id has to be added to CVS for write access, and ??). We should have verbiage promoting contributions to the projects - that don't require a contributor agreement while in the sandbox. The contributor agreement is required if we choose to move a capability to the core product -- or, are we requiring a contributor agreement to contribute to the sandbox?