[prev in list] [next in list] [prev in thread] [next in thread]
List: python-dev
Subject: Re: [Python-Dev] PEP 545: Python Documentation Translations
From: Brett Cannon <brett () python ! org>
Date: 2017-04-04 16:29:55
Message-ID: CAP1=2W61toxtB1oUMpeV6czAXaoyskMj--6Qkx=fAq6kB+b8Ag () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, 4 Apr 2017 at 04:58 Julien Palard <julien@palard.fr> wrote:
> Hi, little follow-up about this PEP.
>
>
> Please check with the PSF that this is what we really want. In the past
> the suggestion has been to **not** use the PSF license with all of its
> historical baggage but instead use something like Apache. But since IANAL
> we really should ask the PSF what the best license for new code is.
>
>
> I checked with the PSF and after a few emails with VanL (thanks), we
> concluded that we need a "Documentation Contribution Agreement" (they're
> working on writing it), then we'll *just* have to ensure contributors are
> understanding and agreeing with it.
>
> I think we should setup a bot like "The Knights Who Say Ni" from PEP 512
> [1]_ or The Knight Who Say Ni itself, configured for the "DCLA" what do you
> think?
>
It's definitely possible. The bot is designed to be easily customizable
from a server hosting, PR hosting, and CLA hosting perspective. Question is
whether the DCLA will be managed the same as the CLA, i.e. a flag set on
bugs.python.org?
-Brett
> The bot will *only* cover contributions from actual github pull requests,
> other means of contributions like transifex can be enforced by other means,
> namely:
>
> - We can write a welcome text like "By contributing to this transifex
> project I accept the Documentation Contribution Licence Agreement…".
> - We can ask contributors to specifically write they accept the licence
> agreement along witht the translation independently of the way they send us
> translations. (It even work for paper…).
>
> .. [1] PEP 512 -- Migrating from hg.python.org to GitHub
> (https://www.python.org/dev/peps/pep-0512/#a-bot-to-enforce-cla-signing
> )
>
> --
> Julien Palard
> https://mdk.fr
>
>
[Attachment #5 (text/html)]
<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Tue, 4 Apr 2017 at \
04:58 Julien Palard <<a href="mailto:julien@palard.fr">julien@palard.fr</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_msg">Hi, little \
follow-up about this PEP.<br class="gmail_msg"></div><div class="gmail_msg"><br \
class="gmail_msg"></div><div class="m_-4950134709528752358protonmail_signature_block \
gmail_msg"><div class="m_-4950134709528752358protonmail_signature_block-proton \
m_-4950134709528752358protonmail_signature_block-empty gmail_msg"><br \
class="gmail_msg"></div></div><blockquote type="cite" \
class="m_-4950134709528752358protonmail_quote gmail_msg"><div dir="ltr" \
class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg">Please \
check with the PSF that this is what we really want. In the past the suggestion has \
been to **not** use the PSF license with all of its historical baggage but instead \
use something like Apache. But since IANAL we really should ask the PSF what the best \
license for new code is. <br class="gmail_msg"></div></div></div></blockquote><div \
class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I checked with \
the PSF and after a few emails with VanL (thanks), we concluded that we need a \
"D<span class="m_-4950134709528752358highlight gmail_msg" \
style="background-color:rgb(255,255,255)"><span class="m_-4950134709528752358colour \
gmail_msg" style="color:rgb(85,85,85)"><span class="m_-4950134709528752358font \
gmail_msg" style="font-family:Arial,"Helvetica \
Neue",Helvetica,sans-serif"><span class="m_-4950134709528752358size gmail_msg" \
style="font-size:14px">ocumentation Contribution Agreement" (they're working \
on writing it), then we'll *just* have to ensure contributors are understanding \
and agreeing with it.</span></span></span></span><br class="gmail_msg"></div><div \
class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I think we \
should setup a bot like "The Knights Who Say Ni" from PEP 512 [1]_ or The \
Knight Who Say Ni itself, configured for the "DCLA" what do you \
think?</div></blockquote><div><br></div><div>It's definitely possible. The bot is \
designed to be easily customizable from a server hosting, PR hosting, and CLA hosting \
perspective. Question is whether the DCLA will be managed the same as the CLA, i.e. a \
flag set on <a href="http://bugs.python.org">bugs.python.org</a>?</div><div><br></div><div>-Brett</div><div> \
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="gmail_msg"> The bot will *only* cover \
contributions from actual github pull requests, other means of contributions like \
transifex can be enforced by other means, namely:<br class="gmail_msg"></div><div \
class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"> - We can write \
a welcome text like "By contributing to this transifex project I accept the \
Documentation Contribution Licence Agreement…".<br \
class="gmail_msg"></div><div class="gmail_msg"> - We can ask contributors to \
specifically write they accept the licence agreement along witht the translation \
independently of the way they send us translations. (It even work for paper…).<br \
class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"></div><div \
class="gmail_msg">.. [1] PEP 512 -- Migrating from <a href="http://hg.python.org" \
class="gmail_msg" target="_blank">hg.python.org</a> to GitHub<br \
class="gmail_msg"></div><div class="gmail_msg"> (<a \
href="https://www.python.org/dev/peps/pep-0512/#a-bot-to-enforce-cla-signing" \
class="gmail_msg" target="_blank">https://www.python.org/dev/peps/pep-0512/#a-bot-to-enforce-cla-signing</a>)<br \
class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"></div><div \
class="m_-4950134709528752358protonmail_signature_block gmail_msg"><div \
class="m_-4950134709528752358protonmail_signature_block-user gmail_msg"><div \
class="gmail_msg">-- <br class="gmail_msg"></div><div class="gmail_msg">Julien \
Palard<br class="gmail_msg"></div><div class="gmail_msg"><a href="https://mdk.fr" \
class="gmail_msg" target="_blank">https://mdk.fr</a><br \
class="gmail_msg"></div></div></div><div class="gmail_msg"><br \
class="gmail_msg"></div></blockquote></div></div>
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/python-dev-marcsub-zyf4%40marc.info
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic