Feature Request Process

Follow this process to submit a new feature and begin development within the BodhiTree platform.

📌 Steps

The feature request form is to be filled in only by those who are being inducted into the BodhiTree organization. For reference, the form is at https://forms.gle/fMgi3BYyhAqdmgq46. If you are already inducted and only need repository access, see Access Request instead.

Follow the process for feature design, system design, and implementation

  1. Create .md file
    Locate docs/features/feature_sample_file.md in the platform repository (template on GitHub). Make a copy of that template and create a new .md file with the following nomenclature: Feature_YYYY_MM_DD_Feature-Name.md. Add all the sections based on the feature that you want to implement. If there are images, put them in the images folder and link them from the main .md file.

  2. Raise a PR to the dev branch Do a PR to the dev branch and track your PR approval by email

  3. Create an Issue on GitHub
    👉 Create a new issue to track your feature. While creating the issue, copy the feature title and feature description from the feature request .md file that you created in step 1 and put them in the description of the issue, along with a link to the .md file. Add the label Feature to the issue.

  4. Assign the Issue to Yourself
    After creating the issue, assign it to your GitHub account to mark ownership.

  5. Notify the Approval Team
    Message the Approval Team on Microsoft Teams once done.

  6. Follow Up
    If you don’t receive a response within a few days, follow up with the team.

  7. Wait for Approval
    Approval will be given by the designated team members (see below).

  8. Begin designing the system/sub-system
    Once you have the approval, start setting up the development environment as per the documentation. See Platform Setup & Installation. Go through the code and proceed for design. See Design Process.

✅ Approval Team Members

  • Prof. Kameswari Chebrolu

  • Prof. Varsha Apte

  • Nagesh Karmali

  • Tejas Ingale

📎 Note: If there is an UI change applicable for any feature, UI design is mandatory. Attach it in the form. You may also include an optional implementation plan.