1*2ec80375SAndrew JefferyHow to use this list: 2*2ec80375SAndrew Jeffery Find the most specific section entry (described below) that matches where 3*2ec80375SAndrew Jeffery your change lives and add the reviewers (R) and maintainers (M) as 4*2ec80375SAndrew Jeffery reviewers. You can use the same method to track down who knows a particular 5*2ec80375SAndrew Jeffery code base best. 6*2ec80375SAndrew Jeffery 7*2ec80375SAndrew Jeffery Your change/query may span multiple entries; that is okay. 8*2ec80375SAndrew Jeffery 9*2ec80375SAndrew Jeffery If you do not find an entry that describes your request at all, someone 10*2ec80375SAndrew Jeffery forgot to update this list; please at least file an issue or send an email 11*2ec80375SAndrew Jeffery to a maintainer, but preferably you should just update this document. 12*2ec80375SAndrew Jeffery 13*2ec80375SAndrew JefferyDescription of section entries: 14*2ec80375SAndrew Jeffery 15*2ec80375SAndrew Jeffery Section entries are structured according to the following scheme: 16*2ec80375SAndrew Jeffery 17*2ec80375SAndrew Jeffery X: NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!> 18*2ec80375SAndrew Jeffery X: ... 19*2ec80375SAndrew Jeffery . 20*2ec80375SAndrew Jeffery . 21*2ec80375SAndrew Jeffery . 22*2ec80375SAndrew Jeffery 23*2ec80375SAndrew Jeffery Where REPO_NAME is the name of the repository within the OpenBMC GitHub 24*2ec80375SAndrew Jeffery organization; FILE_PATH is a file path within the repository, possibly with 25*2ec80375SAndrew Jeffery wildcards; X is a tag of one of the following types: 26*2ec80375SAndrew Jeffery 27*2ec80375SAndrew Jeffery M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>; 28*2ec80375SAndrew Jeffery if omitted from an entry, assume one of the maintainers from the 29*2ec80375SAndrew Jeffery MAINTAINERS entry. 30*2ec80375SAndrew Jeffery R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>; 31*2ec80375SAndrew Jeffery these people are to be added as reviewers for a change matching the repo 32*2ec80375SAndrew Jeffery path. 33*2ec80375SAndrew Jeffery F: Denotes forked from an external repository; has fields URL. 34*2ec80375SAndrew Jeffery 35*2ec80375SAndrew Jeffery Line comments are to be denoted "# SOME COMMENT" (typical shell style 36*2ec80375SAndrew Jeffery comment); it is important to follow the correct syntax and semantics as we 37*2ec80375SAndrew Jeffery may want to use automated tools with this file in the future. 38*2ec80375SAndrew Jeffery 39*2ec80375SAndrew Jeffery A change cannot be added to an OpenBMC repository without a MAINTAINER's 40*2ec80375SAndrew Jeffery approval; thus, a MAINTAINER should always be listed as a reviewer. 41*2ec80375SAndrew Jeffery 42*2ec80375SAndrew JefferySTART OF MAINTAINERS LIST 43*2ec80375SAndrew Jeffery------------------------- 44*2ec80375SAndrew Jeffery 45*2ec80375SAndrew JefferyM: Ed Tanous <ed.tanous@intel.com> <edtanous!> 46*2ec80375SAndrew JefferyM: James Feist <james.feist@intel.com> <jfei!> 47*2ec80375SAndrew JefferyM: Vernon Mauery <veron.mauery@linux.intel.com> <vmauery!> 48