Oops, didn't attach the entire thread, so see below:<br><br><div class="gmail_quote">On Wed, Apr 8, 2009 at 9:50 AM, Jim Baker <span dir="ltr"><<a href="mailto:jbaker@zyasoft.com">jbaker@zyasoft.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">A question that arose on this thread, which I'm forwarding for context (and we're quite happy about it too!):<div>
<ul><li>What is the scope of a patch that requires a contributor agreement? This particular patch on #1188 simply adds obvious (in retrospect of course) handling on SecurityException so that it's treated in a similar fashion to IOException (possibly a bit more buried), so it seems like a minor patch.<br>
</li><li>Do Google employees, working on company time, automatically get treated as contributors with existing contributor agreements on file with the PSF? If so, are there are other companies that automatically get this treatment?<br>
</li><li>Should we change the workflow for roundup to make this assignment of license clearer (see Tobias's idea in the thread about a click-though agreement).</li></ul></div><div>In these matters, Jython, as a project under the Python Software Foundation, intends to follow the same policy as CPython.</div>
<div><br></div><div>- Jim</div></blockquote></div><span class="Apple-style-span" style="font-family: 'Times New Roman'; font-size: 16px; "><div style="margin-top: 8px; margin-right: 8px; margin-bottom: 8px; margin-left: 8px; font: normal normal normal small/normal arial; ">
<br><div class="gmail_quote"><span style="font-size: large; font-weight: bold; ">Forwarded conversation</span><br>Subject: <b class="gmail_sendername">[Jython-dev] Jython on Google AppEngine!</b><br>------------------------<br>
<br><span class="undefined"><font color="#888">From: <b class="undefined">Alan Kennedy</b> <span dir="ltr"><<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>></span><br>Date: Wed, Apr 8, 2009 at 6:37 AM<br>
To: Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, jython users <<a href="mailto:jython-users@lists.sourceforge.net">jython-users@lists.sourceforge.net</a>><br>
</font><br></span><br>Hi all,<br><br>As you may know, Google announced Java for AppEngine yesterday!<br><br><a href="http://googleappengine.blogspot.com/2009/04/seriously-this-time-new-language-on-app.html" target="_blank">http://googleappengine.blogspot.com/2009/04/seriously-this-time-new-language-on-app.html</a><br>
<br>And they're also supporting all of the various languages that run on<br>the JVM, including jython.<br><br><a href="http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine" target="_blank">http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine</a><br>
<br>They say about jython<br><br>"""<br>- Jython 2.2 works out of the box.<br>- Jython 2.5 requires patches which we'll supply until the changes<br>make it directly into Jython:<br> - jython-r5996-patched-for-appengine.jar is the complete jython<br>
binary library, patched for app engine<br> - jython-r5996-appengine.patch is the patch file that contains the<br>source code for the changes<br>"""<br><br>They provide the patches they used to make 2.5 work<br>
<br><a href="http://google-appengine-java.googlegroups.com/web/jython-r5996-appengine.patch" target="_blank">http://google-appengine-java.googlegroups.com/web/jython-r5996-appengine.patch</a><br><br>I definitely think this is an important patch to consider for the 2.5RC!<br>
<br>It would be nice if Google could say Jython 2.2 works out of the box,<br>and jython 2.5 works out of the box.<br><br>Alan.<br><br>------------------------------------------------------------------------------<br>This SF.net email is sponsored by:<br>
High Quality Requirements in a Collaborative Environment.<br>Download a free trial of Rational Requirements Composer Now!<br><a href="http://p.sf.net/sfu/www-ibm-com" target="_blank">http://p.sf.net/sfu/www-ibm-com</a><br>
_______________________________________________<br>Jython-dev mailing list<br><a href="mailto:Jython-dev@lists.sourceforge.net">Jython-dev@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a><br>
<br>----------<br><span class="undefined"><font color="#888">From: <b class="undefined">Tobias Ivarsson</b> <span dir="ltr"><<a href="mailto:thobes@gmail.com">thobes@gmail.com</a>></span><br>Date: Wed, Apr 8, 2009 at 8:18 AM<br>
To: Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br>Cc: Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>><br></font><br>
</span><br>Most things in that patch look ok. I'd like to do a more thorough analysis of the implications of each change though.<br><br>The catching of SecurityException is fine, but I want to look at the places where they drop the exceptions that they caught in their context, and make sure that silently ignoring the exception is a valid approach. The other changes are few but slightly more controversial.<br>
<br>Are Google willing to sign a contributors agreement and license this patch to us? otherwise someone who has not looked on it yet (i.e. not me), should probably experiment with Jython on GAE and find out what needs to be patched to get Jython to run there.<br>
<font color="#888888"><br>/Tobias</font><div><div></div></div><br>------------------------------------------------------------------------------<br>This SF.net email is sponsored by:<br>High Quality Requirements in a Collaborative Environment.<br>
Download a free trial of Rational Requirements Composer Now!<br><a href="http://p.sf.net/sfu/www-ibm-com" target="_blank">http://p.sf.net/sfu/www-ibm-com</a><br>_______________________________________________<br>Jython-dev mailing list<br>
<a href="mailto:Jython-dev@lists.sourceforge.net">Jython-dev@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a><br>
<br><br>----------<br><span class="undefined"><font color="#888">From: <b class="undefined">Jim Baker</b> <span dir="ltr"><<a href="mailto:jbaker@zyasoft.com">jbaker@zyasoft.com</a>></span><br>Date: Wed, Apr 8, 2009 at 8:33 AM<br>
To: Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br>Cc: Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, jython users <<a href="mailto:jython-users@lists.sourceforge.net">jython-users@lists.sourceforge.net</a>><br>
</font><br></span><br>This is the same patch set requested in <a href="http://bugs.jython.org/issue1188" target="_blank">http://bugs.jython.org/issue1188</a>: "Patch against trunk to handle SecurityExceptions". Now we know the source of the request, and the specific application is very clear: a sandboxed Jython, running under a fairly strict security manager.<br>
<br>The bug is a blocker for the release candidate, so this fix will be part of 2.5.<br><br>We would love to see more work testing the full scope of environments Jython needs to run under, and any resulting bugs.<br><br>- Jim<br>
<br><div class="gmail_quote"><div><div></div></div></div><font color="#888888"><br><br clear="all"><br>-- <br>Jim Baker<br><a href="mailto:jbaker@zyasoft.com" target="_blank">jbaker@zyasoft.com</a><br></font><br>----------<br>
<span class="undefined"><font color="#888">From: <b class="undefined">James Robinson</b> <span dir="ltr"><<a href="mailto:jamesr@google.com">jamesr@google.com</a>></span><br>Date: Wed, Apr 8, 2009 at 8:30 AM<br>To: Tobias Ivarsson <<a href="mailto:thobes@gmail.com">thobes@gmail.com</a>><br>
Cc: Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br></font><br></span><br>
I have a patch up on your issue tracker already, I'll ping it shortly. It's a very small patch and the SecurityExceptions that are caught and ignored are treated the same as I/O exceptions in the vast majority of cases (which they really are).<br>
<font color="#888888"><br>- James</font><div><div></div></div><br>------------------------------------------------------------------------------<br>This SF.net email is sponsored by:<br>High Quality Requirements in a Collaborative Environment.<br>
Download a free trial of Rational Requirements Composer Now!<br><a href="http://p.sf.net/sfu/www-ibm-com" target="_blank">http://p.sf.net/sfu/www-ibm-com</a><br>_______________________________________________<br>Jython-dev mailing list<br>
<a href="mailto:Jython-dev@lists.sourceforge.net">Jython-dev@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a><br>
<br><br>----------<br><span class="undefined"><font color="#888">From: <b class="undefined">Jim Baker</b> <span dir="ltr"><<a href="mailto:jbaker@zyasoft.com">jbaker@zyasoft.com</a>></span><br>Date: Wed, Apr 8, 2009 at 8:36 AM<br>
To: James Robinson <<a href="mailto:jamesr@google.com">jamesr@google.com</a>><br>Cc: Tobias Ivarsson <<a href="mailto:thobes@gmail.com">thobes@gmail.com</a>>, Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br>
</font><br></span><br>Right, this is a very small patch, we haven't required contributor agreements in similar cases. I think we want to consider how to replicate this setup however so we don't inadvertently reverse things.<br>
<font color="#888888"><br>- Jim</font><div><div></div></div><div><div></div></div><br>----------<br><span class="undefined"><font color="#888">From: <b class="undefined">Tobias Ivarsson</b> <span dir="ltr"><<a href="mailto:thobes@gmail.com">thobes@gmail.com</a>></span><br>
Date: Wed, Apr 8, 2009 at 8:40 AM<br>To: Jim Baker <<a href="mailto:jbaker@zyasoft.com">jbaker@zyasoft.com</a>><br>Cc: James Robinson <<a href="mailto:jamesr@google.com">jamesr@google.com</a>>, Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br>
</font><br></span><br><br><br><div class="gmail_quote"><div><br>Could we add a click-through agreement for patch submissions? Patches are usually small enough to not be a big deal, but such a thing would leave us entirely safe.<br>
<br>/Tobias<br></div></div><br><br>----------<br><span class="undefined"><font color="#888">From: <b class="undefined">Frank Wierzbicki</b> <span dir="ltr"><<a href="mailto:fwierzbicki@gmail.com">fwierzbicki@gmail.com</a>></span><br>
Date: Wed, Apr 8, 2009 at 8:44 AM<br>To: Tobias Ivarsson <<a href="mailto:thobes@gmail.com">thobes@gmail.com</a>><br>Cc: Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br>
</font><br></span><br>Google is a member of the PSF, so as long as Google wants this<br>contributed I think it's okay. To be safe we should get an explicit<br>statement, but since the patch is small, this probably isn't strictly<br>
necessary. FWIW this is how my on-the-clock contributions to Jython<br>are protected (Sun is a member of the PSF and allows my<br>contributions).<br><font color="#888888"><br>-Frank<br></font><div><div></div></div><br>----------<br>
<span class="undefined"><font color="#888">From: <b class="undefined">James Robinson</b> <span dir="ltr"><<a href="mailto:jamesr@google.com">jamesr@google.com</a>></span><br>Date: Wed, Apr 8, 2009 at 9:22 AM<br>To: Frank Wierzbicki <<a href="mailto:fwierzbicki@gmail.com">fwierzbicki@gmail.com</a>><br>
Cc: Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br></font><br></span><br>
<br><br><div class="gmail_quote"><div><br>I submitted 1188 and I'm a Google employee working on company time. Let me know if anything further is needed, but we have quite a few contributors to the Python project working here.<br>
<font color="#888888"><br>- James<br> </font></div></div><br><br>------------------------------------------------------------------------------<br>This SF.net email is sponsored by:<br>High Quality Requirements in a Collaborative Environment.<br>
Download a free trial of Rational Requirements Composer Now!<br><a href="http://p.sf.net/sfu/www-ibm-com" target="_blank">http://p.sf.net/sfu/www-ibm-com</a><br>_______________________________________________<br>Jython-dev mailing list<br>
<a href="mailto:Jython-dev@lists.sourceforge.net">Jython-dev@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a><br>
<br><br>----------<br><span class="undefined"><font color="#888">From: <b class="undefined">Frank Wierzbicki</b> <span dir="ltr"><<a href="mailto:fwierzbicki@gmail.com">fwierzbicki@gmail.com</a>></span><br>Date: Wed, Apr 8, 2009 at 9:33 AM<br>
To: Tobias Ivarsson <<a href="mailto:thobes@gmail.com">thobes@gmail.com</a>><br>Cc: Jim Baker <<a href="mailto:jbaker@zyasoft.com">jbaker@zyasoft.com</a>>, Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br>
</font><br></span><br>A click through is a very good idea, I think Jim is going to find out<br>what they do for CPython.<br><font color="#888888"><br>-Frank<br></font><br>----------<br><span class="undefined"><font color="#888">From: <b class="undefined">Frank Wierzbicki</b> <span dir="ltr"><<a href="mailto:fwierzbicki@gmail.com">fwierzbicki@gmail.com</a>></span><br>
Date: Wed, Apr 8, 2009 at 9:32 AM<br>To: James Robinson <<a href="mailto:jamesr@google.com">jamesr@google.com</a>><br>Cc: Jython Developers <<a href="mailto:jython-dev@lists.sourceforge.net">jython-dev@lists.sourceforge.net</a>>, Alan Kennedy <<a href="mailto:jython-dev@xhaus.com">jython-dev@xhaus.com</a>><br>
</font><br></span><br>Excellent, and thanks! 1188 was already slated for inclusion in our<br>upcoming RC, but knowing that it is in support of GAE moves it up to a<br>very high priority.<br><div><div></div></div><br></div>
<br><br clear="all"><br>-- <br>Jim Baker<br><a href="mailto:jbaker@zyasoft.com">jbaker@zyasoft.com</a></div></span><br clear="all"><br>-- <br>Jim Baker<br><a href="mailto:jbaker@zyasoft.com">jbaker@zyasoft.com</a><br>