Simple Machines Blogs > SMF Team Blog

Guidelines Update (Customization License)

<< < (4/7) > >>

IchBin™:
The link for comparisons is a great way to quickly decide what you want without having to do a lot of research.
http://en.wikipedia.org/wiki/Comparison_of_free_software_licenses

The whole purpose of the license is to help the community. Abandoned mods is a big problem because nobody can take them over under a closed license.

We require a license be chosen. If one is not chosen, then you must specify that you reserve all rights as stated in the guidelines.
http://wiki.simplemachines.org/smf/Customization_approval_guidelines#Customization_License

Sheda:
Thanks. Think i've found one that sounds good.

Labradoodle-360:

--- Quote from: Sheda on February 06, 2012, 03:33:33 PM ---Thanks. Think i've found one that sounds good.

--- End quote ---
Great to hear! We look forward to reviewing your customization :)

Sheda:
:P
You'll probably be disappointed, though... as the code is already available, it's just stuffed into another mod and now i'm going... uh... stand-alone. Hopefully with all the bugs fixed. Well, we'll see.
By the way, where do you think the license-related text should go?
Should i make a comment right at the beginning above the <? xml, or maybe in the line below that, or below the name of my mod, or maybe below the whole code? No matter where, it seems a little out of place.

Labradoodle-360:
If your modification adds any files, those files should include licensing information at the top of the file, in the file comments. The readme should contain the license, or a link to the license in addition to the description on the mod site.

Furthermore, there is an XML element-tag called <license></license> that is applicable to package-info.xml :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page