NOTE: PyCon US next year is going to move over to a similar system
where we require people to give the PSF a license to redistribute and
to put the talk materials under one of 3 Creative Commons licenses
(the choice part is still under discussion). This past year we
collected A/V for all talks and tutorials (with one minor gap). We
have not been able to get this video out to the public due to the
release forms.
The problem is the video was collected w/o being split by talk and we
ran into a chicken-egg problem. Only a few people could do the most
difficult job of tagging/splitting the AV. This bottleneck means we
either need to hire consultants and have them sign their own legalese
paperwork, or have the people who are already familiar with the
materials do the work in their spare time. We are going with the
latter, and then will get the video out to the community to clean up
and complete the processing on. Just having one talk which needs to be
pulled out from the rest causes a huge amount of work. (NOTE: we are
talking about 80GB files which get broken down into 3GB files for a
30min talk so distrobution will have other issues as well lest
re-encoding becomes a bottleneck.)
There was much discussion about this and we decided the talks we would
loose out on would open up more room for those we would normally have
to decline (especially as we are now declining 70% of our received
proposals).
If you are planning on doing AV, you need to plan well in advance and
have a post processing plan set in place. We have learned this the
hard way. Just having volunteers record the video in an adhock manner
creates exponentially more work in the end.
So +1 for enforcing a CC license and have the submission form double
as a release form. The alternative ends up robbing the community of
valuable materials, and generating problems on the AV end.
-Doug
On Mon, May 26, 2008 at 6:20 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2008-05-24 01:05, Christian Tismer wrote:
>>
>> * Whether you do not want your talk to be recorded and distributed
>>
>> The form at
>> http://registration.europython.eu/submit.html
>> does not provide an entry for the last point.
>> I propose to add it.
>
> I think that you should reconsider the talk publishing policy. There are
> a few things that cause bad vibes and it's not really necessary:
>
> * By submitting a talk and not excluding its use from the policy, the
> speaker is to implicitly declare compliance with the policy.
>
> This feels a lot like shrink-wrapped licenses and is not really
> in the spirit of Python or EuroPython (and I'm sure, it's not
> intended to feel that way).
>
> * Licensing a talk under the proposed CC license prevents any
> control over how the talk recording is used.
>
> People will not necessarily like their talks to appear on YouTube
> or elsewhere with no possibly to take them down again.
>
> Many EPC speakers have put their talks up online in the past, so
> there's no need to policy them into doing so. Recording talks is
> nice (I plan to do that again for my talk(s) like I did last
> year), but how the recording is used should really be in realm
> of the speaker and not be freed in the proposed way.
>
> I think it would be better to make the recording opt-in rather than
> opt-out and there shouldn't be a specific license on it - after all,
> the speaker owns the copyright, even if someone else records the
> talk.
>
> Thanks,
> --
> Marc-Andre Lemburg
> eGenix.com
>
> Professional Python Services directly from the Source (#1, May 26 2008)
>>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
> ________________________________________________________________________
>
> :::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::
>
>
> eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
> D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
> Registered at Amtsgericht Duesseldorf: HRB 46611
> _______________________________________________
> Europython-improve mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/europython-improve
>
_______________________________________________
Europython-improve mailing list
[email protected]
http://mail.python.org/mailman/listinfo/europython-improve
