github.com/docker/compose-on-kubernetes@v0.5.0/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  			"simon-ferquel",
    26  			"chris-crone",
    27  			"silvin-lubecki",
    28  		]
    29  
    30  	[Org."Docs maintainers"]
    31  
    32  	# TODO Describe the docs maintainers role.
    33  
    34  		people = [
    35  			"simon-ferquel",
    36  			"chris-crone",
    37  			"silvin-lubecki",
    38  		]
    39  
    40  	[Org.Curators]
    41  
    42  	# The curators help ensure that incoming issues and pull requests are properly triaged and
    43  	# that our various contribution and reviewing processes are respected. With their knowledge of
    44  	# the repository activity, they can also guide contributors to relevant material or
    45  	# discussions.
    46  	#
    47  	# They are neither code nor docs reviewers, so they are never expected to merge. They can
    48  	# however:
    49  	# - close an issue or pull request when it's an exact duplicate
    50  	# - close an issue or pull request when it's inappropriate or off-topic
    51  
    52  		people = [
    53  			"simon-ferquel",
    54  		]
    55  
    56  [people]
    57  
    58  # A reference list of all people associated with the project.
    59  # All other sections should refer to people by their canonical key
    60  # in the people section.
    61  
    62  	# ADD YOURSELF HERE IN ALPHABETICAL ORDER
    63  
    64  	[people.simonferquel]
    65  	Name = "Simon Ferquel"
    66  	Email = "simon.ferquel@docker.com"
    67  	GitHub = "simonferquel"
    68  
    69  	[people.chris-crone]
    70  	Name = "Christopher Crone"
    71  	Email = "christopher.crone@docker.com"
    72  	GitHub = "chris-crone"
    73  
    74  	[people.silvin-lubecki]
    75  	Name = "Silvin Lubecki"
    76  	Email = "silvin.lubecki@docker.com"
    77  	GitHub = "silvin-lubecki"