-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.github Bridge (docs) update #5
base: master
Are you sure you want to change the base?
Conversation
- `main` is for stable production code | ||
- `develop` is the integration branch for new features |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: update these to main
and release
(Note to self)
<summary>**Click here for our code of conduct page**</summary> | ||
|
||
`````` | ||
# Code of Conduct |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this the same one in the code of conduct file? should this be a link to that instead of duplicating the text? alternatively, that file could link to this content here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Idea is having them templated and available for reproducibility, if you look at it on the doc site its a page that just has all the relevant community resources in an easy to copy paste manner
Just noticed this repo is unprotected, not sure if intentional |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Displays fine everywhere for me (I'm using chrome)
@@ -0,0 +1 @@ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
placeholder?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This allows people to make an issue without any templating, serves any possible edge case outside of your feature request and bug templates
@@ -0,0 +1,81 @@ | |||
# If we choose to use the codeowners functionality update the file as a .md then uncomment and update the following: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment makes me think this is meant more as a template than as an org-wide article?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which leads me to ask both what the original source if the template is, and are there instructions anywhere on what these templates are for? e.g. "when creating a new repo you will find these X and Y and Z files, which are used in the following scenarios..." etc.
do we have that somewhere I've missed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Briefly explained here: https://docs.overture.bio/docs/standards/github#codeowners
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is completely optional if you don't want it than we can remove it just wanted to offer all that is possible
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported to the community leaders responsible for enforcement at | ||
[this email]([email protected]). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wonder whether we should have a different email for this (which of course gets redirected to this same one under the hood). the purpose being to make it seem like there's more/different people handling this, hoping to bolster legitimacy beyond a single catch-all bucket
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need, even in the event that is the case contact emails can route to multiple people
|
||
This repo hosts a few templates to be applied across all repos in this organisation. | ||
It also holds the organisation's profile, which is public to everyone. | ||
This repository contains organization-wide GitHub configurations and community health files for the Overture project. These files serve as default community health files for all Overture repositories that don't have their own specific versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've noticed a few "code of conduct" files in other repos. Do those need "specific versions" of that? I think they can be removed from there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed and updating now
- `ISSUE_TEMPLATE/`: Contains templates for different types of issues. | ||
- `workflows/`: Can hold GitHub Actions workflow files for CI/CD. | ||
- `profile/`: Contains the files used for the organization landing page readme found on https://github.com/overture-stack. | ||
- `Standards/`: Includes organizational documentation standards and guidelines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've noticed in other repos these bullet points have initial capitals here regardless of the actual casing of the folder above. this should be consistent everywhere.
... and to be clear, I mean the bullets, not the folders themselves
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
capitalization are reflective of actual casing of the folder/file referenced "`` " is enough to reflect that
- `profile/`: Contains the files used for the organization landing page readme found on https://github.com/overture-stack. | ||
- `Standards/`: Includes organizational documentation standards and guidelines. | ||
- All Root-level files are community health files and GitHub-specific templates. | ||
- These will serve as default files for all Overture repositories that don't have their own versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
standards/01-github.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this seems like a document for us to create organisations or repos, not for other people to read about Overture... but perhaps I'm misreading it? I guess I'm not clear on what the purpose for this one is here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Standards can be applied to other projects that use Overture (PCGL), it's just a nice value add also a marker of the health of the project
Co-authored-by: Anders Richardsson <[email protected]>
Co-authored-by: Anders Richardsson <[email protected]>
Co-authored-by: Anders Richardsson <[email protected]>
Co-authored-by: Anders Richardsson <[email protected]>
profile/portal-services.webp
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was ist das? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
The active voice is concise and more accessible for readers to comprehend. Active voice is naturally used in conversation and therefore, readers understand and engage more with writing in the active voice. | ||
|
||
| 👎 Disengaging| 👍 Engaging| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
consistency with other suggestions
| 👎 Disengaging| 👍 Engaging| | |
| 👎 Disengaging | 👍 Engaging | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@justincorrigible this file contains the "old" branch model. needs updates once we finish switching over to the "new" one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any and all works
Ensure all links correctly resolve and names and content are updated based on your project needs. Use the `CONTRIBUTING.md` copy here to get you started: | ||
|
||
<details> | ||
<summary><b>Click here for a copy of our contributing.md</b></summary> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this one be in full caps too, to keep things consistent?
- `main` is for stable production code | ||
- `develop` is the integration branch for new features | ||
- `feature/<name>` for feature branches | ||
- `release/v<version>` for release branches | ||
- `hotfix/<name>` for hotfix branches |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self @justincorrigible:
Update this!
- `main` is for stable production code | ||
- `develop` is the integration branch for new features | ||
- `feature/<name>` for feature branches | ||
- `release/v<version>` for release branches | ||
- `hotfix/<name>` for hotfix branches |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@justincorrigible here too
Co-authored-by: Anders Richardsson <[email protected]>
This repository contains organization-wide GitHub configurations and community health files for the Overture project. These files serve as default community health files for all Overture repositories that don't have their own specific versions.
I am also putting our documentation standards content here in the
/standards
folder and rendered out to the docs site here (.github is a submodule within the future OvertureDev repo)Repository Structure
The repository is organized with the following structure:
ISSUE_TEMPLATE/
: Contains templates for different types of issues.workflows/
: Can hold GitHub Actions workflow files for CI/CD.profile/
: Contains the files used for the organization landing page readme found on https://github.com/overture-stack.Standards/
: Includes organizational documentation standards and guidelines.