Community & Contributing

The Agentic Commerce Protocol is an open standard that benefits from community involvement. Whether you’re building integrations, writing documentation, or sharing knowledge, there are many ways to contribute.

Join the Community

Discussion Channels

Stay Updated

• Newsletter: Subscribe for protocol updates and best practices
• Blog: Read technical deep-dives and case studies
• Release Notes: Track specification changes

Ways to Contribute

Documentation

Help improve our documentation:

1. Find an issue - Look for documentation issues labeled docs or good first issue

2. Fork the repository

   git clone https://github.com/your-org/acp-docs.git

3. Make your changes - Edit MDX files in the content/ directory

4. Submit a pull request - Include a clear description of your changes

Code Examples

Share your integration patterns:

## Example Submission Template
 
**Title**: [Your example name]
**Platform**: [e.g., Node.js, Python, Go]
**Category**: [Product Feed / Checkout / Payment]
 
### Description
Brief description of what this example demonstrates.
 
### Code
```[language]
// Your code here

Notes

Any important considerations or limitations.

### Bug Reports

Found a bug? Help us fix it:

1. **Check existing issues** - Search to see if it's already reported

2. **Gather information**
   - What you expected
   - What actually happened
   - Steps to reproduce
   - Environment details

3. **Create detailed report** - Use our issue template for consistency

4. **Follow up** - Respond to questions and test fixes

### Feature Requests

Suggest new features:

<Callout type="info" emoji="💡">
  Good feature requests include:
  - Clear problem statement
  - Proposed solution
  - Use cases
  - Potential impact
</Callout>

## Code of Conduct

We're committed to providing a welcoming and inclusive environment.

### Our Standards

**Be respectful**: Treat everyone with respect. No harassment, discrimination, or personal attacks.

**Be constructive**: Provide helpful feedback. Focus on improvement, not criticism.

**Be patient**: Remember that everyone is learning. Be patient with questions.

**Be collaborative**: Work together. Share knowledge freely.

### Unacceptable Behavior

- Harassment or discrimination
- Personal attacks or insults
- Spam or self-promotion
- Sharing private information
- Disruptive behavior

### Enforcement

Violations may result in:
1. Warning
2. Temporary ban
3. Permanent ban

Report issues to: community@example.com

## Contributing Guidelines

### Pull Request Process

1. **Create a branch**
   ```bash
   git checkout -b feature/your-feature-name

2. Make changes - Follow our coding standards

3. Write tests - Ensure adequate test coverage

4. Update documentation - Document any new features

5. Submit PR - Use our PR template

Commit Messages

Follow conventional commits:

type(scope): description

[optional body]

[optional footer]

Types:

• feat: New feature
• fix: Bug fix
• docs: Documentation
• style: Formatting
• refactor: Code restructuring
• test: Tests
• chore: Maintenance

Examples:

feat(checkout): add support for gift wrapping
fix(products): correct price calculation for variants
docs(tutorials): add Python integration guide

Code Standards

JavaScript/TypeScript

// Use meaningful names
const checkoutSession = await createSession(cart);
 
// Handle errors properly
try {
  const result = await processPayment(token);
} catch (error) {
  logger.error('Payment failed:', error);
  throw new PaymentError(error.message);
}
 
// Document public APIs
/**
 * Creates a new checkout session
 * @param {Cart} cart - The shopping cart
 * @param {BuyerContext} context - Buyer information
 * @returns {Promise<Session>} The created session
 */
async function createSession(cart, context) {
  // ...
}

Documentation

• Use clear, concise language
• Include code examples
• Add callouts for important notes
• Keep formatting consistent
• Test all code samples

Recognition

Contributors

We recognize contributors in several ways:

• Contributors page: Listed on our website
• Release notes: Mentioned in changelogs
• Social media: Highlighted on Twitter/X

Hall of Fame

Top contributors who have made significant impact:

Roadmap Input

Help shape the future of ACP:

Current Priorities

Feature Voting

Vote on upcoming features in GitHub Discussions:

• 👍 Upvote features you want
• 💬 Comment with use cases
• 📝 Propose alternatives

Events

Upcoming Events

Past Events

FAQ for Contributors

How do I get started?

1. Read the documentation
2. Try the tutorials
3. Pick a good first issue
4. Ask questions in Discord

Can I contribute without coding?

Yes! We need help with:

• Documentation improvements
• Translation
• Design feedback
• Testing and bug reports
• Community support

How long do PRs take to review?

We aim to provide initial feedback within 1 week. Complex changes may take longer.

Can I use ACP in my commercial project?

Yes! ACP is an open standard. See our license for details.

Resources for Contributors

Contact

General Questions

• Discord: Fastest response
• GitHub Discussions: Detailed technical questions
• Email: community@example.com

Security Issues

Report security vulnerabilities privately:

• Email: security@example.com
• Do not create public issues for security problems

Media Inquiries

• Email: press@example.com