feat: add marketplace metrics, privacy features, and service registry endpoints
- Add Prometheus metrics for marketplace API throughput and error rates with new dashboard panels - Implement confidential transaction models with encryption support and access control - Add key management system with registration, rotation, and audit logging - Create services and registry routers for service discovery and management - Integrate ZK proof generation for privacy-preserving receipts - Add metrics instru
This commit is contained in:
oib
203
governance/README.md
Normal file
203
governance/README.md
Normal file
@ -0,0 +1,203 @@
|
||||
---
|
||||
title: AITBC Governance
|
||||
description: Community governance and decision-making for the AITBC protocol
|
||||
layout: default
|
||||
---
|
||||
|
||||
# AITBC Governance
|
||||
|
||||
Welcome to the AITBC governance hub. This site serves as the central location for all governance-related information, including RFCs, decision records, and community participation guidelines.
|
||||
|
||||
## Quick Navigation
|
||||
|
||||
- [RFC Process](/rfc-process) - How to propose changes to AITBC
|
||||
- [Active RFCs](/active-rfcs) - Currently under discussion
|
||||
- [Accepted RFCs](/accepted-rfcs) - Approved proposals
|
||||
- [Community Calls](/calls) - Meeting schedule and recordings
|
||||
- [Governance Framework](/framework) - Roles and responsibilities
|
||||
- [Decision Log](/decisions) - Historical decisions and rationale
|
||||
|
||||
## Latest Updates
|
||||
|
||||
### Recent RFCs
|
||||
|
||||
| RFC | Title | Status | Date |
|
||||
|-----|-------|--------|------|
|
||||
| [RFC-001](/rfcs/001-multi-tenant-architecture) | Multi-tenant Architecture | Accepted | 2024-01-15 |
|
||||
| [RFC-002](/rfcs/002-ecosystem-certification) | Ecosystem Certification Program | Accepted | 2024-01-15 |
|
||||
|
||||
### Upcoming Events
|
||||
|
||||
- **Community Call**: 2024-01-22 at 14:00 UTC
|
||||
- **RFC Review**: 2024-01-24 at 16:00 UTC
|
||||
- **Governance Meeting**: 2024-01-29 at 15:00 UTC
|
||||
|
||||
## How to Participate
|
||||
|
||||
### 1. Stay Informed
|
||||
- Join our [Discord server](https://discord.gg/aitbc)
|
||||
- Subscribe to the [governance mailing list](mailto:governance@aitbc.io)
|
||||
- Watch the [rfcs repository](https://github.com/aitbc/rfcs)
|
||||
|
||||
### 2. Contribute to RFCs
|
||||
- Review draft RFCs on GitHub
|
||||
- Comment with technical feedback
|
||||
- Submit implementation proposals
|
||||
- Join community discussions
|
||||
|
||||
### 3. Join Community Calls
|
||||
- Weekly technical syncs (Tuesdays 14:00 UTC)
|
||||
- Bi-weekly governance meetings (alternating Mondays)
|
||||
- Monthly RFC reviews (last Thursday)
|
||||
|
||||
### 4. Vote on Decisions
|
||||
- Informal voting via GitHub reactions
|
||||
- Formal governance votes (when applicable)
|
||||
- Delegate participation if unable to attend
|
||||
|
||||
## Governance Structure
|
||||
|
||||
### Current Model: Benevolent Dictator
|
||||
- AITBC Foundation holds final decision authority
|
||||
- Community input strongly considered
|
||||
- Transparent decision-making process
|
||||
- Gradual decentralization planned
|
||||
|
||||
### Transition Plan
|
||||
- Phase 1 (Current): Foundation-led with community input
|
||||
- Phase 2 (After 100 RFCs): Delegate voting system
|
||||
- Phase 3 (Future): Full on-chain governance
|
||||
|
||||
### Roles and Responsibilities
|
||||
|
||||
#### AITBC Foundation
|
||||
- Maintains core protocol
|
||||
- Ensures network security
|
||||
- Facilitates community growth
|
||||
- Holds veto power (with sunset clause)
|
||||
|
||||
#### Core Team
|
||||
- Technical review of RFCs
|
||||
- Implementation of accepted proposals
|
||||
- Network operations
|
||||
- Security oversight
|
||||
|
||||
#### Community Contributors
|
||||
- RFC proposals and reviews
|
||||
- Code contributions
|
||||
- Documentation
|
||||
- Testing and feedback
|
||||
|
||||
#### Delegates
|
||||
- Represent stakeholder interests
|
||||
- Vote on governance decisions
|
||||
- Participate in working groups
|
||||
- Communicate with constituencies
|
||||
|
||||
## Working Groups
|
||||
|
||||
### Protocol Working Group
|
||||
- Core protocol improvements
|
||||
- Consensus mechanisms
|
||||
- Cross-chain functionality
|
||||
- Network parameters
|
||||
|
||||
### Ecosystem Working Group
|
||||
- SDK standards
|
||||
- Connector specifications
|
||||
- Certification requirements
|
||||
- Developer experience
|
||||
|
||||
### Governance Working Group
|
||||
- Process improvements
|
||||
- Election procedures
|
||||
- Community guidelines
|
||||
- Transparency initiatives
|
||||
|
||||
### Security Working Group
|
||||
- Security audits
|
||||
- Vulnerability disclosure
|
||||
- Best practices
|
||||
- Incident response
|
||||
|
||||
## Decision Making Process
|
||||
|
||||
### Types of Decisions
|
||||
|
||||
#### Protocol Changes
|
||||
- Require RFC process
|
||||
- Technical review mandatory
|
||||
- Security assessment required
|
||||
- Implementation timeline specified
|
||||
|
||||
#### Governance Changes
|
||||
- Require RFC process
|
||||
- Community consultation required
|
||||
- 30-day comment period
|
||||
- Supermajority approval needed
|
||||
|
||||
#### Operational Decisions
|
||||
- Made by Core Team
|
||||
- Documented in decision log
|
||||
- Community notification required
|
||||
- Appeal process available
|
||||
|
||||
### Voting Mechanisms
|
||||
|
||||
#### Informal Voting
|
||||
- GitHub reactions on RFC PRs
|
||||
- Discord polls for minor decisions
|
||||
- Show of hands in community calls
|
||||
- Non-binding but influential
|
||||
|
||||
#### Formal Voting
|
||||
- Token-based voting (Phase 2)
|
||||
- Delegate voting (Phase 2)
|
||||
- Multi-sig wallet approvals
|
||||
- On-chain execution
|
||||
|
||||
## Transparency and Accountability
|
||||
|
||||
### Decision Records
|
||||
- All decisions documented
|
||||
- Rationale clearly explained
|
||||
- Alternatives considered
|
||||
- Implementation status tracked
|
||||
|
||||
### Financial Transparency
|
||||
- Foundation treasury reports
|
||||
- Grant program updates
|
||||
- Expense documentation
|
||||
- Annual financial statements
|
||||
|
||||
### Performance Metrics
|
||||
- Network statistics
|
||||
- Developer activity
|
||||
- Ecosystem growth
|
||||
- Governance participation
|
||||
|
||||
## Get Started
|
||||
|
||||
1. **Read the RFC Process** - Understand how to propose changes
|
||||
2. **Join the Community** - Connect with other contributors
|
||||
3. **Review Active RFCs** - Participate in current discussions
|
||||
4. **Attend a Call** - Join the next community meeting
|
||||
5. **Contribute** - Start with documentation or testing
|
||||
|
||||
## Contact
|
||||
|
||||
- **Governance**: governance@aitbc.io
|
||||
- **RFC Process**: rfcs@aitbc.io
|
||||
- **Security**: security@aitbc.io
|
||||
- **General**: community@aitbc.io
|
||||
|
||||
## Archives
|
||||
|
||||
- [Historical Decisions](/archives/decisions)
|
||||
- [Past Community Calls](/archives/calls)
|
||||
- [Rejected RFCs](/archives/rejected-rfcs)
|
||||
- [Governance Evolution](/archives/evolution)
|
||||
|
||||
---
|
||||
|
||||
*This governance site is maintained by the AITBC community. Last updated: 2024-01-15*
|
||||
283
governance/calls.md
Normal file
283
governance/calls.md
Normal file
@ -0,0 +1,283 @@
|
||||
---
|
||||
title: Community Calls
|
||||
description: Schedule, recordings, and participation guidelines for AITBC community calls
|
||||
layout: default
|
||||
---
|
||||
|
||||
# AITBC Community Calls
|
||||
|
||||
Community calls are regular meetings where the AITBC community discusses technical topics, reviews RFCs, and makes governance decisions. All calls are open to the public.
|
||||
|
||||
## Call Schedule
|
||||
|
||||
### Weekly Technical Sync
|
||||
- **When**: Every Tuesday at 14:00 UTC
|
||||
- **Duration**: 60 minutes
|
||||
- **Focus**: Technical updates, development progress, Q&A
|
||||
- **Recording**: Yes, published within 24 hours
|
||||
|
||||
### Bi-weekly Governance Meeting
|
||||
- **When**: Alternating Mondays at 15:00 UTC
|
||||
- **Duration**: 90 minutes
|
||||
- **Focus**: RFC reviews, governance decisions, policy discussions
|
||||
- **Recording**: Yes, published within 48 hours
|
||||
|
||||
### Monthly RFC Review
|
||||
- **When**: Last Thursday of the month at 16:00 UTC
|
||||
- **Duration**: 120 minutes
|
||||
- **Focus**: Deep dive into active RFCs, author presentations
|
||||
- **Recording**: Yes, published within 72 hours
|
||||
|
||||
### Quarterly Town Hall
|
||||
- **When**: First Friday of the quarter at 18:00 UTC
|
||||
- **Duration**: 90 minutes
|
||||
- **Focus**: Roadmap updates, ecosystem announcements, community awards
|
||||
- **Recording**: Yes, live-streamed
|
||||
|
||||
## Upcoming Calls
|
||||
|
||||
| Date | Time (UTC) | Type | Agenda | Recording |
|
||||
|------|------------|------|--------|------------|
|
||||
| 2024-01-16 | 14:00 | Technical Sync | [Agenda](#) | - |
|
||||
| 2024-01-22 | 15:00 | Governance | [Agenda](#) | - |
|
||||
| 2024-01-23 | 14:00 | Technical Sync | [Agenda](#) | - |
|
||||
| 2024-01-25 | 16:00 | RFC Review | [Agenda](#) | - |
|
||||
|
||||
## How to Join
|
||||
|
||||
### Video Call
|
||||
- **Zoom**: [Link](https://zoom.us/aitbc)
|
||||
- **Meeting ID**: 123-456-7890
|
||||
- **Password**: aitbc2024
|
||||
|
||||
### Audio Only
|
||||
- **Phone**: +1 (555) 123-4567
|
||||
- **International**: [List of numbers](https://aitbc.io/call-numbers)
|
||||
|
||||
### Chat
|
||||
- **Discord**: #community-calls channel
|
||||
- **Slack**: #general channel
|
||||
|
||||
## Participation Guidelines
|
||||
|
||||
### Before the Call
|
||||
1. **Review the Agenda** - Add topics to GitHub issues
|
||||
2. **Prepare Questions** - Submit via GitHub or Discord
|
||||
3. **Test Your Setup** - Check audio/video before joining
|
||||
4. **Respect Time Zones** - Be mindful of global participants
|
||||
|
||||
### During the Call
|
||||
1. **Mute When Not Speaking** - Reduce background noise
|
||||
2. **Use Raise Hand Feature** - Wait to be called on
|
||||
3. **Be Concise** - Keep comments brief and on-topic
|
||||
4. **Be Respectful** - Professional discourse required
|
||||
|
||||
### After the Call
|
||||
1. **Continue Discussion** - Use GitHub issues for follow-up
|
||||
2. **Share Feedback** - Help us improve the format
|
||||
3. **Take Action Items** - Complete assigned tasks
|
||||
4. **Join Next Time** - Regular participation valued
|
||||
|
||||
## Call Recordings
|
||||
|
||||
### 2024-01-09 - Technical Sync
|
||||
- **Topics**: Multi-tenant architecture, certification program
|
||||
- **Duration**: 58 minutes
|
||||
- **Recording**: [YouTube](https://youtu.be/example)
|
||||
- **Summary**: [Notes](/calls/2024-01-09-summary)
|
||||
- **Action Items**: [GitHub Project](https://github.com/aitbc/projects/1)
|
||||
|
||||
### 2024-01-02 - Governance Meeting
|
||||
- **Topics**: RFC process approval, governance framework
|
||||
- **Duration**: 82 minutes
|
||||
- **Recording**: [YouTube](https://youtu.be/example)
|
||||
- **Summary**: [Notes](/calls/2024-01-02-summary)
|
||||
- **Action Items**: [GitHub Project](https://github.com/aitbc/projects/1)
|
||||
|
||||
### 2023-12-26 - Technical Sync
|
||||
- **Topics**: Holiday break, Q1 planning
|
||||
- **Duration**: 45 minutes
|
||||
- **Recording**: [YouTube](https://youtu.be/example)
|
||||
- **Summary**: [Notes](/calls/2023-12-26-summary)
|
||||
|
||||
## Call Archives
|
||||
|
||||
All recordings are available on:
|
||||
- [YouTube Playlist](https://youtube.com/aitbc-calls)
|
||||
- [Podcast Feed](https://aitbc.io/podcast)
|
||||
- [Transcripts](/calls/transcripts)
|
||||
|
||||
## Call Templates
|
||||
|
||||
### Technical Sync Agenda Template
|
||||
|
||||
```markdown
|
||||
## Technical Sync - YYYY-MM-DD
|
||||
|
||||
### Welcome & Announcements (5 min)
|
||||
- Community updates
|
||||
- New contributors
|
||||
- Upcoming events
|
||||
|
||||
### Development Updates (20 min)
|
||||
- Core protocol progress
|
||||
- SDK updates
|
||||
- Infrastructure status
|
||||
- Bug fixes
|
||||
|
||||
### RFC Review (15 min)
|
||||
- New RFCs
|
||||
- Active discussions
|
||||
- Implementation status
|
||||
|
||||
### Community Updates (10 min)
|
||||
- Ecosystem news
|
||||
- Partner updates
|
||||
- Community highlights
|
||||
|
||||
### Q&A (10 min)
|
||||
- Open floor for questions
|
||||
- Help wanted items
|
||||
- Next steps
|
||||
|
||||
### Action Items Review (5 min)
|
||||
- Previous items status
|
||||
- New assignments
|
||||
- Follow-up required
|
||||
```
|
||||
|
||||
### Governance Meeting Agenda Template
|
||||
|
||||
```markdown
|
||||
## Governance Meeting - YYYY-MM-DD
|
||||
|
||||
### Call to Order (5 min)
|
||||
- Quorum check
|
||||
- Previous minutes approval
|
||||
- Action items review
|
||||
|
||||
### RFC Discussions (30 min)
|
||||
- RFC-XXX: [Title]
|
||||
- Status update
|
||||
- Feedback summary
|
||||
- Decision needed
|
||||
- RFC-YYY: [Title]
|
||||
- Implementation progress
|
||||
- Blockers identified
|
||||
|
||||
### Governance Matters (20 min)
|
||||
- Process improvements
|
||||
- Policy updates
|
||||
- Community feedback
|
||||
- Election updates
|
||||
|
||||
### Ecosystem Updates (15 min)
|
||||
- Partner certifications
|
||||
- Developer metrics
|
||||
- Grant programs
|
||||
- Marketing initiatives
|
||||
|
||||
### Open Floor (10 min)
|
||||
- Community proposals
|
||||
- Urgent matters
|
||||
- Future agenda items
|
||||
|
||||
### Adjournment (5 min)
|
||||
- Summary of decisions
|
||||
- Action items assigned
|
||||
- Next meeting date
|
||||
```
|
||||
|
||||
## Moderation Guidelines
|
||||
|
||||
### Moderators
|
||||
- **Primary**: AITBC Foundation representative
|
||||
- **Secondary**: Core team member
|
||||
- **Community**: Rotating volunteer
|
||||
|
||||
### Responsibilities
|
||||
1. Keep discussions on topic
|
||||
2. Ensure all voices are heard
|
||||
3. Manage time effectively
|
||||
4. Document decisions and action items
|
||||
5. Enforce code of conduct
|
||||
|
||||
### Code of Conduct
|
||||
- Be respectful and inclusive
|
||||
- No harassment or discrimination
|
||||
- Professional language required
|
||||
- Confidential information protected
|
||||
- Violations result in removal
|
||||
|
||||
## Special Events
|
||||
|
||||
### Hackathons
|
||||
- **Frequency**: Quarterly
|
||||
- **Duration**: 48 hours
|
||||
- **Format**: Virtual + optional meetups
|
||||
- **Prizes**: Grants and recognition
|
||||
|
||||
### Workshops
|
||||
- **Frequency**: Monthly
|
||||
- **Topics**: Technical deep dives
|
||||
- **Format**: Interactive sessions
|
||||
- **Materials**: Published afterward
|
||||
|
||||
### Conferences
|
||||
- **Frequency**: Annual
|
||||
- **Location**: Rotating global cities
|
||||
- **Tracks**: Technical, Business, Community
|
||||
- **CFP**: Open 6 months prior
|
||||
|
||||
## Feedback and Improvement
|
||||
|
||||
### Provide Feedback
|
||||
- **Survey**: Quarterly community survey
|
||||
- **Issues**: Use GitHub for suggestions
|
||||
- **Email**: calls@aitbc.io
|
||||
- **Discord**: #feedback channel
|
||||
|
||||
### Metrics We Track
|
||||
- Attendance numbers
|
||||
- Geographic distribution
|
||||
- Participation diversity
|
||||
- Satisfaction scores
|
||||
- Action item completion
|
||||
|
||||
### Recent Improvements
|
||||
- Added transcription service
|
||||
- Improved audio quality
|
||||
- Better agenda management
|
||||
- Enhanced documentation
|
||||
- Mobile-friendly access
|
||||
|
||||
## FAQ
|
||||
|
||||
### Q: Can I present at a community call?
|
||||
A: Yes! Submit your topic via GitHub issue with "presentation:" tag.
|
||||
|
||||
### Q: Are calls mandatory for contributors?
|
||||
A: No, but regular participation is valued for governance decisions.
|
||||
|
||||
### Q: How are moderators selected?
|
||||
A: Initially by Foundation, transitioning to community elections.
|
||||
|
||||
### Q: Can I request a specific topic?
|
||||
A: Absolutely! Add it to the agenda GitHub issue.
|
||||
|
||||
### Q: What if I can't make the time?
|
||||
A: All calls are recorded and transcribed for asynchronous participation.
|
||||
|
||||
### Q: How are action items tracked?
|
||||
A: Via GitHub Projects with assignees and due dates.
|
||||
|
||||
## Contact
|
||||
|
||||
- **Call Schedule**: schedule@aitbc.io
|
||||
- **Technical Issues**: tech@aitbc.io
|
||||
- **Moderation**: moderation@aitbc.io
|
||||
- **General**: community@aitbc.io
|
||||
|
||||
---
|
||||
|
||||
*Last updated: 2024-01-15*
|
||||
Reference in New Issue
Block a user