I'm not sure how that would look like in FlySpray, but I agree that an issue tracker would be best place for handling this kind of stuff. Today the public changlog are made manually mostly from memory. http://www.dokuwiki.org/changes If we are going to stick with FlySpray I suggest we write our own "How to" because the docs sucks. /Håkan