Project management:Current tasks

Welcome to the current tasks of the project management department!

Right away

 * Add fields of work terminology to glossary and membership articles
 * Go over split up help wanted articles with the other lead devs and see what should be added/changed
 * Document content >> code/assets/documentation terminology
 * Request feedback concerning How_to_work_with_proposals
 * Invite the writers to spend 1 month with us
 * This might result in a heavy workload for the developers due the amount of required communication and coordination
 * Fire interested writer at gdnet and blooddoll an email as soon as we've worked out a starting task
 * Reread Scrum book and extract notes about:
 * Project backlog
 * Sprint concept, pre sprint meeting, post sprint meeting
 * How to define "done"?
 * Take care of Wiki maintenance tasks

Set back

 * Add commit guidelines to how to use SVN articles of the departments; how about revert guidelines? when should we try to revert changes?
 * Sepearate How to use Trac articles for each department; featuring information how trac is utilized in this specific department and providing templates for common trac tasks
 * Take into account that the workflow might be slightly different for developers with SVN write access and occasional contributors who send in their code/assets
 * Incorporate "one username prefered" policy into contribution guidelines
 * Functional requirements are part of feature proposal articles; smaller feature requests are created as trac tickets after initial feedback has been requested at IRC and/or forums
 * Items: description + backstory (writing department) & stats (mechanics department)
 * Creative vision: WHAT do we want to create? Why do we want to create it this way?
 * Department philosophy: HOW do we want to create it? Why do we approach the process in the way we do?
 * Department-specific wiki editing guidelines
 * Do further research on dual licensing assets (baked vs. raw ones)
 * Extract proposals how the Scrum framework could be applied to improve PARPG development from Agile game development with Scrum
 * Flesh out long term proposal to switch to Distributed version control software; incorporate feedback given here:
 * http://www.gamedev.net/community/forums/topic.asp?topic_id=589797
 * http://stackoverflow.com/questions/4389578/can-artists-realistically-cope-with-distributed-version-control-in-an-open-sour