I setup http://www.projectsycamore.org/Bugs and http:// www.projectsycamore.org/Feature_Requests as described below. I tried to make it flexible for the user by pointing to trac and mentioning that they can also use the wiki.
We should emphasize using the wiki as the report mechanism for users of Sycamore that don't wish to get involved in the development process. AD On May 22, 2007, at 4:32 PM, [EMAIL PROTECTED] wrote: > > Using the Project Sycamore wiki as the user interface to the project > is a good idea. I don't think normal user should have to deal with > TRAC to report issues. Ya, you're right. I tried. :) > For bugs: > > JaneUser submits bug report at ProjectSycamore.org/Bugs > > An active developer examines the report and creates a ticket in TRAC > if its determined to actually be a bug (not a feature or a mis- > configuration of the software). The bug report is removed or archived > at ProjectSycamore.org/Known_Bugs. We'll have to work to keep track of what sycamore version, affected wikis, etc. For example bug x affects rocwiki but not daviswiki. > For Feature Requests: > > > JaneUser submits a request at ProjectSycamore.org/Feature_Requests > > > The development community examines the requests, and if its a feature > to explore, a Wiki page is created to facilitate discussion. > ProjectSycamore.org/Feature_Requests/Do_XYZ > > Once the development community has determine to implement a request, > it is entered into TRAC and assigned to the appropriate milestone. Sounds good to me. _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
