At the WP lead meeting we agreed development models shouldn’t be too closely defined in beginning. Iterative process starting small and testing different ways to see which works best. With vary based on partners, their resources, the challenge and solution, how much overlap/work there is to do
Collaboration can include face to face to keep community active, but it should be structured so that different developers, partners, and non-SCORE cities can easily incorporate themselves after projects have started to continue working on solutions.
We should have a community manager for developers. This includes communication portal (slack?), have overview of who is collaborating with who, and monitor mutual quality assurance process. Also answering questions about the charter/guidelines on data publishing, etc.
We could use Docker, Heroku and micro services containers to facilitate collaboration, and include a designated space for code-sharing. This means people can deploy software without having to set up own servers which avoids having to reconstruct specific environments, at least for the QA, test and prototype production.
Two possible governance structures for solution development:
- Leader/follower
One city pioneers, and actively develops solution with support of other subscriber cities. Pioneer helps subscribers to also integrate in their cities - Full collaboration
Full collaborative development between cities
Three possible ways of developing together:
- Working on the same solution at the same time
- Working on different components which can later be integrated into a single solution
- Work on alternative approaches and solutions to solving the same problem
This is a core component of SCORE - how would you set up the collaboration structure?