[issue9162] License for multiprocessing files

R. David Murray added the comment: Committed in r87225, r87226, and r87227. Thanks, Daniel. -- nosy: +r.david.murray resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker

[issue9162] License for multiprocessing files

Daniel Tavares added the comment: Replaced all entries of "--- see COPYING.txt" with the BSD license. See patch attached. -- keywords: +patch Added file: http://bugs.python.org/file19866/issue9162.patch ___ Python tracker

[issue9162] License for multiprocessing files

Jesse Noller added the comment: We have to add the BSD header and maintain the copyright clause on all of the multiprocessing files. Apologies for the delay -- ___ Python tracker __

[issue9162] License for multiprocessing files

Daniel Tavares added the comment: Hi Jesse, Any word from PSF board regarding this issue? I was hoping to fix it and have it be my 1st contribution to Python. Thanks -- nosy: +dBugSlayer ___ Python tracker _

[issue9162] License for multiprocessing files

Jesse Noller added the comment: On Thu, Sep 16, 2010 at 8:15 AM, Michael Fladischer wrote: > > Michael Fladischer added the comment: > > Is there any timeline on when this will be fixed? It's currently blocking > work on a python-related package for Debian. > I'll ping the PSF board for the

[issue9162] License for multiprocessing files

Michael Fladischer added the comment: Is there any timeline on when this will be fixed? It's currently blocking work on a python-related package for Debian. -- ___ Python tracker __

[issue9162] License for multiprocessing files

Jesse Noller added the comment: Egad No! I gotcha. I'll find out what the deal with the contrib. agreement is. Pretty sure we had to wait on it when we brought it in. -- ___ Python tracker

[issue9162] License for multiprocessing files

Stefan Krah added the comment: Jesse, there's no doubt that you know the original license. :) I should have been more verbose: My BSD comment was intended for public consumption. People often think GPL if they see a reference to COPYING.txt. -- ___

[issue9162] License for multiprocessing files

Jesse Noller added the comment: Hi Stefan - I'm familiar with the license/etc of the original module. This bug isn't urgent; I shot a quick email to the PSF's secretary Pat to confirm we have a contributor agreement however. -- ___ Python tracker

[issue9162] License for multiprocessing files

Stefan Krah added the comment: If I'm not mistaken, the original code was BSD, so in the absence of a contributor agreement one could include the full BSD license in each file. http://pyprocessing.berlios.de/doc/COPYING.html -- ___ Python tracker <

[issue9162] License for multiprocessing files

Stefan Krah added the comment: [Cc: p...@python.org] Jesse Noller wrote: > > Yes; the copyright has to stay; but the license data can leave afaik. If R Oudkerk signed the agreement, replacing 'see COPYING.txt' with 'Licensed to PSF under a Contributor Agreement.' should be fine. Does the PS

[issue9162] License for multiprocessing files

Jesse Noller added the comment: Yes; the copyright has to stay; but the license data can leave afaik. -- ___ Python tracker ___ ___ Py

[issue9162] License for multiprocessing files

Changes by Antoine Pitrou : -- assignee: -> jnoller nosy: +jnoller priority: normal -> high versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ _

[issue9162] License for multiprocessing files

Changes by Stefan Krah : -- nosy: +roudkerk resolution: accepted -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue9162] License for multiprocessing files

Stefan Krah added the comment: Éric, I don't think it's that simple. The author still has the copyright, even if he licensed the files under the contributor agreement. At the very least you have to leave his name and copyright notice. -- nosy: +skrah __

[issue9162] License for multiprocessing files

Éric Araujo added the comment: Third-party code contributed to the stdlib is covered by an agreement that allows PSF to use it under PSF license. Comments in multiprocessing files can just be removed (this happened for argparse some time ago). Thanks for noticing this! -- keywords: +

[issue9162] License for multiprocessing files

Changes by Ask Solem : -- nosy: +asksol ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue9162] License for multiprocessing files

New submission from Michael Fladischer : The files in Lib/multiprocessing (except __init__.py) are referring to their license by point to a nonexistent file called COPYING.txt. This possibly needs clarification as if this file is missing or the license is to be found somewhere else. -