community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jan i <j...@apache.org>
Subject Re: ApacheCon Europe status and ToDo
Date Thu, 24 Apr 2014 08:26:52 GMT
On 24 April 2014 10:02, Andrea Pescetti <pescetti@apache.org> wrote:

> On 23/04/2014 Rich Bowen wrote:
>
>> If you would like to be involved in reviewing the content for the
>> conference, please let me know.
>>
>
> I missed Denver but I'll be happy to help with Budapest. Account
> "pescetti".
>
>
>  The conference format is 3+2 - three days keynotes and conference
>> sessions, then two days other stuff. Other stuff includes tutorials (if
>> we can get them to fly this time), the CloudStack conference, a one or
>> two day Open Office user event (depending on the content we can get for
>> this)
>>
>
> The OpenOffice (one word please) event sounds like a wonderful
> opportunity. It would need to be substantially different from the "main"
> ApacheCon in terms of audience, fee and spirit. How can we make it
> excellent? Is this a task of the Linux Foundation, of the PMCs, of some
> individuals? I see a problem in waiting for content before having some
> basic event details settled. Of course, feel free to bring this to the PMC
> if you need feedback, a small discussion has already started.
>

Especially the fee would be very different (hence my focus on a user
event), In my opinion we need to hear from LF first, it they want to play
ball. As soon as they come back with a hopefully positive answer, then  the
AOO PMC can start discussing content/targets/marketing etc.

I basically expect LF to provide a room for the event, in parallel with the
cloudstack room. That way the AOO community gets more aquinted with ASF and
visa versa.

At the end of the day, success of such events always boils down to
individuals making it happen, LF provide the facilities, PMC group provide
the guidelines and individuals do the hard work.


rgds
jan I



> Regards,
>   Andrea.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message