This content was approved by the EdgeX TSC (12/14) and update of the EdgeX Charter, Section 4.c.
The content in this shaded section was modified by the EdgeX TSC (10/7).
Table of Contents
PROPOSED - this content is pending review and approval of the TSC and EdgeX Governing Board
This page will eventually replace contents from here: Technical Work in the EdgeX Foundry Project
Project Team Roles
Projects are driven by the people - people contributing code, documentation, tests, etc. (some product artifact) as well as volunteers that serve to oversee and manage the incoming contributions.
There are three defined roles associated with artifact contributions. Note, these definitions are based on elements from https://www.linuxfoundation.org/resources/open-source-guides/participating-open-source-communities/ and https://opensource.guide/leadership-and-governance/.
Contributor: anyone who comments on an issue or pull request, people who add value to the project (whether it’s triaging issues, writing code, or organizing events), or anybody with a merged pull request (perhaps the narrowest definition of a contributor). Anyone, whether a member of EdgeX or not, can be a contributor; for example, anyone can make a pull request on one of the GitHub repositories and make a code contribution. Any contribution must be have an appropriate DCO sign off and the author is required to follow the laws and policies with regard to copyright law, Apache 2 license agreements, and Linux Foundation policies, but all . All contributions that follow these rules and policies are greatly appreciated, subject to project review and possible incorporation into the project. A person making a contribution is deemed a contributor.
Committer: the people with commit access to EdgeX repositories. It is a committerMaintainer: Maintainers own one or several components in the projects source tree. A maintainer reviews and approves changes that affect their components. It is a maintainer's prime responsibility to review, comment on, co-ordinate, accept and accept merge additions and patches from contributors and to maintain the design cohesion of their the project components. Maintainers are listed in a MAINTAINERS list on this page for each code repository.
Larger projects may have special maintainer roles such as a release manager and stable branch maintainers. In addition, larger projects may award different maintainers different levels of influence. Any specializations and implications are documented in the respective MAINTAINERS file.
Committers are members of the EdgeX community who feel responsibility over the direction of the project and are committed to improving it. Committers hold technical leadership within the EdgeX community and are typically people who have greatly contributed to the project and are considered reliable and responsible enough to be allowed to commit directly to all or some parts of the project.
Maintainer: Maintainers create the EdgeX repository and have access rights to perform administrative functions, archive or even delete them. Often, a member of the Linux Foundation, maintainers are also committers in EdgeX by default, but typically do not participate in reviews or contribute commits to the project except in performing administrative duties or to repair a repository issueCommitter: Committers are Maintainers that are allowed to commit changes into the source code repository. The committer acts on the wishes of the maintainers and applies changes that have been approved by the respective maintainer(s) to the source tree. Due to their status in the community, committers can also act as referees should disagreements amongst maintainers arise. Committers are listed on this page for each code repository.
Nomination and Approval of Maintainers and Committers
...
By default, project working group leads (aka – working group chairpersons) are automatically committers for repositories assigned to their working group. Working TSC members (to include working group leads) can nominate and approve additional committers for repositories assigned to their working group. Approval of new committers requires the approval of 3 members of the TSC with at least two approvals coming from TSC members from different companiesto EdgeX repositories. No additional TSC member approval is required. As a courtesy, the TSC member that nominates and approves committer rights should inform the work group with responsibility over the affected repository.
Committer and maintainer changes must be submitted by a TSC member by change request to the LF release engineering via the LF Project Services web site (https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2).
The TSC chair and vice chair are automatic committers for all repositories.
The TSC may appoint (with a simple majority vote) other committers and maintainers as it sees fit based on merit (such as architectural purview of the project, knowledge of the project, volume of contributions, etc.) or need.
The TSC can, by simple majority vote, revoke the committer or maintainer privilege.
WG Leads are requested to update the lists below on the approval of any new committer or maintainer at their request. The TSC Vice Chair will update this list when a TSC committer or maintainer is added/removed on a decision taken outside of a request from a WG lead.
Current Committers List
Last Updated: 12/9/18
edgex-go (mutliple WG lead responsibility)
- @akramtexas, Akram Ahmad akramtexas
- @andyf1967, andyf1967
- @anonymouse64, Ian Johnson anonymouse64
- @brandonforster, Brandon Forster brandonforster
- @drasko, Drasko DRASKOVIC drasko
- @feclare, Fede Claramonte feclare
- @janko, isidorovic Janko Isidorovic , -isidorovic
- @jdharms, Daniel Harms jdharms
- @jduranf, Joan Duran jduranf
- @jpwhitemn, Jim White jpwhitemn
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @lenny, intel Lenny Goodell , -intel
- @michaelestrin, Michael Estrin michaelestrin
- @SteveOss, Steve Osselton SteveOss
- @tingyuz, tingyuz
- @tonyespy, Tony Espy tonyespy
- @tsconn23, Trevor Conn tsconn23
- @xmlviking, Eric Cotter xmlviking
device-sdk-go (device service WG responsibility)
- @cloudxxx8, cloudxxx8
- @jdharms, Daniel Harms jdharms
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @lenny, intel Lenny Goodell , -intel
- @michaelestrin, Michael Estrin michaelestrin
- @SteveOss, Steve Osselton SteveOss
- @tonyespy, Tony Espy tonyespy
device-sdk-c (device service WG responsibility)
- @iain, anderson iain-anderson
- @jdharms, Daniel Harms jdharms
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @lenny, intel Lenny Goodell lenny-intel
- @michaelestrin, Michael Estrin michaelestrin
- @SteveOss, Steve Osselton SteveOss
device-mqtt-go (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @lenny, intel Lenny Goodell lenny-intel
- @SteveOss, Steve Osselton SteveOss
device-modbus-go (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @lenny, intel Lenny Goodell lenny-intel
- @SteveOss, Steve Osselton SteveOss
device-random (device service WG responsibility)
- @andyf1967, andyf1967
- @cloudxxx8, cloudxxx8
- @jdharms, Daniel Harms jdharms
- @jpwhitemn, Jim White jpwhitemn
- @jwagantall, jwagantall Maintainer
- @lenny, intel Lenny Goodell , -intel
- @mhall119, Michael Hall mhall119
- @michaelestrin, Michael Estrin michaelestrin
- @SteveOss, Steve Osselton SteveOss
- @tonyespy, Tony Espy tonyespy
- @weichou1229, Bruce weichou1229
device-grove-c (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @SteveOss, Steve Osselton SteveOss
device-opcua-c (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @SteveOss, Steve Osselton SteveOss
edgex-ui-go (general TSC responsibility)
- @badboy, huaqiao badboy
- @gaofeng3695, gaofeng3695
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @thank037, 谢谢谢 thank037
- @TiejunChina, Tiejun Chen TiejunChina
- @yanghua, vinoyang yanghua
edgex-ui-clojure (general TSC responsibility)
- @cloudxxx8, cloudxxx8
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @SteveOss, Steve Osselton SteveOss
developer-scripts (general TSC responsibility)
- @akramtexas, Akram Ahmad akramtexas
- @andyf1967, andyf1967
- @brandonforster, Brandon Forster brandonforster
- @jdharms, Daniel Harms jdharms
- @jpwhitemn, Jim White jpwhitemn
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @lenny, intel Lenny Goodell lenny-intel
- @michaelestrin, Michael Estrin michaelestrin
- @tingyuz, tingyuz
- @tsconn23, Trevor Conn tsconn23
- @xmlviking, Eric Cotter xmlviking
blackbox-testing (test/QA WG responsibility)
- @akramtexas, Akram Ahmad akramtexas
- @andyf1967, andyf1967
- @cloudxxx8, cloudxxx8
- @jdharms, Daniel Harms jdharms
- @jpwhitemn, Jim White jpwhitemn
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @lenny, intel Lenny Goodell lenny-intel
- @michaelestrin, Michael Estrin michaelestrin
- @trcox, Tyler Cox trcox
ci-managment (DevOps WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
- @jwagantall, jwagantall Maintainer
- @trcox, Tyler Cox trcox
- @tsconn23, Trevor Conn tsconn23
- @tykeal, Andrew Grimberg tykeal Maintainer
- @zxiiro, Thanh Ha zxiiro Maintainer
As the Linux Foundation maintains the EdgeX repository collection, maintainers are typically appointed by the Linux Foundation and are generally employees of the LF. The TSC can approve additional maintainers by simple majority vote.
All changes to the maintainers and committers should be documented in TSC minutes and the change request submitted by the TSC chair, vice chair or appropriate working group chair to the LF releng at support.linuxfoundation.org.
Maintainers and Committers
The links below will take the reader to the list of committer/maintainer teams for each of the EdgeX repositories. The team members can be viewed under the Members tab of each team.
Committer teams: https://github.com/orgs/edgexfoundry/teams?query=committers
...
Maintainer teams: Note: For additional smaller and less used EdgeX Foundry Repository and committers lists, see https://github.com/orgs/edgexfoundry/teams, click on the repository of interest, select on the members for that repository, and then selecting the Role (Committer, Maintainer, Member) from the Role drop down.
Current Maintainers List
Last Updated: 12/9/18
edgex-go
- @JPWKU, Jeremy Phelps JPWKU Maintainer
device-sdk-go
- @JPWKU, Jeremy Phelps JPWKU Maintainer
device-sdk-c (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
device-mqtt-go (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
device-modbus-go (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
device-random (device service WG responsibility)
- @jwagantall, jwagantall Maintainer
device-grove-c (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
device-opcua-c (device service WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
edgex-ui-go (general TSC responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
edgex-ui-clojure (general TSC responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
developer-scripts (general TSC responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
blackbox-testing (test/QA WG responsibility)
- @JPWKU, Jeremy Phelps JPWKU Maintainer
ci-managment (DevOps WG responsibility)
...