Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: 80.244.253.218 is neither permitted
 nor denied by domain of jan@php.net)
References: <E10DBD0A-7506-4011-90B5-1EE1FD2D2127@apache.org>
 <CAPaJBx4fkigLoXpgBBV4=vZHhZui24dZoF5NV-KQWBDO4w=RCA@mail.gmail.com>
 <CAGt9U8hYeYDQG1pQ04G1B_Ty33+R30Sc=JPSjMZqe0VE2d8KUQ@mail.gmail.com>
 <CAPaJBx5McxR1c0y_tjqoSx63Qnwh9ouu5Fkcs4u9ma_Ab1-umw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: 
 <CAPaJBx5McxR1c0y_tjqoSx63Qnwh9ouu5Fkcs4u9ma_Ab1-umw@mail.gmail.com>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7426322-BBF1-4E32-9B44-C0EA6C92672A@php.net>
Cc: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
From: Jan Lehnardt <jan@php.net>
Subject: Re: Focus
Date: Tue, 6 Nov 2012 20:19:21 +0100
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>

On 06.11.2012, at 18:37, Noah Slater <nslater@apache.org> wrote:

> Octavian, I think Jan was just saying that Futon.Next should be part of ou=
r
> current focus.
>=20
> The 1.3 release is orthogonal. We cut it when we cut it. :)

Correct, thanks for the clarification! :)

Jan
--


>=20
> On 6 November 2012 17:06, Octavian Damiean <mainerror@gmail.com> wrote:
>=20
>> Quick question. Apparently I misunderstood something in the first meeting=

>> because I was thinking that Futon.Next is such a if it's ready for 1.3 we=

>> ship it if not then in 1.4.
>>=20
>> I'm asking because Futon.Current can do everything necessary at the momen=
t,
>> which makes Futon.Next a non-stopper in my opinion. I'm just asking, not
>> trying to discuss or propose anything.
>>=20
>> On Tue, Nov 6, 2012 at 5:03 PM, Noah Slater <nslater@apache.org> wrote:
>>=20
>>> I think this is a great initiative Jan.
>>>=20
>>> I am sure there are a few people right now who are thinking "Hey, but I
>> am
>>> working on X, and Jan didn't mention X, so is X important? Or is Jan
>>> telling me I shouldn't be working on X?" Well, I understand that. As it
>>> happens, I am working on the docs, and Jan didn't mention them.
>>>=20
>>> But I don't think the idea is that anything not on the list is
>> unimportant,
>>> or that if you're working on something else, then you should stop. Just
>>> that we need to have a regularly updated list of our current PROJECT
>> LEVEL
>>> focus.
>>>=20
>>> And so, with that caveat out of the way...
>>>=20
>>> Jan, as this is your initiative, can I ask you to start a page on the
>> wiki?
>>> We should document this.
>>>=20
>>> I think the wiki page should probably have three things on it. A list of=

>>> our current focus areas. An archived list of previous focus areas. And a=

>>> list of areas to focus on in the future.
>>>=20
>>> I think we should also review this monthly. Each month, review the
>> current
>>> focus areas, see what has been done and what has not. Archive the list.
>>> Create a new one for the current month. And decide on whether we want to=

>>> add any other items. This should be a dev-level decision making process,=

>>> perhaps in the first IRC meeting of the month.
>>>=20
>>> A monthly email to both user and dev, along with general project status,=

>>> might be a good thing to come out of this too.
>>>=20
>>> Thoughts?
>>>=20
>>>=20
>>> On 6 November 2012 15:47, Jan Lehnardt <jan@apache.org> wrote:
>>>=20
>>>> Hey all,
>>>>=20
>>>> I=E2=80=99m trying something new here. Please send any feedback you mig=
ht have.
>>>>=20
>>>> DISCLAIMER: I won=E2=80=99t keep anyone working on or discussing anythi=
ng. All
>> I
>>>> want is find a way to make us all more productive.
>>>>=20
>>>> * * *
>>>>=20
>>>>=20
>>>> With that out of the way:
>>>>=20
>>>>=20
>>>> Let=E2=80=99s Focus!
>>>>=20
>>>>=20
>>>> My hypothesis is this:
>>>>=20
>>>>  This group, dev@, has a limited amount of time and attention to move
>>>> CouchDB forward. We have so many important things to do that it is very=

