Promotion to 1.0.0

Android.mk

@@ -0,0 +1,4 @@
+ifneq ($(AUDIO_USE_STUB_HAL), true)
+    include $(call all-subdir-makefiles)
+endif
+

CODE-OF-CONDUCT.md

@@ -60,7 +60,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
-[GitHub.CoC](mailto:github.coc@qti.qualcomm.com?subject=GitHub%20Qualcomm%20Code%20of%20Conduct%20Report).
+[GitHub.QuIC.CoC](mailto:GitHub.QuIC.CoC@qti.qualcomm.com?subject=GitHub%20QuIC%20Code%20of%20Conduct%20Report).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

CONTRIBUTING.md

@@ -1,76 +1,28 @@
-# Contributing to <REPLACE-ME>
+## Contributing to AudioReach Graph Service
 
 Hi there!
 We’re thrilled that you’d like to contribute to this project.
 Your help is essential for keeping this project great and for making it better.
 
 ## Branching Strategy
 
-Development happens directly on branch main. Open a PR targeting main
+In general, contributors should develop on branches based off of `master` and pull requests should be made against `master`.
 
 ## Submitting a pull request
 
-1. Please read our [code of conduct](CODE-OF-CONDUCT.md) and [license](LICENSE.txt).
-1. [Fork](https://github.com/qualcomm-linux/pkg-template/fork) and clone the repository.
-
-    ```bash
-    git clone https://github.com/qualcomm-linux/pkg-template.git
-    ```
-
-1. Create a new branch based on `main`:
-
-    ```bash
-    git checkout -b <my-branch-name> main
-    ```
-
-1. Create an upstream `remote` to make it easier to keep your branches up-to-date:
-
-    ```bash
-    git remote add upstream https://github.com/qualcomm/<REPLACE-ME>.git
-    ```
-
+1. Please read our [code of conduct](CODE-OF-CONDUCT.md) and [license](LICENSE).
+1. Fork and clone the repository.
+1. Create a new branch based on `master`: `git checkout -b <my-branch-name> master`.
 1. Make your changes, add tests, and make sure the tests still pass.
-1. Commit your changes using the [DCO](https://developercertificate.org/). You can attest to the DCO by commiting with the **-s** or **--signoff** options or manually adding the "Signed-off-by":
-
-    ```bash
-    git commit -s -m "Really useful commit message"`
-    ```
-
-1. After committing your changes on the topic branch, sync it with the upstream branch:
-
-    ```bash
-    git pull --rebase upstream main
-    ```
-
-1. Push to your fork.
-
-    ```bash
-    git push -u origin <my-branch-name>
-    ```
-
-    The `-u` is shorthand for `--set-upstream`. This will set up the tracking reference so subsequent runs of `git push` or `git pull` can omit the remote and branch.
-
-1. [Submit a pull request](https://github.com/qualcomm/<REPLACE-ME>/pulls) from your branch to `main`.
+1. Commit your changes using the [DCO](http://developercertificate.org/). You can attest to the DCO by commiting with the **-s** or **--signoff** options or manually adding the "Signed-off-by":
+1. Push to your fork and submit a pull request from your branch to `master`.
 1. Pat yourself on the back and wait for your pull request to be reviewed.
 
-## Security Analysis of Pull Requests
-
-To maintain the security and integrity of this project, all pull requests from external contributors are automatically scanned using [Semgrep](https://github.com/semgrep/semgrep) to detect insecure coding patterns and potential security flaws.
-
-**Static Analysis with Semgrep:**  We use Semgrep to perform lightweight, fast static analysis on every PR. This helps identify risky code patterns and logic flaws early in the development process.
-
-**Contributor Responsibility:** If any issues are flagged, contributors are expected to resolve them before the PR can be merged.
-
-**Continuous Improvement:** Our Semgrep ruleset evolves over time to reflect best practices and emerging security concerns.
-
-By submitting a PR, you agree to participate in this process and help us keep the project secure for everyone.
-
-
 Here are a few things you can do that will increase the likelihood of your pull request to be accepted:
 
-- Follow the existing style where possible. **INSERT LINK TO STYLE, e.g. PEP8 for python**
+- Follow the existing style where possible. We try and adhere to [pep8](https://www.python.org/dev/peps/pep-0008/).
 - Write tests.
 - Keep your change as focused as possible.
   If you want to make multiple independent changes, please consider submitting them as separate pull requests.
-- Write a [good commit message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 - It's a good idea to arrange a discussion with other developers to ensure there is consensus on large features, architecture changes, and other core code changes. PR reviews will go much faster when there are no surprises.

LICENSE

@@ -0,0 +1,29 @@
+Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice,
+   this list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its contributors
+   may be used to endorse or promote products derived from this software
+   without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+SPDX-License-Identifier: BSD-3-Clause

Makefile.am

@@ -0,0 +1 @@
+SUBDIRS = spf ar_osal ar_util acdb gpr gsl acdb/ats

README.md

@@ -1,146 +1,18 @@
-# pkg-template
+# AudioReach Graph Service
 
-This repository serves as a template for creating Debian package repositories within the Qualcomm Linux ecosystem. It provides the essential structure, GitHub workflows, and configuration necessary to integrate with the [qcom-build-utils](https://github.com/qualcomm-linux/qcom-build-utils) repository, enabling standardized Debian package building processes.
+## Introduction
 
-## Quick Start
+This repository hosts a set of platform independent graph service libraries and implementation of abstraction layer for different OS and platform.  These libraries together setup and manage audio graphs in the signal processing framework.
 
-To create a new Debian package repository using this template:
+## Documentation
 
-1. Navigate to this repository's GitHub page and click the **"Use this template"** button located in the top right corner.
-2. Select **qualcomm-linux** as the organization in the drop-down menu. This is necessary.
-3. Name the new repository with the prefix `pkg-` to adhere to the naming convention for package repositories. This is necessary.
-4. Ensure the **"Include all branches"** option is enabled. Otherwise by default, only the default branch "main" is cloned.
+Refer AudioReach docs [here](https://audioreach.github.io/design/args_design.html)
 
-## Branches
+## Build instructions
 
-- **main**: The primary branch containing workflow logic in the `.github/` folder, along with boilerplate documentation files such as license, contribution guidelines, and this README.
-- **debian/qcom-next**: An orphan branch with unrelated history from main. It contains a debian/ folder with template files. Its just to give a starting point and structure. The first job for the user templating from this repo will be to update this debian/ folder. The information about the name **debian/qcom-next** and other naming conventions can be found [here](https://qualcomm-confluence.atlassian.net/wiki/spaces/LinuxCoreOS/pages/2879858691/pkg-+repository+specification)
-
-## Workflows
-
-The `main` branch includes the following workflows in the `.github/workflows/` directory:
-
-- **qcom-preflight-checks.yml**: A sanity check workflow inherited from the base Qualcomm template.
-- **stale-issues.yml**: A workflow for managing stale issues, also inherited from the base template.
-- **build-debian-package.yml**: Builds the Debian package for this repository. This workflow serves as an entry point that invokes reusable workflows from the centralized qcom-build-utils repository.
-- **pr-pre-post-merge.yml**: This workflow executes during a PR, and once the PR is merged. 
-- **promote-upstream.yml**: Promotes the package's tracking version to a new upstream release. This workflow also triggers reusable workflows in qcom-build-utils.
-- **release**: Used to trigger a release of a package
-
-## IMPORTANT: Workflow to paste in the upstream source repo
-
-The .github/TO_PASTE_IN_UPSTREAM_REPO/pkg-build-pr-check.yml needs to be transfered over to the source repo.
-Once this is done, delete the TO_PASTE_IN_UPSTREAM_REPO as it is not necessary to keep in this repository once the workflow has been transfered.
-
-**This workflow needs to be put in the default branch of the source repo (likely branch main unless you modify it), otherwise it wont work** This is per new December Github update
-
-## Repository Configuration
-
-### Runners
-
-All the workflows are running on the github arm64 runners. Some sections need to run on the AWS runners where access to S3 buckets and artifactory. You will need to ask **Steve Manley** to enable the repo for the AWS runners.
-
-### GHCR Registry Access
-
-The build workflows rely on the `pkg-builder` container image hosted in the qualcomm-linux GitHub Container Registry (GHCR). For your newly created repository to be able to pull this image, it must be explicitly granted `packages:read` access.
-
-To request this, please contact **Mark Matyas** (mmatyas@qti.qualcomm.com) and ask him to add your repository to the list of repositories authorized to access the `pkg-builder` package. The relevant settings page is:
-
-https://github.com/orgs/qualcomm-linux/packages/container/pkg-builder/settings
-
-### Repository Variables
-
-Set the following repository variables to establish links between upstream and package repositories:
-
-- **UPSTREAM_REPO_GITHUB_NAME**: In this package repo, this is the GitHub name of the upstream repository (e.g. in the case of the pkg-example, `qualcomm-linux/qcom-example-package-source`).
-- **PKG_REPO_GITHUB_NAME**: This variable is set in the upstream project repo; the GitHub name of the package repository (e.g., `qualcomm-linux/pkg-example`).
-
-### Branch Protection Rules
-
-Configure branch protection for `debian/**` and `qcom/**`:
-
-- Restrict deletions.
-- Require pull requests before merging.
-- Block force pushes.
-- Add `build / build-debian-package` as a required status check.
-- Add the `qcom-service-bot` account with admin rights
-- Add the Admin role to the branche protection ruleset so that the qcom-service-bot can push directly to those branches
-### Additional Settings
-
-- Enable **"Automatically delete head branches"** for pull requests.
-- Allow only merge commits for pull request merges.
-- Enable **release immutability** in the upstream repository.
-- Add the Qualcomm Github Service bot as a user with write access :
-  - While the repo is private, add the Github user **qcom-service-bot**.
-  - If/when the repo is made public, there will be a big change in how the contributors are handled. 
-    After that, the contributors list is cleared, and one need to re-enroll as a contributor. The way
-    to do that is completely different from when the repo was private. When it was private, the creator
-    of the repo had the possibility to go into the repo settings and add whoever. When made public, the
-    repo's maintainer/contributor list is managed by a Qualcomm internal mailing list. If the repo is
-    named pkg-foo, then the Maintainer list will be named Maintainers.pkg-foo, and one need to request
-    access via https://lists.qualcomm.com, find the list and ask access. For the bot, you must add it via
-    its qualcomm username **githubservice**@qti.qualcomm.com, as opposed to its Github handle above.
-
-## Making your pkg-repo to public
-
-When your pkg-repo is mature enough, it will need to be made public.
-
-### How to make the repo go public
-
-The first step in making a repo go public is the Tradesmark/legal process.
-Your POC (Person of Contact) in this step is [Stephanie Arce](sarce@qti.qualcomm.com)
-
-You need to [complete an OSS Contribution Request](https://jira-dc4.qualcomm.com/jira/secure/CreateIssue.jspa?pid=46536&issuetype=13440)
-
-Here is a bit of help on the mandatory fields when filling the form:
-
-- Components : Select "Other"
-- Summary : Give a short description such as "Debian packaging repository for X"
-- Project name: This would be the repo name, such as "pkg-example"
-- Destination URL: Give the Github URL, such as "www.github.com/qualcomm-linux/pkg-example"
-- Description: Give a description about the repo being a debian packaging repo, which packages another upstream project X
-- Project Licenses: Give the license of the repo. Unless something changes, it should remain  BSD-3-Clause License.
-- Contribution plan: 
-  - Project Description: You can give the same project description as above
-  - What are ourr general plan with the Project: Talk about it being the debian packaging for project X
-  - Do we have any Leadership positions in the project: Give yourself/manager
-  - Is Qualcomm expanding the project by contributing technology implementations: Likely a simple no
-
-More information can be found [here](https://github.qualcomm.com/pages/osdo/handbook/qcom-github/docs/new-project-checklist/)
-
-Once submitted, it will generally take a couple of days to a week to get approval from Legal.
-
-The, once you receive an email about the acceptance of the Legal team, you will have to submit a ticket about enabling the repo.
-
-In this process, your POC will be [Mark Matyas](mmatyas@qti.qualcomm.com)
-
-Complete the form : https://ossops.qualcomm.com/github/enable-repo/
-
-### Note about Github Repo roles after going public
-
-When creating a repo withing the organization, it always starts as a private repo and one need to go through an approval
-process in order to have the repo go public. 
-
-Upon creation of the repo, the person who created it gets to be assigned the maintainer responsability and has full control
-over it in the settings. When the repo goes public, this changes. The repo creator stops having all the powers over the repo,
-and in order to join the repo as a contributor, one needs to enroll via a github mailing list instead of directly through the repo
-settings. 
-
-This is the link to go to in order to ask to be a contributor or a maintainer of a Qualcomm publib github repo : 
-https://lists.qualcomm.com/ListManager
-
-In the searchbox, one need to find the contributor/maintainer list corresponding to the repo. 
-If the repo is named "pkg-example", then the list(s) to search for are : 
-
-- contributors.pkg-example
-- maintainers.pkg-example
-
-It takes about an hour between the list acceptance and the new role to reflect in Github
-
-## Getting in Contact
-
-For support or inquiries, contact sbeaudoi@qti.qualcomm.com.
+Graph service repository supports various build systems: Android, Autotools. CMake is work in progress.
+Refer meta-audioreach [README](https://github.com/Audioreach/meta-audioreach?tab=readme-ov-file#openembedded-build--development-process) for instructions to use Graph Service on OpenEmbedded system.
 
 ## License
 
-pkg-template is licensed under the [BSD-3-Clause License](https://spdx.org/licenses/BSD-3-Clause.html). See [LICENSE.txt](LICENSE.txt) for the full license text.
+Graph service is licensed under the BSD-3-Clause. Check out the [LICENSE](LICENSE) for more details.