[yocto] can all of the licensing discussion be centralized in an appendix?

[Tom Zanussi]

On Mon, 2012-03-26 at 14:26 +0000, Rifenbark, Scott M wrote:
> Is BSP licensing different than non-BSP licensing?  If not, then licensing could be combined into a single section.  Can someone answer this for me?
> 

The focus of those sections are different and should probably be in
separate sections - the BSP licensing section of the BSP Guide deals
mainly with the licensing considerations affecting BSP images, while the
rest of the Manual deals with the nuts and bolts of how to deal with
licenses when writing recipes.

> Also, good point on the BSP guide appearing as a chapter in the reference manual.  I have not liked this.  Is there any rational reason to have it this way?
> 

I guess it's there for convenience, but the only reason I can see for
keeping it there other than that is that it's the only chapter that
deals with the kernel.

It would probably make sense would be to remove everything in the the
BSP Guide from the reference manual, except for the kernel section,
which should stay since it's of general interest and not just to people
dealing with BSPs.

Does that make sense?

Tom

> Scott
> 
> -----Original Message-----
> From: yocto-bounces at yoctoproject.org [mailto:yocto-bounces at yoctoproject.org] On Behalf Of Robert P. J. Day
> Sent: Monday, March 26, 2012 5:53 AM
> To: Yocto discussion list
> Subject: [yocto] can all of the licensing discussion be centralized in an appendix?
> 
> 
>   still clawing my way through the ref manual and it seems that
> there's *way* too much coverage of licensing sprinkled throughout.
> most people are not going to care about licensing until the time comes
> to maybe start distributing their BSP.
> 
>   as it stands, in the *development* version of the ref manual,
> section 3.4 is all about licensing, then ch 4 is essentially the BSP
> guide where section 4.2.1 is "License Files" and all of section 4.3 is
> "BSP Licensing Considerations."
> 
>   that just seems like too much licensing info that breaks up the flow
> of the reference manual.  can all of that be moved to one location and
> referenced from there?
> 
> rday
> 
> p.s.  i'm also not keen on an entire chapter of the ref manual being
> nothing more than an include of the BSP guide.  if you've got a
> perfectly respectable BSP guide, there's no point having it magically
> appear as part of another manual.  but that's just my $0.02.
>