+1 to the proposal

@Matthias could you share more about the dynamics in how people in the
community would be able to add videos and who would be owning the curation
of the channel?

G



On 21 February 2018 at 09:08, Matthias Baetens <matthias.baetens@datatonic.
com> wrote:

> Hi Gaurav,
>
> Thanks for pointing that out. The channel can be found here
> <https://www.youtube.com/channel/UChNnb_YO_7B0HlW6FhAXZZQ>.
> No videos there yet though, waiting for approval to publish the first one!
>
> Cheers,
> Matthias
>
> On Wed, Feb 21, 2018 at 12:55 AM, Gaurav Thakur <gaurav2...@gmail.com>
> wrote:
>
>> How can people get access to the channel?
>>
>> Thanks, Gaurav
>>
>> On Wed, Feb 21, 2018 at 1:34 PM, Matthias Baetens <
>> matthias.baet...@datatonic.com> wrote:
>>
>>> Hi all,
>>>
>>> This is a proposal to launch the Apache Beam YouTube channel and at the
>>> same time add the first video to the channel.
>>>
>>> We would like to use the channel to centralize all videos / recordings
>>> related to Apache Beam and make it a community driven channel, so people
>>> have a one stop shop for learnings about Beam.
>>>
>>> The first video would be the recording of the second Beam meetup in
>>> London:
>>> Apache Beam meetup London 2: use case in finance + IO in Beam and
>>> Splittable DoFns. The video can be seen on the channel if you have login
>>> details (it is currently set to private).
>>>
>>> Please let me know if there are any questions or comments!
>>>
>>> Best regards,
>>> Matthias
>>>
>>
>>
>
>
> --
>
>
> *Matthias Baetens*
>
>
> *datatonic | data power unleashed*
>
> office +44 203 668 3680 <+44%2020%203668%203680>  |  mobile +44 74 918
> 20646
>
> Level24 | 1 Canada Square | Canary Wharf | E14 5AB London
> <https://maps.google.com/?q=1+Canada+Square+%7C+Canary+Wharf+%7C+E14+5AB+London&entry=gmail&source=g>
>
>
> We've been announced
> <https://blog.google/topics/google-cloud/investing-vibrant-google-cloud-ecosystem-new-programs-and-partnerships/>
>  as
> one of the top global Google Cloud Machine Learning partners.
>

Reply via email to