PostNuke Organizational Structure

Task Forces

Task forces may be formed as necessary for individual tasks. An example of this are is PostNuke site redesign task force. These are more dynamic team elements, led by a specific member of the PostNuke team (not necessarily a team leader named above). Task forces are more temporary, and could include members of the community who are not PostNuke team members but offer a specific skill set needed for the task in hand. Leaders of task forces should also report to the Steering Committee monthly.

Reporting Structure

Each team and task force leader should report to the PostNuke Steering Committee approximately once per month outlining progress (if any has been made). 'Reporting' is meant in a loose sense, and can be a quick informal chat or an email. This information is then combined with information on the activities of the Steering Committee and sent to the postnuke-teams list for internal review. When internal discussions on the information presented have taken place (this could be setting goals, making suggestions, improving plans), a community announcement should be made.

This is not set in stone. Everyone is a volunteer and timescales are flexible as a result. It is also entirely acceptable to report 'nothing has been done', providing the project can be seen to progress at regular intervals. Deadlines and completion dates will not be set unless absolutely necessary, such as when one project is dependent upon the actions of another. In general, flexibility is the key.

Team Members

Team leaders in bold.

All teams come under the Steering Committee excepting development, which at this time has autonomy for the purposes of keeping the development of PostNuke software objective.