csnitker-godaddy · Oct 27, 2026 · Oct 27, 2026 · Oct 27, 2026 · Oct 28, 2026 · Oct 28, 2026
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -0,0 +1,2 @@
+# Review routing; merge permissions are managed separately.
+* @agentnameservice/sdk-java-maintainers @agentnameservice/sdk-java-reviewers @agentnameservice/tsc @agentnameservice/tsc-owners
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -1,133 +1,5 @@
+# Code of Conduct
 
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-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, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[email protected].
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
-
-Community Impact Guidelines were inspired by 
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
-at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations
+The [ANS Code of Conduct](https://github.com/agentnameservice/governance/blob/main/CODE_OF_CONDUCT.md)
+applies to participation in this repository. It defines the reporting process,
+contacts, and enforcement procedures for the project.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,91 +1,43 @@
 # Contributing
 
-Everyone is welcome to contribute to GoDaddy's Open Source Software.
-Contributing doesn’t just mean submitting pull requests. To get involved,
-you can report or triage bugs, and participate in discussions on the
-evolution of each project.
+Follow the [ANS contribution guide](https://github.com/agentnameservice/.github/blob/main/CONTRIBUTING.md)
+and [governance](https://github.com/agentnameservice/governance/blob/main/GOVERNANCE.md).
+They define DCO sign-off, pull request review, issue references, and disclosure
+of AI assistance.
 
-No matter how you want to get involved, we ask that you first learn what’s
-expected of anyone who participates in the project by reading the Contribution
-Guidelines and our [Code of Conduct][coc].
+The [Code of Conduct](CODE_OF_CONDUCT.md) applies to all participation.
+Report vulnerabilities privately using [SECURITY.md](SECURITY.md).
+The repository's [Maintainers](MAINTAINERS.md) handle reviews and releases.
 
-## Answering Questions
+## Licensing new contributions
 
-One of the most important and immediate ways you can support this project is
-to answer questions on [Github][issues]. Whether you’re
-helping a newcomer understand a feature or troubleshooting an edge case with a
-seasoned developer, your knowledge and experience with a programming language
-can go a long way to help others.
+This policy applies to new original contributions submitted after its adoption.
+By submitting such a contribution for inclusion in ANS, you agree to license it
+under the [Apache License, Version 2.0](LICENSE), including its copyright and
+patent grants. Only submit material that you have the right to license on those
+terms, and sign off each commit under the Developer Certificate of Origin below.
 
-## Reporting Bugs
+Pre-existing contributions retain the licenses under which they were submitted.
+In particular, earlier MIT-licensed contributions remain under
+[LICENSES/MIT.txt](LICENSES/MIT.txt); this policy does not claim an Apache patent grant from
+those contributors for their earlier work. Preserve existing copyright and
+third-party license notices when modifying or incorporating material.
 
-**Do not report potential security vulnerabilities here. Refer to
-[SECURITY.md](./SECURITY.md) for more details about the process of reporting
-security vulnerabilities.**
+## Development
 
-Before submitting a ticket, please search our [Issue Tracker][issues] to make
-sure it does not already exist and have a simple replication of the behavior. If
-the issue is isolated to one of the dependencies of this project, please create
-a Github issue in that project. All dependencies should be open source software
-and can be found on Github.
-
-Submit a ticket for your issue, assuming one does not already exist:
-
-- Create it on the project's [issue Tracker][issues].
-- Clearly describe the issue by following the template layout
-  - Make sure to include steps to reproduce the bug.
-  - A reproducible (unit) test could be helpful in solving the bug.
-  - Describe the environment that (re)produced the problem.
-
-## Triaging bugs or contributing code
-
-If you're triaging a bug, first make sure that you can reproduce it. Once a bug
-can be reproduced, reduce it to the smallest amount of code possible. Reasoning
-about a sample or unit test that reproduces a bug in just a few lines of code
-is easier than reasoning about a longer sample.
-
-From a practical perspective, contributions are as simple as:
-
-1. Fork and clone the repo, [see Github's instructions if you need help.][fork]
-1. Create a branch for your PR with `git checkout -b pr/your-branch-name`
-1. Make changes on the branch of your forked repository.
-1. When committing, reference your issue (if present) and include a note about
-   the fix.
-1. Please also add/update unit tests for your changes.
-1. Push the changes to your fork and submit a pull request to the 'main
-   development branch' branch of the projects' repository.
-
-If you are interested in making a large change and feel unsure about its overall
-effect, start with opening an Issue in the project's [Issue Tracker][issues]
-with a high-level proposal and discuss it with the core contributors through
-Github comments. After reaching a consensus with core
-contributors about the change, discuss the best way to go about implementing it.
-
-> Tip: Keep your main branch pointing at the original repository and make
-> pull requests from branches on your fork. To do this, run:
->
-> ```
-> git remote add upstream https://github.com/agentnameservice/ans-sdk-java.git
-> git fetch upstream
-> git branch --set-upstream-to=upstream/main main
-> ```
->
-> This will add the original repository as a "remote" called "upstream," Then
-> fetch the git information from that remote, then set your local main
-> branch to use the upstream main branch whenever you run git pull. Then you
-> can make all of your pull request branches based on this main branch.
-> Whenever you want to update your version of main, do a regular git pull.
+See the [build and test instructions](README.md#building-from-source) in the README.
 
 ## Commit Messages
 
 This project uses [Conventional Commits](https://www.conventionalcommits.org/) to
 automate versioning and changelog generation. Commit messages must follow this format:
 
-```
+```text
 <type>[optional scope]: <description>
 ```
 
 Common types:
+
 - `feat:` — A new feature (minor version bump)
 - `fix:` — A bug fix (patch version bump)
 - `docs:` — Documentation changes
@@ -101,80 +53,3 @@ breaking changes.
 
 Commits that do not follow this format are ignored by the release automation and will
 not appear in the changelog or trigger a version bump.
-
-## Code Review
-
-Any open source project relies heavily on code review to improve software
-quality. All significant changes, by all developers, must be reviewed before
-they are committed to the repository. Code reviews are conducted on GitHub
-through comments on pull requests or commits. The developer responsible for a
-code change is also responsible for making all necessary review-related changes.
-
-Sometimes code reviews will take longer than you would hope for, especially for
-larger features. Here are some accepted ways to speed up review times for your
-patches:
-
-- Review other people’s changes. If you help out, others will more likely be
-  willing to do the same for you.
-- Split your change into multiple smaller changes. The smaller your change,
-  the higher the probability that somebody will take a quick look at it.
-
-**Note that anyone is welcome to review and give feedback on a change, but only
-people with commit access to the repository can approve it.**
-
-## Attribution of Changes
-
-When contributors submit a change to this project, after that change is
-approved, other developers with commit access may commit it for the author. When
-doing so, it is important to retain correct attribution of the contribution.
-Generally speaking, Git handles attribution automatically.
-
-## Code Style and Documentation
-
-Ensure that your contribution follows the standards set by the project's style
-guide with respect to patterns, naming, documentation and testing.
-
-## Developer Certificate of Origin
-
-This project follows the Linux Foundation contribution model. Every commit
-must carry a `Signed-off-by:` trailer certifying the
-[Developer Certificate of Origin](https://developercertificate.org) — your
-assertion that you have the right to submit the change under the project's
-license. Sign off each commit with:
-
-```
-git commit -s
-```
-
-Missing sign-offs on an existing branch can be fixed with
-`git rebase --signoff origin/main` followed by a force-push. The `DCO`
-status check — the org-wide [DCO app](https://github.com/apps/dco), the
-same enforcement used across Linux Foundation projects — validates this
-on every pull request; bot-authored commits (Dependabot, release-please)
-and merge commits are exempt.
-
-## AI-Assisted Contributions
-
-AI-assisted contributions are welcome **with disclosure**, following the
-[Linux kernel convention](https://docs.kernel.org/process/coding-assistants.html):
-
-- Disclose the tooling in the pull request's **AI assistance** section,
-  naming the tool and model, e.g. `Assisted-by: Claude Code (claude-fable-5)`.
-- AI tools must never add `Signed-off-by:` lines. DCO certification belongs
-  to the human submitter, who remains fully responsible for the correctness
-  and licensing of the contribution.
-
-## Linking Issues
-
-Every pull request must reference an issue with a closing keyword (e.g.
-`Fixes #123`). Open the issue first — issues are where triage and
-prioritization happen.
-
-# Additional Resources
-
-- [General GitHub Documentation](https://help.github.com/)
-- [GitHub Pull Request documentation](https://help.github.com/send-pull-requests/)
-
-[issues]: https://github.com/agentnameservice/ans-sdk-java/issues
-[coc]: ./CODE_OF_CONDUCT.md
-[fork]: https://help.github.com/en/articles/fork-a-repo
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		# Review routing; merge permissions are managed separately.
		* @agentnameservice/sdk-java-maintainers @agentnameservice/sdk-java-reviewers @agentnameservice/tsc @agentnameservice/tsc-owners