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: 
 <CAMK9kTg94qQVZaJ-yUDzSiyjDZW_Hk8B8ZoGEL5zd+ReMOad2Q@mail.gmail.com>
References: 
 <CAP-ksoi5c-tSn3dZSMkGdipp9ebnyJN7eLNrQnEBHWJAJSbG2g@mail.gmail.com>
	<CACm2uJjTY+S5pN2_7QK9ERZakYgLWiEMuyy2cgq6FEfy6kZRHw@mail.gmail.com>
	<1334160489.3622.11.camel@sybil-gnome>
	<CAP-ksoihu2bXLnes=brGh1V=rNc+L8gVnep_XJEH6G3tFNOi=w@mail.gmail.com>
	<1334551826.2646.66.camel@sybil-gnome>
	<1334677919.4871.15.camel@sybil-gnome>
	<CAMK9kTg94qQVZaJ-yUDzSiyjDZW_Hk8B8ZoGEL5zd+ReMOad2Q@mail.gmail.com>
Date: Tue, 17 Apr 2012 18:54:53 +0200
Message-ID: 
 <CAP-ksojM4EHo9hfhtqqTvEgnqr0CyVUj_GfvKfO8kRevF+jsUw@mail.gmail.com>
Subject: Re: Apache OpenOffice Project Twitter Account
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, Apr 17, 2012 at 6:02 PM, Alexandro Colorado <jza@apache.org> wrote:
> I think this provide a bit of confussion on the user end. Also I
> recognize the struggle of keeping the accounts active. Making multiple
> accounts will increase the job.
>

I think the main consideration will be the number of PPMC members who
can post to the account. I'm proposing to have up to 10 PPMC members
have access to the Twitter account.  That should ease the challenge of
keeping the account active.

> The blog itself has not been updated that frequently, and I am not
> sure if this will increase as we get a release.
>

Surely writing a tweet is easier and requires less effort than writing
a blog post.

> Most of the use of the accounts on my experience is support-like
> issues. So relying on one single point of contact is also pretty bad.
>

That's why I propose to have up to 10 PPMC members on the account.
Also, I think users will understand that technical support cannot be
done in 140 characters or less. I'd expect we refer users to the
support page in most cases.

> Having an AOO-Support and AOO-Annoucement is equally not good strategy
> in my account because people will tend to stick to the account that
> they see crossing their path. (Just because we structure one way,
> doesnt mean users will do so).
>

I don't think anyone is proposing two official AOO Twitter accounts.
We're talking about one.  (Unless I missed something).

> One of the issues of openofficeorg accounts both on Facebook Google
> plus and twitter had been the issue of keeping the content fresh and
> also interacting as a group as opposed to an individual.
>

I'm sure this will remain an issue for AOO and we'll learn and improve
at this over time.

> I would argue to stop taking liberties on creating new accounts and
> instead take liberties on designing a good strategy to solve some of
> these basic issues that tackle these problems.
>

I think that is what we're discussing right now.

> So far I am not even sure how these accounts could be handle by
> infrastructure and what are the requirements. Rob mention that
> infrastructure should manage these, but I am also not sure how long
> will they take to proxy the messages specially when it comes to
> support and we get 100 inquiries a day (for example).
>

I've connected the ApacheOO Twitter account to BirdHerd, which allows
us to enable up to 10 PPMC members to interact with the single Twitter
account.

http://birdherd.com/

So I think we have a reasonable solution for that.

-Rob

>
> On 4/17/12, drew <drew@baseanswers.com> wrote:
>> On Mon, 2012-04-16 at 00:50 -0400, drew wrote:
>>> On Sun, 2012-04-15 at 18:25 -0400, Rob Weir wrote:
>>> > On Wed, Apr 11, 2012 at 12:08 PM, drew <drew@baseanswers.com> wrote:
>>> > > On Wed, 2012-04-11 at 17:43 +0200, Roberto Galoppini wrote:
>>> > >> On Wed, Apr 11, 2012 at 4:09 PM, Rob Weir <robweir@apache.org> wro=
te:
>>> > >>
>>> > >> > Social media outreach, via Twitter, Facebook, Google+, etc., is =
an
>>> > >> > important part of outreach to users. Although the Apache develop=
er
>>> > >> > community is firmly rooted in mailing lists, we know that our us=
ers
>>> > >> > live in a different world. =C2=A0 If we want to engage with them=
 we need
>>> > >> > to
>>> > >> > use the tools that they use, and communicate the way they
>>> > >> > communicate.
>>> > >> >
>>> > >> > Now that we're very close to the AOO 3.4 release, I'd like to st=
art
>>> > >> > with a project Twitter account, under PPMC control.
>>> > >> >
>>> > >> > By "under PPMC control" I mean something similar to how we treat
>>> > >> > the
>>> > >> > project blog:
>>> > >> >
>>> > >> > -- Any PPMC member, upon request, can have write access.
>>> > >> >
>>> > >> > -- We can use the project's official logo in conjunction with th=
e
>>> > >> > account.
>>> > >> >
>>> > >> > -- We would promote the account on our project's website.
>>> > >> >
>>> > >> > -- We would generally treat the account as an official voice of =
the
>>> > >> > project, not as a personal account.
>>> > >> >
>>> > >> > I'm not saying we need to pre-review and and approve every "twee=
t"
>>> > >> > sent through the account. =C2=A0But we should set expectations t=
hat the
>>> > >> > account is to be used in a professional fashion, upholding the
>>> > >> > standards of this project, not used to settle personal disputes,=
 to
