Home

How to propose change to decidim (Octree Process)

We describe here the Octree process to propose change in the Decidim Product. It is based on our actual Holacracy Governance, so for outsider of Octree, this document might be obscure.

Bug

Triage

We handle bug solving in group, to organize release sprints of fixes. To report a bug in Decidim, go through the email [email protected]. This bug will then be registered as a problem and dispatched to one of the following:

• Voca PO if its related to voca product
• Decidim Module Developper, if its related to a module
• Decidim Contributor, it its related to the decidim itself.

-> We are in the space of Decidim Contributor, and we will describe only the flow for this last item.

Report the bug

1. Create an issue
2. Test on https://try.decidim.org
3. Test on a 0.27 voca instance
4. Give back stacktrace and errbit information if you have any.
5. Always joins a screenshot.

Plan a bug

1. Link the plan to a milestone
2. Add to the issue the label todo
3. Describe in the issue the Tasks to be done, with checkboxes.

Working on a bug

1. Replace the label todo in doing
2. Create a branches named fix/<name of the issue>
3. Assign a Reviewer.

Place the bug in review

1. Replace the label doing by review
2. Write in the issue a comment mentionning the reviewer.
3. Write in again in the slack, in the #voca channel, mentionning the reviewer.

Place the bug in testing

1. Put a live instance with the bug fixed. Named <name of the issue>.dev.voca.city
2. Ask someone to test the instance (someone accountable for the customers relations).
3. Wait the tester validate the resolution.

Do the PR

1. Decidim Contributor makes the PR describing:
   1. What has been done
   2. The link to the octree issue
   3. The temporary instance with the fix