github.com/ijc/docker-app@v0.6.1-0.20181012090447-c7ca8bc483fb/MAINTAINERS (about)

     1  # Docker maintainers file
     2  #
     3  # This file describes who runs the docker/app project and how.
     4  # This is a living document - if you see something out of date or missing, speak up!
     5  #
     6  # It is structured to be consumable by both humans and programs.
     7  # To extract its contents programmatically, use any TOML-compliant
     8  # parser.
     9  #
    10  # This file is compiled into the MAINTAINERS file in docker/opensource.
    11  #
    12  [Org]
    13  
    14  	[Org."Core maintainers"]
    15  
    16  	# The Core maintainers are the ghostbusters of the project: when there's a problem others
    17  	# can't solve, they show up and fix it with bizarre devices and weaponry.
    18  	# They have final say on technical implementation and coding style.
    19  	# They are ultimately responsible for quality in all its forms: usability polish,
    20  	# bugfixes, performance, stability, etc. When ownership  can cleanly be passed to
    21  	# a subsystem, they are responsible for doing so and holding the
    22  	# subsystem maintainers accountable. If ownership is unclear, they are the de facto owners.
    23  
    24  		people = [
    25  			"chris-crone",
    26  			"mat007",
    27  			"mnottale",
    28  			"shin-",
    29  			"silvin-lubecki",
    30  			"vdemeester",
    31  		]
    32  
    33  	[Org."Docs maintainers"]
    34  
    35  	# TODO Describe the docs maintainers role.
    36  
    37  		people = [
    38  			"thajeztah"
    39  		]
    40  
    41  	[Org.Curators]
    42  
    43  	# The curators help ensure that incoming issues and pull requests are properly triaged and
    44  	# that our various contribution and reviewing processes are respected. With their knowledge of
    45  	# the repository activity, they can also guide contributors to relevant material or
    46  	# discussions.
    47  	#
    48  	# They are neither code nor docs reviewers, so they are never expected to merge. They can
    49  	# however:
    50  	# - close an issue or pull request when it's an exact duplicate
    51  	# - close an issue or pull request when it's inappropriate or off-topic
    52  
    53  		people = [
    54  			"thajeztah"
    55  		]
    56  
    57  [people]
    58  
    59  # A reference list of all people associated with the project.
    60  # All other sections should refer to people by their canonical key
    61  # in the people section.
    62  
    63  	# ADD YOURSELF HERE IN ALPHABETICAL ORDER
    64  
    65  
    66  	[people.chris-crone]
    67  	Name = "Christopher Crone"
    68  	Email = "christopher.crone@docker.com"
    69  	GitHub = "chris-crone"
    70  	
    71  	[people.mat007]
    72  	Name = "Mathieu Champlon"
    73  	Email = "mathieu.champlon@docker.com"
    74  	GitHub = "mat007"
    75  	
    76  	[people.mnottale]
    77  	Name = "Matthieu Nottale"
    78  	Email = "matthieu.nottale@docker.com"
    79  	GitHub = "mnottale"
    80  
    81  	[people.shin-]
    82  	Name = "Joffrey F"
    83  	Email = "joffrey@docker.com"
    84  	GitHub = "shin-"
    85  
    86  	[people.silvin-lubecki]
    87  	Name = "Silvin Lubecki"
    88  	Email = "silvin.lubecki@docker.com"
    89  	GitHub = "silvin-lubecki"
    90  
    91  	[people.thajeztah]
    92  	Name = "Sebastiaan van Stijn"
    93  	Email = "github@gone.nl"
    94  	GitHub = "thaJeztah"
    95  
    96  	[people.vdemeester]
    97  	Name = "Vincent Demeester"
    98  	Email = "vincent@sbr.pm"
    99  	GitHub = "vdemeester"
   100