diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index 8ac2ab3..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,51 +0,0 @@ -# 参与者公约 - -## 我们的承诺 - -为建设开放友好的环境，我们贡献者和维护者承诺：不论年龄、体型、身体健全与否、民族、性征、性别认同与表征、经验水平、教育程度、社会地位、国籍、相貌、种族、信仰、性取向，我们项目和社区的参与者皆免于骚扰。 - -## 我们的准则 - -有助于创造积极环境的行为包括但不限于： - -* 措辞友好且包容 -* 尊重不同的观点和经验 -* 耐心接受有益批评 -* 关注对社区最有利的事情 -* 与社区其他成员友善相处 - -参与者不应采取的行为包括但不限于： - -* 发布与性有关的言论或图像、不受欢迎地献殷勤 -* 捣乱/煽动/造谣行为、侮辱/贬损的评论、人身及政治攻击 -* 公开或私下骚扰 -* 未经明确授权便发布他人的资料，如住址、电子邮箱等 -* 其他有理由认定为违反职业操守的不当行为 - -## 我们的义务 - -项目维护者有义务诠释何谓“妥当行为”，并妥善公正地纠正已发生的不当行为。 - -项目维护者有权利和义务去删除、编辑、拒绝违背本行为标准的评论（comments）、提交（commits）、代码、wiki 编辑、问题（issues）等贡献；项目维护者可暂时或永久地封禁任何他们认为行为不当、威胁、冒犯、有害的参与者。 - -## 适用范围 - -本行为标准适用于本项目。当有人代表本项目或本社区时，本标准亦适用于此人所处的公共平台。 - -代表本项目或本社区的情形包括但不限于：使用项目的官方电子邮件、通过官方媒体账号发布消息、作为指定代表参与在线或线下活动等。 - -代表本项目的行为可由项目维护者进一步定义及解释。 - -## 贯彻落实 - -可以致信[admin@hackfun.org]，向项目团队举报滥用、骚扰及不当行为。 - -维护团队将审议并调查全部投诉，妥善地予以必要的回应。项目团队有义务保密举报者信息。具体执行方针或将另行发布。 - -未切实遵守或执行本行为标准的项目维护人员，经项目负责人或其他成员决议，可能被暂时或永久地剥夺参与本项目的资格。 - -## 来源 - -本行为标准改编自[参与者公约](https://www.contributor-covenant.org)的1.4版本，可[在此](https://www.contributor-covenant.org/zh-cn/version/1/4/code-of-conduct.html)查阅。 - -You can view the Contributor Covenant Translations [here](https://www.contributor-covenant.org/translations). \ No newline at end of file diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index a786cf7..0000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,42 +0,0 @@ -# Contribution Guidelines - -Before opening any issues or proposing any pull requests and to get the greatest chance of helpful responses, please observe the following notes. - -## Good Bug Reports - -Please be aware of the following things when filing bug reports: - -1. Avoid raising duplicate issues. *Please* use the GitHub issue search feature - to check whether your bug report or feature request has been mentioned in - the past. Duplicate bug reports and feature requests are a huge maintenance - burden on the limited resources of the project. If it is clear from your - report that you would have struggled to find the original, that's ok, but - if searching for a selection of words in your issue title would have found - the duplicate then the issue will likely be closed extremely abruptly. -2. When filing bug reports about exceptions or tracebacks, please include the - *complete* traceback. Partial tracebacks, or just the exception text, are - not helpful. Issues that do not contain complete tracebacks may be closed - without warning. -3. Make sure you provide a suitable amount of information to work with. This - means you should provide: - - - Guidance on **how to reproduce the issue**. Ideally, this should be a - *small* code sample that can be run immediately by the maintainers. - Failing that, let us know what you're doing, how often it happens, what - environment you're using, etc. Be thorough: it prevents us needing to ask - further questions. - - Tell us **what you expected to happen**. When we run your example code, - what are we expecting to happen? What does "success" look like for your - code? - - Tell us **what actually happens**. It's not helpful for you to say "it - doesn't work" or "it fails". Tell us *how* it fails: do you get an - exception? A hang? A non-200 status code? How was the actual result - different from your expected result? - - Tell us **what version of OneForAll you're using**, and - **how you installed it**. Different versions of Requests behave - differently and have different bugs, and some distributors of Requests - ship patches on top of the code we supply. - - If you do not provide all of these things, it will take us much longer to - fix your problem. If we ask you to clarify these and you never respond, we - will close your issue without fixing it. \ No newline at end of file diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index 8b13789..0000000 --- a/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1 +0,0 @@ -