Maintaining an open source project
Being working on GLib from few days, few things -
- Attach difficulty level label on your tickets
- Close tickets or add a label which you don't plan shipping
- Attach priorities label on your tickets (attach release numbers?)
- Review your very old tickets
- Add a code of conduct
- Publish how you review, minimum reviews required
Useful for GLib?
As GLib is an open source project this
- Sorts out your GLib priorities
- Better tracking
- Better workflow
- Better work estimation
- A heavily commented ticket should not be asked more information about tasks and thought about on an MR.
Useful for committer?
- No repetitions, one can read and follow
- Less and no task thoughts iteration on MRs. MRs should have discussion about implementation and not tasks
- Committers would be aware of your priorities before picking up a ticket
- No comment claiming
Edited by Tapasweni Pathak