PSF Python Job Board
The Python job board was run by single volunteers for many years. Since the job board activities have significantly increased in recent years, and the last Chris Withers, who ran the board in the years 2010-2013, left the project, the PSF would like to relaunch the project using a team of volunteers.
At the same time, we'd like to move the job board from the legacy site to the new relaunched http://www.python.org/ Django based site.
Contents
Old job board process
Please note that this description may not be completely correct. It just describes the process based on the how-to document.
Job submissions were processed using email, a ReST template and a page in a subversion repository.
Job submitters created a job posting based on the template listed on the Job board how-to page
- Submissions were checked against a list of quality criteria
- Submissions which needed refinement were sent back with a notice of what to fix
- Good submissions were added to the job page in order of submission date (in most recent first order)
Page cleanup:
- entries older than three months were regularly removed
- filled positions were removed upon request by the job submitter
New job board process
Please note that this process is just a sketch. It may well change and get more refinements in coming weeks.
Job submissions are entered into a web form, the form creates a database record which is then used for review. After approval the Django site will then list the submissions automatically.
- Job submitters log in to the website (after having registered for an account)
- Submitters create a job posting record
- Submissions are checked against a list of quality criteria by the reviewers
- Submissions which needed refinement are flagged and an email is sent back to the job submitter asking for changes
- Good submissions are approved and then automatically listed on the job board page in order of submission date (in most recent first order)
Questions:
- How to inform the job submitters of problems with their submissions ?
- Should we have 1 person or 2 person reviews ?
Possible solutions for questions:
- The submission could be like a blog post, that way, the submitter could edit the submission while it's not published and leaving the team members to comment on the submission (alerting the submitter of any comments) regarding problems with the submission.
- The submitter could also tick a checkbox to delete his submission.
To be clarified:
- Exact status workflow of job submission records
- Classification of job submissions (there are multiple categories available)
- Quality criteria
- Team member assignments to the review process (e.g. by category)
- Porting the existing job board submissions into the new site's database
What we need:
- team members who can help refine the job board Django app (good Django skills are necessary)
- team members who regularly log in and review postings
- team members who can help interface to the Django site maintainers, e.g.review and process pull requests, issue tickets in case of problems with the site
- team members who lead the groups and signal problems to the PSF board, should any arise
Project Mailing List
The project is run using a mailing list dedicated for the team:
The list gets all email sent to jobs@python.org. The old process used this email address for job submissions. The new process will use a web form based approach instead.
If you want to help in the job board team, please write to jobs@python.org.
Here's the mailing list archive with our current job submission backlog:
Python Jobs List Archive (requires login)
The last processed job submission is dated 12-Feb-2014.
Resources
New job board
New job board This will be the new location of the Python job board, run using Django and backed by a database.
Note: At the moment this still redirects to the legacy website.
Old job board
Job board listing ported from the legacy site This is a single page which has to be manually maintained via the Django admin interface.
Legacy job board site This page was manually maintained through the Subversion repository which runs the legacy website.
Job board how-to explaining the process that was used for the legacy site
Web site administration
New site's issue trackers If you find problems with the job app, please open tickets on this tracker.