www-apachecon-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre Smits <pierre.sm...@gmail.com>
Subject Re: Apache Flex
Date Tue, 24 Jul 2012 07:08:42 GMT
Der all,

Now that the Call for Papers has been announced broadly via the official Apache communication
channels and others, whereas the announcement of the EU event was communicated more informally,
we see a lot of potential presentations, talks and workshops popping up that have a hard time
to be placed in any of the listed tracks. 

I agree that a renaming of tracks and a realignment of projects and papers could not only
lessen the confusion for the submitters of papers but also enhance the importance of the event
for potential visitors. 

The track name proposal of Tim makes sense in that way, but only with good descriptions 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 business out-of-the-box, how they can be implemented and

The target audiences of this track are not only the decision takers and influences in the
enterprise, like the IT Managers and architects, but also everybody (user, developer, etc)
else who want to gain insights in the Enterprise ready solutions of Apache.

Example of projects falling in above mentioned track could be those like James and Ofbiz.

Of course, broad descriptions of such generic tracks could also lead to new and heated discussions
about where projects and papers should go, like 'our development solution for enterprise data
storage is an enterprise ready development framework and should go in this Track, but should
also be mentioned under 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 projects and paper
for the EU Event with the risk of losing our audience or creating more or new confusion for
submitters, and/or,
- should we treat this as a lesson to be learned and apply it to the US event in 2013.

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



Verstuurd vanaf mijn iPad

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

> On Mon, Jul 23, 2012 at 5:21 AM, Mohammad Nour El-Din
> <nour.mohammad@gmail.com> wrote:
>> Hi
>> On Mon, Jul 23, 2012 at 11:14 AM, Olivier Lamy <olamy@apache.org> wrote:
>>> Tools track ?
>> You mean the Apache Daily ?
>> 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 ?
>> I suggested that because there you will find Apache related projects which
>> enable you to develop similar application to what you mentioned about Flex.
>> 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.
>> 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 ?
> 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:
> o) Search
> o) Data Storage
> o) Enterprise
> o) Developer tooling
> o) Infrastructure
> Of course, four sentences ago would have been an ideal time to ask who
> the primary target audience is? :)
> Thanks,
> --tim

View raw message