If I recall, we talked about putting it on the wiki, but there didn’t seem to be a way to lock it so only board/officers could update it.
There are several ways to do this, I have personally done this two different ways using two different methods using mediawiki which appears to be what the hive is using as their wiki software. I'd be willing to assist with this, just let me know.
I would just like to insert one thing into this conversation in regards to readability and accessibility: The bylaws ARE available on the wiki, they are accurate and auto-updated whenever the github master branch is changed. The github serves primarily as a stable location to keep the original source for the bylaws. And as someone who has spent several years maintaining mediawiki installations for multiple organizations, well... stable is not the first adjective that comes to mind. Bylaws are meant to be stable; Wikis are meant to be fluid. I'm not saying that github is the only solution, but I definitely don't think that the wiki is the way to go.
- Ian B.
Well look what happens when I actually use the search feature. lol
https://wiki.hive13.org/view/Bylaws
Er, to be honest, I thought that they were linked on the front page. Apparently I dropped the ball on that. I've added a "bylaws" list to the front page and told my wikibot to keep that updated as well. 
- Ian B.
That is my take on Wikis as well, having also dealt with some. Wikis seem to lean towards storing their documents and version history in whatever database system, database schema, and markup format happened to be “cool” at the time. Using standard version control underneath (as GitHub does) decouples that from the documentation format and the presentation of it.
Perhaps this issue has become less common with the advent of things like Markdown and with Wikis hosted on top of version control, like the Wiki functionality in GitHub, GitLab, and Fossil.