@Dave
Yup.
I see your note on the -set.xml file
Thanks for pointing that out.
I already added you to the Repo summary author's list.
About "Best Practices". I really wonder too.
I guess Ed. d'Auvergne can enlighten us a bit here. He seems well versed in these topics.
My suggestions are: Keep a COPYING or LICENSE file with the unedited version of the LICENSE you are applying to your work: Be GPL, CC, or whatever. [Hopefully it is still free software, as in free speech --allowing copying and redistribution]
My second suggestion is keep an AUTHORS.txt file with all mentions (authors, and honorific mentions are OK -testers? acknowledgements, etc?)
and maybe add a COPYRIGHT file (or indicate this on AUTHORS txt) indicating who is the "copyright" owner(s) of the work.
In the devel list last 2 weeks an extensive argument about headers for individual files were mentioned.
Quite complicated, and extreme in my opinion, given that the license usually covers the whole work and not part of it.
It usually can be applied to all content of the repository (not the submodules, if any).
More complicated setups may be done editing a LICENSE file indicating what licenses cover particular files or so, and so.
The important thing I believe is make safe clarity of the author's intent with this license file, I believe.
Also, I preffer (1000times) GPL content. I use GPL content whenever possible. even if I am no-one to modify it myself. It's kind of a matter of principle now.
Ed. may bring you also the point that adding a license file is not necessarily fully legally binding. That a registration with the patent offices or whatever may be required. He may be right. Still, in my opinion, if real trouble were to arise, a git repository may be a great tool to demostrate innoncence --and even true originality/ownership. Keep in mind that in git everything is time-stamped. And the copy brings those time stamps too -- of, as an example, when did you make a commit. And who made the commit, and the exact content of the diff, to the semicolon at the end of lines precision. You can prove when/why/how/who a change was made with very little doubt left. A zip file on a mediafire link is useless for such purpose. So I would say, a git repository is a good practice as well.
Those are just loose thoughts,
Have fun developing
(and thanks for your hard works making nice thrustflames last weeks!)
Best,
IH-COL
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it? Probably not, because if they don’t recognise their freedoms, they’ll let their freedoms fall