Good news that there are no bad news (: Since noone objects, will proceed with following plan. -- ,,,^..^,,,
On Mon, Oct 26, 2015 at 4:38 PM, Alexander Shorin <[email protected]> wrote: > Hi everyone. > > Recently we had quite hot discussions around CouchApps feature: what > the future it has, what the problems it has, what the plans people > have on it and so on, but basically we have a lot of talks, but only. > However, these discussions showed that we have quite enough people in > our community who loves that feature, who wishes it to become better > and who wanted to make it better. > > While CouchDB Team has no enough resources to completely support this > feature and improve it, I propose to create CouchApp Work Group (CAWG) > which will be organized by active CouchApp activists and people who > would like to work on it and provide support of any kind that can. > > > === What CAWG will do? > > - Restore good name of CouchApp and couchapp.org website; > - Search for solutions of technical and ideological issues; > - Provide informational and technical support; > - Involve more people into CouchDB ecosystem; > - Provide feedback to CouchDB dev team for the existed features that > CouchApps counts vital, proposals and, I wish, pull requests for new > features and improvements; > > As was previously wisely noticed, CouchApp is a metafeature that based > on top of CouchDB, but it tightly coupled with CouchDB and we cannot > ignore it existence nor try to bury history of our project. > > > === How CAWG will interact with core devs? > > There were asked some concerns that CouchDB devs cannot maintains > CouchApp related requests now, work on new features and so on, and so > on, so all the new feature requests discussion almost always ended > with the same resolution. > > Accounting past experience, I propose the following format: CAWG works > on it own without disturbing core developers by ideas, requests and > what else. > > All feature requests are forms as good proposals on CWiki or ML with > rationale part. If CWAG could generate pull requests with features > implementations and bug fixes - that is the best case of our > cooperation. > > > === Who the tools CAWG will use? > > - New ML [email protected] for discussion, support, etc. > - CWiki for designing proposals, ideas, documenting workflow etc. > - JIRA with CouchApp component to track issues and work on them > - couchapp.org website as main informational base. I guess, we'll be > need in git repository to manage it content on the first steps, unless > there are other alternatives. > > > === Who are all these peoples? > > Everyone in CouchDB community who want to work on CouchApp feature. > Keyword - work, because there are a lot of people here with a lot of > ideas, but without implementing them nothing will get changed. > > So far I'd propose to promote these folks: > - Ermouth > - Giovanni Lenzi > - Harald Kisch > - Josh E. > - Benjamin Young > > Anyone else? > > (Note, I know that some devs had not the best discussions with some of > these people, but I would like if we can abstract from emotions of the > past here, shake our hands and try to work together in the new format) > > My personal role here is to be a bridge: connect CAWG with CouchDB and > provide help with Erlang bits and other project routines. > > > === How this all means to CouchDB Future? > > Our last mottos and slogans were focused on that we're, basically, > database for web that replicates. For now CouchApp feature is not in > the best state to put it on the front of CouchDB marketing. > > If we can get CouchApps back to live and this will really work and > involve more people into CouchDB project and ecosystem - we're all in > win-win situation. > > > > Thoughts? > > > -- > ,,,^..^,,,
