openIDL Navigation
...
Here is a video on contributing to opensource. Here is a course on how to contribute to open source : - https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github
There is also a readme.md file at the top level that guides common activities.
The application components run in kubernetes. As a result, they must be packaged as images that can be picked up by the deployment specs.
Local development works differently for this than for production uat and production releases.
The flow of activities is something like this:
First pull or fork the latest from the develop branch.
...
Every pull request must follow the guidelines set here to be approved and considered for merging. Every pull request should be linked to a reported GitHub Issue in the openIDL project. Pull requests have been set up with checks that all have to pass. At least two maintainers should approve the pull request.
Rule | Required | Comment |
---|---|---|
2 Approvals from maintainers from two different organizations | ||
The pull request is linked to a GitHub Issue (new feature or a bug) | ||
Developer Certificate of Origin (DCO) | Always commit your changes with git commit -s (--signoff) | |
Automated builds pass | ||
Automated tests pass |
Name | Organization | GitHub ID |
---|---|---|
Jeff Braswell | openIDL | tahoeblue |
Sean Bohan | openIDL | SeanBohan |
Ken Sayers | AAIS | kens-aais |
Peter Antley | AAIS | antleypk2 |
Aashish | Chainyard | aashishchainyard |
Surya Lanka | Chainyard | suryalanka-cy |
Tsvetan Georgiev | Senofi | TsvetanG |
Yanko Zhelyazkov | Senofi | yzhivkov |
Note |
---|
New maintainers are welcome. |
Each subdirectory has a readme.md file that helps with the details of local development.
...