Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-lager/pull/1#issuecomment-113902936
Naming is indeed one of the hardest CS problems (:
I'd like to go with "standalone": it clearly (at least for me) defines that
this project is shaped to work alone without all the other CouchDB stuff (at
least without most of it parts).
With "public" name I'm not sure: it's good, but assumes that there is
something "private". In fact, there are no such bits, everything is already
_public_, just master is heavily coupled on root couchdb repository.
Any thoughts? Objections? @rnewson @chewbranca @robertkowalski @janl ? If
there are not, I'd like to go with standalone branch (not the best name, but
cannot figure anything clear and better).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
