Coord/ckan

= CKAN Coordination =

This page is an attempt to set out the task list for CKAN so we can identify where the are the key areas in which the project needs more coordination and clear decision making

CFP: Project Manager for CKAN Project
For more information contact: info@ckan.org - Apply at jobs@okfn.org 

The Open Knowledge Foundation (http://okfn.org/) is seeking a project-manager to handle projects related to its open-source CKAN software (http://okfn.org/projects/ckan/) for partners and clients including data.gov.uk. Responsibilities include:


 * Represent the project at meetings with partners and clients
 * Manage the project team, keeping in touch with developers and the wider community
 * Plan iterations with developers of project work and handle reporting (and track issues)
 * Ensure project documents are complete, current, and stored appropriately
 * Communicate project progress to partners and clients as well as the OKF community and wider public
 * Manage project budgets
 * Track team hours and expenses

Some technical knowledge/experience required. Experience with coding (especially with web-applications and relational databases) would be a plus but not required.

About CKAN
CKAN is a registry or catalogue system for datasets or other "knowledge" resources. CKAN aims to make it easy to find, share and reuse open content and data, especially in ways that are machine automatable. CKAN is currently being used to power the UK Governments open data portal data.gov.uk, publicdata.eu as well as numerous other data portals around the world. See http://ckan.org for more information.

CKAN is a web-application written in python using a relational DB. It utilizes components such as Pylons webapp framework, SQLAlchemy ORM, Postgresql database, Solr index, and Rabbitmq messaginging system.

Tasks
Cf. The longer OKF task list, everything here should be reflected there, e.g. everything on this list (apart from really CKAN specific things) either comes from that list or should be on it.


 * Plan iterations of project work
 * Define outcomes attached to iterations
 * Work with developers to keep on track with plans
 * Keep clients and partners on paid projects up to date with progress
 * Listen to and document partner concerns around projects
 * Ensure project documents are complete, current, and stored appropriately
 * Communicate project progress to the OKF community and wider public
 * Manage project budgets
 * Track team hours and expenses
 * Monitor the tracker and assign issues to people and followup
 * Participate in the project mailing list(s)
 * Run regular meetings and publish notes from them
 * Maintaining service uptime level
 * Managing the hosting infrastructure
 * Identify dependencies between projects (at a technical level - e.g. CKAN -> LOD2) and make sure that everyone is aware of impact of any changes or new requirements
 * Resolve conflicts between people within projects, where they appear
 * Assess peoples work after probation period
 * Follow up with people who have raised issues
 * Follow up with people who've expressed interest in helping out

Potentially also:
 * Make platform choices (Squid/Varnish, RDBMS->RDF e.g) and justify and pursue them
 * Find new people who could be involved (coding, UI, running local CKANs etc)
 * Agree terms of work with new people
 * Commit to contracts with people