public
Description: A simple Django app that provides a ticker like news section including row level permission based workflow
Homepage: http://github.com/jezdez/django-ticker
Clone URL: git://github.com/jezdez/django-ticker.git
name age message
file LICENSE Fri Mar 20 05:29:07 -0700 2009 Removed more unused files. Updated LICENSE. Bum... [bartTC]
file README Fri Mar 20 08:25:50 -0700 2009 Fixed some typos in README [jezdez]
directory example_project/ Fri Mar 20 04:47:08 -0700 2009 Created a new, good looking example site. [bartTC]
file setup.py Sun Mar 22 17:57:57 -0700 2009 Fixed stupid bug with non-ASCII character in ad... [jezdez]
directory ticker/ Sun Mar 22 17:57:57 -0700 2009 Fixed stupid bug with non-ASCII character in ad... [jezdez]
README
=============
django-ticker
=============

django-ticker is a reusable Django_ application that provides a ticker like
news section including row level permissions. What does this mean?

In django-ticker you have a fine grained permission control what the
(administrative) user can do and what not. Besides the default Django
permissions -- add, change, delete -- there are some extra permissions:

- change_foreign
- publish

Originally this was created for the news section of the `German Django community`_ 
where foreign users could add articles but had no permission to publish
them, cause a moderator must check these articles first. 

It's easy to create a pressroom like workflow, assumed we have different
people with different permissions:

The freelance journalist:
    Granted permissions: add, change
    
    - can add articles
    - can change his articles (only his own)
    - can not delete his articles
    - can set the status of the article to "closed" or "draft". Draft means,
      that the article is ready for check by a moderator.
    - in the admin list of articles, they see only they own

The journalist:
    Granted permissions: add, change, delete, publish
    
    - can add articles
    - can change and delete his articles (only his own)
    - can set the status of the article to "closed", "draft" or "published"
    - in the admin list of articles, they see only their own

The chief editor (or moderator):
    Granted permissions: add, change, delete, publish, change_foreign
    
    - can add articles
    - can change and delete all (!) articles
    - can set the status of the article to "closed", "draft" or "published"
    - in the admin list of articles, they see all articles
    
The proofreader (or subject specialist):
    Granted permissions: change, change_foreign
    
    - can not add articles
    - can not delete articles
    - can not publish articles
    - can change all articles (e.g. for correction)
    - in the admin list of articles, they see all articles
    
So, you can mix these permissions and create a workflow that perfectly 
fits your needs.

.. _`Django`: http://www.djangoproject.com/
.. _`German Django Community`: http://django-de.org/