Changes between Version 11 and Version 12 of DevGuide


Ignore:
Timestamp:
Aug 24, 2014 8:08:55 AM (2 months ago)
Author:
rjollos
Comment:

More license tags.

Legend:

Unmodified
Added
Removed
Modified
  • DevGuide

    v11 v12  
    3434 The use of the XML comment marker as shown is important so that the text does not get rendered to the output. Make sure not to use the alternate form, which is rendered to the output as a hidden comment: `<!-- This is also a comment -->` 
    3535 1. Add a `COPYING` file with the license text in the top-level directory of the project ([browser:/plantumlmacro/trunk/COPYING example]). 
    36  1. Add an appropriate tag to the wiki page: [tag:bsd-license], [tag:apache-license], [tag:gpl-license], [tag:lgpl-license], [tag:mit-license]. Additional tags can be created for additional or more descriptive license types 
     36 1. Add an appropriate tag to the wiki page: [tag:apache-license], [tag:beerware-license], [tag:boost-license], [tag:bsd-license], [tag:creativecommons-license], [tag:gpl-license], [tag:lgpl-license], [tag:mit-license], [tag:unlicense-license]. Additional tags can be created for additional or more descriptive license types 
    3737 
    3838Currently it is not recommended to add license text to static resources (i.e. file in `htdocs`), since doing so will increase the size of the content that is sent to the client. This issue will be addressed in the Trac core when support is added for minimization (trac:#10672).