Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 176598 - Illegal redistribution of sourcecode from 3gpp.org
Summary: Illegal redistribution of sourcecode from 3gpp.org
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Media-video project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-30 15:54 UTC by Ben de Groot (RETIRED)
Modified: 2008-12-22 03:18 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben de Groot (RETIRED) gentoo-dev 2007-04-30 15:54:47 UTC
The Gentoo mirrors redistribute sourcecode zips from 3gpp.org, as used in ffmpeg and mplayer for the AMR codecs. These zips contain code that is patented and documentation that needs written permission to redistribute. Please remove them from the mirrors to prevent legal problems.

Reproducible: Always

Steps to Reproduce:



Expected Results:  
These zips should be mirror-restricted.
Comment 1 Wulf Krueger (RETIRED) gentoo-dev 2007-04-30 17:00:35 UTC
About the code: http://www.3gpp.org/faq/faq_2005_2.htm#A3.8
(The source code can be used without explicit permission.)

About the doc: This is the restriction in the copyright notice:

"No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media."

I think reproduction != redistribution but I'm not a lawyer.

The docs could simply be removed if we *assume* we're allowed to re-package their archives.

I suggest one dev from media-video contacts upstream (3gppContact@etsi.org; from  http://www.3gpp.org/legal/legal.htm) and asks about this matter without referring to any 3rd party.

Another suggestion on IRC was to bindist restrict the stuff.
Comment 2 Torsten Veller (RETIRED) gentoo-dev 2007-04-30 17:49:50 UTC
(In reply to comment #1)
> About the code: http://www.3gpp.org/faq/faq_2005_2.htm#A3.8
> (The source code can be used without explicit permission.)

It says also:
"This means that you must not provide verbatim copies of source code (or lightly modified copies) without seeking permission from 3GPP."

(But honestly I suck at reading legal stuff.)
Comment 3 Steve Dibb (RETIRED) gentoo-dev 2007-04-30 21:26:16 UTC
So has anyone contacted them?  We should probably move this to -dev ML now..
Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2007-04-30 21:53:23 UTC
Why does this need to go to -dev?

If we cannot legally redistribute it, then we stop redistributing it.  This isn't a -dev or a PR problem.  It is a maintainer problem.  The maintainers need to make modifications to the ebuilds.  At *most* it would be an issue for the trustees, but *definitely* not PR.
Comment 5 Luca Barbato gentoo-dev 2007-05-02 15:56:14 UTC
I'd stop mirroring it...
Comment 6 William L. Thomson Jr. (RETIRED) gentoo-dev 2008-05-18 19:37:21 UTC
Looks like it has been addressed. Closing as fixed.
Comment 7 Torsten Veller (RETIRED) gentoo-dev 2008-05-18 20:25:58 UTC
We still mirror the following files:

# 26104-510.zip
# 26104-610.zip
# 26204-510.zip
# 26204-600.zip

They are not removed from mirrors because they are on the "gentoo-2007.0" whitelist.
Comment 8 Torsten Veller (RETIRED) gentoo-dev 2008-06-04 13:28:23 UTC
(In reply to comment #7)
> # 26104-510.zip
> # 26104-610.zip
> # 26204-510.zip
> # 26204-600.zip
> 
> They are not removed from mirrors because they are on the "gentoo-2007.0"
> whitelist.

Who can remove them? Where are these release whitelists kept?
Comment 9 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2008-06-04 21:12:04 UTC
whitelist updated.
It lives on the master distfiles source, so that we can prevent files from being expired if they were used by old release media.
Comment 10 Ben de Groot (RETIRED) gentoo-dev 2008-12-22 03:18:08 UTC
*** Bug 252140 has been marked as a duplicate of this bug. ***