Comment 1 for bug 675504
Revision history for this message
| Michael Nelson (michael.nelson) wrote Re: Is Review.hide redundant or ModerationRequest itself? | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I've just spent some time investigating both django-moderation and django-gatekeeper.
Both have lots of useful functionality, but also miss one-or-two features we'd need.
django-moderation
===============
url: https:/
Overview: The "normal" use-case with this app is that new objects require moderation by default. Although this behaviour can be overridden, it seems that there is currently no field on the ModeratedObject model to store who flagged/requested the moderation. Otherwise this app has most features we'd need (and some that we'd not need - such as re-moderating when an object is edited and displaying the changes).
django-gatekeeper
===============
url: https:/
Overview: This app *does* support flagging - great, seems to match our requirements and is very configurable, but doesn't support a reason for flagging in its model.
So we could either branch and contribute to one of these, or start with the simple functionality that we already have (perhaps moving it into a separate django app though) and learn from the work of these other projects. If in the end we can replace our app with one of those - great.