.github Bridge (docs) update

CODEOWNERS.txt

@@ -0,0 +1,81 @@
+# If we choose to use the codeowners functionality update the file as a .md then uncomment and update the following:
+
+<!--
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+*       @global-owner1 @global-owner2
+
+# Order is important; the last matching pattern takes the most
+# precedence. When someone opens a pull request that only
+# modifies JS files, only @js-owner and not the global
+# owner(s) will be requested for a review.
+*.js    @js-owner
+
+# You can also use email addresses if you prefer. They'll be
+# used to look up users just like we do for commit author
+# emails.
+*.go docs@example.com
+
+# Teams can be specified as code owners as well. Teams should
+# be identified in the format @org/team-name. Teams must have
+# explicit write access to the repository.
+/apps/ @organization/app-team
+
+# In this example, @doctocat owns any files in the build/logs
+# directory at the root of the repository and any of its
+# subdirectories.
+/build/logs/ @doctocat
+
+# The `docs/*` pattern will match files like
+# `docs/getting-started.md` but not further nested files like
+# `docs/build-app/troubleshooting.md`.
+docs/*  docs@example.com
+
+# In this example, @octocat owns any file in an apps directory
+# anywhere in your repository.
+apps/ @octocat
+
+# In this example, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+/scripts/ @doctocat @octocat
+
+# In this example, @octocat owns any file in the `/apps` 
+# directory in the root of your repository except for the `/apps/github` 
+# subdirectory, as its owners are left empty.
+/apps/ @octocat
+/apps/github -->
+
+
+<!-- ## Example Here
+# Overall ownership
+*       @overture-stack/coreMaintainers
+
+# Workflow files
+/.github/workflows/   @overture-stack/devops
+
+# Issue templates
+/.github/ISSUE_TEMPLATE/   @overture-stack/outreach
+
+# Documentation files
+*.md    @overture-stack/outreach
+
+# Security-related files
+/SECURITY.md   @overture-stack/coreMaintainers
+
+# Community health files
+/CODE_OF_CONDUCT.md   @overture-stack/outreach
+/CONTRIBUTING.md      @overture-stack/outreach
+
+# Funding related files
+/FUNDING.yml   @overture-stack/managers
+
+# Standards directory
+/Standards/    @overture-stack/outreach
+
+# Profile directory
+/profile/      @overture-stack/outreach
+ -->