Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Replaced unmaintained lists with hyperlinks to query dynamically from Github (in coordination with Jim White)

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

ePROPOSED - 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. 

...

Maintainer:  Maintainers create the EdgeX repository and have access rights to perform administrative functions, archive or even delete the repositorythem.  Often, a member of the Linux Foundation, maintainers are also committers in EdgeX by default, but typically do not participate in review reviews or contribute commits to the project except in performing administrative duties or to repair a repository issue.

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 companies.  Nominations are initiated via email to the TSC (edgex-tsc@lists.edgexfoundry.org) and approvals must be documented in TSC meeting minutes.  On approval, an email must be sent from the TSC chair, TSC vice-chair or applicable WG Lead to helpdesk@edgexfoundry.org to formally get the LF release engineer (releng) to add the new committerto 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.

...

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 helpdesk@edgexfoundrysupport.linuxfoundation.org.

...

Maintainers and Committers

The links below will take the reader to the list of committerscommitter/maintainers maintainer teams for each of the active EdgeX repositories.

Committers

Maintainers

...

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

https://github.com/orgs/edgexfoundry/teams

...

?

...

query=

...

For smaller, archived or less used EdgeX Foundry Repository committer / maintainer 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.

...

maintainers

...

Current Committers List

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

security-api-gateway (Security WG responsibility)

  • @alain2s,Alain Pulluelo alain2sf
  • @Dunstable, Dunstable
  • @Ferriera, Ferriera
  • @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

security-secret-store (Security WG responsibility)

  • @alain2s,Alain Pulluelo alain2sf
  • @Dunstable, Dunstable
  • @Ferriera, Ferriera
  • @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

Current Maintainers List

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)

  • @JPWKU, Jeremy Phelps JPWKU Maintainer
  • @jwagantall, jwagantall Maintainer
  • @tykeal, Andrew Grimberg tykeal Maintainer
  • @zxiiro, Thanh Ha zxiiro Maintainer

security-api-gateway (Security WG responsibility)

  • @JPWKU, Jeremy Phelps JPWKU Maintainer

security-secret-store (Security WG responsibility)

...