community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sally Khudairi>
Subject Re: YouTube Nonprofit Program
Date Tue, 06 Nov 2012 19:54:22 GMT
Thanks so much, Rob. This is great.

Our current YouTube account was created for the ASF's 10th Anniversary, and I'm a bit disappointed
that we haven't had a chance to do more with it. Bandwidth and all.

However, I love the idea for PMCs to post project updates, project/events/activity snippets,
community initiatives, and the like. Whilst we can't be all things to all people, it would
be fantastic to have added content that would more clearly represent the Apache footprint.

So yes, it would be great to become part of the YouTube Non-profit program. Not sure we can
transfer over, but that would be ideal.

I'm absolutely swamped for the next month or there any chance we've got some volunteer
energy to help out? ComDev, are your sleeves rolled up?

Thanks in advance,


> From: Rob Weir <>
>Sent: Tuesday, 6 November 2012, 11:43
>Subject: Re: YouTube Nonprofit Program
>On Tue, Nov 6, 2012 at 11:06 AM, Ross Gardler
><> wrote:
>>> -----Original Message-----
>>> From: Rob Weir []
>>> Sent: 06 November 2012 15:36
>>> To:
>>> Subject: YouTube Nonprofit Program
>>> It appears that we have an ASF "channel" on YouTube:
>>> I see that there is also a YouTube Nonprofit Program, that brings some extra
>>> perks beyond a normal account:
>>> Does anyone know, is our channel currently part of that nonprofit program?
>> I don't know the answer but Sally "owns" this channel. I've cc'd press@ (Sally more
useful info below)
>> Rob, in terms of your question. Yes we (ComDev) are interested in this as we are
experimenting with video from conferences as we speak.
>Great.  It seems that YouTube has both publicity/communications
>potential as well as community development potential.  (Or you could
>say those are two sides of the same coin.)
>My immediate interest is figuring out what the best way for an Apache
>project to engage with YouTube, especially if we anticipate having,
>over time, many videos.
>The options in theory are:
>1) Individual volunteers upload using their own personal accounts,
>perhaps adopting some tagging scheme to show their commonality.  The
>project them hosts a webpage that links to or embeds the various
>videos.  This is the simplest method, but doesn't cause anything to
>formally be contributed to the ASF, the videos are thus not
>necessarily under a license that allows easy remixing, etc.  Over time
>things become messy also, with outdated content and no way to control
>that from a project's perspective.   This is what happens now with
>2) An account per project, registered as a "user" in Youtube -- messy
>from security standpoint, the "shared secret" issue.
>3) Everyone use the ASF account -- but that then gets a bit unwieldy
>and inherits issue 2).
>4) Use the "related organization" clause of the YouTube Nonprofit
>program so every PMC can have its own channel if it wishes.  Adopt
>consistent branding, etc.  This may be the most flexible of the
>options, but requires the most coordination.
>Maybe other options as well.
>>> If we are part of that program (or are interesting in joining it) then there
>>> this interesting note:
>>> "We only allow one membership per organization. However, branches of
>>> umbrella organizations that share Employee Identification Numbers
>>> (EINs) with their parent organizations are eligible for individual memberships.
>>> Branches must indicate that they are applying as a "related organization"
>>> during the application process and go through additional screening."
>>> This might be an avenue for having project-specific accounts as well, which
>>> might be interesting for projects like Apache OpenOffice, which have already
>>> produced a number of Youtube videos, but all scattered among individual
>>> user accounts.
>>> Anyone else interested in this?  Is this worth pursuing?  Who controls the
>>> current ASF YouTube account?
>>> Regards,
>>> -Rob
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message