Hi Tiger,

please make sure to reply to the developer list, instead of just me personally.

CouchDB’s admin UI is already written in React, so there is no new decision to 
be made here.

In addition, CouchDB was one the first open source databases that came with a 
built-in UI that was generally usable, and it has helped project adoption a 
lot, so we’re disagreeing on its importance.


> On 10. Aug 2017, at 12:42, support-tiger <supp...@tigernassau.com> wrote:
> 1) re working with React + licensing -> Don't!  There are totally FOSS React 
> type alternatives such as Preact - Just say no to Facebook and to licenses or 
> anything that is not 100% FOSS. It's easy to say everyone else is using it - 
> but that doesn't mean there are not potential problems.  Just look at the 
> lawsuit over Java.
> 2)  GUI for DBA work is non intelligent (put it nicely for the list) - yeah 
> we understand there are lots of "windows type" folks that love the flashy 
> point & click but the lack of any migration and settings audit trail for an 
> enterprise server system is a disaster waiting to happen.   Whether it's a 1 
> person developer or global enterprise, using non-trackable changes to the 
> database is just terrible practice so why waste precious CouchDB resources on 
> it.   Even the popular Ruby Rails framework has a specific database migration 
> system (which shows it is better to have settings or any schema set in code 
> scripts and just maybe one of the reasons Rails is so popular).   CouchDB has 
> a great url syntax for admin settings - if that is too difficult for people 
> to use they should not be in charge of data, period.
> A better use of resources would be on better install and initial setup 
> scripts.
> On 08/10/2017 06:34 AM, Jan Lehnardt wrote:
>> ## Description:
>>  - Seamless multi-master sync, that scales from Big Data to Mobile,
>>    with an Intuitive HTTP/JSON API and designed for Reliability.
>> ## Issues:
>>  - there are no issues requiring board attention at this time
>> ## Activity:
>>  - Released version 2.1.0, details on the blog:
>>    https://blog.couchdb.org/2017/08/07/2-1/ (tl;dr: a major new feature
>>    for users at scale, tons of post 2.0.0 bugfixes, and:
>>  - Massively overhauled      test suites, jenkins setup, worked with Infra 
>> around
>>    lots      of little and gnarly issues; all this resulting in being able to
>>    make      more reliable release in quicker succession from now on. We 
>> haven’t
>>    settled on anything yet, but      are discussing a release per quarter 
>> plus
>>    security ad bugfix releases as needed. Special shout      out for PMC 
>> member
>>    Joan      “wohali” Touzet, for primarily driving this effort to success.
>>  - Currently awaiting Facebook’s decision on licensing their React & adjunct
>>    JavaScript frameworks, which      are in use in our admin UI Fauxton:
>>    https://github.com/facebook/react/issues/10191 — We have discussed
>>    alternatives, but made no contingency plans just yet.
>> ## Health report:
>>  - The project is doing fine overall. We’ll be doing a dedicated drive for
>>    JavaScript contributors for our admin UI after the licensing discussion
>>    is over, and we have more certainty about future direction. Current
>>    contributors are moving towards other areas of the projects, and it’s
>>    a great place for people to get into the project without having to
>>    learn Erlang.
>> ## PMC changes:
>>  - Currently 14 PMC members.
>>  - No new PMC members added in the last 3 months
>>  - Last PMC addition was Garren Smith on Mon Oct 19 2015
>> ## Committer base changes:
>>  - Currently 58 committers.
>>  - Glynn Bird was added as a committer on Mon May 29 2017
>> ## Releases:
>>  - 2.1.0 was released on Mon Aug 07 2017
> -- 
> Support Dept
> Tiger Nassau, Inc.
> www.tigernassau.com
> 406-624-9310

Professional Support for Apache CouchDB:

Reply via email to