> On 12 May 2015, at 16:57, Alexander Shorin <[email protected]> wrote: > > On Tue, May 12, 2015 at 5:51 PM, Jan Lehnardt <[email protected]> wrote: >>> On 12 May 2015, at 14:29, Jan Lehnardt <[email protected]> wrote: >>> >>>> >>>> On 12 May 2015, at 14:22, ermouth <[email protected]> wrote: >>>> >>>>> I left my suggestions here: >>>>> Here are my suggestions: >>>> >>>> Collegues, if you have someone who is a) native English speaker, b) has >>>> skills in writing good copy – could you please ask him/her to review the >>>> source? >>> >>> Good call, let’s see: https://twitter.com/janl/status/598102651222523904 :) >> >> Here’s one: https://gist.github.com/nolanlawson/09cab7798aed9ec9044c > > All is perfect! But CouchDB Core text need to be a bit improved: > >> Help shape the future of CouchDB! There's still plenty of exciting work to >> be done on the core database. We use modern tools like JIRA and Github to >> track issues and pull requests. > > Future of CouchDB is shaped not only by core,
The text doesn’t claim that the core *only* shapes the future and the fact that the other areas of contributions are right there next to it should make that clear. > but Fauxton, Docs, > Marketings and all the other cards as well. Statement about "we use > ... JIRA and Github to track issues and pull requests" may be read as > "We use two issues trackers and that why we have a lot of work to do”. Heh, nice catch, I hadn’t read it that way, maybe we can rephrase the whole thing? :) I think the intention is 1. “we have a lot to do” 2. “we use standard tools that you are familiar with to work” Best Jan -- > > Any thoughts? > > -- > ,,,^..^,,, -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/
