Re: Python Software Foundation - Jython CLA

Jeff Allen <[email protected]>
Newsgroups gmane.comp.lang.jython.devel
Message-ID <[email protected]>
Hi Ewa,

On 18/06/2018 16:26, Ewa Jodlowska wrote:
> Hi Jeff -
>
> On Sun, Jun 17, 2018 at 9:30 AM, Jeff Allen <[email protected] 
> <mailto:[email protected]>> wrote:
>
>     Jim, Ewa, Ernest, hi.
>
>     (Also, congratulation to Ernest.)
>
>     " ... there is currently no way to designate whether the CLA is
>     for Jython."
>
>     There is equally no way to designate that the CLA is for CPython.
>     And no way to designate that the CLA is for some other PSF
>     artefact that is not, itself, CPython or Jython.
>
>     I think this is deliberate, and a good thing, so my conclusion is
>     opposite to that in the thread below.
>
>     We're not simply re-using the design of a PSF form. Contributors
>     to Jython give their work to the PSF, and the PSF lets  everyone
>     else use it. (https://hg.python.org/jython/file/tip/LICENSE.txt
>     <https://hg.python.org/jython/file/tip/LICENSE.txt>). If we then
>     want to contribute elsewhere in the PSF, as I have in a small way,
>     there is no additional barrier.
>
>     It would be convenient if, whatever one contributed to the PSF,
>     submitting a CLA didn't involve signing up to bugs.python.org
>     <http://bugs.python.org> when all other interaction is via GitHub.
>     But as that's easily done, and there's a comprehensible reason, I
>     don't worry too much it will put people off. When you make this
>     even simpler, could you make sure that it still works for Jython?
>
> Can you clarify what the tracking process is for Jython's CLAs? Ernest 
> and I are not familiar with this process or any context related to it.
>
>     We do need to get rid of the misleading Jython-specific form,
>     though. I signed that one too, in the day, before being corrected.
>     I assume there was a good reason for it at one time, but I can
>     only speculate what it was.
>
>
> Currently, the only Jython "form" I found online is 
> https://www.python.org/psf/contrib/contrib-form-jython/ 
> <https://www.python.org/psf/contrib/contrib-form-jython/>. Do you know 
> of any others?
>
> Thanks,
>
> Ewa
>

I believe I have found (belatedly stumbled upon) the definitive PSF 
answer to this question. In this page there are three links to PSF 
contributor forms: https://www.python.org/psf/contrib/

The first link is to the one I think we want people to use for all PSF 
projects: https://www.python.org/psf/contrib/contrib-form/

The second and third, the top page makes clear, are to cover "past 
contributions":
https://www.python.org/psf/contrib/contrib-form-python/   (to "Python")
https://www.python.org/psf/contrib/contrib-form-jython/   (to "Jython")

This reinforces what we already concluded, and what Frank remembered of 
the history, that contributions to Jython are contributions to the PSF, 
and the one form of agreement should normally govern them all equally.

The problem arises because these "past contribution" forms may be 
mistaken for the real thing when you land there directly (which you will 
if you think you want a CLA for Jython). Maybe these "past contribution" 
forms are still necessary for some reason. The solution is a clear 
statement on them that directs visitors to use the central PSF 
Contributor Form, unless they've been specifically asked to use the 
retrospective version e.g. by PSF staff.

If we think we will never need them again, they're no more than an 
attractive nuisance and we know what to do.

Is there somewhere I can lodge a change request about this? Is it 
bugs.python.org?

Jeff Allen

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.