We could form a focus group (no sarcasm intended) with users, IWGers and developers to see what we envision for the process.
On Sat, Oct 22, 2011 at 8:57 AM, Ted Schulman <email@example.com>
We have to define the use-cases against potential audiences - there may be more than one ticketing system if necessary.
On Sat, Oct 22, 2011 at 8:32 AM, Chaz Cheadle <firstname.lastname@example.org>
That is incredibly awesome work!
One question, is the ticket tracking system mean to be internal or external+internal?
That is, will the public put in actual tickets? or will we accept feedback/input from the public and then internally generate and manage tickets then report back to the public when/if the issue is resolved? If its purely internal, OpenAtrim w/CaseTracker will fit the bill. We are currently moving one of our clients from Basecamp to that solution as it provides all of Basecamp's pluse the Drupal backend for module expansion.
On Sat, Oct 22, 2011 at 8:10 AM, Ted Schulman <email@example.com>
Here's a link to the first draft (google doc for now) of the FLO Solutions Workgroup Technology Roadmap for OWS enterprise infrastructure.
We will be moving this to the Solutions wiki.
Share your thoughts, comments, etc.