I hope to present a set of Micro Lightning Talks at the upcoming Mozilla Summit, called “Things Mozilla Developers Need To Know”. Micro Lightning Talks (which I just invented) are one or two sentences – one of instruction and one optional additional sentence of rationale – so a lot of them can fit into a conventional “long” lightning talk. The sentences have a common theme, in this case our development process.
So each Micro Lightning Talk tells people, in one or two sentences, something that it would be good if everyone on the Mozilla project knew, and why – either because it would make their own lives easier, or because it would make someone else’s life easier! Here are some examples:
- When creating new tri-licensed files, you should use the boilerplate linked from the mozilla.org/MPL rather than copy-pasting from an existing file. This is so the formatting is right for automated tools.
- When you change the meaning of a string in a DTD or .properties file, you must also change its name. Otherwise, localizers won’t know to re-localize it.
- You need let the licensing team know before importing third party code into the tree. This is so we can meet our licensing obligations.
If your life would be made easier if everyone in the project knew a very simple Mozilla-development-related thing, then please post your ideas here, in one or two sentences – one of instruction and possibly one of rationale. I will consider all submissions :-)