Consider improvements to member onboarding template

[clausmullie]

Some older work that set out to make two improvements to the membership proposal template

This work was done to make it more directed at a) the actual likely problems a government organization may face, and b) the likely benefits codebase stewardship will have in the organization.

Can be merged into the current template, or perhaps included somewhere else.

## The challenges of digitalizing as a government organization

Software-as-digital-public-infrastructure is increasingly core to the succesful functing of any public organization.
This ranges from back-end digital systems that support existing activities (such as traffic or waste management) or entirely new digital systems (such as open data portals or data-driven decision making tools).

As public organizations mature in their approaches to their digital public infrastructure, typical challenges include: 
* **Operational delivery**: developing the exertise to operationally manage digital innovation projects, including in-house development, procurement, and the management of third party vendors, often without in-house technical expertise 
* **Governance**: understanding the interplay between political governance (policy and legal code) and the decisions that are encoded into software.
* **Economies of scale and silos**: learning to work together with partner-organizations to collaborative around a single shared system, rather than each having their own 
* **Sustainable relationships with third parties**: avoiding lock-in situations, in which the organization's data and/or digital workflow is controlled by an third party, leading to a reduced autonomy and potentially prohibitive liscensing, upgrade and migration costs
* **Future-proofing**: understanding how decisions about their digital public infrastructure will open up or limit possibility of future upgrades, add-ons and innovation potential in the future
* **Technical debt**: working around an ever increasing set of aging digital systems that create dependies and a potential drag on service delivery
* **Balancing local and global**: stiking a balance between existing offers of global parties, while still investing in local businesses

## What can codebase stewardship mean for my organization?
## What can codebase stewardship mean for my organization?

### Within own org dev process
codebase stewardship and standard:
* find reliable existing code
* stability in turnover of staff
* legible code for long term maintenance 
* agile policy interventions, ensuring tech reflects policy accurately 
* future-proof systems which are easier to upgrade and add-on to quickly 
* clean documentation, 
* tool to improve communication and collaboration within multidisciplinary teams 
* make your projects more attractive for funding, from internal or external sources (eg EU or private) 

### Your collaboration with external development or implementation parties
codebase stewardship and standard:
* tested and reliable standard
* easier to set up multi-vendor collaboration
* interchanability of vendors making more diverse and reliable acccess to market partries

### For development or implementation parties you work with
codebase stewardship and standard:
* reduce risk and uncertainty for vendors thanks to professionalised procurement and monitoring process
* satisfaction of building high quality, reusable and scalable code
* community management to ensure dev happiness and improve collab with other venders working on same codebase
* marketing and productification of their code to help their work scale
* implementation support to ensure dev can focus on dev, implement can focus on implement

### Collab with other public org
codebase stewardship and standard:
* economy of scale to share maintenence costs and burden, as well as leverage each others' investments in new features and upgrades
* neutral quality guarantee to reassure all parties of contributed code
* netural oversight over common assets (such as documentation, community vibe and events, generic product marketing)
* more attractive collaboration for others to join and further increase economy of scale 

### Codebase ecosystem level
* large, healthy and diverse community of public organizations and venders maintaining and contributing 
* hedge risk and ensure longgevity
* security, quality and cost effectiveness of open source at scale, mirroring projects like linux etc. 

### For citizens, residents, end-users, and general public
*