>>> > >> > promote personal business, etc.
>>> > >> >
>>> > >>
>>> > >> An option could be to agree on a simple guideline for that, so tha=
t
>>> > >> everyone knows how to handle it. I'm thinking not only about the
>>> > >> style of
>>> > >> communication, but also about who to follow, how to engage in
>>> > >> conversations, improve outreach, etc.
>>> > >>
>>> > >>
>>> > >> > There are already several Twitter accounts that use the OOo name=
 or
>>> > >> > trademarks:
>>> > >> >
>>> > >> > http://twitter.com/#!/openofficeorg =C2=A0--- This account has 1=
571
>>> > >> > followers. =C2=A0But it is not sharing any AOO status, no links =
to blog
>>> > >> > posts, announcements, etc. =C2=A0Who controls it? =C2=A0Are
>>> > >> > we able to get it under PPMC control? =C2=A0Can we rebrand it as=
 Apache
>>> > >> > OpenOffice?
>>> > >> >
>>> > >>
>>> > >> That could be a good starting point, I think. It seems like if you=
're
>>> > >> the
>>> > >> only one who can send DM to the actual owner's account.
>>> > >>
>>> > >>
>>> > >> >
>>> > >> > http://twitter.com/#!/openoffice -- This account seems unused.
>>> > >> > Only one
>>> > >> > tweet.
>>> > >> >
>>> > >>
>>> > >> I'd try to get that it too. It's better than ApacheOO, and you mig=
ht
>>> > >> want
>>> > >> to put the full name in the Settings > Account > Name.
>>> > >>
>>> > > Hi Roberto, Rob
>>> > >
>>> > > I just did so now, and followed up with an email to the account
>>> > > contact
>>> > > in the whois database for the domain listed, the linked sub-domain =
has
>>> > > been dead for a while IIRC, though the main site is alive - anyway,
>>> > > I'll
>>> > > report back when (or if) I hear anything back.
>>> > >
>>> >
>>> > Hi Drew,
>>> >
>>> > It has been 5 days now. =C2=A0Have you received any response from tha=
t domain
>>> > owner?
>>>
>>> No nothing.
>>>
>>> >
>>> > If not, I'm ready to go with a new account:
>>> > https://twitter.com/#!/apacheoo
>>>
>>> a good account name for an announcement stream, even with the other IMO=
.
>>
>> Howdy all,
>>
>> Wanted to follow up on this.
>>
>> As I think about, IMO, this is a good moment to use a new account(s) for
>> a more formal, account of record if you will, for the project; Apache
>> OpenOffice. The use of the apache in the account name makes very good
>> sense to me for this purpose.
>>
>> The flip side of that then would be to treat the existing social media
>> account as more community, less formal, voices.
>>
>> Anyawy - the apacheoo does get my vote for an appropriate name, for the
>> project account.
>>
>> I took the liberty then to register the same name with the identi.ca
>> network.
>> http://identi.ca/apacheoo
>>
>> IMO identi.ca, which has a smaller user base then twitter, represents an
>> important target group to the project.
>>
>> The two accounts, if we use them for this, should be tied together.
>> Certainly at the level that a post to the identi.ca should automatically
>> broadcast to the twitter network. (easy to do)
>>
>> A couple of thoughts on 'formal account of record':
>>
>> Would recommend that the accounts not be used to follow lots of other
>> accounts.
>>
>> The accounts should not be used to re-tweet others messages.
>>
>> The accounts should _not_ be used for auto-generated scheduled postings.
>>
>> The accounts do need to be used on a regular basis to build up
>> followers.
>>
>> Ability to 'follow' the accounts needs to be easily done within the main
>> web infrastructure and there should be some naturally well fitting
>> locations where that can be done.
>>
>> Anyone using the accounts should remember to keep the message focused to
>> the project.
>>
>> Well, that's a good spot to shutup huh :-) and let folks add their
>> wisdom here.
>>
>> So what you think - Use the new ApacheOO accounts?
>>
>> Thanks,
>>
>> //drew
>>
>>
>>
>>>
>>> //drew
>>>
>>> > I have it configured with the BirdHerd service, so up to 10 PPMC
>>> > members will be able send tweets via that account.
>>> >
>>> > -Rob
>>> >
>>> >
>>> > > //drew
>>> > >
>>> > >
>>> > > <snip>
>>> > >
>>> >
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> Alexandro Colorado
> OpenOffice.org Espa=C3=B1ol
> http://es.openoffice.org