Great thread. I've nothing specific to add except some comments from
my experience as a manager.
1. You can expect your contribution (in hours / head space) to be
roughly the same this year as last year unless you had Major Life
Change. Don't expect New Year's miracles.
2. We need to focus on a
My personal technical and community goals for this year :
- give more visibility of what's going on. ANd for me it is just about
to let you know what do each others (and specifically the devs) on the
ml or on the media I am. This isn't marketing. I just want do do it
because I also miss that
(warning, grumpy rant forthcoming...)
On Wed, Mar 6, 2013 at 7:14 PM, Noah Slater nsla...@apache.org wrote:
Thoughts?
It seems to me that a lot of this hinges on releases. Releases
generate publicity and therefore developer interest, thus developer
engagement. Releases make sure that work
On Mar 7, 2013, at 12:04 , Dirkjan Ochtman dirk...@ochtman.nl wrote:
(warning, grumpy rant forthcoming...)
Dirkjan,
understood, loud and clear. And I think we all agree with you :)
In fact, we made a few changes to the way we manage the code and releases
to improve all of that, but I think
Agreed. Thanks for the honest feedback. Massively appreciated.
I have been very frustrated with the 1.3.0 release. It was, and still is,
supposed to be the first of our regular releases. Unfortunately, the
release was mired with a raft of CVEs that came first, and then some thorny
blockers. Not
+1. We are conscious of our release process failings but it's great to
see an uninhibited reminder like this.
We're aiming for regular, frequent releases after this one, as Noah
says. I want to see that process so regular that it becomes boring.
You should come to expect that a fix is out within
There's a lot of work that could be done to a lot of the internals of
CouchDB to clean things up and put us back in a place where we can be
quicker to innovate.
1. Rewrite the HTTP layer to not be a gobbledygook function call
spiderweb for request dispatching. Whether we use something like
Thanks for calling this to action Noah!
My personal list for this year:
-1. Get people excited to contribute to CouchDB.
0. Help remove roadblocks for any sort of contribution, docs, code, tests,
bugs, whatever it takes.
1. A bunch of features that I’d like to rally some activity around, as
My goals right now for CouchDB are focused around how users interact with
the system.
Specifically, I want to see fauxton fully functional with a vibrant plugin
ecosystem.
The other big area is how users extend functionality of CouchDB with
javascript. I think the first big step is switching to
Hello community,
I'd like to start a thread and collect a list of goals for 2013.
We have a few exciting things in the pipeline. BigCouch is about to land.
Benoit's rcouch is also going to land. We're probably going to be moving to
V8. And if Jan has anything to do with it, we'll be getting a
10 matches
Mail list logo
