-
Notifications
You must be signed in to change notification settings - Fork 619
Stop using django.contrib.comments #591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
A quick thought: The basic idea here is that a comment posted on a job will be sent to the set:
But I don't actually know how we distinguish who will have the ability to see, respond to and post moderator-type comments on job submissions waiting for approval. Is there a |
Yes there is a 'Job Board Admin' group, see https://github.com/python/pythondotorg/blob/master/jobs/views.py#L12-L13 |
Current status:
|
First off, django.contrib.comments is being unbundled from Django and removed in Django 1.8 (and already raises deprecation warnings in Django 1.7). Second, it's overkill for what we're using it for.
Instead, replace it with a simpler model that can live in the jobs app and store the basic information it needs (sender and message, associated with a particular job posting) and use that to handle comments back and forth about job postings.
The text was updated successfully, but these errors were encountered: