X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fdocumentation;h=4ed2e6a6639195f250598ce651e8d27fecf7e316;hb=c55ce9b7f88c0ac1d7e163455822dbac93805062;hp=f67fce7d9e4d4274655b1fbe3209b69ce74cf58e;hpb=983d92c25f124849761b0ece45f5fc6d1f60e4b1;p=mono.git
diff --git a/web/documentation b/web/documentation
index f67fce7d9e4..4ed2e6a6639 100644
--- a/web/documentation
+++ b/web/documentation
@@ -1,46 +1,62 @@
* Documentation
- A project like Mono will require a lot of documentation to be
- written. Although most of the concepts from Microsoft.NET can
- be applied to the Mono platform once finished, we do need to
- have a complete set of free documentation written for it.
+ Although most of the concepts from Microsoft.NET can
+ be applied to the completed Mono platform, we do need to
+ have a complete set of free documentation written specifically
+ for Mono.
- The documentation license we have chosen is the FSF FDL which
- is the standard for most documents on the free software
- world.
+ The documentation license we have chosen is the GNU Free
+ Documentation License (FDL), the standard for most documents
+ in the free software world.
- We need documentation to be written on a number of topics:
+ We need documentation on a number of topics:
+
+
* The development tools (compilers, assembler tools,
language reference, design time features).
- * Freely redistributable Frequently Asked Question
- compilations.
+ * Frequently Asked Question compilations.
- * Freely redistributable HOWTO documents.
+ * HOWTO documents.
* The Class Libraries
- * Tutorials on Mono and the specifics of running it
- compared to the Microsoft.NET Framework SDK
-
- * Differences between the Microsoft.NET Framework SDK
- development mode and the Mono version.
+ * Tutorials on Mono and the specifics of running it.
-** Class Library documentation
+ * A guide to Mono as compared to the Microsoft.NET
+ Framework SDK
- When contributing to the Class Library effort, please use the
- inline XML documentation tags to document your classes so we
- can automatically generate the documentation from the class
- libraries.
-
- If you provide examples, please do not embed them into the
- source code, as that will make the source code harder to read
- and maintain. Instead put examples for your code into a
- subdirectory of the class libraries. Also make that sample
- code a full standalone application that people can compile
- (ideally our documentation browser could let you edit, modify
- and run the sample programs, as Tcl/Tk used to let you do in
- the past).
+
+** Class Library documentation
+ We are moving to a new setup for documenting the class libraries,
+ and you can read about it here.
+
+ A few words of warning and advice for class documentors:
+
+ A well-documented API can ease hours of frustration; as Mono
+ matures, robust and complete class library documentation will
+ become increasingly important. As you write API documentation,
+ whether it is embedded in source files or in external Monodoc XML,
+ please keep the following in mind:
+
+ Plagarism, even if it's unintentional, is a Bad Thing(TM).
+ Microsoft's .NET Framework Class Library documentation is an
+ excellent resource for understanding the behavior and properties of
+ a type, and a lot of hard work went in to creating this (copyrighted)
+ resource. Please don't copy from Microsoft's reference when
+ documenting a type.
+
+ To avoid this, I (jbarn@httcb.net)
+ suggest that you read the complete Microsoft documentation for a type,
+ ponder it for a while, and write the Mono documentation in your own
+ words. While it's certainly okay to refer to the Microsoft
+ documentation to clarify your understanding of behavior or properties,
+ please don't open the Microsoft docs and refer to them for each member
+ you document.
+
+ There's a lot of domain expertise among the class library contributors;
+ let's put the same personal stamp on the class library documentation
+ that we have on the class libraries themselves.
\ No newline at end of file