Hi everyone,
There appears to be general consensus on the RFC process, with no
objections to the proposal itself.
I'd like to propose the following changes to our bylaws:
https://github.com/apache/couchdb-www/commit/8ae3a5a230b1717d7affe23625eeb288635aa542
Quick summary:
* Added the RFC
That looks really slick. I like it!
Adam
> On Feb 12, 2019, at 12:08 PM, Nick Vatamaniuc wrote:
>
> Shard Splitting API Proposal
>
> I'd like thank everyone who contributed to the API discussion. As a result
> we have a much better and consistent API that what we started with.
>
> Before
Shard Splitting API Proposal
I'd like thank everyone who contributed to the API discussion. As a result
we have a much better and consistent API that what we started with.
Before continuing I wanted to summarize to see what we ended up with. The
main changes since the initial proposal were
Hi,
I like the idea of RFC's and agree with Joan that they should help with the
actual (and perceived) gaps in cooperation from large corporate vendors.
I would like to see a mandatory "Security Considerations" section added to the
template. Not every RFC will have anything to say on the
I’ve applied ~all requested updates, last call for 2.3.1 *rings bell*
Best
Jan
—
> On 7. Feb 2019, at 16:41, Jan Lehnardt wrote:
>
> Hi everyone,
>
> we’ve had some great fixes come in since we release 2.3.0 in early December.
>
> Some of those fixes should make it into our user’s hands
