chore(security): enhance environment configuration, CI workflows, and wallet daemon with security improvements
- Restructure .env.example with security-focused documentation, service-specific environment file references, and AWS Secrets Manager integration - Update CLI tests workflow to single Python 3.13 version, add pytest-mock dependency, and consolidate test execution with coverage - Add comprehensive security validation to package publishing workflow with manual approval gates, secret scanning, and release
This commit is contained in:
oib
73
docs/governance/CODEOWNERS
Normal file
73
docs/governance/CODEOWNERS
Normal file
@@ -0,0 +1,73 @@
|
||||
# CODEOWNERS file for AITBC project
|
||||
# This file defines individuals or teams that are responsible for code review
|
||||
# for each file/directory in the repository.
|
||||
|
||||
# Global owners - can review any file
|
||||
* @aitbc/core-team @aitbc/maintainers
|
||||
|
||||
# Core maintainers - can review any file
|
||||
* @aitbc/core-team
|
||||
|
||||
# Security team - responsible for security-related files
|
||||
/SECURITY.md @aitbc/security-team
|
||||
/security/ @aitbc/security-team
|
||||
*.pem @aitbc/security-team
|
||||
*.key @aitbc/security-team
|
||||
bandit.toml @aitbc/security-team
|
||||
slither.config.json @aitbc/security-team
|
||||
|
||||
# Smart contracts team
|
||||
/contracts/ @aitbc/solidity-team
|
||||
*.sol @aitbc/solidity-team
|
||||
hardhat.config.js @aitbc/solidity-team
|
||||
|
||||
# CLI team
|
||||
/cli/ @aitbc/cli-team
|
||||
aitbc_cli/ @aitbc/cli-team
|
||||
tests/cli/ @aitbc/cli-team
|
||||
|
||||
# Backend/API team
|
||||
/apps/coordinator-api/ @aitbc/backend-team
|
||||
apps/*/tests/ @aitbc/backend-team
|
||||
|
||||
# Frontend team
|
||||
/apps/explorer-web/ @aitbc/frontend-team
|
||||
apps/pool-hub/ @aitbc/frontend-team
|
||||
website/ @aitbc/frontend-team
|
||||
|
||||
# Infrastructure team
|
||||
/infra/ @aitbc/infra-team
|
||||
docker-compose*.yml @aitbc/infra-team
|
||||
Dockerfile* @aitbc/infra-team
|
||||
.github/workflows/ @aitbc/infra-team
|
||||
|
||||
# Documentation team
|
||||
/docs/ @aitbc/docs-team
|
||||
*.md @aitbc/docs-team
|
||||
README.md @aitbc/docs-team
|
||||
|
||||
# GPU acceleration team
|
||||
/gpu_acceleration/ @aitbc/gpu-team
|
||||
|
||||
# Testing team
|
||||
/tests/ @aitbc/testing-team
|
||||
pytest.ini @aitbc/testing-team
|
||||
pyproject.toml @aitbc/testing-team
|
||||
|
||||
# Configuration files
|
||||
.env.example @aitbc/core-team
|
||||
*.toml @aitbc/core-team
|
||||
*.yaml @aitbc/core-team
|
||||
*.yml @aitbc/core-team
|
||||
|
||||
# Scripts and automation
|
||||
/scripts/ @aitbc/infra-team
|
||||
dev/scripts/ @aitbc/infra-team
|
||||
|
||||
# Package management
|
||||
packages/ @aitbc/core-team
|
||||
poetry.lock @aitbc/core-team
|
||||
|
||||
# Default fallback - if no other rule matches
|
||||
# This line should be last
|
||||
* @aitbc/core-team
|
||||
360
docs/governance/COMMUNITY_STRATEGY.md
Normal file
360
docs/governance/COMMUNITY_STRATEGY.md
Normal file
@@ -0,0 +1,360 @@
|
||||
# AITBC Community Adoption Strategy
|
||||
|
||||
## 🎯 Community Goals
|
||||
|
||||
- **Developers**: 100+ active contributors within 6 months
|
||||
- **Plugins**: 20+ production plugins within 3 months
|
||||
- **Adoption**: 1000+ active users within 6 months
|
||||
- **Engagement**: 80%+ satisfaction rate in community surveys
|
||||
|
||||
## 👥 Target Audiences
|
||||
|
||||
### Primary Audiences
|
||||
1. **Blockchain Developers**: Building on AITBC platform
|
||||
2. **AI/ML Engineers**: Integrating AI capabilities
|
||||
3. **Security Researchers**: Contributing to security enhancements
|
||||
4. **Open Source Contributors**: General development contributions
|
||||
|
||||
### Secondary Audiences
|
||||
1. **Enterprise Users**: Production deployments
|
||||
2. **Academic Researchers**: Research and development
|
||||
3. **Students**: Learning and development
|
||||
4. **Hobbyists**: Experimentation and innovation
|
||||
|
||||
## 🏗️ Community Infrastructure
|
||||
|
||||
### 1. Developer Portal
|
||||
```yaml
|
||||
Developer Portal Features:
|
||||
- Interactive API documentation
|
||||
- Plugin development tutorials
|
||||
- Code examples and templates
|
||||
- Development environment setup
|
||||
- Contribution guidelines
|
||||
- Code of conduct
|
||||
```
|
||||
|
||||
### 2. Community Platforms
|
||||
```yaml
|
||||
Primary Platforms:
|
||||
- GitHub Discussions: Technical discussions
|
||||
- Discord: Real-time chat and support
|
||||
- Community Forum: Long-form discussions
|
||||
- Stack Overflow Tag: Technical Q&A
|
||||
|
||||
Secondary Platforms:
|
||||
- Twitter/X: Announcements and updates
|
||||
- LinkedIn: Professional networking
|
||||
- Reddit: Community discussions
|
||||
- YouTube: Tutorials and demos
|
||||
```
|
||||
|
||||
### 3. Recognition System
|
||||
```yaml
|
||||
Contributor Recognition:
|
||||
- GitHub Contributors list
|
||||
- Community spotlight blog posts
|
||||
- Contributor badges and ranks
|
||||
- Annual community awards
|
||||
- Speaking opportunities
|
||||
```
|
||||
|
||||
## 📋 Onboarding Journey
|
||||
|
||||
### Phase 1: Discovery (Day 1)
|
||||
- **Landing Page**: Clear value proposition
|
||||
- **Quick Start Guide**: 5-minute setup
|
||||
- **Interactive Demo**: Hands-on experience
|
||||
- **Success Stories**: Real-world examples
|
||||
|
||||
### Phase 2: Exploration (Week 1)
|
||||
- **Documentation**: Comprehensive guides
|
||||
- **Tutorials**: Step-by-step learning
|
||||
- **Examples**: Real use cases
|
||||
- **Community Introduction**: Welcome and orientation
|
||||
|
||||
### Phase 3: Contribution (Week 2-4)
|
||||
- **First Contribution**: Good first issues
|
||||
- **Plugin Development**: Guided plugin creation
|
||||
- **Code Review**: Learning through review process
|
||||
- **Community Integration**: Becoming part of the team
|
||||
|
||||
### Phase 4: Advocacy (Month 2+)
|
||||
- **Advanced Contributions**: Complex features
|
||||
- **Community Leadership**: Mentoring others
|
||||
- **Content Creation**: Tutorials and articles
|
||||
- **Conference Speaking**: Sharing knowledge
|
||||
|
||||
## 🎯 Engagement Strategies
|
||||
|
||||
### 1. Content Strategy
|
||||
```yaml
|
||||
Content Types:
|
||||
- Technical Tutorials: Weekly
|
||||
- Developer Spotlights: Monthly
|
||||
- Feature Announcements: As needed
|
||||
- Best Practices: Bi-weekly
|
||||
- Case Studies: Monthly
|
||||
|
||||
Distribution Channels:
|
||||
- Blog: aitbc.dev/blog
|
||||
- Newsletter: Weekly digest
|
||||
- Social Media: Daily updates
|
||||
- Community Forums: Ongoing
|
||||
```
|
||||
|
||||
### 2. Events and Activities
|
||||
```yaml
|
||||
Regular Events:
|
||||
- Community Calls: Weekly
|
||||
- Office Hours: Bi-weekly
|
||||
- Hackathons: Quarterly
|
||||
- Workshops: Monthly
|
||||
- Conferences: Annual
|
||||
|
||||
Special Events:
|
||||
- Plugin Contests: Bi-annual
|
||||
- Security Challenges: Annual
|
||||
- Innovation Awards: Annual
|
||||
- Contributor Summit: Annual
|
||||
```
|
||||
|
||||
### 3. Support Systems
|
||||
```yaml
|
||||
Support Channels:
|
||||
- Documentation: Self-service
|
||||
- Community Forum: Peer support
|
||||
- Discord Chat: Real-time help
|
||||
- Office Hours: Expert guidance
|
||||
- Issue Tracker: Bug reports
|
||||
|
||||
Response Times:
|
||||
- Critical Issues: 4 hours
|
||||
- High Priority: 24 hours
|
||||
- Normal Priority: 72 hours
|
||||
- Low Priority: 1 week
|
||||
```
|
||||
|
||||
## 📊 Success Metrics
|
||||
|
||||
### Community Health Metrics
|
||||
```yaml
|
||||
Engagement Metrics:
|
||||
- Active Contributors: Monthly active
|
||||
- PR Merge Rate: % of PRs merged
|
||||
- Issue Resolution Time: Average resolution
|
||||
- Community Growth: New members per month
|
||||
- Retention Rate: % of contributors retained
|
||||
|
||||
Quality Metrics:
|
||||
- Code Quality: Pre-commit hook success
|
||||
- Test Coverage: % coverage maintained
|
||||
- Documentation Coverage: % of APIs documented
|
||||
- Plugin Quality: Plugin review scores
|
||||
- Security Posture: Security scan results
|
||||
```
|
||||
|
||||
### Adoption Metrics
|
||||
```yaml
|
||||
Usage Metrics:
|
||||
- Downloads: Package downloads per month
|
||||
- Active Users: Monthly active users
|
||||
- Plugin Usage: Plugin installations
|
||||
- API Calls: API usage statistics
|
||||
- Deployments: Production deployments
|
||||
|
||||
Satisfaction Metrics:
|
||||
- User Satisfaction: Survey scores
|
||||
- Developer Experience: DX surveys
|
||||
- Support Satisfaction: Support ratings
|
||||
- Community Health: Community surveys
|
||||
- Net Promoter Score: NPS score
|
||||
```
|
||||
|
||||
## 🚀 Growth Tactics
|
||||
|
||||
### 1. Developer Evangelism
|
||||
```yaml
|
||||
Evangelism Activities:
|
||||
- Conference Presentations: 5+ per year
|
||||
- Meetup Talks: 10+ per year
|
||||
- Webinars: Monthly
|
||||
- Blog Posts: Weekly
|
||||
- Social Media: Daily
|
||||
|
||||
Target Conferences:
|
||||
- PyCon: Python community
|
||||
- ETHGlobal: Ethereum community
|
||||
- KubeCon: Cloud native
|
||||
- DevOps Days: Operations
|
||||
- Security Conferences: Security focus
|
||||
```
|
||||
|
||||
### 2. Partnership Programs
|
||||
```yaml
|
||||
Partnership Types:
|
||||
- Technology Partners: Integration partners
|
||||
- Consulting Partners: Implementation partners
|
||||
- Training Partners: Education partners
|
||||
- Hosting Partners: Infrastructure partners
|
||||
- Security Partners: Security auditors
|
||||
|
||||
Partner Benefits:
|
||||
- Co-marketing opportunities
|
||||
- Technical support
|
||||
- Early access to features
|
||||
- Joint development projects
|
||||
- Revenue sharing opportunities
|
||||
```
|
||||
|
||||
### 3. Incentive Programs
|
||||
```yaml
|
||||
Incentive Types:
|
||||
- Bug Bounties: Security rewards
|
||||
- Plugin Bounties: Development rewards
|
||||
- Documentation Bounties: Content rewards
|
||||
- Community Awards: Recognition rewards
|
||||
- Travel Grants: Event participation
|
||||
|
||||
Reward Structure:
|
||||
- Critical Bugs: $500-$2000
|
||||
- Feature Development: $200-$1000
|
||||
- Documentation: $50-$200
|
||||
- Community Leadership: $100-$500
|
||||
- Innovation Awards: $1000-$5000
|
||||
```
|
||||
|
||||
## 📋 Implementation Timeline
|
||||
|
||||
### Month 1: Foundation
|
||||
- [ ] Set up community platforms
|
||||
- [ ] Create onboarding materials
|
||||
- [ ] Launch developer portal
|
||||
- [ ] Establish moderation policies
|
||||
- [ ] Create contribution guidelines
|
||||
|
||||
### Month 2: Engagement
|
||||
- [ ] Launch community events
|
||||
- [ ] Start content creation
|
||||
- [ ] Begin developer outreach
|
||||
- [ ] Implement recognition system
|
||||
- [ ] Set up support channels
|
||||
|
||||
### Month 3: Growth
|
||||
- [ ] Launch partnership program
|
||||
- [ ] Start incentive programs
|
||||
- [ ] Expand content strategy
|
||||
- [ ] Begin conference outreach
|
||||
- [ ] Implement feedback systems
|
||||
|
||||
### Month 4-6: Scaling
|
||||
- [ ] Scale community programs
|
||||
- [ ] Expand partnership network
|
||||
- [ ] Grow contributor base
|
||||
- [ ] Enhance support systems
|
||||
- [ ] Measure and optimize
|
||||
|
||||
## 🔄 Continuous Improvement
|
||||
|
||||
### Feedback Loops
|
||||
```yaml
|
||||
Feedback Collection:
|
||||
- Community Surveys: Monthly
|
||||
- User Interviews: Weekly
|
||||
- Analytics Review: Daily
|
||||
- Performance Metrics: Weekly
|
||||
- Community Health: Monthly
|
||||
|
||||
Improvement Process:
|
||||
- Data Collection: Ongoing
|
||||
- Analysis: Weekly
|
||||
- Planning: Monthly
|
||||
- Implementation: Continuous
|
||||
- Review: Quarterly
|
||||
```
|
||||
|
||||
### Community Governance
|
||||
```yaml
|
||||
Governance Structure:
|
||||
- Core Team: Strategic direction
|
||||
- Maintainers: Technical decisions
|
||||
- Contributors: Code contributions
|
||||
- Community Members: Feedback and ideas
|
||||
- Users: Product feedback
|
||||
|
||||
Decision Making:
|
||||
- Technical Decisions: Maintainer vote
|
||||
- Strategic Decisions: Core team consensus
|
||||
- Community Issues: Community discussion
|
||||
- Conflicts: Mediation process
|
||||
- Changes: RFC process
|
||||
```
|
||||
|
||||
## 📚 Resources and Templates
|
||||
|
||||
### Communication Templates
|
||||
```yaml
|
||||
Welcome Email:
|
||||
- Introduction to community
|
||||
- Onboarding checklist
|
||||
- Resource links
|
||||
- Contact information
|
||||
|
||||
Contribution Guide:
|
||||
- Development setup
|
||||
- Code standards
|
||||
- Testing requirements
|
||||
- Review process
|
||||
|
||||
Issue Templates:
|
||||
- Bug report template
|
||||
- Feature request template
|
||||
- Security issue template
|
||||
- Question template
|
||||
```
|
||||
|
||||
### Documentation Templates
|
||||
```yaml
|
||||
Plugin Template:
|
||||
- Plugin structure
|
||||
- Interface implementation
|
||||
- Testing requirements
|
||||
- Documentation format
|
||||
|
||||
Tutorial Template:
|
||||
- Learning objectives
|
||||
- Prerequisites
|
||||
- Step-by-step guide
|
||||
- Expected outcomes
|
||||
|
||||
API Documentation:
|
||||
- Endpoint description
|
||||
- Parameters
|
||||
- Examples
|
||||
- Error handling
|
||||
```
|
||||
|
||||
## 🎯 Success Criteria
|
||||
|
||||
### Short-term (3 months)
|
||||
- [ ] 50+ active contributors
|
||||
- [ ] 10+ production plugins
|
||||
- [ ] 500+ GitHub stars
|
||||
- [ ] 100+ Discord members
|
||||
- [ ] 90%+ documentation coverage
|
||||
|
||||
### Medium-term (6 months)
|
||||
- [ ] 100+ active contributors
|
||||
- [ ] 20+ production plugins
|
||||
- [ ] 1000+ GitHub stars
|
||||
- [ ] 500+ Discord members
|
||||
- [ ] 1000+ active users
|
||||
|
||||
### Long-term (12 months)
|
||||
- [ ] 200+ active contributors
|
||||
- [ ] 50+ production plugins
|
||||
- [ ] 5000+ GitHub stars
|
||||
- [ ] 2000+ Discord members
|
||||
- [ ] 10000+ active users
|
||||
|
||||
This comprehensive community adoption strategy provides a roadmap for building a thriving ecosystem around AITBC, focusing on developer experience, community engagement, and sustainable growth.
|
||||
Reference in New Issue
Block a user