This is going to be particularly useful for automatically generating a reasonably useful changelog between releases. For one, I’m hoping it’ll help the release working group put out release notes sooner.
As for adopting it ourselves, maybe we could start with thinking about writing good commit messages first, rather than going from no rules to an extensive framework? One can write good messages without labels, !’, UPPERCASE TAGS:, or shudders emoji.
on the edX OEP side, I’m optimistic because I’m hoping this will result in less cases where large changes have been made and there is a one line commit message and a PR with no description. Although, there currently isn’t anything in the spec that asks to explain why a change was made, so we may just end up with more verbose commit messages that don’t tell us anything.