Edgewall Software
Modify

Opened 15 years ago

Closed 15 years ago

Last modified 10 years ago

#8654 closed enhancement (duplicate)

Mandatory comment on wiki changes

Reported by: luca.ceresoli@… Owned by:
Priority: normal Milestone:
Component: wiki system Version: 0.11.5
Severity: normal Keywords:
Cc: leho@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

I'd like to be able to force users to enter a non-empty comment when editing a wiki page.

Motivation:

It's easy to forget (or to be too lazy) to add a comment when editing wiki pages.

As a project admin, this makes it hard for me to find a specific change in the wiki page history or to review recent activity on the timeline.

It would also be nice to force a minimum comment length, or they'll quickly learn they can just hit space.

Attachments (0)

Change History (6)

comment:1 by Christian Boos, 15 years ago

Resolution: duplicate
Status: newclosed

This has been brought up numerous time, search:"mandatory wiki comment".

See #2839 which even has a patch.

comment:2 by Remy Blank, 15 years ago

This sounds like a nice and simple sample plugin, that we could even place into tracext so that it can be easily enabled.

Should I write a formal proposal for this tracext namespace on trac-dev, or just go ahead and create it?

in reply to:  description comment:3 by Ryan Ollos <ryano@…>, 15 years ago

Replying to luca.ceresoli@…:

I'd like to be able to force users to enter a non-empty comment when editing a wiki page.

There is a ForceCommentPlugin on Trac-Hacks.

in reply to:  2 ; comment:4 by Christian Boos, 15 years ago

Replying to rblank:

This sounds like a nice and simple sample plugin, that we could even place into tracext so that it can be easily enabled.

Why not if you find it useful (this will at least illustrate IWikiManipulator).

Should I write a formal proposal for this tracext namespace on trac-dev, or just go ahead and create it?

Both ;-)

We should then discuss about how to nicely present those extra optional features to the admin, as the current "Plugins" admin panel is not really user friendly enough (e.g. group components by module path instead of a flag list, show the component docstring for easier discovery of what a component does).

in reply to:  4 comment:5 by Remy Blank, 15 years ago

Replying to cboos:

(e.g. group components by module path instead of a flag list, show the component docstring for easier discovery of what a component does).

Good ideas! I'll start the tracext namespace, add to it the commit_ticket_updater plugin in multirepos, and write a message to trac-dev.

Oh, and open a new ticket for that, so that I don't need to hijack this one ;-)

comment:6 by lkraav <leho@…>, 10 years ago

Cc: leho@… added

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.