... | ... | @@ -26,4 +26,9 @@ centralized git repository vs OSSR |
|
|
| | Advantages | Drawbacks |
|
|
|
|---|---|---|
|
|
|
| git repository | - pull requests to add env // - continuous integration to build and test the recipe | - gitlab in2p3: accounts and access // - not all OSSR advantages |
|
|
|
| OSSR | - versioned, archived, citable, discoverable // - same metadata schema as other OSSR entries // - many sources (can be managed on whatever platform, be part of several communities...) | - curation process? only one curator at the moment // - no merge request process with direct feedback, trial and error to reach accepted recipe| |
|
|
\ No newline at end of file |
|
|
| OSSR | - versioned, archived, citable, discoverable // - same metadata schema as other OSSR entries // - many sources (can be managed on whatever platform, be part of several communities...) | - curation process? only one curator at the moment // - no merge request process with direct feedback, trial and error to reach accepted recipe|
|
|
|
|
|
|
Can we get the best of both worlds?
|
|
|
- central git repo --> archived in OSSR = NOT a good solution
|
|
|
- a recipe should be a single identifiable record
|
|
|
- GitHub actions? How to use the CI to get from a centralized repository to single OSSR records? |
|
|
\ No newline at end of file |