Re: [boost] [Boost Library Incubator] Unable to submit library

Subject: Re: [boost] [Boost Library Incubator] Unable to submit library
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-07-22 02:54:32

On Mon, Jul 21, 2014 at 11:50 PM, Robert Ramey <ramey_at_[hidden]> wrote:
> Andrey Semashev-2 wrote
>> On Monday 21 July 2014 08:16:10 Robert Ramey wrote:
>>> Paul A. Bristow-2 wrote
>>
>> Keeping auto-generated files in git is not a good idea. Syncing is not as
>> simple as it may seem, it also spams history and increases the repo size.
>> There was a discussion about this earlier, and I think the consensus was
>> unanimous.
>
> lol - maybe it was unanimous among those who see it as an issue.
>
> But remember that the incubator is not boost.

I don't quite agree.

> Each developer can use the
> method he wants.  The only requirement set by the indicator is that there
> be browsable html documentation.  How that is produced and maintained
> is totally up the library developer/submitter.  The incubator only points
> to the finished product.

I agree that some degree of freedom is needed, and in fact I'm
typically in favor of less restricting approaches. However, libraries
in Blincubator are targeted for inclusion in Boost and therefore
should respect requirements and preferences imposed by Boost. For
example, I expect all libraries in Blincubator to be licensed under
BSL. The libraries should follow directory layout and symbol naming
guidelines set by Boost. The choice of documentation format and build
system is probably less strict but obviously QuickBook and Boost.Build
should be the first candidates. The same goes for preference of not
storing auto-generated files in the library repo.