>>>> hard for us to say =E2=80=9Cno=E2=80=9D to any one thing that is brough=
t up.
>>> Historically,
>>>> whenever there is a surge of activity, we (myself definitely included)
>>> tend
>>>> to bring up more issues than we can work on at a time and as a result
>> we
>>>> end up doing less than we could.
>>>>=20
>>>>=20
>>>> My proposal to solve this:
>>>>=20
>>>> Say =E2=80=9Cno=E2=80=9D.
>>>>=20
>>>> More specifically, we need to learn to say =E2=80=9Cno=E2=80=9D to thin=
gs that, while
>>> they
>>>> are definitely important, are not important enough =E2=80=9Cright now=E2=
=80=9D and
>> should
>>>> be deferred to a later time.
>>>>=20
>>>> For example, currently I think our most important topics are:
>>>>=20
>>>> - Get CORS and docs into shape that we can merge them to master/1.3.x
>>>> - Ship 1.3.0
>>>> - Help the Futon.Next folks out as much as we can to build & deliver
>>>> Futon.Next.
>>>>=20
>>>> At the same time, there are many more discussions going on that are
>>>> distracting us from the points above done.
>>>> (This includes my Plugins Proposal, I am clearly guilty of this.)
>>>>=20
>>>> Note that the list above is a strong =E2=80=9Cin my opinion=E2=80=9D, y=
our shortlist is
>>>> likely to differ and that=E2=80=99s great. We as a group need to figure=
 out
>>>> together what the things are that we care about *and* that we can care
>>>> about at any one time.
>>>>=20
>>>> This includes things we discuss on dev@, in the weekly meetings,
>> patches
>>>> we request reviews & comments on.
>>>>=20
>>>> I strongly believe that when we can agree on a short list of things we
>>>> care about, and get them done, and *then* move on to the next few
>> things,
>>>> we=E2=80=99ll get more accomplished than we do right now.
>>>>=20
>>>> * * *
>>>>=20
>>>> It would be illusionary to imagine a fully sequential workflow, so I
>>> won=E2=80=99t
>>>> pretend we should try to achieve that, we=E2=80=99ll always have things=
 going
>> on
>>> at
>>>> the same time, some by different group members, some by the same
>> people.
>>> I
>>>> also don=E2=80=99t suggest to add a layer of classical project manageme=
nt. Some
>>>> discussions are broader (BigCouch merge, source reorg) and need more
>>> time,
>>>> others should be resolved quickly. And to reiterate the disclaimer, I
>>> won=E2=80=99t
>>>> keep anyone from working on or discussing anything at any time.
>>>>=20
>>>> All I suggest is that we, as a group, are a little more mindful about
>> the
>>>> things we can handle at any one point. This will change depending on
>> how
>>>> much time each of us can spend in a given week or month. I hope over
>> time
>>>> the list of things we can do at a time grows, as we add more members to=

>>> the
>>>> dev team (hello Futon.Next folks! :)
>>>>=20
>>>> * * *
>>>>=20
>>>> In practical terms, I=E2=80=99ll be asking the questions =E2=80=9Cis th=
is relevant
>> right
>>>> now?=E2=80=9D and =E2=80=9Cshould this be on our short list of things t=
o care about?=E2=80=9D a
>>> lot
>>>> more often, and I hope, given you agree with the broad strokes above,
>> can
>>>> do the same.
>>>>=20
>>>> Thanks for your time and attention!
>>>>=20
>>>> Cheers
>>>> Jan
>>>> --
>>>=20
>>>=20
>>> --
>>> NS
>=20
>=20
>=20
> --=20
> NS