Contribution model for Fiscal Data Package

[pwalsh]

trafficstars

Description

See discussion here and here.

I proposed a high-level outline for a feedback stage, based on a draft done in the open, with primary work done by @pwalsh @akariv and @rufuspollock . @timgdavies made some good suggestions here, and we'll move towards this after the current spike draft for v1, designed for sharing and consultation with GIFT Stewards.

Tasks

• [x] Work it out

[pwalsh]

Based on the links in the first post on this issue, input from Tim here, and a general notion of what is needed, and practical in the given project constraints, I suggest the following points to form the contribution model for Fiscal Data Package v1, and as a basis for the future:

• A core team of @rufuspollock @akariv and @pwalsh are authoring a draft v1 specification. There is very little outside contribution at this first draft stage. This is based on two simple facts:
  • The work we set out for v1 is based on issues we have discussed in implementing systems around Fiscal Data Package v0.3, and so we are largely concerned with addressing that in terms of the spec itself
  • The need for better documentation has been established, we are painfully aware of it, and others have given feedback on it. We think this can be addressed by feedback on draft iterations, rather then gathering feedback now before we draft v1 changes
• An early draft of changes will be shared with GIFT Stewards in mid-October. It will also be publicly accessible
• Once we address initial feedback from GIFT Stewards and incorporate any changes needed, we will publish the next draft iteration, backed by a wider feedback stage. How the feedback stage is managed will be discussed here, but in general, I think we should limit this to a 6 week feedback phase (again, this is a pragmatic choice based on project constraints)
• After the 6 week phase, we will incorporate any changes agreed upon into a v1 beta release of the specification. Based on this beta release, we will start to implement changes in the OpenSpending platform to support the v1 specification, and use this work to improve the specification and move towards a release candidate
• After at least one call for comments on the release candidate, we'll aim to release Fiscal Data Package v1 in January 2018

Comments @DianaMPG @timgdavies @jpmckinney @pudo @akariv @rufuspollock ?