minor update to readmes and links in contributing and code of conduct

MitchellShiell · MitchellShiell · commit 161d2c16adc9 · 2024-11-02T19:25:37.000-04:00
diff --git a/submodules/.github b/submodules/.github
@@ -1 +1 @@
-Subproject commit 1338169f3c61f1699cc0dc49f0f54ee5cebe3f91
+Subproject commit 60c5ab1e3329a8ea5039dad4320b08d1493da1f4
diff --git a/submodules/arranger b/submodules/arranger
@@ -1 +1 @@
-Subproject commit f8fa29ffd4832f7244162ae33990124e2270fa73
+Subproject commit 66df196e19c3f30742dfb781dd27708c8d9544b4
diff --git a/submodules/lectern b/submodules/lectern
@@ -1 +1 @@
-Subproject commit ca7f0f41c45ceb240c79fd4c100b99b0183b81c0
+Subproject commit b7dac62e3088d64fdc9d3c4fc1259ddd57bec22e
diff --git a/submodules/lyric b/submodules/lyric
@@ -1 +1 @@
-Subproject commit fc8fd98a23877072412bf36b5f09aeeb209c22ca
+Subproject commit f459ba25156d3ee18ce37a9bef4b58c38cfc2aef
diff --git a/submodules/maestro b/submodules/maestro
@@ -1 +1 @@
-Subproject commit 2be105b032f79da33a2863b7201146e30e4c0662
+Subproject commit 7a545af0f52efce903f34972846bcb53ab2d7376
diff --git a/submodules/score b/submodules/score
@@ -1 +1 @@
-Subproject commit dc8a4c2cd245200722a44e486616430323577f99
+Subproject commit da1f7dfd175ed9700712f0910519cb0ce916704a
diff --git a/submodules/song b/submodules/song
@@ -1 +1 @@
-Subproject commit 9ccf47ed6f2a19654414c01a3cc729961dfe142a
+Subproject commit c77f252ad009ab9f29cbf5a203426d733b6615bf
diff --git a/submodules/stage b/submodules/stage
@@ -1 +1 @@
-Subproject commit 9a22c8000a096054d6b849888d37e5e8b55672fb
+Subproject commit 7c64c2232e71aa9fc191790604e2941c94be50ab
diff --git a/website/community/00-support.md b/website/community/00-support.md
@@ -6,6 +6,10 @@ We take pride in our software and are passionate about helping others use them.
 
 Our primary platform for community support, feature requests, and general discussions is GitHub Discussions. This allows us to keep all conversations in one place and make them easily searchable for future reference.
 
