From 3493e6209beda2821a938fdf3cef0660e9858547 Mon Sep 17 00:00:00 2001 From: winterlinn <39840327+winterlinn@users.noreply.github.com> Date: Mon, 29 Oct 2018 17:49:59 +0300 Subject: [PATCH 1/2] cancer removal --- .../code-of-conduct-interpretation.rst | 156 ------------------ 1 file changed, 156 deletions(-) delete mode 100644 Documentation/process/code-of-conduct-interpretation.rst diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst deleted file mode 100644 index e899f14a4ba240..00000000000000 --- a/Documentation/process/code-of-conduct-interpretation.rst +++ /dev/null @@ -1,156 +0,0 @@ -.. _code_of_conduct_interpretation: - -Linux Kernel Contributor Covenant Code of Conduct Interpretation -================================================================ - -The :ref:`code_of_conduct` is a general document meant to -provide a set of rules for almost any open source community. Every -open-source community is unique and the Linux kernel is no exception. -Because of this, this document describes how we in the Linux kernel -community will interpret it. We also do not expect this interpretation -to be static over time, and will adjust it as needed. - -The Linux kernel development effort is a very personal process compared -to "traditional" ways of developing software. Your contributions and -ideas behind them will be carefully reviewed, often resulting in -critique and criticism. The review will almost always require -improvements before the material can be included in the -kernel. Know that this happens because everyone involved wants to see -the best possible solution for the overall success of Linux. This -development process has been proven to create the most robust operating -system kernel ever, and we do not want to do anything to cause the -quality of submission and eventual result to ever decrease. - -Maintainers ------------ - -The Code of Conduct uses the term "maintainers" numerous times. In the -kernel community, a "maintainer" is anyone who is responsible for a -subsystem, driver, or file, and is listed in the MAINTAINERS file in the -kernel source tree. - -Responsibilities ----------------- - -The Code of Conduct mentions rights and responsibilities for -maintainers, and this needs some further clarifications. - -First and foremost, it is a reasonable expectation to have maintainers -lead by example. - -That being said, our community is vast and broad, and there is no new -requirement for maintainers to unilaterally handle how other people -behave in the parts of the community where they are active. That -responsibility is upon all of us, and ultimately the Code of Conduct -documents final escalation paths in case of unresolved concerns -regarding conduct issues. - -Maintainers should be willing to help when problems occur, and work with -others in the community when needed. Do not be afraid to reach out to -the Technical Advisory Board (TAB) or other maintainers if you're -uncertain how to handle situations that come up. It will not be -considered a violation report unless you want it to be. If you are -uncertain about approaching the TAB or any other maintainers, please -reach out to our conflict mediator, Mishi Choudhary . - -In the end, "be kind to each other" is really what the end goal is for -everybody. We know everyone is human and we all fail at times, but the -primary goal for all of us should be to work toward amicable resolutions -of problems. Enforcement of the code of conduct will only be a last -resort option. - -Our goal of creating a robust and technically advanced operating system -and the technical complexity involved naturally require expertise and -decision-making. - -The required expertise varies depending on the area of contribution. It -is determined mainly by context and technical complexity and only -secondary by the expectations of contributors and maintainers. - -Both the expertise expectations and decision-making are subject to -discussion, but at the very end there is a basic necessity to be able to -make decisions in order to make progress. This prerogative is in the -hands of maintainers and project's leadership and is expected to be used -in good faith. - -As a consequence, setting expertise expectations, making decisions and -rejecting unsuitable contributions are not viewed as a violation of the -Code of Conduct. - -While maintainers are in general welcoming to newcomers, their capacity -of helping contributors overcome the entry hurdles is limited, so they -have to set priorities. This, also, is not to be seen as a violation of -the Code of Conduct. The kernel community is aware of that and provides -entry level programs in various forms like kernelnewbies.org. - -Scope ------ - -The Linux kernel community primarily interacts on a set of public email -lists distributed around a number of different servers controlled by a -number of different companies or individuals. All of these lists are -defined in the MAINTAINERS file in the kernel source tree. Any emails -sent to those mailing lists are considered covered by the Code of -Conduct. - -Developers who use the kernel.org bugzilla, and other subsystem bugzilla -or bug tracking tools should follow the guidelines of the Code of -Conduct. The Linux kernel community does not have an "official" project -email address, or "official" social media address. Any activity -performed using a kernel.org email account must follow the Code of -Conduct as published for kernel.org, just as any individual using a -corporate email account must follow the specific rules of that -corporation. - -The Code of Conduct does not prohibit continuing to include names, email -addresses, and associated comments in mailing list messages, kernel -change log messages, or code comments. - -Interaction in other forums is covered by whatever rules apply to said -forums and is in general not covered by the Code of Conduct. Exceptions -may be considered for extreme circumstances. - -Contributions submitted for the kernel should use appropriate language. -Content that already exists predating the Code of Conduct will not be -addressed now as a violation. Inappropriate language can be seen as a -bug, though; such bugs will be fixed more quickly if any interested -parties submit patches to that effect. Expressions that are currently -part of the user/kernel API, or reflect terminology used in published -standards or specifications, are not considered bugs. - -Enforcement ------------ - -The address listed in the Code of Conduct goes to the Code of Conduct -Committee. The exact members receiving these emails at any given time -are listed at https://kernel.org/code-of-conduct.html. Members can not -access reports made before they joined or after they have left the -committee. - -The initial Code of Conduct Committee consists of volunteer members of -the TAB, as well as a professional mediator acting as a neutral third -party. The first task of the committee is to establish documented -processes, which will be made public. - -Any member of the committee, including the mediator, can be contacted -directly if a reporter does not wish to include the full committee in a -complaint or concern. - -The Code of Conduct Committee reviews the cases according to the -processes (see above) and consults with the TAB as needed and -appropriate, for instance to request and receive information about the -kernel community. - -Any decisions by the committee will be brought to the TAB, for -implementation of enforcement with the relevant maintainers if needed. -A decision by the Code of Conduct Committee can be overturned by the TAB -by a two-thirds vote. - -At quarterly intervals, the Code of Conduct Committee and TAB will -provide a report summarizing the anonymised reports that the Code of -Conduct committee has received and their status, as well details of any -overridden decisions including complete and identifiable voting details. - -We expect to establish a different process for Code of Conduct Committee -staffing beyond the bootstrap period. This document will be updated -with that information when this occurs. From 9f057c7d35e5dd35d069677f8037ba3cdf558565 Mon Sep 17 00:00:00 2001 From: winterlinn <39840327+winterlinn@users.noreply.github.com> Date: Mon, 29 Oct 2018 17:50:27 +0300 Subject: [PATCH 2/2] cancer removal --- Documentation/process/code-of-conduct.rst | 86 ----------------------- 1 file changed, 86 deletions(-) delete mode 100644 Documentation/process/code-of-conduct.rst diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst deleted file mode 100644 index be50294aebd5db..00000000000000 --- a/Documentation/process/code-of-conduct.rst +++ /dev/null @@ -1,86 +0,0 @@ -.. _code_of_conduct: - -Contributor Covenant Code of Conduct -++++++++++++++++++++++++++++++++++++ - -Our Pledge -========== - -In the interest of fostering an open and welcoming environment, we as -contributors and maintainers pledge to making participation in our project and -our community a harassment-free experience for everyone, regardless of age, body -size, disability, ethnicity, sex characteristics, gender identity and -expression, level of experience, education, socio-economic status, nationality, -personal appearance, race, religion, or sexual identity and orientation. - -Our Standards -============= - -Examples of behavior that contributes to creating a positive environment -include: - -* Using welcoming and inclusive language -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members - - -Examples of unacceptable behavior by participants include: - -* The use of sexualized language or imagery and unwelcome sexual attention or - advances -* Trolling, insulting/derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others’ private information, such as a physical or electronic - address, without explicit permission -* Other conduct which could reasonably be considered inappropriate in a - professional setting - - -Our Responsibilities -==================== - -Maintainers are responsible for clarifying the standards of acceptable behavior -and are expected to take appropriate and fair corrective action in response to -any instances of unacceptable behavior. - -Maintainers have the right and responsibility to remove, edit, or reject -comments, commits, code, wiki edits, issues, and other contributions that are -not aligned to this Code of Conduct, or to ban temporarily or permanently any -contributor for other behaviors that they deem inappropriate, threatening, -offensive, or harmful. - -Scope -===== - -This Code of Conduct applies both within project spaces and in public spaces -when an individual is representing the project or its community. Examples of -representing a project or community include using an official project e-mail -address, posting via an official social media account, or acting as an appointed -representative at an online or offline event. Representation of a project may be -further defined and clarified by project maintainers. - -Enforcement -=========== - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the Code of Conduct Committee at -. All complaints will be reviewed and investigated -and will result in a response that is deemed necessary and appropriate -to the circumstances. The Code of Conduct Committee is obligated to -maintain confidentiality with regard to the reporter of an incident. -Further details of specific enforcement policies may be posted -separately. - -Attribution -=========== - -This Code of Conduct is adapted from the Contributor Covenant, version 1.4, -available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html - -Interpretation -============== - -See the :ref:`code_of_conduct_interpretation` document for how the Linux -kernel community will be interpreting this document.