> So, my opinion is that we have the sycamore wiki for design > docs/discussion (mainly because it's familiar and I don't want to taint my > wiki knowledge by using multiple wikis), the trac wiki just point to the > sycamore wiki (as it does now), and have users report bugs directly into > the trac ticket tracker (I'm notoriously lazy). All discussion about a > particular *bug* should be in the comments of the ticket (not on the > mailing list). For *features* that require design changes, database > changes, etc these should be made into a wiki page and a ticket should be > added for that feature. There should be a link to the ticket in the wiki > and to the wiki in the ticket. The discussion for large features could > happen in the wiki or on the mailing list but it should be stored on the > wiki for posterity.
I don't think wiki end-users will go through the hoops needed to put a ticket into devjavu. At rocwiki, we have a Bug Report page and then we move the bugs into trac. In general, the lower the barrier for entry, the more likely you're going to get a bug report. The rest of this is fine with me. I don't see real integration between trac's ticket system and the wiki, so links would be needed no matter what. Storing everything for posterity is critical. _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