+:::info Contacting by email
+If you have a collaboration or business enquiry you can reach us by email at **contact@overture.bio**
+:::
+
 ### Getting Help
 
 - [**Create a Support Discussion**](https://github.com/overture-stack/docs/discussions/categories/support)
@@ -16,7 +20,7 @@ Our primary platform for community support, feature requests, and general discus
 
 We love hearing your ideas for improving Overture! Before making a feature request, please check our current roadmap to see if your idea is already planned:
 
-- [**Overture Roadmap**](https://github.com/users/MitchellShiell/projects/2/views/4)
+- [**Overture feature roadmap](https://github.com/orgs/overture-stack/projects/11/views/1)
 
 If your idea isn't on the roadmap, feel free to create a new discussion in our Ideas category:
 
@@ -49,4 +53,5 @@ When participating in our community, please adhere to the following guidelines:
 2. Provide as much relevant information as possible when asking for help.
 3. Use clear and descriptive titles for your discussions and issues.
 4. Search existing discussions before creating a new one to avoid duplicates.
-5. Follow the GitHub Community Guidelines and abide by our [code of conduct](/community/code-of-conduct).
+5. Follow the GitHub Community Guidelines and abide by our [code of conduct](/community/code-of-conduct).
+
diff --git a/website/community/03-code-of-conduct.md b/website/community/03-code-of-conduct.md
@@ -4,7 +4,7 @@ We as members, contributors, and leaders pledge to make participation in our
 community a harassment-free experience for everyone, regardless of age, body
 size, visible or invisible disability, ethnicity, sex characteristics, gender
 identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
+nationality, personal appearance, caste, color, religion, or sexual
 identity and orientation.
 
 We pledge to act and interact in ways that contribute to an open, welcoming,
@@ -58,7 +58,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-[INSERT CONTACT METHOD].
+[this email](contact@overture.bio).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
diff --git a/website/community/04-contribution.md b/website/community/04-contribution.md
@@ -19,7 +19,7 @@ By participating in this project, you are expected to abide by our [Code of Cond
 
 - **Getting Help:** If you need assistance with Overture, please create a [new discussion in our support category](https://github.com/overture-stack/docs/discussions/categories/support).
   - Before creating a new discussion, please search existing discussions to see if your question has already been answered.
-- **Feature Requests & Proposals:** We love hearing your ideas for improving Overture! Before making a feature request, please check our [**current roadmap**](https://github.com/users/MitchellShiell/projects/2/views/4) to see if your idea is already planned.
+- **Feature Requests & Proposals:** We love hearing your ideas for improving Overture! Before making a feature request, please check our [**feature roadmap**](https://github.com/orgs/overture-stack/projects/11/views/1) to see if your idea is already planned.
   - If your idea isn't on the roadmap, feel free to [**submit a feature request**](https://github.com/overture-stack/docs/discussions/categories/ideas) by creating a new discussion in our Ideas category 
 - **Report a Potential Bug:** We use GitHub Issues primarily for tracking confirmed bugs and ticketing development tasks. If you come across a potential bug or issue, please first post it to our [**GitHub support discussion forum**](https://github.com/overture-stack/docs/discussions/categories/support).
   - This allows us to confirm the issue and gather more information if needed. If we determine that further development is required, we will create and tag you into a GitHub Issue from your discussion post.
@@ -57,19 +57,18 @@ We welcome and encourage pull requests from the community. To submit a pull requ
 
 2. **Use descriptive titles:** Start with a verb (e.g., "Add", "Fix", "Update", "Refactor"), briefly summarize the main purpose of the PR and include the issue number if applicable (e.g., "Fix user authentication bug (#123)").
 
-3. **Describe how you tested it:** Explain the testing process you followed and mention any new tests you've added.
+3. **Describe how you tested it:** Explain the testing process you followed and mention any new automated tests you've added.
 
 4. **Provide a clear description:** Explain the purpose of your changes and list the main modifications you've made. Mention any potential side effects or areas that might need extra attention.
 
 5. **Link related issues:** Reference any related issues or pull requests. Use GitHub keywords to automatically link issues (e.g., "Closes #123", "Fixes #456").
-
-6. **Keep the PR up-to-date:** Regularly rebase your branch on the latest main branch and resolve any merge conflicts promptly.
+6. **Keep the PR's branch up-to-date:** Regularly rebase your branch on the latest main branch and resolve any merge conflicts promptly.
 
 7. **Respond to feedback:** Be open to suggestions and willing to make changes. Address all comments from reviewers. If you disagree with a suggestion, explain your reasoning politely.
 
 8. **Include documentation updates:** If your changes affect user-facing features, update or create and issue detailing the relevant changes need to the documentation. Where appropriate include inline comments for complex code sections.
 
-10. **Be patient:** Reviewers will likely not be able to respond immediately. Follow up politely if you haven't received feedback after a reasonable time.
+10. **Be patient:** Reviewers will likely be unable to respond immediately. However, feel free to follow up politely if you haven't received feedback after a reasonable time.
 
 ### Using Draft Pull Requests
 
@@ -91,7 +90,7 @@ Guidelines for Draft Pull Requests:
    - Highlight areas where feedback is specifically needed
 3. **Updates**:
    - Regularly update the description or provide comments following commits with progress notes
-   - Use task lists (- [ ]) to track completion of sub-tasks
+- Use task lists (using `- [ ]` in Markdown) to track completion of sub-tasks
 4. **Collaboration**:
    - Encourage early feedback and discussion
    - Use the pull request comments for design discussions
diff --git a/website/docs/contribution.md b/website/docs/contribution.md
@@ -19,7 +19,7 @@ By participating in this project, you are expected to abide by our [Code of Cond
 
 - **Getting Help:** If you need assistance with Overture, please create a [new discussion in our support category](https://github.com/overture-stack/docs/discussions/categories/support).
   - Before creating a new discussion, please search existing discussions to see if your question has already been answered.
-- **Feature Requests & Proposals:** We love hearing your ideas for improving Overture! Before making a feature request, please check our [**current roadmap**](https://github.com/users/MitchellShiell/projects/2/views/4) to see if your idea is already planned.
+- **Feature Requests & Proposals:** We love hearing your ideas for improving Overture! Before making a feature request, please check our [**feature roadmap**](https://github.com/orgs/overture-stack/projects/11/views/1) to see if your idea is already planned.
   - If your idea isn't on the roadmap, feel free to [**submit a feature request**](https://github.com/overture-stack/docs/discussions/categories/ideas) by creating a new discussion in our Ideas category 
 - **Report a Potential Bug:** We use GitHub Issues primarily for tracking confirmed bugs and ticketing development tasks. If you come across a potential bug or issue, please first post it to our [**GitHub support discussion forum**](https://github.com/overture-stack/docs/discussions/categories/support).
   - This allows us to confirm the issue and gather more information if needed. If we determine that further development is required, we will create and tag you into a GitHub Issue from your discussion post.
@@ -57,19 +57,18 @@ We welcome and encourage pull requests from the community. To submit a pull requ
 
 2. **Use descriptive titles:** Start with a verb (e.g., "Add", "Fix", "Update", "Refactor"), briefly summarize the main purpose of the PR and include the issue number if applicable (e.g., "Fix user authentication bug (#123)").
 
-3. **Describe how you tested it:** Explain the testing process you followed and mention any new tests you've added.
+3. **Describe how you tested it:** Explain the testing process you followed and mention any new automated tests you've added.
 
 4. **Provide a clear description:** Explain the purpose of your changes and list the main modifications you've made. Mention any potential side effects or areas that might need extra attention.
 
 5. **Link related issues:** Reference any related issues or pull requests. Use GitHub keywords to automatically link issues (e.g., "Closes #123", "Fixes #456").
-
-6. **Keep the PR up-to-date:** Regularly rebase your branch on the latest main branch and resolve any merge conflicts promptly.
+6. **Keep the PR's branch up-to-date:** Regularly rebase your branch on the latest main branch and resolve any merge conflicts promptly.
 
 7. **Respond to feedback:** Be open to suggestions and willing to make changes. Address all comments from reviewers. If you disagree with a suggestion, explain your reasoning politely.
 
 8. **Include documentation updates:** If your changes affect user-facing features, update or create and issue detailing the relevant changes need to the documentation. Where appropriate include inline comments for complex code sections.
 
-10. **Be patient:** Reviewers will likely not be able to respond immediately. Follow up politely if you haven't received feedback after a reasonable time.
+10. **Be patient:** Reviewers will likely be unable to respond immediately. However, feel free to follow up politely if you haven't received feedback after a reasonable time.
 
 ### Using Draft Pull Requests
 
@@ -91,7 +90,7 @@ Guidelines for Draft Pull Requests:
    - Highlight areas where feedback is specifically needed
 3. **Updates**:
    - Regularly update the description or provide comments following commits with progress notes
-   - Use task lists (- [ ]) to track completion of sub-tasks
+- Use task lists (using `- [ ]` in Markdown) to track completion of sub-tasks
 4. **Collaboration**:
    - Encourage early feedback and discussion
    - Use the pull request comments for design discussions
