On Thu, May 29, 2014 at 7:35 AM, Alexander Shorin <[email protected]> wrote:
> On Thu, May 29, 2014 at 8:45 AM, Benoit Chesneau <[email protected]> > wrote: > > > > 1. create a separate website: couchapps.couchdb.org or > > couchdb.apache.org/couchapps (maybe better). Once it would be possible > > redirect couchapp.org to it. > > couchdb.org serve only propose to redirect requests to > couchdb.apache.org, so the final variant looks like: > couchapp.couchdb.apache.org. > Technically, separate domain looks more reasonable to couchapps since > they contains quite much bits of third party projects which are not > related to CouchDB directly, but I'm +1 for any variant. > By separate domain you mean couchapps.couchdb.apache.org (shorters a apps.couhdb.apache.org) or anything else. > > > 2. move the old content to a static website or wiki > > +1 for static website (it's simpler and faster), also it's good idea > to move all the content to sphinx, put it to git and serve via RTD (in > this case new domain sounds good) as we done for CouchDB docs. > sphinx or any other tools are fine for me. Would be good to have to old content. Though we can rebuild some content from scratch. Old content was really old... > > > 3. create a couchapp mailing-list that come with the website outside of > > googlegroups. > > +1 for [email protected] > > > small detail, but it should be [email protected] so we handle all kind of possible couch embedded applications. Both are ok for me though. > -- > ,,,^..^,,, >
