Development Process Transparency: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
No edit summary
Line 10: Line 10:
*participants filling out the [[Team Culturing]] survey
*participants filling out the [[Team Culturing]] survey
*following the [[Web Collaboration Strategy]]
*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]]; evaluating [[Bid Proposals]] with the [[Technical Review Team]]
*project funding being voted with the wallets of funders.
*project funding being voted with the wallets of funders, and the [[GVCS Development Priorities]] for any blank votes


For the last point, it may be instructive to develop
For the last point, it may be instructive to develop an explicit voting page. Any donor has the opportunity to vote on a project. A project will be begun upon the necessary [[Development Prerequisites]] being met according to the [[GVCS Development Template]].

Revision as of 09:33, 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:

For the last point, it may be instructive to develop an explicit voting page. Any donor has the opportunity to vote on a project. A project will be begun upon the necessary Development Prerequisites being met according to the GVCS Development Template.