Thankfully, LibBars-1.0 is still working with patch 4.01, but I have a couple of questions for Antiarc if he's still around, or the community in general if not.
Is Antiarc still around? Is he updating his addons, specifically this one?
The Repository can be accessed by anyone. While a simple .toc bump would be nice, it isn't necessary. However, I've scanned threads and saw people talking about APIs, and that there is a complete lack of documentation. What about committing an update with a .docmeta?
What happens when a different author adds a .docmeta? Will it still show up on the appropriate page, or do you have to be the author of the lib?
No, I do NOT want to take over the project, as I do not know enough about the code to maintain it. I'm just asking about a couple of simple things.
If it's unclear whether an addon has an active maintainer, it's probably best to not make any commits unless you're willing to take over maintenance and support for the addon. While your commit may be helpful in the short term, in the long term all it accomplishes is making users think the addon is still being updated and supported, when it isn't.
That said, LibBars-1.0 is used by BigWigs, so you should probably get in touch with one of its authors.
BigWigs uses LibCandyBar-3.0, actually. There currently are only 11 addons using LibBars-1.0 that have been updated in 2010.
I wonder if LibBars-1.0 is done? Would be a shame, all things being equal, since it provides things LibCandyBar-3.0 does not (and vice versa). The sad part is, as I said, LibBars-1.0 still works fine, and is only hampered by a lack of documentation.
My mistake. The first part of what I wrote still applies, though. If the library isn't being maintained/supported by anyone, it's probably best not to encourage new addons to use it by writing documentation that makes it easier to use. If you're already using it, you either (a) already know how to use it, or (b) know enough about it that you can look at its code to figure out how to use it in new ways.
.docmeta just tells the packager that some file (or files) in the repository contains documentation, what format that documentation is in (markdown, luadoc, etc.), and what to do with it (copy to Main pag, etc.).
For example, I maintain Grid's description page using the Markdown-formatted README.txt file in the repository. To edit the description, I just edit the README file and commit it. When the packager makes a new zip, it also updates the Main page.