[Clfs-dev] Travis-CI?

[William Harrington]

On 2019-04-23 08:39, Andrew Bradford wrote:
> Hi William,
> 
> On Mon, Apr 22, 2019 at 6:12 PM William Harrington
> <kb0iic at berzerkula.org> wrote:
>> On Mon, 22 Apr 2019 08:01:44 -0400
>> Andrew Bradford <bradfa at gmail.com> wrote:
> <snip>
>> > The core value that I see in something like Travis CI is to ensure
>> > that if someone finds an issue with the book and wants to contribute a
>> > change that we make it as easy as possible for them to do so.  With
>> > Travis checking every pull request to ensure that the book builds
>> > correctly, it makes it easier (in my opinion) for new contributors to
>> > get their pull request merged.  The feedback loop with Travis isn't
>> > instant, but it's decently fast and reasonably friction free for the
>> > contributor as no maintainer of the book needs to be bothered by
>> > looking at broken pull requests.  The contributor can easily see that
>> > if their change broke the book that it probably won't be merged.
>> >
>> > Travis can be used for many things, my intention was to use it in its
>> > most simple format of checking pull requests so as to help
>> > contributors to more easily get their changes integrated into the book
>> > by providing quicker feedback when their edits break the book.
>> Okay, I get a better view of it then. We can give it a whirl see how 
>> things go. This isn't one of them things where
>> if it isn't broke, don't fix it.
> 
> OK, thanks.  Is it OK with you if I add Travis access back to the
> Embedded book in GitHub and reenable checking of merge requests?
> Thanks,
> Andrew

Hello Andrew,

I don't make the decisions. I'm usually if it works let it go. That way 
is becoming more of a burden.
You seem to be the more active contributor with the embedded book. Do as 
you will.

Sincerely,
William Harrington

-- 
You feel a whole lot more like you do now than you did when  you used 
to.