Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <4EA6FD16.8000000@wtnet.de>
References: 
 <CAP-ksogQXDhx_UwMj3GVvZjvtwPyDs_Vaz0mibEb9x+dQcyixg@mail.gmail.com>
	<0ECD6081-A7CF-4E6E-83AA-A2ECE9E395D9@comcast.net>
	<CAP-ksohWqDN-CEv2-7RdevLDW4vLW_4Qtzp2Bj9HKxr8Yf9deg@mail.gmail.com>
	<4EA6FD16.8000000@wtnet.de>
Date: Tue, 25 Oct 2011 14:28:03 -0400
Message-ID: 
 <CAP-ksoiTHuLcmnNezuW2piw6y-4RgxtbRz4mjkKzeUooax+WYw@mail.gmail.com>
Subject: Re: Draft mailing list notification post
From: Rob Weir <robweir@apache.org>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 25, 2011 at 2:16 PM, Marcus (OOo) <marcus.mail@wtnet.de> wrote:
> Am 10/25/2011 07:58 PM, schrieb Rob Weir:
>>
>> On Tue, Oct 25, 2011 at 1:45 PM, Dave Fisher<dave2wave@comcast.net>
>> =C2=A0wrote:
>>>
>>> I wonder if this is too technically detailed.
>>>
>>> Since the recipient is a ML user that impact should be noted near the
>>> top.
>>>
>>> The information about what the ASF / podling process is all about shoul=
d
>>> be at the end.
>>>
>>
>> The feedback we received when we sent an earlier list migration note
>> to the users and discuss list, after we initially set up ooo-users,
>> was along the lines of "Who the hell are you and why is this the first
>> we are hearing about the migration?". =C2=A0That is why I put the
>> introductory ASF stuff at the top, to put it in context.
>>
>> Of course, doing that could lead people to ignore the note, thinking
>> there is nothing important in it. =C2=A0So that's why I started by sayin=
g
>> the note was important. =C2=A0But I realize that that itself could incre=
ase
>> the chance of the email being ignored, =C2=A0since emails that say they =
are
>> important rarely are.
>>
>> So how can we have both an good intro as well as get a high response rat=
e?
>
> There will be always a number of people that will not do what you (we) wo=
uld
> expect. So, we should try to make it best as possible. IMHO the draft is
> that.
>
>> Maybe split this into two emails, and space them a week apart? =C2=A0So =
one
>> email that is the intro, gives the background on the Incubation, the
>> migration effort, etc. =C2=A0Short and sweet. =C2=A0They might actually =
read it.
>> =C2=A0Then follow a week later with "As we previously mentioned in our n=
ote
>> last week.... =C2=A0We're starting the list migration now. To join the n=
ew
>> list you will need to...."
>>
>> Would that be better?
>
> Maybe. But then the first mail should contain something like "... today w=
e
> want to explain who we are, where the OOo project is going to and what wi=
ll
> happen with this ML in x days. A second mail will be sent with more detai=
ls
> and techncial stuff ...".
>

We can also use the initial email to prompt the discussion on whether
there is sufficient interest for an NL list.   Requesting a new list
can take 1 or 2 weeks, so we do need some lead time for this,  An
initial note could be useful for that purpose.

>>> Information here to go to find out about AOOo release plans would be
>>> helpful. A wiki page with updates.
>>>
>>
>> We have a release plan? =C2=A0 I suppose we can put a placeholder page.
>>
>>> A link to the ooo blog.
>>>
>>
>> Good idea.
>
> Yes, some more links for the normal user.
>
>> Maybe also include on every post a link to the ooo-dev and ooo-users
>> lists, since those are our main ones.
>
> Marcus
>
>
>
>>> On Oct 25, 2011, at 5:57 AM, Rob Weir wrote:
>>>
>>>> On the wiki here:
>>>>
>>>>
>>>> https://cwiki.apache.org/confluence/display/OOOUSERS/Email+Migration+P=
ost
>>>>
>>>> Feel free to make changes directly on the wiki, or suggest them as
>>>> responses to this note. =C2=A0I don't think we want to overburden the
>>>> reader with a recitation of migration facts, but instead motivate them
>>>> to take the desired actions. =C2=A0But since this will be for many the
>>>> first note they officially receive from the PPMC, it should probably
>>>> have some introductory information, and a welcome and invitation to
>>>> get involved (stay involved) with the project.
>>>>
>>>> -Rob
>