Coord/tasks

= OKF tasks =

This is a fairly unordered list of tasks that have to be done to keep OKF running healthily. It is probably not complete yet.

= Planning and Project Management =


 * Make plans (RP: what kind of plans)
 * Revise plans to meet changing needs and requirements.
 * Collaborate with skilled contractors on projects
 * Where there are contracts with defined deliverables, review deliverables before passing to client
 * 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
 * Maintain an overview of activity on all live projects
 * Keep track of delivery schedules, cashflow etc on projects
 * Assess and manage risk to the organisation incurred by project work
 * Create an overview report of activity at least quarterly
 * Participate in Coordination Committee meetings
 * Help to spot opportunities for different project groups to work together, or to learn from each other's experiences
 * Identify and eliminate process duplication

= Events =


 * Organise OKCon, the OKF's annual Spring conference
 * Organise other public events on topics central to the OKF's remit
 * Identify prospective venues, partners, co-organisers, sponsors, participants

= Funding =


 * Raise funds for new work
 * Monitor the tracker and assign issues to people and followup

= Sysadmin =


 * Follow the monitoring services for OKF servers (munin, monit)
 * Fix up / centralise / configure the monitoring services
 * Listen to system alerts and act on them or assign actions
 * Set up on-call rotation/phone paging for servers
 * Make backups (and know what the priorities for services are)
 * Understand and plan automated provisioning of servers (we are somewhat tightly tied to Amazon)
 * Separate out the provision and replication of specialised services (distinct database servers e.g.)
 * Plan monitoring for new services (Rabbit, Solr etc)
 * Maintain an inventory all the running services and dependencies between them
 * Make platform choices (MTAs, uWSGI e.g) and justify and pursue them
 * Assess the relevance of running services to OKF's mission/priorities and make the arguments needed for keeping or dropping them
 * 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
 * take on responsibility for OKF infrastructure maintenance tasks (migrating the website, etc)

= Communication and Community =


 * Respond to conferences/invitations
 * Speak for OKF at conferences
 * Talk with others using OKF software to run services
 * follow up with people who've expressed interest in helping out
 * Match OKF folks to WGs they may be interested in
 * also for volunteers, identifying people, talking to people and cajoling them
 * Encouraging people to join and post to OKF mailing lists
 * Encouraging people to participate in OKF virtual and physical events/meetings
 * Encouraging people to contribute to OKF projects
 * Write to monitor on mailing lists - http://lists.okfn.org/mailman/listinfo (too many for one person)
 * Write blog posts (1 or 2 per week)
 * Solicit and publish guest blogs
 * Compiling and sending out newsletter (~2 hours every 3-4 months)
 * Index existing documentation (piratepads, trackers, wiki pages) and present a synthesis overview

= Adminstration =


 * Get paid expenses, arrange travel etc
 * Pay expenses where OKF is given funds
 * run weekly review meetings where everyone chats / reviews what is happening
 * publish actions and minutes from meetings
 * Prepare management accounts in collaboration with the Chair's administrative assistant and the Treasurer
 * Publish summary of accounts quarterly
 * Flag up potential legal problems with General Counsel

= Code =


 * Write some code
 * be in project partner discussions
 * suggest and pursue strategy if project partners are wobbling

= Miscellaneous =


 * identify what peoples' strengths are suggest where they are best focused
 * identify new people to be involved in OKF work (either paid or volunteered)
 * talk to the broader network of open knowledge interest about people who could be involved
 * agree terms of work with new people
 * commit to contracts with people
 * resolve conflicts between people within projects, where they appear
 * assess peoples work after probation period

= Unallocated =


 * Administer blog
 * follow up with people who have raised issues
 * Make sure each WG has:
 * An active coordinator
 * An actively updated calendar of events
 * A regular public meeting (e.g. bi-monthly, monthly, bi-weekly, ...)
 * Identify opportunities for new WGs
 * Identify and follow up opportunities for funding open knowledge projects (not just for OKF) at regional, national, and international levels
 * Create stubs for project documentation
 * Encourage people to document their work
 * Identify areas where projects and people need more support
 * Work with people to create project plans and documentation
 * Encourage discussion of and decision about new project proposals
 * Make lists of tasks and encourage people to adopt responsibility for them