Re: Quality control in open source development

2008-10-13 Thread Steve Holden
Dave wrote: With the open source licenses that allow redistribution of modified code, how do you keep someone unaffiliated with the Python community from creating his or her own version of python, and declaring it to be Python 2.6, or maybe Python 2.7 without any approval of anyone at the

Quality control in open source development

2008-10-08 Thread Dave
With the open source licenses that allow redistribution of modified code, how do you keep someone unaffiliated with the Python community from creating his or her own version of python, and declaring it to be Python 2.6, or maybe Python 2.7 without any approval of anyone at the PSF? Maybe their

Re: Quality control in open source development

2008-10-08 Thread Chris Mellon
On Wed, Oct 8, 2008 at 10:43 AM, Dave [EMAIL PROTECTED] wrote: With the open source licenses that allow redistribution of modified code, how do you keep someone unaffiliated with the Python community from creating his or her own version of python, and declaring it to be Python 2.6, or maybe

Re: Quality control in open source development

2008-10-08 Thread Peter Otten
Dave wrote: With the open source licenses that allow redistribution of modified code, how do you keep someone unaffiliated with the Python community from creating his or her own version of python, and declaring it to be Python 2.6, or maybe Python 2.7 without any approval of anyone at the

Re: Quality control in open source development

2008-10-08 Thread Christian Heimes
Dave wrote: If licensees can redisribute as they like, isn't this a huge problem? Is this dealt with be restricting use of the Python trademarks? Just curious.. From http://www.python.org/psf/summary/ --- The PSF also holds and protects the trademarks behind the Python programming language.

Re: Quality control in open source development

2008-10-08 Thread Samuel A. Falvo II
On Oct 8, 8:43 am, Dave [EMAIL PROTECTED] wrote: With the open source licenses that allow redistribution of modified code, how do you keep someone unaffiliated with the Python community from creating his or her own version of python, and declaring it to be Python 2.6, or maybe Python 2.7

Re: Quality control in open source development

2008-10-08 Thread Terry Reedy
Dave wrote: With the open source licenses that allow redistribution of modified code, how do you keep someone unaffiliated with the Python community from creating his or her own version of python, and declaring it to be Python 2.6, or maybe Python 2.7 without any approval of anyone at the PSF?

Re: Quality control in open source development

2008-10-08 Thread Tim Chase
I think it's pretty self-evident that it's not a huge problem, don't you? Do you see lots of low quality python forks cluttering up the internet? hardly any...the best python fork I found: http://www.woopit.com/albums/Australian-snakes/GreenPythonSnake.jpg though they look more like tweezers

Re: Quality control in open source development

2008-10-08 Thread Matimus
On Oct 8, 8:43 am, Dave [EMAIL PROTECTED] wrote: With the open source licenses that allow redistribution of modified code, how do you keep someone unaffiliated with the Python community from creating his or her own version of python, and declaring it to be Python 2.6, or maybe Python 2.7

Re: Quality control in open source development

2008-10-08 Thread Martin v. Löwis
Matimus wrote: Others have made some pretty sound arguments around trademarks and such, but I'm going to simply argue that Python as a community has its own inertia, and it simply isn't a practical to be concerned about a dubious fork. It simply wouldn't take off. I think this is indeed the