You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Rob Vesse <rv...@dotnetrdf.org> on 2013/12/13 17:51:46 UTC
FW: Content Committee, ApacheCon 2014
If no-one has any objections or would like to do this I'm happy to be the
Jena representative for this
Rob
On 12/12/2013 19:52, "Rich Bowen" <rb...@rcbowen.com> wrote:
>Dear PMCs,
>
>In the coming days, we'll be hearing more about ApacheCon 2014, and what
>we need to do to make it happen.
>
>This time around, we, the folks at the ASF, will be responsible for
>selecting content, while the conference producer will be responsible for
>*EVERYTHING* else.
>
>Content selection is no small task, and I need help. While there are
>several people who have already volunteered to be part of a content
>selection committee, I'd also like to ask each PMC which wants to be
>represented in the selection process to volunteer one person to
>represent them in this task.
>
>We'll be using the RFP infrastructure supplied by the producer so all
>you'd be on the hook for is being willing to review a list of talk
>proposals specific to your project, and voting for/against them in some
>method which that RFP process provides. Final schedule construction
>falls to the producer, and, I suppose, to me.
>
>Thanks!
>
>--
>Rich Bowen
>rbowen@rcbowen.com
>http://rcbowen.com/
>
Re: Content Committee, ApacheCon 2014
Posted by Rob Vesse <rv...@dotnetrdf.org>.
Hi Rich
I'm volunteering to be on the content selection committee on behalf of the
Apache Jena project
Regards,
Rob
On 13/12/2013 18:35, "Andy Seaborne" <an...@apache.org> wrote:
>On 13/12/13 16:51, Rob Vesse wrote:
>> If no-one has any objections or would like to do this I'm happy to be
>>the
>> Jena representative for this
>
>Go for it.
>
> Andy
>
>>
>> Rob
>>
>> On 12/12/2013 19:52, "Rich Bowen" <rb...@rcbowen.com> wrote:
>>
>>> Dear PMCs,
>>>
>>> In the coming days, we'll be hearing more about ApacheCon 2014, and
>>>what
>>> we need to do to make it happen.
>>>
>>> This time around, we, the folks at the ASF, will be responsible for
>>> selecting content, while the conference producer will be responsible
>>>for
>>> *EVERYTHING* else.
>>>
>>> Content selection is no small task, and I need help. While there are
>>> several people who have already volunteered to be part of a content
>>> selection committee, I'd also like to ask each PMC which wants to be
>>> represented in the selection process to volunteer one person to
>>> represent them in this task.
>>>
>>> We'll be using the RFP infrastructure supplied by the producer so all
>>> you'd be on the hook for is being willing to review a list of talk
>>> proposals specific to your project, and voting for/against them in some
>>> method which that RFP process provides. Final schedule construction
>>> falls to the producer, and, I suppose, to me.
>>>
>>> Thanks!
>>>
>>> --
>>> Rich Bowen
>>> rbowen@rcbowen.com
>>> http://rcbowen.com/
>>>
>>
>>
>>
>>
>
Re: FW: Content Committee, ApacheCon 2014
Posted by Andy Seaborne <an...@apache.org>.
On 13/12/13 16:51, Rob Vesse wrote:
> If no-one has any objections or would like to do this I'm happy to be the
> Jena representative for this
Go for it.
Andy
>
> Rob
>
> On 12/12/2013 19:52, "Rich Bowen" <rb...@rcbowen.com> wrote:
>
>> Dear PMCs,
>>
>> In the coming days, we'll be hearing more about ApacheCon 2014, and what
>> we need to do to make it happen.
>>
>> This time around, we, the folks at the ASF, will be responsible for
>> selecting content, while the conference producer will be responsible for
>> *EVERYTHING* else.
>>
>> Content selection is no small task, and I need help. While there are
>> several people who have already volunteered to be part of a content
>> selection committee, I'd also like to ask each PMC which wants to be
>> represented in the selection process to volunteer one person to
>> represent them in this task.
>>
>> We'll be using the RFP infrastructure supplied by the producer so all
>> you'd be on the hook for is being willing to review a list of talk
>> proposals specific to your project, and voting for/against them in some
>> method which that RFP process provides. Final schedule construction
>> falls to the producer, and, I suppose, to me.
>>
>> Thanks!
>>
>> --
>> Rich Bowen
>> rbowen@rcbowen.com
>> http://rcbowen.com/
>>
>
>
>
>