... | ... | @@ -25,8 +25,8 @@ 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|
|
|
|
| git repository | <ul><li> pull requests to add env </li><li> continuous integration to build and test the recipe </li></ul> | <ul><li> gitlab in2p3: accounts and access </li><li> not all OSSR advantages </li></ul> |
|
|
|
| OSSR | <ul><li> versioned, archived, citable, discoverable </li><li> same metadata schema as other OSSR entries </li><li> many sources (can be managed on whatever platform, be part of several communities...) </li></ul> | <ul><li> curation process? only one curator at the moment </li><li> no merge request process with direct feedback, trial and error to reach accepted recipe </li></ul>|
|
|
|
|
|
|
Can we get the best of both worlds?
|
|
|
- central git repo --> archived in OSSR = NOT a good solution
|
... | ... | |