Christophe Rhodes csr21@cam.ac.uk writes:
I suppose what I'm getting at is that I've interacted with bug trackers that are so much better in terms of convenience than an HTML textarea that I'm pretty unwilling to spend my time with a vanilla cliki on something which shouldn't interfere with my workflow. (Don't feel too bad about this, though, because I have the same visceral
I don't feel bad at all, I actually do appreciate your feedback. That's the kind of feedback I wished I got when I created the bug list page at McCLIM CLiki.
Given limited resources, I thought that a CLiki-based bug list might have been an acceptable tradeoff between hunting for bug reports in the mailing list archive, and setting up some more formal and/or convenient bug tracking system.
Any comments from the McCLIM developers? What should be done with the bug list page at McCLIM CLiki? Shall we drop it?
hatred of both the Sourceforge bug tracker and bugzilla-based systems -- in all cases, they are /way/ too much work for the end-user to submit bugs, and quite often they are also too much work for the administrator).
You should probably check the simple bug reporting procedures and systems that Aunt Tillie uses for reporting bugs of her favorite office suite and web browser, i.e. OpenOffice and Firefox :)
Firefox Help: Reporting Bugs http://www.mozilla.org/support/firefox/bugs
qa: Bugs&Issues Explained (OpenOffice.org) http://qa.openoffice.org/issue_handling/project_issues.html
Paolo