-
Current location: https://software.llnl.gov/about/policies/
Consists of: 18 markdown files (https://github.com/LLNL/llnl.github.io/tree/main/pages/project/policies)
Questions & possible tasks:
…
-
Adding the Contributor Guidelines.
-
There seems to be agreement to discontinue the securesystemslib schema facility (see https://github.com/secure-systems-lab/securesystemslib/issues/183). We still need to be able to validate all **inpu…
-
The [contribution docs say](https://github.com/theupdateframework/tuf/blob/develop/docs/GOVERNANCE.md#contributions), new software features or changes must be unit tested, but the current test suite i…
-
Add a document for stating the contributing guidelines. These can also include things like:
- [x] signing your commits (which should nevertheless be tested by the CI)
- [x] following the 50/72 guide…
-
Modularity
Single Responsibility
etc.
-
"Having firm guidelines on project management and getting involved is extremely valuable"
@kayabaNerve
https://github.com/MerosCrypto/Meros#contributing this is not enough, will research on some …
-
Add a section in README to call out contribution guidelines. This will include steps to import the code into local machine, make change, build, test etc.
-
We should utilize GH issue and pull request template as well as contributing guidelines to make it easier for contributors to add components. The data format is still work in progress, but as soon it …
-
- [ ] All endpoints should be fully tested. The Rails Driver Spec Harness is not a substitute for writing your own tests.
- [ ] All endpoints will expect to return JSON data
- [ ] All endpoints shou…