@@ -258,6 +258,41 @@ Our code is organized as follows:
258258 - If code has a complex algorithm or non-obvious implementation, prefer to use ` ///<remarks> `
259259- Document new features and changes in the Docs repository of the BrighterCommand organization.
260260
261+ ### Licensing
262+ - We add a license comment to every src file, at the top of the file.
263+ - We use the MIT licence.
264+ - You should add your name and the year, if it is a new file.
265+ - You should put the license comment in a ` # region Licence ` block
266+ - An LLM should use the name and year of the contributor instructing the LLM
267+ - As an example
268+
269+ `
270+ #region Licence
271+
272+ /* The MIT License (MIT)
273+ Copyright © [ Year] [ Your Name] [ Your Contact Email]
274+
275+ Permission is hereby granted, free of charge, to any person obtaining a copy
276+ of this software and associated documentation files (the “Software”), to deal
277+ in the Software without restriction, including without limitation the rights
278+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
279+ copies of the Software, and to permit persons to whom the Software is
280+ furnished to do so, subject to the following conditions:
281+
282+ The above copyright notice and this permission notice shall be included in
283+ all copies or substantial portions of the Software.
284+
285+ THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
286+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
287+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
288+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
289+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
290+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
291+ THE SOFTWARE. * /
292+
293+ #endregion
294+ `
295+
261296## Dependency Management
262297
263298- Use Directory.Packages.props for central package management.
0 commit comments