I'm starting to get a bit confused about bugs in my plugins, and of the status of some plugins, because of the free-form way the Dev pages get edited. The protocol for reporting bugs in plugins is currently to edit the Dev page for the plugin, which is fine and dandy at first but rapidly becomes confusing, as the page grows and as people other than the author submit patches and fixes.

Could we please have a formalised reporting mechanism for issues in plugins? And change the status of the Dev pages to that of brainstorming discussion on future directions? Separate from the Support web?

Some possibilities:

1. Direct people to report plugin bugs to the support web, core team then assigns them to the plugin author
2. Duplicate the support web mechanisms in the plugins web
3. Use bugzilla, and install BugzillaLinkPlugin on twiki.org (my preference, I think)

-- CrawfordCurrie - 10 Dec 2003

I think it's best to keep feedback focused on the Dev topics, but you could have some CommentPlugin or html forms templates which could be put on the Dev topics that would save feedback to different topics, or keep on the Dev page but use these formated capture templates to keep it structured.

-- SamHasler - 11 Sep 2004

mmm, would installing ActionTrackerPlugin do this job? (including for DevelopBranch, DeveloperBranches and personal goals?)

-- SvenDowideit - 31 Oct 2004

This will hopefull be resolved by TWikiExtensionBug and ProposedNewFormsInCodev.

-- SamHasler - 31 Oct 2004