Conversation
| - `main` is for stable production code | ||
| - `develop` is the integration branch for new features |
There was a problem hiding this comment.
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.
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.
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.
Displays fine everywhere for me (I'm using chrome)
| @@ -0,0 +1 @@ | |||
|
|
|||
There was a problem hiding this comment.
This allows people to make an issue without any templating, serves any possible edge case outside of your feature request and bug templates
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported to the community leaders responsible for enforcement at | ||
| [this email](contact@overture.bio). |
There was a problem hiding this comment.
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.
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.
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.
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.
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.
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. No newline at end of file |
There was a problem hiding this comment.
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.
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 <2107110+justincorrigible@users.noreply.github.com>
Co-authored-by: Anders Richardsson <2107110+justincorrigible@users.noreply.github.com>
Co-authored-by: Anders Richardsson <2107110+justincorrigible@users.noreply.github.com>
Co-authored-by: Anders Richardsson <2107110+justincorrigible@users.noreply.github.com>
There was a problem hiding this comment.
@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.
Any and all works
| - `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 |
| - `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 |
Co-authored-by: Anders Richardsson <2107110+justincorrigible@users.noreply.github.com>
Co-authored-by: Anders Richardsson <2107110+justincorrigible@users.noreply.github.com>
| The XYZ Library (http://xyz-library.com) | ||
| Copyright (c) [Year] [Copyright Owner] | ||
| Licensed under Apache License 2.0 | ||
| ------------------------------------------------------------------------ No newline at end of file |
There was a problem hiding this comment.
| ------------------------------------------------------------------------ | |
| ------------------------------------------------------------------------ | |



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
/standardsfolder 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.