+1. I think it makes sense to adopt CLA Assistant, and it seems like it will
make our workflow much smoother.
Colin
> On May 3, 2018, at 5:47 PM, Justin Obara wrote:
>
> It’s been a while since the last e-mail discussing potential CLA services for
> Fluid repos.
t; To: Justin Obara <obara.jus...@gmail.com>; Bates, Simon <sba...@ocadu.ca>
> Cc: Fluid Work <fluid-w...@fluidproject.org>; Gill, Avtar <ag...@ocadu.ca>;
> Harnum, Alan <ahar...@ocadu.ca>
> Subject: Re: CLA service for Fluid GitHub repos
>
> Hello,
>
&
cadu.ca>
> Cc: Fluid Work <fluid-w...@fluidproject.org>; Gill, Avtar <ag...@ocadu.ca>;
> Harnum, Alan <ahar...@ocadu.ca>
> Subject: Re: CLA service for Fluid GitHub repos
>
> Hello,
>
> On one hand, cla-assistant introduces a new database for us (MongoDB). On
&g
ion
>
> Avtar
>
>
> -Original Message-
> From: Tirloni, Giovanni
> Sent: Tuesday, April 10, 2018 12:37 PM
> To: Justin Obara <obara.jus...@gmail.com>; Bates, Simon <sba...@ocadu.ca>
> Cc: Fluid Work <fluid-w...@fluidproject.org>; Gill, Avtar <ag...@
ocadu.ca>;
Harnum, Alan <ahar...@ocadu.ca>
Subject: Re: CLA service for Fluid GitHub repos
Hello,
On one hand, cla-assistant introduces a new database for us (MongoDB). On the
other, clahub is in Ruby and we have more people with JS knowledge. New
database vs. New language. It's har
Hello,
On one hand, cla-assistant introduces a new database for us (MongoDB). On the
other, clahub is in Ruby and we have more people with JS knowledge. New
database vs. New language. It's hard to say.
Moving on to ecosystem analysis...
* clahub last commit was in Feb 2017 and they have 14
Something that we may want to take into consideration is the implementation
language/technology (if we end up hosting an instance ourselves).
cla-assistant is JavaScript Node.js with MongoDB for persistence
and clahub is Ruby on Rails
Simon
From: