Preparations for 2.0.0 release.

git-svn-id: svn://svn.code.sf.net/p/chibios/svn/trunk@1951 35acf78f-673a-0410-8e92-d51de3d6d3f4

1 files changed, 43 insertions, 2 deletions

diff --git a/docs/src/credits.dox b/docs/src/credits.dox
index 28343dc14..bb65a625e 100644
--- a/docs/src/credits.dox
+++ b/docs/src/credits.dox
@@ -18,9 +18,50 @@
 */

 

 /**

- * @page credits Credits

- * @brief Contributors

+ * @page credits Copyright and Credits

+ * @brief Copyright and Credits

  *

+ * <h2>Copyright Statement</h2>

+@verbatim

+    ChibiOS/RT - Copyright (C) 2006,2007,2008,2009,2010 Giovanni Di Sirio.

+@endverbatim

+ *

+ * <h2>Contributions and Copyright Assignment</h2>

+ * Contributing to the ChibiOS/RT project requires assigning the copyright

+ * on the contributed code to myself (Giovanni Di Sirio).<br>

+ * There are several reasons for this requirement:

+ * - ChibiOS/RT will probably become also a commercial product and I could not

+ *   re-license the code without ownership. Note that the commercial product

+ *   would not be a different or better product, just the same GPL product

+ *   made available, on request, under a different license. The code will

+ *   always be available to you under the current licensing terms.

+ * - I need ownership when changing the licensing terms and this happens

+ *   each time the project goes from development/unstable to stable and

+ *   back because the addition/removal of the GPL linking exception.

+ * - It will be easier for the project adopters to have a single ownership

+ *   point in case of licensing issues (both GPL or commercial).

+ * - Losing the ownership on the code could preclude me the opportunity to

+ *   make this project a full time job as I hope.

+ * - I definitely don't want to have to sort out copyright related issues

+ *   in the future so better be clear than sorry.

+ * .

+ * Note that contributions will always be welcome even without such copyright

+ * assignment, the difference is that the contributed code would not be

+ * merged into the main line, it will still made available as contributed

+ * code with the contributor(s) copyright notice intact.<br>

+ * Submissions of code with copyright notice should only happen through

+ * email, please do not commit code with copyright notices directly on

+ * the repository.<br>

+ * When submitting code please <b>state clearly your intention to keep the

+ * copyright</b> on your work by adding your own copyright notice within the

+ * source code and by clearly mentioning your intentions in the message. Code

+ * contributed without copyright notice will be considered donated.<br>

+ * If in doubt with licensing issues please don't hesitate to contact me

+ * in order to sort out any problem you may have.<br>

+ * Of course the copyright assignment does not mean you would not be

+ * recognized for your hard work, see the following section.

+ *

+ * <h2>Credits</h2>

  * I want to thank to all the people that directly or indirectly contributed

  * to the project, I beg pardon if someone is missing:

  * - <b>Adamo Reggiani</b>, working on the Fujitsu port.