https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30998
--- Comment #15 from Arthur Suzuki <arthur.suz...@biblibre.com> --- Just my 2 cents here. Isn't the devs who provides code at the best place to know exactly what the code is doing or how it changes its behavior? and therefore documenting it? Just like it is now mandatory to provides unit tests and test plans in the commit message, we could make a documentation mandatory for an enhancement or big change to reach Koha Community code. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
