volcano.sh/apis@v1.8.2/GOVERNANCE.md (about)

     1  # Volcano Governance
     2  
     3  ## Principles
     4  
     5  The Volcano community adheres to the following principles:
     6  
     7  - Open: Volcano is open source community.
     8  - Welcoming and respectful: See [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
     9  - Transparent and accessible: Changes to the Volcano organization, Volcano code repositories, and CNCF related activities (e.g. level, involvement, etc) are done in public.
    10  - Merit: Ideas and contributions are accepted according to their technical merit and alignment with
    11    project objectives, scope, and design principles.
    12  
    13  ## Expectations from Maintainers
    14  
    15  Every one carries water...
    16  
    17  Making a community work requires input/effort from everyone. Maintainers should actively
    18  participate in Pull Request reviews. Maintainers are expected to respond to assigned Pull Requests
    19  in a *reasonable* time frame, either providing insights, or assign the Pull Requests to other
    20  maintainers.
    21  
    22  Every Maintainer is listed in the
    23  [MAINTAINERS](https://github.com/volcano-sh/volcano/blob/master/MAINTAINERS.md)
    24  file, with their Github handle.
    25  
    26  ## Becoming a Maintainer
    27  
    28  Please see the requirement [here](community-membership.md#maintainer)
    29  
    30  ## Changes in Maintainership
    31  
    32  If a Maintainer feels she/he can not fulfill the "Expectations from Maintainers", they are free to
    33  step down.
    34  
    35  The Volcano organization will never forcefully remove a current Maintainer, unless a maintainer
    36  fails to meet the principles of Volcano community,
    37  or adhere to the [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
    38  
    39  ## Decision making process
    40  
    41  Decisions are build on consensus between maintainers.
    42  Proposals and ideas can either be submitted for agreement via a github issue or PR.
    43  
    44  In general, we prefer that technical issues and maintainer membership are amicably worked out between the persons involved.
    45  If a dispute cannot be decided independently, get a third-party maintainer (e.g. a mutual contact with some background
    46  on the issue, but not involved in the conflict) to intercede.
    47  If a dispute still cannot be decided, the project lead has the final say to decide an issue.
    48  
    49  Decision making process should be transparent to adhere to
    50  the principles of Volcano project.
    51  
    52  All proposals, ideas, and decisions by maintainers or the project lead
    53  should either be part of a github issue or PR.
    54  
    55  ## Github Project Administration
    56  
    57  The __volcano__ GitHub project maintainers team reflects the list of Maintainers.
    58  
    59  ## Other Projects
    60  
    61  The Volcano organization is open to receive new sub-projects under its umbrella. To accept a project
    62  into the __Volcano__ organization, it has to meet the following criteria:
    63  
    64  - Must be licensed under the terms of the Apache License v2.0
    65  - Must be related to one or more scopes of the Volcano ecosystem:
    66    - Volcano project artifacts (website, deployments, CI, etc)
    67    - External plugins
    68    - Other AI/BigData related processing
    69  - Must be supported by a Maintainer not associated or affiliated with the author(s) of the sub-projects
    70  
    71  The submission process starts as a Pull Request or Issue on the
    72  [volcano-sh/volcano](https://github.com/volcano-sh/volcano) repository with the required information
    73  mentioned above. Once a project is accepted, it's considered a __CNCF sub-project under the umbrella
    74  of Volcano__.
    75  
    76  ## Volcano and CNCF
    77  
    78  Volcano is a CNCF project. As such, Volcano might be involved in CNCF (or other CNCF projects) related
    79  marketing, events, or activities. Any maintainer could help driving the Volcano involvement, as long as
    80  create a GitHub Pull Request to call for participation
    81  from other maintainers. The `Call for Participation` should be kept open for no less than a week if time
    82  permits, or a _reasonable_ time frame to allow maintainers to have a chance to volunteer.
    83  
    84  ## Code of Conduct
    85  
    86  The [Volcano Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) is aligned with the CNCF Code of Conduct.
    87  
    88  ## Credits
    89  
    90  Sections of this documents have been borrowed from [CoreDns](https://github.com/coredns/coredns/blob/master/GOVERNANCE.md).