Differences between revisions 9 and 10
Revision 9 as of 2014-03-05 13:50:13
Size: 6960
Comment:
Revision 10 as of 2014-03-05 13:58:06
Size: 6960
Comment:
Deletions are marked like this. Additions are marked like this.
Line 80: Line 80:
== Project Organization == == Project organization ==

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.

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.

  1. Job submitters created a job posting based on the template listed on the Job board how-to page

  2. Submissions were checked against a list of quality criteria
  3. Submissions which needed refinement were sent back with a notice of what to fix
  4. 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.

  1. Job submitters log in to the website (after having registered for an account)
  2. Submitters create a job posting record
  3. Submissions are checked against a list of quality criteria by the reviewers
  4. Submissions which needed refinement are flagged and an email is sent back to the job submitter asking for changes
  5. 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

Jobs app design

The jobs Django app is already available, but not yet complete.

To get it to a usable state, we'll have to work some more on the code and the templates. Here's what we need to do:

  • review the existing app
  • come up with user stories to define the workflows and UI
  • open tickets and implement the changes necessary to make those user stories work

Please run reviews of the existing app and post them on the review page:

We collect user stories on this page:

Project organization

Roles

We have so far identified these roles in the team:

  • /Reviewers - team members who review job postings and help giving usability feedback to the developers

  • /Developers - team members with Django skills to help with improving the Django app

We will also need leaders of both groups and possibly an overall project lead to coordinate the work of the groups and provide an interface to the PSF board.

Once established, we should transfer the project into a regular PSF work group.

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:

The last processed job submission is dated 12-Feb-2014.

Issue tracker

Please open tickets for any problems you find with the jobs app. The tickets should be labeled as "job board", if possible (github restricts using labels). If not possible, please prefix the ticket title with "JB:" or use "job board" in the title. We can then add labels after ticket creation.

Resources

New job board

  • New job board This is a temporary location of the new Python job board, run using Django and backed by a database.

  • New job board This will be the production location of the Python job board.

    Note: At the moment this still redirects to the legacy single page job board.

Old job board

Web site administration

Web site code base

PSF Python Job Board (last edited 2015-05-27 12:28:13 by MarcAndreLemburg)

Unable to edit the page? See the FrontPage for instructions.