[
https://issues.apache.org/jira/browse/ROL-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743257#comment-13743257
]
Glen Mazza commented on ROL-1358:
---------------------------------
While such a change would probably do more good than harm, I could also imagine
a manager wanting to see all changes via RSS/Atom feeds and concerned about
somebody making a malicious change of some sort (say, an outgoing employee
badmouthing the company) and checking the "minor edit" button so to circumvent
company review. If we allowed this, I suspect we'd need a admin-level setting
"allow edits to be marked as minor" to allow this functionality to be shut off.
> Minor Edit button in edit entry forms
> -------------------------------------
>
> Key: ROL-1358
> URL: https://issues.apache.org/jira/browse/ROL-1358
> Project: Roller
> Issue Type: New Feature
> Components: Newsfeed Aggregation, Weblog Editor
> Affects Versions: 3.0
> Environment: all
> Reporter: Henry Story
> Assignee: Allen Gilliland
>
> There is a serious need for a "minor edit" button on the editing forms, that
> would allow an author specify that an update he is about to make is
> insignificant [1], and so that the updated time stamp of the associated atom
> feed should not be updated.
> Insignificant changes include things such as:
> - html or markup fixes
> - link renaming (perhaps a remote resource was moved, deleted, hijacked,
> or some such...)
> - minor spelling or grammatical corrections
> - add or delete tags, or change the category of a post
> ...
> Currently any of the above changes the update time stamp, which will appear
> to many aggregators as spam. This is because people are interested in updates
> to articles, be they blog articles or wiki articles [2]. But if absolutely
> minor changes have the effect of changing the updated time stamp, then the
> value of the updated time stamp is lost. Currently I am having this problem
> with any minor edit affecting the panetrdf feed. [3]
> There is one very simple solution to this problem:
> Add a "minor update" check box to the entry field. If checked the updated
> time stamp does not get changed.
> The Atom Application Protocol does make an app:edited [4] time stamp
> available, to allow clients to synchronise their state up to minor edits with
> the server. This could also be made available in the server, and will
> probably be important at some point in the future. This will require a change
> to the database. This feature request does not require it.
> Henry Story
> [1] to use the terminology of Atom rfc 4287
> http://www.atompub.org/rfc4287.html#element.updated
> [2] Tim Bray made the point in the atom application protocol mailing list
> http://www.imc.org/atom-protocol/mail-archive/msg05601.html
> [3] http://blogs.sun.com/bblfish/entry/sorry_for_the_updates
> [4]
> http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-13.html#rfc.section.10.2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
