-
Notifications
You must be signed in to change notification settings - Fork 0
TEAM.md
Document Type: Team, Roles & Contribution Structure Project: CeloHT Status: Active / Evolving Last Updated: August 2026 Authors: CeloHT Community
CeloHT is a community-oriented Web3 ecosystem focused on financial inclusion, education, decentralized services, and environmental impact.
The project is built around community participation rather than dependence on a traditional centralized corporate hierarchy.
CeloHT recognizes that sustainable development requires contributions from people with different skills, responsibilities, and areas of expertise.
Johnny Dubic is the founder of CeloHT.
The founder provides historical context, strategic direction, project continuity, and support for ecosystem development.
Founder status does not automatically mean unilateral authority over all community decisions.
CeloHT's governance model is designed to encourage community participation and collective decision-making.
CeloHT is designed around a community-oriented governance model.
Depending on the decision, participation may occur through:
- Community discussions
- Proposals
- Voting
- Working groups
- Governance bodies
- Contributor review
The exact authority of each mechanism is defined in the relevant governance documentation.
CeloHT values:
- Contribution over titles
- Accountability over hierarchy
- Transparency over secrecy
- Collaboration over isolation
- Evidence over unsupported claims
- Community benefit over individual recognition
CeloHT may organize work around the following functions:
Long-term project direction and priorities.
Software development, infrastructure, integrations, and technical architecture.
Security engineering, vulnerability management, audits, and incident response.
Training programs, curriculum development, and financial literacy.
Community organization, events, communications, and contributor engagement.
Agent onboarding, training, operations, and support.
Reforestation and environmental initiatives.
Research, analysis, documentation, and evidence-based program development.
Public information, media, publications, and project communications.
Coordination, documentation, administration, and program execution.
CeloHT contributors may include:
- Developers
- Designers
- Educators
- Researchers
- Community organizers
- Agents
- Writers
- Translators
- Security researchers
- Environmental volunteers
- Technical contributors
Contributors may participate on a voluntary, contractual, partnership, or other appropriate basis.
CeloHT may organize contributors into specialized working groups.
Examples include:
- Technology Working Group
- Education Working Group
- Community Working Group
- Security Working Group
- Environmental Working Group
- Research Working Group
- Communications Working Group
See WORKING_GROUPS.md.
Where established under the CeloHT governance framework, a Governance Council may help coordinate important community decisions.
Its authority should be explicitly defined.
Council membership should not be confused with ownership of the project.
Maintainers are contributors responsible for maintaining specific technical or documentation areas.
Responsibilities may include:
- Reviewing contributions
- Managing issues
- Approving changes
- Maintaining documentation
- Monitoring project quality
- Coordinating releases
Repository maintainers should have access appropriate to their responsibilities.
Administrative access should follow least-privilege principles.
Access should be reviewed periodically.
Developers may contribute to:
- Frontend applications
- Backend services
- APIs
- Smart contracts
- Wallet integrations
- Testing
- Infrastructure
- Automation
Developers should follow CeloHT engineering and security policies.
Security contributors may help with:
- Code reviews
- Threat modeling
- Vulnerability research
- Security testing
- Audit preparation
- Incident response
Security researchers should follow responsible-disclosure procedures.
Educators support CeloHT's learning mission.
Responsibilities may include:
- Delivering training
- Developing curriculum
- Supporting learners
- Measuring learning outcomes
- Maintaining educational materials
Community organizers help connect CeloHT programs with local communities.
They may coordinate:
- Events
- Workshops
- Community meetings
- Outreach
- Local partnerships
Agents may provide community-level access to supported CeloHT services.
Agent responsibilities should be defined through appropriate operational procedures.
Agents should never request:
- Seed phrases
- Private keys
- Wallet passwords
Volunteers may contribute time and skills without being formal employees or contractors.
Examples include:
- Documentation
- Translation
- Events
- Community outreach
- Research
- Environmental activities
- Testing
See VOLUNTEERS.md.
Partners are external organizations or individuals collaborating with CeloHT.
Partnerships may involve:
- Technology
- Education
- Research
- Community programs
- Environmental initiatives
- Business development
Partnership status should be documented accurately.
Sponsors provide financial, technical, or other support.
A sponsor does not automatically become:
- A team member
- A governance member
- An owner
- A decision-maker
See SPONSORS.md.
Participation in CeloHT does not automatically establish ownership rights.
Contributor roles should be distinguished from:
- Legal ownership
- Governance authority
- Employment
- Contractual rights
- Sponsorship
Where legal clarification is necessary, qualified professional advice should be obtained.
Decision-making should follow the governance framework appropriate to the decision.
Examples:
May be handled by technical maintainers and contributors.
May require security specialists and appropriate maintainers.
May involve community discussion or voting.
Should follow established treasury and governance controls.
People with significant responsibilities should be accountable for their actions.
Accountability may include:
- Documented decisions
- Review procedures
- Public records where appropriate
- Access logs
- Financial reporting
- Governance oversight
Contributors should disclose material conflicts of interest when relevant.
Examples include:
- Financial interests
- Supplier relationships
- Personal benefits
- Related organizations
- Competing projects
Conflicts should be managed transparently.
CeloHT contributors should interact respectfully.
Unacceptable behavior may include:
- Harassment
- Threats
- Discrimination
- Deliberate deception
- Malicious disruption
- Abuse of project resources
A separate code-of-conduct policy may provide additional procedures.
Contributors should:
- Communicate clearly
- Respect deadlines when agreed
- Document important work
- Protect confidential information
- Report problems honestly
- Follow security requirements
Project access should be granted according to responsibilities.
Examples include:
- GitHub access
- Cloud access
- Database access
- Deployment access
- Administrative privileges
Access should be removed when no longer necessary.
New contributors should receive relevant information about:
- Project mission
- Governance
- Security
- Contribution procedures
- Repository structure
- Communication channels
Technical contributors should understand the applicable development workflow.
When a contributor leaves a role involving privileged access:
- Access should be reviewed.
- Unnecessary permissions should be removed.
- Credentials should be rotated where necessary.
- Responsibilities should be transferred.
- Relevant documentation should be updated.
CeloHT values contributions regardless of role.
Recognition may include:
- Contributor credits
- GitHub contributions
- Community acknowledgments
- Publications
- Event recognition
- Program acknowledgments
Recognition should reflect actual contributions.
Not all CeloHT contributors are necessarily compensated.
Where compensation exists, it should be based on an appropriate agreement.
Compensation should not be represented as guaranteed merely because someone contributes to the project.
Participation in CeloHT documentation or community activities does not by itself establish employment.
Employment, contractor, or consulting relationships should be established separately when applicable.
CeloHT contributors may collaborate across geographic locations.
Remote collaboration should rely on:
- Clear documentation
- Defined responsibilities
- Reliable communication
- Shared project management practices
Official project communications should use appropriate channels.
Important decisions should be documented in durable locations rather than relying exclusively on private conversations.
Every important technical or operational area should have an identifiable maintainer or responsible group where practical.
Examples:
Security → Security contributors
Education → Education group
Technology → Technical maintainers
Reforestation → Environmental group
Governance → Governance participants
Documentation → Documentation maintainers
CeloHT aims to improve transparency around contributors and responsibilities.
Public team information should distinguish between:
- Verified team members
- Contributors
- Volunteers
- Advisors
- Partners
- Sponsors
These categories should not be conflated.
Where contributors choose to be publicly identified, profiles may include:
- Name
- Role
- Area of contribution
- Professional background
- Relevant links
- Contributions
Personal information should only be published with appropriate consent.
Advisors may provide specialized guidance without being operational team members.
Advisory relationships should be described accurately.
CeloHT may engage external specialists for:
- Legal advice
- Security
- Accounting
- Environmental science
- Technology
- Research
External experts should not be presented as permanent team members unless that is accurate.
As CeloHT grows, its organizational structure may evolve.
New roles should be introduced when they solve genuine operational needs.
The project should avoid unnecessary bureaucracy.
Critical responsibilities should not depend permanently on a single individual.
CeloHT should develop:
- Documentation
- Shared knowledge
- Multiple maintainers
- Access continuity
- Role succession
This reduces operational concentration risk.
CeloHT should monitor dependency on individuals for critical systems.
Important knowledge should be documented and shared where appropriate.
The broader CeloHT community can contribute to:
- Ideas
- Governance
- Code
- Education
- Research
- Environmental activities
- Documentation
Participation should be based on contribution and applicable governance rules.
Authority should correspond to responsibility, expertise, and trust.
Holding a title should not automatically grant unrestricted access or decision-making authority.
All contributors with access to CeloHT systems should follow:
SECURITY.mdSECURITY_AUDITS.mdDATA_PRIVACY.md- Access-control policies
- Secrets-management requirements
Where useful, CeloHT may track:
- Active contributors
- Maintainers
- Volunteers
- Educators
- Agents
- Working groups
- Contributions
- Open issues
- Completed initiatives
Metrics should not be artificially inflated.
CeloHT may maintain a public directory with categories such as:
Founder
Core Contributors
Maintainers
Working Groups
Agents
Volunteers
Advisors
Partners
Only verified relationships should be included.
Team documentation should be updated when:
- Roles change
- Contributors join
- Contributors leave
- Responsibilities change
- Governance structures change
Outdated information should be corrected promptly.
This document describes organizational roles.
It does not replace:
GOVERNANCE.mdVOTING_SYSTEM.mdWORKING_GROUPS.mdAUTHORIZATION_MODEL.md
Governance documents determine formal decision-making mechanisms.
CeloHT should communicate team and contributor information honestly.
The project should never fabricate:
- Team members
- Advisors
- Developers
- Partnerships
- Credentials
- Professional affiliations
CeloHT should encourage contributors to develop:
- Technical skills
- Leadership
- Communication
- Security awareness
- Community-management skills
- Domain expertise
A stronger contributor base improves project resilience.
CeloHT is built by people, communities, contributors, and partners working toward a shared mission.
The project should remain open to new contributors while maintaining clear standards for responsibility, security, transparency, and accountability.
The guiding principle is:
Build a strong community, give responsibility to those who earn trust, document what matters, and keep decision-making accountable.
Document Status: Active / Evolving Maintained By: CeloHT Community Founder: Johnny Dubic Primary Principle: Community-driven development and governance
© 2026 CeloHT - Open Source. Global Impact. Licensed under Apache.