Hi, I am looking at empty ideas page at: https://wiki.python.org/moin/SummerOfCode/2014/python-core and I'd like to propose idea for GSoC students. https://bitbucket.org/techtonik/python-stdlib This needs to be extended and integrated into stdlib development process. The idea is to get a focused development gathered around modules. This includes creating a pydotorg pages (Django) that will list feeds of activity per module, including: Iteration one: - bugs - patches - discussions - votes - commits - hiscore based on all the above (shamelessly stolen from https://twistedmatrix.com/highscores/) Iteration two: - sprints info (short term activities and coordination in real-time) - past - planned - current - bug research and development (long term with visualization and reports) - subscribe to the research team - publish research materials - get scores and achievements This is just for the start. -- anatoly t.
On 28 February 2014 07:32, anatoly techtonik <techtonik@gmail.com> wrote:
https://bitbucket.org/techtonik/python-stdlib
This needs to be extended and integrated into stdlib development process.
Wow Anatoly. Are you finally going to sign the PSF Contributor Agreement? Tim Delaney
On Fri, Feb 28, 2014 at 8:00 AM, Tim Delaney <timothy.c.delaney@gmail.com> wrote:
Wow Anatoly. Are you finally going to sign the PSF Contributor Agreement?
It's a lot easier to do it now than it was when I first looked into it. Can't remember what it took then, but I remember being put off by a combination of legalese verbiage and administrative fiddliness. The wads of legalese are still there (I basically just trusted that the PSF isn't trying to con me into giving up vital organs for science), but it's now a matter of proving identity and signing digitally. Fairly convenient. ChrisA
On Fri, Feb 28, 2014 at 12:00 AM, Tim Delaney <timothy.c.delaney@gmail.com> wrote:
On 28 February 2014 07:32, anatoly techtonik <techtonik@gmail.com> wrote:
https://bitbucket.org/techtonik/python-stdlib
This needs to be extended and integrated into stdlib development process.
Wow Anatoly. Are you finally going to sign the PSF Contributor Agreement?
This idea is for GSoC students. python-stdlib is free from the license burden with UNLICENSE, so you better ask PSF why they don't accept it. Offtopic, but since it is about GSoC, and there are people studying copyright and open source, I'll explain my position just in case somebody will be able to help with that in the future. I don't sign CLA, because: 1. I don't want to release my code under restrictive PSF license https://tldrlegal.com/license/python-license-2.0 2. PSF doesn't comply with terms of Apache 2.0 license (include license) which is probably chosen by at least one contributor for CLA https://tldrlegal.com/license/apache-license-2.0-(apache-2.0) 3. I don't want to give PSF exclusive rights for all code and documentation to be released under any other "open source" license. PSF may be bought by some corporation and they will have the right to impose their own "open source license text" on it. (yes, I don't trust people at all). 4. If I sign, I will be less motivated to open the Python docs under CC-BY license with examples that can be copy-pasted without requiring PSF license in your project. Right now using logging examples without it is illegal. 5. Everything is owned by PSF is wrong. Python is a community project, and core code should be shared as open as possible (with credits where due). Public domain with optional crediting and patent grant is ideal. Trademarks are not affected. Nobody is forced and can do what they want. And current licensing uncertainty no good for collaboration. 6. I want people to have free entry for participating in open source projects, meaning that the patent grant and agreement to release their contribution under the open source license that project uses, should work by default without any CLAs.
On 02/27/2014 01:40 PM, anatoly techtonik wrote:
On Fri, Feb 28, 2014 at 12:00 AM, Tim Delaney <timothy.c.delaney@gmail.com> wrote:
On 28 February 2014 07:32, anatoly techtonik <techtonik@gmail.com> wrote:
https://bitbucket.org/techtonik/python-stdlib
This needs to be extended and integrated into stdlib development process.
Wow Anatoly. Are you finally going to sign the PSF Contributor Agreement?
This idea is for GSoC students. python-stdlib is free from the license burden with UNLICENSE, so you better ask PSF why they don't accept it.
Your reasons are irrelevant. If you don't sign the CLA, no code you start will find its way to Python. -- ~Ethan~
On 28 Feb 2014 08:47, "Ethan Furman" <ethan@stoneleaf.us> wrote:
On 02/27/2014 01:40 PM, anatoly techtonik wrote:
On Fri, Feb 28, 2014 at 12:00 AM, Tim Delaney <timothy.c.delaney@gmail.com> wrote:
On 28 February 2014 07:32, anatoly techtonik <techtonik@gmail.com>
https://bitbucket.org/techtonik/python-stdlib
This needs to be extended and integrated into stdlib development
wrote: process.
Wow Anatoly. Are you finally going to sign the PSF Contributor
Agreement?
This idea is for GSoC students. python-stdlib is free from the license burden with UNLICENSE, so you better ask PSF why they don't accept it.
Your reasons are irrelevant. If you don't sign the CLA, no code you start will find its way to Python.
But Ethan, you don't understand. Everyone else's interests and obligations are irrelevant, the world is just supposed to conform to Anatoly's every whim. Anatoly: please stop posting ideas inspired solely by your inability to take anyone else's interests into account, even after a PSF director has taken the time to sit down with you at the PyCon US sprints and attempt to explain the legal complexities that led to the introduction of the contributor licensing agreement. Moderators: please don't let such posts out of the moderation queue, they're a complete waste of everyone's time. The core development team has already burned years on Anatoly's antics with nothing much to show for it - it is his decision to opt out of contributing, yet he obstinately refuses to accept the consequence that doing so renders his opinion largely irrelevant to many of us. Regards, Nick.
-- ~Ethan~
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
Nick Coghlan writes:
Moderators: please don't let such posts out of the moderation queue, they're a complete waste of everyone's time.
+1 They're 50% FUD, and 50% just plain wrong. More to the point, they're 100% off-topic once they go beyond "I won't sign the CA so my code is not useful to further the purposes of python-ideas." (I'm happy to discuss both Anatoly's statements and my own -- philosophical BS is a hobby of mine -- but *not on this list*. Reply-to set to <stephen@xemacs.org>, please observe.)
Am 27.02.2014 22:40, schrieb anatoly techtonik:
On Fri, Feb 28, 2014 at 12:00 AM, Tim Delaney <timothy.c.delaney@gmail.com> wrote:
On 28 February 2014 07:32, anatoly techtonik <techtonik@gmail.com> wrote:
https://bitbucket.org/techtonik/python-stdlib
This needs to be extended and integrated into stdlib development process.
Wow Anatoly. Are you finally going to sign the PSF Contributor Agreement?
This idea is for GSoC students. python-stdlib is free from the license burden with UNLICENSE, so you better ask PSF why they don't accept it.
Offtopic, but since it is about GSoC, and there are people studying copyright and open source, I'll explain my position just in case somebody will be able to help with that in the future.
I don't sign CLA, because:
1. I don't want to release my code under restrictive PSF license https://tldrlegal.com/license/python-license-2.0
You don't, the PSF does.
2. PSF doesn't comply with terms of Apache 2.0 license (include license) which is probably chosen by at least one contributor for CLA https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)
This is not true.
3. I don't want to give PSF exclusive rights for all code and documentation to be released under any other "open source" license. PSF may be bought by some corporation and they will have the right to impose their own "open source license text" on it. (yes, I don't trust people at all).
This is a valid concern, however for code with your "UNLICENSE" any corporation can do anything with it right now anyway.
4. If I sign, I will be less motivated to open the Python docs under CC-BY license with examples that can be copy-pasted without requiring PSF license in your project. Right now using logging examples without it is illegal.
This *might* be a valid concern (IANAL), but it's one I've never heard from you so far. Why don't you start discussing this one explicitly?
5. Everything is owned by PSF is wrong.
Well, the PSF owns a lot of money, and I don't think money is wrong. Jokes aside, the PSF explicitly *doesn't* own your copyright due to the CLA.
Python is a community project, and core code should be shared as open as possible (with credits where due). Public domain with optional crediting and patent grant is ideal. Trademarks are not affected. Nobody is forced and can do what they want. And current licensing uncertainty no good for collaboration. 6. I want people to have free entry for participating in open source projects, meaning that the patent grant and agreement to release their contribution under the open source license that project uses, should work by default without any CLAs.
These are again valid concerns from your side, but you will have to understand that the PSF does not have the freedom to abolish the CLA. Georg
On 2/27/2014 3:32 PM, anatoly techtonik wrote:
Hi,
I am looking at empty ideas page at: https://wiki.python.org/moin/SummerOfCode/2014/python-core
Please stop posting disinformation. It is not empty. It has listings by the people who have volunteered to be mentors (2 groups of 2). Adding projects without a mentor available is worse than useless. Besides which, your process that no one besides you wants is out of bounds for GSOC students. -- Terry Jan Reedy
participants (8)
-
anatoly techtonik -
Chris Angelico -
Ethan Furman -
Georg Brandl -
Nick Coghlan -
Stephen J. Turnbull -
Terry Reedy -
Tim Delaney