To Do List

From Open Source Ecology
Jump to: navigation, search


There is a large list of tasks required for the completion of the GVCS. This page explores how we can create a team to define these tasks, their requirements, and how to deploy teams to work on these tasks.

Among the classes of tasks to be done are:

  1. Tasks that require no knowledge of OSE's methods, nor that require OSE's design to even be started
  2. Tasks that require acknowledgement of OSE's design path, such as analysis and calculations of OSE's proposed design, or evaluation of a given design
  3. Tasks that require an understanding of OSE's design principles and philosophies - such as the design of an actual module or machine from scratch
  4. Tasks that focus on creating instructional materials on how to execute various tasks
  5. Study of Organizational Best Practices

Anyone can be involved in the first class of tasks, while only experienced designers - or ones who study OSE's design methodology carefully - can be involved in the third class, with the second class those in between. The fourth class can be done by anyone with a given skill set, but it would require some familiarity with the tools and methods of OSE.

There are ample opportunities for crowdsourcing on all of the classes above.

Background Tasks

There is a wealth of background knowledge required for the successful design of GVCS machines. Among the background tasks that can be defined for each machine, without ANY requirement of prior knowledge of the actual OSE design or OSE Specifications - are:

Getting Involved

Based on the Introduction above and the Background Tasks, here are some ways that students, groups, organizations, and contributors of all types can get involved.

The protocols for how one is involved, and how they document their work, should be listed below. Wiki templates that facilitate involvement should be drawn up.