I just submitted a tiny PR for thredds and noticed that they are now using CLA assistant <https://cla-assistant.io/> PR checks to gather contributor agreements. We should consider this.
- It is convenient and quick and might reduce the barrier for entry.
- Does OSGeo have a policy on contributor agreement collection via third parties?
- Is there a mechanism for whitelisting current contributors?
I would be happy to switch if someone can set it up, I like that it can do a check.
···
On 11 April 2018 at 17:57, Ben Caradoc-Davies <ben@anonymised.com> wrote:
I just submitted a tiny PR for thredds and noticed that they are now using CLA assistant <https://cla-assistant.io/> PR checks to gather contributor agreements. We should consider this.
It is convenient and quick and might reduce the barrier for entry.
Does OSGeo have a policy on contributor agreement collection via third parties?
Is there a mechanism for whitelisting current contributors?
I just submitted a tiny PR for thredds and noticed that they are now using
CLA assistant <https://cla-assistant.io/> PR checks to gather contributor
agreements. We should consider this.
- It is convenient and quick and might reduce the barrier for entry.
I've never heard of it but just tried to sign up. It wants write access
to my public repos and public + secret gists. Not something I'd consider
using myself.
AFAIK, the CLA assistant needs to know your repos. It checks if you have
a valid CLA to support your contributions for that repo. So, behind the
scenes it has to be able to map your repos and the CLAs you signed.
I had the same problem when I signed. But since the software itself is
open source, I decided to grant permissions to the CLA Assistant.
But you raised a good point.
Regards,
Jorge Gustavo
On 12-04-2018 19:40, Kristian Thy wrote:
On Thu, Apr 12, Ben Caradoc-Davies wrote:
I just submitted a tiny PR for thredds and noticed that they are now using
CLA assistant <https://cla-assistant.io/> PR checks to gather contributor
agreements. We should consider this.
- It is convenient and quick and might reduce the barrier for entry.
I've never heard of it but just tried to sign up. It wants write access
to my public repos and public + secret gists. Not something I'd consider
using myself.
/Kristian
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Geomaster, Lda
Avenida Barros e Soares, 423
Nogueira
4715-214 Braga
NIF 510906109
Tel 253 680 223
Tm 910 333 888
Email jgr@anonymised.com
Site geomaster.pt
GPS 41.53322,-8.41929
Now I've had a second look at the website - it seems those permissions
are required for the project using CLA Assistant, not the contributors.
So it's probably correct that it lowers the barrier of participation for
hangarounds like me but on the other hand you'd need to give SAP
write access to the geoserver repos to use it.
(And read access to secret gists. Why, SAP?)
/Kristian
On Thu, Apr 12, Jorge Gustavo Rocha wrote:
Hi Kristian,
AFAIK, the CLA assistant needs to know your repos. It checks if you have
a valid CLA to support your contributions for that repo. So, behind the
scenes it has to be able to map your repos and the CLAs you signed.
I had the same problem when I signed. But since the software itself is
open source, I decided to grant permissions to the CLA Assistant.
But you raised a good point.
Regards,
Jorge Gustavo
On 12-04-2018 19:40, Kristian Thy wrote:
> On Thu, Apr 12, Ben Caradoc-Davies wrote:
>> I just submitted a tiny PR for thredds and noticed that they are now using
>> CLA assistant <https://cla-assistant.io/> PR checks to gather contributor
>> agreements. We should consider this.
>>
>> - It is convenient and quick and might reduce the barrier for entry.
>
> I've never heard of it but just tried to sign up. It wants write access
> to my public repos and public + secret gists. Not something I'd consider
> using myself.
>
> /Kristian
Now I’ve had a second look at the website - it seems those permissions
are required for the project using CLA Assistant, not the contributors.
So it’s probably correct that it lowers the barrier of participation for
hangarounds like me but on the other hand you’d need to give SAP
write access to the geoserver repos to use it.
(And read access to secret gists. Why, SAP?)
/Kristian
On Thu, Apr 12, Jorge Gustavo Rocha wrote:
Hi Kristian,
AFAIK, the CLA assistant needs to know your repos. It checks if you have
a valid CLA to support your contributions for that repo. So, behind the
scenes it has to be able to map your repos and the CLAs you signed.
I had the same problem when I signed. But since the software itself is
open source, I decided to grant permissions to the CLA Assistant.
But you raised a good point.
Regards,
Jorge Gustavo
On 12-04-2018 19:40, Kristian Thy wrote:
On Thu, Apr 12, Ben Caradoc-Davies wrote:
I just submitted a tiny PR for thredds and noticed that they are now using
CLA assistant <https://cla-assistant.io/> PR checks to gather contributor
agreements. We should consider this.
It is convenient and quick and might reduce the barrier for entry.
I’ve never heard of it but just tried to sign up. It wants write access
to my public repos and public + secret gists. Not something I’d consider
using myself.
I just submitted a tiny PR for thredds and noticed that they are now using
CLA assistant <https://cla-assistant.io/> PR checks to gather contributor
agreements. We should consider this.
- It is convenient and quick and might reduce the barrier for entry.
I've never heard of it but just tried to sign up. It wants write access
to my public repos and public + secret gists. Not something I'd consider
using myself.
When submitting a PR, to sign the CLA I only had to grant read-only OAuth access to my email address.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <https://transient.nz/>
New Zealand