...
- For new code that needs a new repository, push your new code to the EdgeX evaluation GitHub project space (github.com/edgexfoundry-holding). You will need to contact the EdgeX DevOps chairperson in order to get a repository created in the eval-GitHub to submit the contribution (Jeremy PhelpsJames Gregg).
- For code to be added to an existing repository, make the necessary Pull Requests (PR) through GitHub on the affected project repositories.
...
4b. The ad-hoc committee will review the contribution for general EdgeX use. However, the committee may find the contribution (or a portion of the contribution) would better exist as a project or addition to a vertical working group solution. Therefore, the ad-hoc committee may pass the contribution (or a portion of the contribution) on to the appropriate vertical working group chairperson where the same evaluation would occur, but in light of any EdgeX vertical solution.
Special note for device service contributions: the device service working group chair has documented a review process for how new device services will be examined.
IMPORTANT PROCESS NOTE: if a contributor does not begin the contribution process by working with the appropriate Working Group chairperson and getting their feedback (i.e. the contributor skips step #1 above), then the contribution can still be made and this process starts at step #2. However, the evaluation of the contribution, as described in this step #4, will generally take longer and could result in many more exchanges with the contributor to understand where it fits in the overall architecture, how it works, etc.
...
If you are not sure if your contribution qualifies as small or large, contact the chairperson of the Working Group with responsibility of the affected repository and seek their guidance. You can reach a Working Group chairperson through the appropriate Slack channel, or the email reflectors.
- Rocket ChatSlack: https://edgexfoundry.slack.com/
- Email Reflector Lists: https://lists.edgexfoundry.org/mailman/listinfo
...