diff --git a/.github/ISSUE_TEMPLATE/documentation.yml b/.github/ISSUE_TEMPLATE/documentation.yml deleted file mode 100644 index dcf33b02ea..0000000000 --- a/.github/ISSUE_TEMPLATE/documentation.yml +++ /dev/null @@ -1,56 +0,0 @@ -name: "Documentation 📖" -description: Did you find an error in our documentation? Report your findings here. -title: "[DOC] - " -labels: ["area: documentation 📖"] - -body: - - type: markdown - attributes: - value: | - # Welcome 👋 - - Thanks for using Nebari and taking some time to contribute to this project. - - Please fill out each section below. This info allows Nebari maintainers to diagnose (and fix!) your issue as - quickly as possible. - Before submitting a bug, please make sure the issue hasn't been already addressed by searching through - [the past issues](https://github.com/nebari-dev/nebari-docs/issues). - - Useful links: - - - Documentation: https://www.nebari.dev - - Contribution guidelines: https://www.nebari.dev/community/ - - - type: checkboxes - attributes: - label: Preliminary Checks - description: Please make sure that you verify each checkbox and follow the instructions for them. - options: - - label: "This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions" - required: true - - type: textarea - validations: - required: true - attributes: - label: Summary - description: | - What problem(s) did you run into that caused you to request a fix to the documentation or additional - documentation? What questions do you think we should answer? - - - type: textarea - validations: - required: true - attributes: - label: Steps to Resolve this Issue - description: | - How can the problem be solved? Are there any additional steps required? Do any other pages need to be updated? - value: | - 1. - 2. - 3. - ... - - - type: markdown - attributes: - value: > - Thanks for contributing 🎉! diff --git a/.github/ISSUE_TEMPLATE/release-checklist.md b/.github/ISSUE_TEMPLATE/release-checklist.md index 1f58d49947..a82409dd71 100644 --- a/.github/ISSUE_TEMPLATE/release-checklist.md +++ b/.github/ISSUE_TEMPLATE/release-checklist.md @@ -1,11 +1,10 @@ --- name: Release Checklist about: For maintainers only. -title: '[RELEASE] <version>' +title: "[RELEASE] <version>" labels: - - 'type: release 🏷' -assignees: '' - + - "type: release 🏷" +assignees: "" --- # Release Checklist @@ -16,14 +15,12 @@ Scheduled release date - <yyyy/mm/dd> Release captain responsible - <@gh_username> - ## Starting point - a new release is out -- [x] Create *this* issue to track and discuss the upcoming release. +- [x] Create _this_ issue to track and discuss the upcoming release. - [ ] Use the previous release issue for any final release-specific discussions, then close. - This can be a good time to debrief and discuss improvements to the release process. - ## Looking forward - planning - [ ] [Create milestone for next release](https://github.com/nebari-dev/nebari/milestones) (if it doesn't already exist) and link it back here. @@ -32,7 +29,6 @@ Release captain responsible - <@gh_username> - This will be, in large part, determined by the roadmap. - Is there a focus for this release (i.e. UX/UI, stabilization, etc.)? - ## Pre-release process - [ ] Decide on a date for the release. @@ -57,10 +53,10 @@ Release captain responsible - <@gh_username> - (Repeat steps if necessary) - [ ] [Update `RELEASE.md` notes.](https://github.com/nebari-dev/nebari/blob/main/RELEASE.md) - ## Cut the official release -*These steps must be actioned in the order they appear in this checklist.* +_These steps must be actioned in the order they appear in this checklist._ + - [ ] [Tag, build and push docker images](https://github.com/nebari-dev/nebari-docker-images/releases/new) - [ ] [Update and cut release for `nebari-dask` meta package on Conda-Forge.](https://github.com/conda-forge/nebari-dask-feedstock) - [ ] [Cut PyPI release via GHA release workflow.](https://github.com/nebari-dev/nebari/releases/new) diff --git a/.github/ISSUE_TEMPLATE/testing-checklist.md b/.github/ISSUE_TEMPLATE/testing-checklist.md index 1a8553a0b6..a811239881 100644 --- a/.github/ISSUE_TEMPLATE/testing-checklist.md +++ b/.github/ISSUE_TEMPLATE/testing-checklist.md @@ -1,16 +1,15 @@ --- name: Testing Checklist about: For maintainers only. -title: 'Testing checklist for <version>' +title: "Testing checklist for <version>" labels: - - 'type: release 🏷' -assignees: '' - + - "type: release 🏷" +assignees: "" --- # Testing Checklist -*Use/modify this checklist to capture the platform's core services that need to be manually tested .* +_Use/modify this checklist to capture the platform's core services that need to be manually tested ._ ## Manual testing: core services @@ -18,6 +17,7 @@ If the integration tests for all of the cloud providers are successful, that is However, the following core services still need to be manually validated (until we can automate them). At minimum, the following services will need to be tested: + - [ ] [Log into keycloak as root user](https://nebari-docs.netlify.app/how-tos/configuring-keycloak#change-keycloak-root-password) - [ ] [Add a user](https://nebari-docs.netlify.app/how-tos/configuring-keycloak#adding-a-nebari-user) - [ ] [Log into conda-store and create](https://nebari-docs.netlify.app/tutorials/creating-new-environments) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000000..5cf1105f2a --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,8 @@ +# Nebari Code of Conduct + +Nebari is a community-oriented and community-led project. +We value the participation of every member of our community and want to ensure that every contributor has an enjoyable and fulfilling experience. +We are committed to creating a friendly and respectful place for learning, teaching, and contributing. +Accordingly, everyone who participates in the Nebari project is expected to show respect and courtesy to other community members at all times. + +You can find the [Nebari Code of Conduct on the `nebari-dev/governance` repository](https://github.com/nebari-dev/governance/blob/main/CODE_OF_CONDUCT.md) and it applies to all spaces managed by Nebari including, but not limited to, in-person and online focus groups and workshops, and communications online via GitHub.