Skip to content

Contribute

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

  • Reporting a bug
  • Discussing the current state of the code
  • Proposing new features
  • Becoming a maintainer

Working Groups

We have different working groups that you can be a part of

1. KOB Technical Working Group (KOBTWG)

Members of the KOBTWG can

  • focus on completion of the feature list of different projects published under the issues section.
  • suggest new features to enhance the capabilities of each project.

2. KOB Marketing & Communications Working Group (KOBMCWG)

Members of the KOBMCWG can

  • focus on scheduling meetups with other working groups or forums.
  • conduct sessions to talk about KOB.
  • conduct sessions to bring in more contributors.
  • identify associations/dsp that can be part of KOB.

3. All KOB Community Working Group

Members of this working group can

  • conduct sessions to new contributors to equip them with necessary knowledge about KOB.

Community Groups

We have different community groups that you can contribute into.

Community Groups Requirements Activities
Dev
  1. KOBPIU
    • Indy-node
    • Indy-sdk
  2. KOBAW
    • Python
    • Django
    • HTML5
  3. KOBConnect
    • Xamarin
    • Android Development
  4. KOBVON
    • indy-node
    • aries
  • Code refactoring
  • Enhancements
  • Code reading
  • Bug fixes
  • Feature demos
DevOps DevOps Security and Release
  • Code integrations
  • CI/CD
  • Build & Deployment
  • Release management
Solution Design/Domain
  • Business Analysts
  • Domain Experts
  • Identify potential business use cases and document them
  • Analyse the current scenario of a jurisdiction and recommend process refinement using KOB
Community
  • Community leads
  • TSC/PMO
  • Cordinate community activities
  • Maintain connect b/w working groups
  • Schedule community meetups to create awareness about KOB

We Develop with Github

We use github to host code, to track issues and feature requests, as well as accept pull requests.
We Use Github Flow, So All Code Changes Happen Through Pull Requests Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:

  1. Fork the repo and create your branch from master.
  2. If you've added code that should be tested, add tests.
  3. Ensure the test suite passes.
  4. Make sure your code lints.
  5. Issue that pull request!

Report bugs using Github's issues

We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!

Great Bug Reports tend to have:

  • A quick summary and/or background
  • Steps to reproduce
  • Be specific!
  • Give sample code snapshots if you can.
  • What you expected would happen
  • What actually happens
  • Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)

People love thorough bug reports.

Processes expected to follow by each contributors:

Use a Consistent Coding Style

You must follow the coding standard described in the KochiOrgBook review Checklist.