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: <0ECD6081-A7CF-4E6E-83AA-A2ECE9E395D9@comcast.net>
References: 
 <CAP-ksogQXDhx_UwMj3GVvZjvtwPyDs_Vaz0mibEb9x+dQcyixg@mail.gmail.com>
	<0ECD6081-A7CF-4E6E-83AA-A2ECE9E395D9@comcast.net>
Date: Tue, 25 Oct 2011 13:58:16 -0400
Message-ID: 
 <CAP-ksohWqDN-CEv2-7RdevLDW4vLW_4Qtzp2Bj9HKxr8Yf9deg@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 1:45 PM, Dave Fisher <dave2wave@comcast.net> wrote:
> 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 should =
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?".  That 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.  So that's why I started by saying
the note was important.  But I realize that that itself could increase
the chance of the email being ignored,  since emails that say they are
important rarely are.

So how can we have both an good intro as well as get a high response rate?

Maybe split this into two emails, and space them a week apart?  So one
email that is the intro, gives the background on the Incubation, the
migration effort, etc.  Short and sweet.  They might actually read it.
 Then follow a week later with "As we previously mentioned in our note
last week....  We're starting the list migration now. To join the new
list you will need to...."

Would that be better?

> Information here to go to find out about AOOo release plans would be help=
ful. A wiki page with updates.
>

We have a release plan?   I suppose we can put a placeholder page.

> A link to the ooo blog.
>

Good idea.

Maybe also include on every post a link to the ooo-dev and ooo-users
lists, since those are our main ones.

-Rob

> On Oct 25, 2011, at 5:57 AM, Rob Weir wrote:
>
>> On the wiki here:
>>
>> https://cwiki.apache.org/confluence/display/OOOUSERS/Email+Migration+Pos=
t
>>
>> 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
>
>