On 14. November 2013 at 17:33:35, Brian Mitchell (br...@strmpnk.co) wrote:
> users can easily activate to test the system.
> >
> > I agree, src/couch_plugins/README.md has a quasi roadmap
> that I want to work
> > towards. The only edit for now would be that I’d like a registry
> that can be
>
Github user BigBlueHat closed the pull request at:
https://github.com/apache/couchdb/pull/100
GitHub user BigBlueHat opened a pull request:
https://github.com/apache/couchdb/pull/105
Fiddly UI tweaks
Just a few small tweaks to CSS and layout bits.
Hope they're not too opinionated. :smiley:
You can merge this pull request into a Git repository by running:
$ git
Cool, thanks!
Please also make changes to whichever email template you think should
be updated to point to this resource.
I recommend this one:
https://git-wip-us.apache.org/repos/asf?p=couchdb-admin.git;a=blob_plain;f=email/done_committer.txt;hb=HEAD
On 14 November 2013 23:40, Andy Wenk wrote
page added ;-)
https://wiki.apache.org/couchdb/Committer_First_Steps
On 14 November 2013 17:10, Noah Slater wrote:
> The wiki is for documenting our community and our processes, i.e. the
> project.
>
> The docs are for documenting the CouchDB database, i.e. the product.
>
>
>
> On 14 November
Thanks Noah,
my conclusion is, that the page should work with IE but we don't have to
put the biggest amount of power in optimising for IE ...
On 14 November 2013 18:56, Noah Slater wrote:
> From Google Analytics:
>
> Chrome 59.77%
> Firefox 22.93%
> Safari 9.62%
> Internet Explorer 4.26%
>
On Thursday 14 November 2013 at 20:15, Brian Mitchell wrote:
> On Thu, Nov 14, 2013 at 1:52 PM, till (mailto:klimp...@gmail.com)> wrote:
> > On Thursday 14 November 2013 at 18:28, Simon Metson wrote:
> > >
> > > I’m interested in this too. Can we pick up stuff from npm?
> > > Cheers
> > > Sim
On Thu, Nov 14, 2013 at 1:52 PM, till wrote:
>
>
> On Thursday 14 November 2013 at 18:28, Simon Metson wrote:
>
>> Hey,
>>
>> > > I agree, src/couch_plugins/README.md (http://README.md) has a quasi
>> > > roadmap that I want to work
>> > > towards. The only edit for now would be that I’d like a r
On Thu, Nov 14, 2013 at 10:52 PM, till wrote:
> - enforce semantic versions
> - don’t allow people to re-upload releases
> - make it easy to mirror it
> - some kind of signature for plugins/verification
All of this could be done with CouchDB, validatation functions and
replication. Why not?
On Thursday 14 November 2013 at 18:28, Simon Metson wrote:
> Hey,
>
> > > I agree, src/couch_plugins/README.md (http://README.md) has a quasi
> > > roadmap that I want to work
> > > towards. The only edit for now would be that I’d like a registry that can
> > > be
> > > update independentl
>From Google Analytics:
Chrome 59.77%
Firefox 22.93%
Safari 9.62%
Internet Explorer 4.26%
Opera 1.23%
Android Browser 0.65%
Mozilla 0.47%
SeaMonkey 0.24%
Opera Mini 0.15%
Safari (in-app) 0.15%
On 13 November 2013 23:06, Andy Wenk wrote:
> On 13 November 2013 22:58, Alexander Shorin wrote:
>
>>
Hey,
> > I agree, src/couch_plugins/README.md (http://README.md) has a quasi roadmap
> > that I want to work
> > towards. The only edit for now would be that I’d like a registry that can be
> > update independently from CouchDB releases. Would you be interested in
> > helping
> > out with that
Dear Sir or Madame,
your database
CouchDB
is listed on www.nosql-database.org.
I am working on my master thesis
„Market research about storing and analysing physical measurement
data
using NoSQL databases.“
In the course of my research
> >> # 4. plans for 1.6 release #
> >> 19:15:31 [Kxepal]: btw. any plans for 1.6 release?
> >> 19:15:46 [awenkhh]: when is 1.6 release scheduled for?
> >> 19:15:46 [Kxepal]: one feature we have: stable Fauxton and replacement
> >> Futon withit. any other goals?
> >> 19:16:37 [Kxepal]: awenkhh: theo
The wiki is for documenting our community and our processes, i.e. the project.
The docs are for documenting the CouchDB database, i.e. the product.
On 14 November 2013 16:50, Andy Wenk wrote:
> happy - that the document helps :-)
>
> For me, both places are good. But while thinking about this
happy - that the document helps :-)
For me, both places are good. But while thinking about this a question
comes to my mind: what is the difference between the wiki and docs? In the
early days, the wiki was both. Now, there are the docs AND there is the
wiki. Which information belong to which plac
This is great, Andy!
I'm going to disagree with dch on this one, and suggest that this is
better suited on the wiki.
How about this:
http://wiki.apache.org/couchdb/Committer_First_Steps
Note that my notes on how to elect people are here:
http://wiki.apache.org/couchdb/Committer_Election_Proces
On 14. November 2013 at 12:36:15, Dirkjan Ochtman (dirk...@ochtman.nl) wrote:
>
> On Thu, Nov 14, 2013 at 12:22 PM, Andy Wenk wrote:
> > I have written down all the things I did after becoming a committer.
> > Dirkjan asked me to share this. So here it is:
> >
> > https://docs.google.com/docu
On Thu, Nov 14, 2013 at 12:22 PM, Andy Wenk wrote:
> I have written down all the things I did after becoming a committer.
> Dirkjan asked me to share this. So here it is:
>
> https://docs.google.com/document/d/1ScQzlUQ-HN9x5WydDLdlnd21iM6iF5i68mSm0u35PbI/edit#
>
> Pleas have a look at it. Any idea
Hi all,
I have written down all the things I did after becoming a committer.
Dirkjan asked me to share this. So here it is:
https://docs.google.com/document/d/1ScQzlUQ-HN9x5WydDLdlnd21iM6iF5i68mSm0u35PbI/edit#
Pleas have a look at it. Any idea for improvements are very welcome. And
also any idea
20 matches
Mail list logo
