Development Process Transparency: Difference between revisions
Jump to navigation
Jump to search
(Created page with "GVCS Development Process Transparency involves documentation of: *clarity on the goals *the identity, skill base, and commitments of the team *the development process procedures ...") |
No edit summary |
||
| Line 9: | Line 9: | ||
*following the [[50/2/2]] goal | *following the [[50/2/2]] goal | ||
*participants filling out the [[Team Culturing]] survey | *participants filling out the [[Team Culturing]] survey | ||
*following the [[Web Collaboration | *following the [[Web Collaboration Strategy]] | ||
*adhering to [[OSE Specifications]] and calculating an [[OSE Specifications Score]] | *adhering to [[OSE Specifications]] and calculating an [[OSE Specifications Score]] | ||
*project funding being voted with the wallets of funders. | *project funding being voted with the wallets of funders. | ||
For the last point, it may be instructive to develop | For the last point, it may be instructive to develop | ||
Revision as of 09:29, 17 February 2011
GVCS Development Process Transparency involves documentation of:
- clarity on the goals
- the identity, skill base, and commitments of the team
- the development process procedures
- evaluation procedures
- decision-making processes
For technical GVCS development, this is satisfied, respectively, by:
- following the 50/2/2 goal
- participants filling out the Team Culturing survey
- following the Web Collaboration Strategy
- adhering to OSE Specifications and calculating an OSE Specifications Score
- project funding being voted with the wallets of funders.
For the last point, it may be instructive to develop