In some cases we are able to commit community building effort to projects that are committed to open development and open source. These "strategic projects" receive additional assistance from us in order to bridge the gap between open development requirements and the project's funded objectives. The assistance takes the form of community development. We do not intend to do software development, that is the job of the project themselves. However, we intend to do some of the things that build a community around a project that the lead project team may not do. That is, build awareness and community beyond the immediate need of the host organisations.
In order to provide this assistance we join the community under the same conditions that any other member does. That is there is an expectation to get something out of value and that it will be greater than what is contributed. In our case we expect to increase our expertise through the experience that will also inform new published resources and support for other projects. Again as with any other community member we will leave when we no longer see the value in being involved. That may sound harsh but one of the benefits of community development is that a vibrant and diverse community will survive the loss of any member.
1. Current Projects
Project |
Status |
Review Date |
2nd openness review |
01 Jan 2010 |
|
2nd openness review |
01 Jan 2010 |
|
? |
01 Jan 2010 |
|
? |
01 Jan 2010 |
2. Previous Projects
Project |
Status |
Review Date |

