1. Building trust
Riitta Piela

2. Using Catalogue…
Try to understand (identify) the end users of catalog: are they always software developers?
All this (implementation) translated to possible end users in “Clear Finnish” (no IT jargon)
Software developer in a single NSI don’t make the decision of implementing a CSPA service (how does the process work?)
Open Source is the only solution, but more information of Open Source ideology is needed
how the process works?
how can you identify a reliable service?
7/25/2019
Riitta Piela

3. Developers Work as “software vendor” (how do you prove your skills?)
How can you tell that the vendor will be with you for the long haul? (and which will disappear after the next outsourcing?)
Building trust: more about use (in production) and about the methods used
Open source community around CSPA services is quite small
How to create a bigger community around katalog’s services for example in Github?
Collaboration needed at many levels…
7/25/2019
Riitta Piela

4. Open source “SLA”
Different aspects: quality, availability, responsibilities
Tests needed for fixing bugs
Is the “service provider” ready to fix bugs or accept pull requests?
Versioning
References:
is the service already somewhere in production?
the community on the background?
status of CI/CD –pipe?
7/25/2019
Riitta Piela

5. CSPA
There are considerations concerning costs sharing during the design phase
Nothing about sharing costs during the maintenance phase
How to combine the open source ideology and statistical software development
7/25/2019
Riitta Piela