Mailing-List: contact apachecon-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: apachecon-discuss@apache.org
Received-SPF: pass (athena.apache.org: domain of pierre.smits@gmail.com
 designates 74.125.82.48 as permitted sender)
Subject: Re: Apache Flex
References: <0519CE75-BA36-4F71-B59F-1947D2626572@classsoftware.com>
 <CAPoyBqRNOWUYLUOHfsxbQWRezJmiRWx01Zmh1Kk8uPPACGjEPQ@mail.gmail.com>
 <CAOvkMobLCVJvLeSd6uw0VNMucRe-U60qvT18vX4v3+rsbX=j0w@mail.gmail.com>
 <CAG_bHoznUm5eUDupp1M5AYv90AN8iQSooEPeE+-1aVRfgE6WkA@mail.gmail.com>
From: Pierre Smits <pierre.smits@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: 
 <CAG_bHoznUm5eUDupp1M5AYv90AN8iQSooEPeE+-1aVRfgE6WkA@mail.gmail.com>
Message-Id: <3D6B4F95-05F4-41C2-93E8-B117E69AC011@gmail.com>
Date: Tue, 24 Jul 2012 09:08:42 +0200
To: "apachecon-discuss@apache.org" <apachecon-discuss@apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Der all,

Now that the Call for Papers has been announced broadly via the official Apa=
che communication channels and others, whereas the announcement of the EU ev=
ent was communicated more informally, we see a lot of potential presentation=
s, talks and workshops popping up that have a hard time to be placed in any o=
f the listed tracks.=20

I agree that a renaming of tracks and a realignment of projects and papers c=
ould not only lessen the confusion for the submitters of papers but also enh=
ance the importance of the event for potential visitors.=20

The track name proposal of Tim makes sense in that way, but only with good d=
escriptions of tracks and target audiences. Let me present an example.

The track Enterprise could have following descriptions and target audience:

The enterprise track is all about Enterprise ready and mature solutions from=
 various Apache projects. The presenters inform you about their capabilities=
, opportunities and pitfalls and show you how these can support your busines=
s out-of-the-box, how they can be implemented and more.

The target audiences of this track are not only the decision takers and infl=
uences in the enterprise, like the IT Managers and architects, but also ever=
ybody (user, developer, etc) else who want to gain insights in the Enterpris=
e ready solutions of Apache.

Example of projects falling in above mentioned track could be those like Jam=
es and Ofbiz.=20

Of course, broad descriptions of such generic tracks could also lead to new a=
nd heated discussions about where projects and papers should go, like 'our d=
evelopment solution for enterprise data storage is an enterprise ready devel=
opment framework and should go in this Track, but should also be mentioned u=
nder the tracks 'Developer tooling' and 'Data storage'.

The question we should ask ourselves now is/are:
- can (or should) we still do this renaming of tracks and realignment of pro=
jects and paper for the EU Event with the risk of losing our audience or cre=
ating more or new confusion for submitters, and/or,
- should we treat this as a lesson to be learned and apply it to the US even=
t in 2013.

I don't know what is the wiser thing to do in this case, and appreciate your=
 opinion.

Regards,

Pierre

Verstuurd vanaf mijn iPad

Op 24 jul. 2012 om 03:15 heeft Tim Williams <williamstw@gmail.com> het volge=
nde geschreven:

> On Mon, Jul 23, 2012 at 5:21 AM, Mohammad Nour El-Din
> <nour.mohammad@gmail.com> wrote:
>> Hi
>>=20
>> On Mon, Jul 23, 2012 at 11:14 AM, Olivier Lamy <olamy@apache.org> wrote:
>>=20
>>> Tools track ?
>>>=20
>>=20
>> You mean the Apache Daily ?
>>=20
>> But I don't think it would be Fair for Flex to be there, I believe it
>> should be in [1]. Justin what do you think ?
>>=20
>> I suggested that because there you will find Apache related projects whic=
h
>> enable you to develop similar application to what you mentioned about Fle=
x.
>> Also it would be better for Flex to be there to show what it can add more=

>> than these other frameworks more specifically when it comes to Enterprise=

>> applications which I know it can do really good and even better than
>> traditional Java Web Applications framework. I have seen stock-market
>> monitoring applications built using Flex technology and it was awesome.
>>=20
>> Please if you still not sure that Flex should be there or in any other
>> existing track, would you please suggest a new one so we can discuss it ?=

>=20
> Personally, I'd suggest that "ApacheEE" is a poorly chosen name.
> Additionally, I think the track listing is too much - I'd suggest we
> attempt to condense the tracks and follow a 5 (+-2) rule - with the
> goal of each track running all days of the conference.  Is it too late
> for that?  If not, I'd offer what I think is a more user-friendly
> track list:
>=20
> o) Search
> o) Data Storage
> o) Enterprise
> o) Developer tooling
> o) Infrastructure
>=20
> Of course, four sentences ago would have been an ideal time to ask who
> the primary target audience is? :)
>=20
> Thanks,
> --tim