|
Size: 1658
Comment:
|
← Revision 26 as of 2015-05-27 12:28:13 ⇥
Size: 5194
Comment: Clarify how to handle filled job postings.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| 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-2014, 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 www.python.org Django based site. |
This page describes the PSF Python Job Board which is run by volunteers to provide the Python community with an important resource to find jobs where they can use Python. |
| Line 9: | Line 7: |
| == Project Mailing List == | == Job board process == |
| Line 11: | Line 9: |
| The project is run using a mailing list dedicated for the team: | 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. 1. Job submitters [[https://www.python.org/accounts/login/?next=/jobs/create/|log in to the website]] (after having registered for an account) 2. Submitters [[https://www.python.org/jobs/create/|create a job posting record]] 3. Submissions are checked against a list of quality criteria by the reviewers using the [[https://www.python.org/jobs/review/|review panel]]; see the [[/Reviewers]] page for details on the review process 4. Submissions which need refinement are rejected together with a note mentioning the reason for rejection (using the "review" button on the review panel). 4. Good submissions are approved and then automatically listed on the job board page in order of submission date (in most recent first order) Job postings are automatically unlisted after 90 days. They can also be removed or archived manually using the Django database interface by setting the job listing status setting to ''removed''. Remarks: * Submissions which have problems could also be refined directly in the system by the submitters, provided they created it while being logged in. The review page doesn't show this status, though, so it's probably better to go with the rejection procedures for the time being. * Reviews by multiple persons would need to be coordinated, since the system does not provide this functionality. For the time being, it's better to have one person do the review. == Project organization == The job board team has decreased a lot due to the long project run time. We will launch with a small team of reviewers: * [[/Reviewers]] - team members who review job postings The review process is also described on the above page. Issues we find are posted to the [[https://github.com/python/pythondotorg/issues|python.org site's issue tracker]] and tagged with "job board". The issues are then either worked on by the PSF contractors assigned to the python.org website project, or volunteers who want to help. The job board team itself will not focus on the development anymore for the time being. == Mailing list == The volunteers use a mailing list to coordinate: |
| Line 15: | Line 44: |
| 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. | The list gets all email sent to jobs@python.org. In the previous system, job postings were sent in via email. This is no longer necessary and new submissions should only be done via the [[https://www.python.org/jobs/create/|web interface]]. The jobs app will send notification about new postings to this list, so that reviewers get notified of new submissions. |
| Line 19: | Line 50: |
| Here's the mailing list archive: * [[https://mail.python.org/mailman/private/jobs/|Python Jobs List Archive]] (requires login) == Relaunch Project == In the years before the relaunch, the jobs board was run by single volunteers. Since the load had increased a lo and the last volunteer, Chris Withers, had left the project, the PSF wanted to replace the jobs board with a team of volunteers using a database driven integrated jobs app. From 2014 to 2015, a team of volunteers worked to relaunch the job board using a jobs app on the new python.org website (which was launched in 2014). The relaunch project page is still available: [[/Relaunch Project]] |
|
| Line 21: | Line 64: |
| * [[http://www.python.org/jobs/|New job board]] | === Production === |
| Line 23: | Line 66: |
| This will be the new location of the Python job board, run using Django and backed by a database. | ''Note: The jobs app used to run under the temporary URL /newjobs/ during development. This has now been changed back to /jobs/.'' |
| Line 25: | Line 68: |
| '''Note: At the moment this still redirects to the legacy website.''' | * [[http://www.python.org/jobs/|Job board jobs listing]] on the production site. |
| Line 27: | Line 70: |
| * [[http://www.python.org/community/jobs/|Job board listing ported from the legacy site]] | * [[http://www.python.org/jobs/review/|Job board review panel]] |
| Line 29: | Line 72: |
| This is a single page which has to be manually maintained via the Django admin interface. | This allows reviewing new job postings. |
| Line 31: | Line 74: |
| * [[http://legacy.python.org/community/jobs/|Legacy job board site]] | === Staging === |
| Line 33: | Line 76: |
| This page was manually maintained through the Subversion repository which runs the legacy website. | ''Note: The jobs app used to run under the temporary URL /newjobs/ during development. This has now been changed back to /jobs/.'' |
| Line 35: | Line 78: |
| * [[http://legacy.python.org/community/jobs/howto/|Job board how-to explaining the process that was used for the legacy site]] | The staging system can be used to check new developments. * [[https://staging.python.org/jobs/|Staging system implementation of the new job board]] This runs a copy of the production database on the master branch of the python.org repository and is updated frequently. * [[http://staging.python.org/jobs/review/|Staging system job board review panel]] on the staging site. === Web site administration === * [[https://www.python.org/admin/|Django admin interface of the python.org site]] * [[https://github.com/python/pythondotorg/issues|New site's issue trackers]] If you find problems with the job app, please open tickets on this tracker. === Web site code base === * [[https://github.com/python/pythondotorg|Github repository of the new site]] (includes the jobs app) * [[https://github.com/python/pythondotorg/tree/master/jobs|Job app code]] |
PSF Python Job Board
This page describes the PSF Python Job Board which is run by volunteers to provide the Python community with an important resource to find jobs where they can use Python.
Contents
Job board process
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 using the review panel; see the /Reviewers page for details on the review process
- Submissions which need refinement are rejected together with a note mentioning the reason for rejection (using the "review" button on the review panel).
- Good submissions are approved and then automatically listed on the job board page in order of submission date (in most recent first order)
Job postings are automatically unlisted after 90 days. They can also be removed or archived manually using the Django database interface by setting the job listing status setting to removed.
Remarks:
- Submissions which have problems could also be refined directly in the system by the submitters, provided they created it while being logged in. The review page doesn't show this status, though, so it's probably better to go with the rejection procedures for the time being.
- Reviews by multiple persons would need to be coordinated, since the system does not provide this functionality. For the time being, it's better to have one person do the review.
Project organization
The job board team has decreased a lot due to the long project run time. We will launch with a small team of reviewers:
/Reviewers - team members who review job postings The review process is also described on the above page.
Issues we find are posted to the python.org site's issue tracker
- and tagged with "job board". The issues are then either worked on by the PSF contractors assigned to the python.org website project, or volunteers who want to help.
The job board team itself will not focus on the development anymore for the time being.
Mailing list
The volunteers use a mailing list to coordinate:
The list gets all email sent to jobs@python.org. In the previous system, job postings were sent in via email. This is no longer necessary and new submissions should only be done via the web interface.
The jobs app will send notification about new postings to this list, so that reviewers get notified of new submissions.
If you want to help in the job board team, please write to jobs@python.org.
Here's the mailing list archive:
Python Jobs List Archive (requires login)
Relaunch Project
In the years before the relaunch, the jobs board was run by single volunteers. Since the load had increased a lo and the last volunteer, Chris Withers, had left the project, the PSF wanted to replace the jobs board with a team of volunteers using a database driven integrated jobs app.
From 2014 to 2015, a team of volunteers worked to relaunch the job board using a jobs app on the new python.org website (which was launched in 2014).
The relaunch project page is still available: /Relaunch Project
Resources
Production
Note: The jobs app used to run under the temporary URL /newjobs/ during development. This has now been changed back to /jobs/.
Job board jobs listing on the production site.
Job board review panel This allows reviewing new job postings.
Staging
Note: The jobs app used to run under the temporary URL /newjobs/ during development. This has now been changed back to /jobs/.
The staging system can be used to check new developments.
Staging system implementation of the new job board This runs a copy of the production database on the master branch of the python.org repository and is updated frequently.
Staging system job board review panel on the staging site.
Web site administration
New site's issue trackers If you find problems with the job app, please open tickets on this tracker.
Web site code base
Github repository of the new site (includes the jobs app)