documentation

[Samuel Gaist]

On 6 août 2014, at 11:33, Aaron J. Seigo <aseigo at kde.org> wrote:

> On Wednesday, August 6, 2014 11.11:34 Marco Martin wrote:
>> that would mix 2 licenses in the same file?
> 
> yes; and with some simple processing tools it should be able to tell you the 
> *actual* final license of your application and whether or not there are any 
> licensing problems.
> 
>> maybe something like
>> MyModule 1.0 {
>>  License {
>>    license: GPLv2+
>>    ids: aseigo_gpl, notmart_gpl
>>  }
> 
> indeed, probably needs to communicate the intended license as it can not just 
> be derived from the combined contributions in all cases. so, yes, this kind of 
> syntax will absolutely be needed.
> 
> additional information such as bug tracker location, homepage, etc. should 
> also be allowed in the top-level project metadata. modules would not need to 
> reference that, but having it in the package would be rather nice compared to 
> what we tend to do today. (e.g. put some values there once and then fail to 
> keep it up to date. ;)
> 
> 
> aside: i've also contemplated things like having the ability to register your 
> information in a central location so that you can change your personal 
> information (e.g. email) in one place and have it reflected in *all* projects 
> that use your code. not sure exactly how to do that (where to put such things, 
> etc.) but it would be nice to eventually get there in the future ...
> 
> -- 

Are you thinking of something like svn keyword substitution ?