Re: Compliance with Boost copyright and license guidelines

From: pbristow_at_[hidden]
Date: 2019-08-21 07:32:14

> -----Original Message-----
> From: Boost <boost-bounces_at_[hidden]> On Behalf Of Raffi Enficiaud via
> Boost
> Sent: 20 August 2019 20:35
> To: boost_at_[hidden]
> Cc: Raffi Enficiaud <raffi.enficiaud_at_[hidden]>
> Subject: Re: [boost] Compliance with Boost copyright and license guidelines
> 
> On 19.08.19 17:45, Rene Rivera via Boost wrote:
> > On Mon, Aug 19, 2019 at 2:57 AM Hans Dembinski via Boost <
> > boost_at_[hidden]> wrote:
> >
> >> [snip]
> >
> > It would be fantastic to see a PR for the existing library check
> > Python program <
> >
> https://github.com/boostorg/boost/blob/develop/status/boost_check_library.py
> >.
> > as that would achieve the goal of providing continuous visibility on a
> > per branch and per library basis as you suggest.
> >
> 
> Do you want to run inspect using this python script or do you want a full
> implementation of inspect in python?

Won't requiring Python put off some library authors from applying a run the inspect program to their own code?

(Having the Python program will be valuable for providing an externally visible and usable list). 

My experience is that one needs to work through ones library fixing each issue and re-running the inspect program - and re-running ones examples and tests to make sure one hasn't screwed up 😉

Waiting for the CI system to catch up with that is intolerably slow.

I think that clearing the compliance hurdle only requires some tweaks to the existing inspect program - and some improvements in documentation telling exactly how to run locally, and what to do to be compliant.  

Paul

Paul A. Bristow
Prizet Farmhouse
Kendal, Cumbria 
LA8 8AB           UK