| ... | ... | @@ -12,7 +12,7 @@ The document summarised the collection of best practices for |
|
|
|
| Choice of Development Platform | development | internal and external platforms, both open source and commercial | github and gitlab | harmonisation needed? | none |
|
|
|
|
| Continuous Integration/Deployment | deployment | automated platform for CI/CD including software tests | gitlab/github CI/CD | harmonisation | harmonisation |
|
|
|
|
| Containerisation | development, deployment, archiving, maintenance | containers as overarching solution for flexible software distribution and handling | including Kubernetes | research (overview gathering) | development |
|
|
|
|
| Avoiding Vendor Lock-In | general |
|
|
|
|
| Avoiding Vendor Lock-In | general | vendor lock-in should be avoided by using general approaches or use global common services where vendor transfer is highly probable | e.g. use make files for tests, github as global standard| research | adoption |
|
|
|
|
| Prepare software for archiving, choose archive | Archiving | Archives available, OSSR will help | Zenodo, Software Heritage | automation in OSSR | harmonisation |
|
|
|
|
| Maintenance takes more resources than development | Maintenance | Most projects focused on development, maintenance took into consideration by the platform, resources only partly available | funding for long-term maintenance not securable | raise awareness | harmonisation |
|
|
|
|
|
