Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Received-SPF: pass (nike.apache.org: domain of pierre.smits@gmail.com
 designates 74.125.82.170 as permitted sender)
Subject: Re: ApacheCon - How you can help
References: <541C3187.1090401@apache.org>
From: Pierre Smits <pierre.smits@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <541C3187.1090401@apache.org>
Message-Id: <8C380DCD-33CB-46F7-A71C-1BC74C722C88@gmail.com>
Date: Sun, 21 Sep 2014 11:19:37 +0200
To: "dev@community.apache.org" <dev@community.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Also done in the Apache Dirctory mailing list.

Verstuurd vanaf mijn iPad

> Op 19 sep. 2014 om 15:37 heeft Rich Bowen <rbowen@rcbowen.com> het volgend=
e geschreven:
>=20
> Here's the most important ways that you can help with ApacheCon EU right n=
ow, in order of importance.
>=20
> * If you are involved in an Apache project that has content at ApacheCon, s=
end messages to your users@ and dev@ list telling them about that content, a=
nd telling people that they need to be there. Tell them specifically what ta=
lks they need to come for, and what developers they'll get to hang out with a=
t the event. Tell them that they are doing their career a disservice if they=
 don't come to this event. Remind them that committers have a deep discount,=
 so if they're not committers now, here's a *great* reason for them to get o=
n that train for next time. Remind the US audience that if they can't make i=
t to Budapest, they should plan to come to Austin in April.
>=20
> * Reach out to other audiences - Twitter, Facebook, and G+, certainly, but=
 also other non-Apache projects you're involved with that have strong overla=
p with our content. Again, mention specific talks and people that will be at=
 the event.
>=20
> * If your company cares about or relies on any Apache technology, encourag=
e them to sponsor the event and/or send an employee to the event. Remind the=
m that it's about more than just the technical content - they will get to ha=
ve first-hand contact with the people that develop the software, and become p=
art of that community, with the possibility to participate in shaping the fu=
ture of that product. If there's a spark of interest in sponsorship, have th=
em get in touch with me - rbowen@apache.org - and we'll take it from there.
>=20
> * Follow and retweet the @apachecon account.
>=20
> --=20
> rbowen@apache.org
> http://apache.org/
>=20