There are active Special Interest Groups (SIGs) around individual contributions and what they could be made and how. Please understand that this process might change as time goes on.
Tazama welcomes technology professionals willing to work as a community to develop open-source solutions for financial crime scenarios. Whether you have a fully packed project, ideas, or code, here is how one can be involved:
- Share Use Cases & Ideas in SIGS. If you want to share use cases or propose an avenue for the industry to solve crucial issues, our SIG provides a platform for like-minded professionals to look at a common pain point and other opportunities for open collaboration. See our SIGs and engage with others to help spark significant solutions.
- Contributing to an Existing Tazama Project is one of the simplest ways to join. Contribute to a live Tazama project. Contributions can include:
- Code development
- Documentation updates
- Test cases and requirements
- Reporting issues and submitting pull requests
We would like to encourage all contributors to:
Join in the project discussions on Slack or in GitHub. Look at a roadmap for the project and focus areas (most often included in its README).
Please note that contributions with Git commits & pull requests need to follow Tazama’ Contribution Compliance Requirements.
- Propose a New Project in Tazama If you have an existing product, project, or tool compliant with Tazama’ community interests, you can propose it to be developed as a new Tazama project.
How To Contribute
Step 1: Convergence Evaluation
Evaluate whether your submission is open-source appropriate. Are the objectives and goals of your development aligned with those of Tazama?
Step 2: Submission of a Contribution Proposal
Write a proposal draft and enter it as a GitHub issue. Your proposal needs to discuss:
- Problem/solutions: What does it attempt to answer? How does the proposed solution resolve that problem?
- Future roadmap: Purpose, phases of development, and success criteria.
- Current status History, level of maturity, key milestones that have been achieved.
- Existing materials: Repository links, documentation, or any other relevant work available already.
- Development team Key contributors, their role, and where they come from. Contributor commitment (e.g., availability of developer time, marketing, etc.).
Step 3: Open Up to Community Interest
You can propose your project to the Tazama Community by introducing your proposition to community@tazama.org while also providing a link to your GitHub submissions.
Note: Anyone could contribute to any project; however, only Tazama Members are permitted to propose their projects. If it happens that you are not a member, this step will help you request sponsorship.
Step 4: Compliance Review & IP Transition
Tazama will conduct due diligence by reviewing the proposal against all compliance requirements, covering anything from IP and trademark compliance towards a determination of selecting key project names that denote uniqueness or transferring trademark rights as necessary. All cascade licenses and types, must align with the Tazama Apache-compatible license policy, the legal requirements-notice of attribution and contributor agreement.
Step 5: Approval Process
Is this a good fit for Tazama? Tazama community interest:
- Special Interest Groups and Open Standards → Approved by the Governing Board;
- All other projects → reviewed by the Technical Oversight Committee (TOC).
Step 6: Transition and Onboarding
Upon approval, Tazama will help transition the project to its new home by establishing:
- A GitHub project repository
- A project website and wiki
- Maintainer permissions
- The checks of code validation, setting of build process configurations, and publishing of documentation will be completed.
Step 7: Community Announcement
When the onboarding is done, it is time to announce your project! Send an email to announce@tazama.org.