Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dave2wave@comcast.net
 designates 76.96.27.228 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Support page of website - work planned
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: <1324318342.15371.YahooMailNeo@web160904.mail.bf1.yahoo.com>
Date: Mon, 19 Dec 2011 13:19:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB8AA16D-33FE-4CAA-A832-B43CE98D46B2@comcast.net>
References: 
 <CALaBZo64bu-VB4eb8i8AEL9LshUaQOiHD821L=acXZ314kv_+g@mail.gmail.com>
 <087301ccbde9$9db3aed0$d91b0c70$@16degrees.com.au>
 <CALaBZo6f4ACB3HwyA3_JgY+YzpVVnsvUX6mWUpeb86RqJhQm=Q@mail.gmail.com>
 <4EEF7D27.8010708@googlemail.com>
 <1324318342.15371.YahooMailNeo@web160904.mail.bf1.yahoo.com>
To: ooo-dev@incubator.apache.org

On Dec 19, 2011, at 1:12 PM, Joe Schaefer wrote:

> Well on the one hand announcing plans is
> never a bad thing, we don't want to instill
> the idea that work from committers needs
> to be pre-negotiated prior to execution.
> Part of the Apache Way, and in fact the supporting
> version control systems, is to allow concurrent
> activity to proceed largely unimpeded.  Only
> when conflicts happen does there need to be
> a discussion about intentions.
>=20
> This "non-coordinated" workflow is what we
> mean when we refer to concepts like CTR or
> JFDI.  It can be a difficult lesson for a
> large group to ultimately adopt, but is something
> we should aspire to at least until it proves
> unsustainable.

I agree.

In this case it was good to pre-announce. It definitely meant people =
were paying attention to Jean's first commit in ooo-site.

Regards,
Dave


>=20
>=20
>=20
>=20
>=20
>> ________________________________
>> From: J=FCrgen Schmidt <jogischmidt@googlemail.com>
>> To: ooo-dev@incubator.apache.org=20
>> Sent: Monday, December 19, 2011 1:06 PM
>> Subject: Re: Support page of website - work planned
>>=20
>> On 12/19/11 2:06 AM, Jean Weber wrote:
>>> On Mon, Dec 19, 2011 at 11:00, Gavin =
McDonald<gavin@16degrees.com.au>  wrote:
>>>>=20
>>>>> -----Original Message-----
>>>>> From: Jean Weber [mailto:jeanweber@gmail.com]
>>>>> Sent: Monday, 19 December 2011 10:35 AM
>>>>> To: OOo-dev Apache Incubator
>>>>> Subject: Support page of website - work planned
>>>>>=20
>>>>> I am going to update the support page (currently at http://ooo-
>>>>> site.apache.org/support/index.html). FYI, here is what I intend to =
do. (If
>>>>> there is a place on the planning wiki for this info, I'll put it =
there
>>>> too.)
>>>>>=20
>>>>> * Check all the links and remove or correct any out of date ones.
>>>>>=20
>>>>> * Remove all the third-party or related material marked for OOo =
1.x or OOo
>>>>> 2.x, along with at least one item mis-labelled as "all versions"
>>>>> which is obsolete.
>>>>>=20
>>>>> * Update links to, and info about, some of the v3.x books that I =
know have
>>>>> later editions than those listed.
>>>>>=20
>>>>> * Correct typos.
>>>>>=20
>>>>> --Jean
>>>>=20
>>>> I believe this is a CTR project (Commit then Review) , and each =
edit results
>>>> is a commit
>>>> log message so unless it is a major policy change or something you =
really
>>>> are unsure of,
>>>> I would just go ahead and do the work. Folks will shout if they =
spot
>>>> anything they think
>>>> warrants further discussion.
>>>>=20
>>>> Thanks
>>>>=20
>>>> Gav...
>>>=20
>>> Just going ahead is what I intended, so thanks for the confirmation,
>>> Gav. My note was to alert people who might be thinking of working on
>>> the same page, so they can say, "Oh, good, that's something I don't
>>> need to do; I can just review it when Jean's done." In the interest =
of
>>> reducing noise on this list, would it be better if I avoided such
>>> messages in future?
>>>=20
>>=20
>> I think putting a note on the list that you intend to work on a page =
is=20
>> a good idea to avoid duplicate work or to simply organize the work. =
It=20
>> can only help ;-)
>>=20
>> Juergen
>>=20
>>=20
>>=20
>>=20
>>=20
>>> --Jean
>>=20
>>=20
>>=20