docs: link to contribution guide updated

[Sandy-at-Tazama]

SPDX-License-Identifier: Apache-2.0

What did we change?

• Changed the contribution guide link from frmscoe to tazama-lf org

Why are we doing this?

• tazama-lf is the primary public org

How was it tested?

• Locally
• Development Environment
• Not needed, changes very basic
• Husky successfully run
• Unit tests passing and Documentation done

Summary by CodeRabbit

• Documentation
  • Updated Code of Conduct reference to direct community members to current governance documentation
  • Updated Contribution Guide reference to provide access to latest contribution standards
  • These updates ensure consistency with project resources and support effective community engagement

[coderabbitai]

📝 Walkthrough

Walkthrough

Community documentation files updated to reference the new tazama-lf GitHub organization instead of frmscoe, with links to Code of Conduct and Contributing guides redirected accordingly.

Changes

Cohort / File(s)	Summary
Community Documentation Links Community/Tazama-Code-of-Conduct.md, Community/Tazama-Contribution-Guide.md	Updated GitHub organization references from frmscoe to tazama-lf in links to CODE_OF_CONDUCT.md and CONTRIBUTING.md.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 The burrow's been renamed, you see,
From frmscoe to tazama-lf with glee,
Links updated, bright and new,
Community guides pointing true! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: link to contribution guide updated' accurately reflects the main change: updating documentation links from frmscoe to tazama-lf organization.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch tazama/contribution_guide

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@Community/Tazama-Contribution-Guide.md`:
- Line 5: Search the repository for all occurrences of the legacy organization
string "frmscoe" (including "@frmscoe" npm scope, "frmscoe/" repository links,
and any URLs or clone commands), then update them to "tazama-lf" (or
"@tazama-lf" for npm scopes and "tazama-lf/" for repo paths) while preserving
any intentional historical references (leave JIRA/Atlassian wiki links unchanged
if they must remain). Specifically, update mentions in
Community/Tazama-Contribution-Guide.md, package.json npm scopes, CI/CD workflow
files, processor/config docs, integration guides (Mojaloop adapter), README
clone commands, and CHANGELOG entries; run a repository-wide grep to locate all
instances, perform safe replacements, update any affected URLs, and verify
references compile and tests/CI still pass. Ensure commit message clearly states
the rename from frmscoe to tazama-lf and include a short PR description listing
files changed.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Search for any remaining references to frmscoe organization

# Search for frmscoe references in markdown files
rg -i 'frmscoe' --type=md -C 2

Repository: tazama-lf/docs

Length of output: 30539

---

Multiple remaining references to frmscoe organization found throughout the repository that should be updated to tazama-lf.

The search confirmed numerous references beyond the Community contribution guide, including:

• Repository links in technical documentation (processor configs, CI/CD workflows, release management)
• Integration guides (Mojaloop Payment Platform Adapter, upstream/downstream integration)
• Setup and development guides
• Product documentation and glossaries
• npm package scope references (@frmscoe)
• Git clone commands and CHANGELOG entries

Review and update references as appropriate, noting that some JIRA/Atlassian wiki links may be intentional historical references that do not require migration.

🤖 Prompt for AI Agents

In `@Community/Tazama-Contribution-Guide.md` at line 5, Search the repository for
all occurrences of the legacy organization string "frmscoe" (including
"@frmscoe" npm scope, "frmscoe/" repository links, and any URLs or clone
commands), then update them to "tazama-lf" (or "@tazama-lf" for npm scopes and
"tazama-lf/" for repo paths) while preserving any intentional historical
references (leave JIRA/Atlassian wiki links unchanged if they must remain).
Specifically, update mentions in Community/Tazama-Contribution-Guide.md,
package.json npm scopes, CI/CD workflow files, processor/config docs,
integration guides (Mojaloop adapter), README clone commands, and CHANGELOG
entries; run a repository-wide grep to locate all instances, perform safe
replacements, update any affected URLs, and verify references compile and
tests/CI still pass. Ensure commit message clearly states the rename from
frmscoe to tazama-lf and include a short PR description listing files changed.