Mailing-List: contact dev-help@ctakes.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ctakes.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: "Bleeker, Troy C." <Bleeker.Troy@mayo.edu>
To: "dev@ctakes.apache.org" <dev@ctakes.apache.org>
Subject: RE: ctakes twitter account
Thread-Topic: ctakes twitter account
Thread-Index: AQHONh6D1pV8jfl2JEypkxv9hw0uo5jQx9OAgACMeID//8PgUIAAA09g
Date: Thu, 11 Apr 2013 15:22:15 +0000
Message-ID: 
 <B1D5DE3F00E17F458CC1B5158EA798B30C4349@MSGPEXCEI10A.mfad.mfroot.org>
References: <5165B80C.2030706@childrens.harvard.edu>
 <F94329B1-79B8-4E48-8314-D934DFBA8804@gmail.com>
 <5166C509.5010206@childrens.harvard.edu>
 <924DE05C19409B438EB81DE683A942D9104D5B9E@CHEXMBX1A.CHBOSTON.ORG>
In-Reply-To: <924DE05C19409B438EB81DE683A942D9104D5B9E@CHEXMBX1A.CHBOSTON.ORG>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

If you project to your constituents by using social media and then end up w=
ith stale content those constituents won't come back to the social media af=
ter checking it just once. I've done one of these before, and it seems easy=
 at first, but after a few months ... 6 months ... a year ... it gets harde=
r and harder to think of something fresh to tweet. You can find numerous we=
b sites/blogs that talk about the need to be relevant and current in social=
 media or you might as well not bother.

A few things I learned in my experience:
- One or two persons should be dubbed "responsible" for tweeting. If not, m=
ost community members will expect someone else to do it and it won't get do=
ne.
- This takes a small amount of time for the tweeter, but ends up needing to=
 be a weekly (at the longest), repeated calendar item for them or it will f=
all off the radar.
- If the micro-blogging ends up only being for announcements then perhaps c=
onsider making the description of the social media account state that. Mayb=
e even the name.
- Tweeters will want to install a plug-in for their favorite device, email =
client, or anything they use daily that is twitter friendly - allowing for =
fast sends.
- Tweeters will need to learn a URL link minimizer.
...

Thanks
Troy
-----Original Message-----
From: dev-return-1498-Bleeker.Troy=3Dmayo.edu@ctakes.apache.org [mailto:dev=
-return-1498-Bleeker.Troy=3Dmayo.edu@ctakes.apache.org] On Behalf Of Chen, =
Pei
Sent: Thursday, April 11, 2013 9:41 AM
To: dev@ctakes.apache.org
Subject: RE: ctakes twitter account

This would be a great outlet for things like the below -just to name a few:
- applications that implemented cTAKES,
- new papers published involving cTAKES
- General PR
perhaps we can begin by retweeting the ASFTweet: https://twitter.com/TheASF=
/status/321593488728788992

--Pei

> -----Original Message-----
> From: Dmitriy Dligach [mailto:dmitriy.dligach@childrens.harvard.edu]
> Sent: Thursday, April 11, 2013 10:14 AM
> To: dev@ctakes.apache.org
> Subject: Re: ctakes twitter account
>=20
> Great, let's keep @apachectakes for now. I contacted the @ctakes=20
> handle owner but it's not likely that he will respond or let us use=20
> his account anyway...
>=20
> Dima
>=20
> On 04/11/2013 01:50 AM, Andy McMurry wrote:
> >> https://twitter.com/apachectakes
> > ApacheCtakes is better -- conveys some meaning to someone who has no
> exposure to cTakes.
> > assuming that the twitters is for public messaging, that is  important.
> >
> > my 2 cents,
> > --A
> >
> > On Apr 10, 2013, at 12:05 PM, Dmitriy Dligach
> <dmitriy.dligach@childrens.harvard.edu> wrote:
> >
> >> FYI:
> >>
> >> I tried to create a twitter account for ctakes. Turns out @ctakes=20
> >> handle is
> taken. Meanwhile I was able to create @apachectakes account:
> >>
> >> https://twitter.com/apachectakes
> >>
> >> Dima