29 Jan 2003 10:45:01 -0500
Sign up for mono-docs-list, at:
Documentation discussions (occasionally) happen there. At present, most
work appears to be going into the HOWTOs (in the monkeyguide CVS
If you're a die-hard (and possibly insane), you can write documentation
now. Documentation is in the monodoc CVS module, in the
"class/<assembly-name>/<language>/<namespace>" directory (e.g.
class/corlib/en/System, class/System/en/System.Net, etc.). Alas, the
documentation is in XML -- very verbose XML, using the same schema as
the documentation provided with the ECMA standard -- and the only way to
edit it is by hand.
There are documentation programs in the works (e.g.
doctools/gtk-monodoc), but I haven't had any success in using them to
write new documentation. Furthermore, I don't know when these tools
will be complete; more work appears to be going into the documentation
browser (in browser/), but that only views existing documentation.
Perhaps the documentation editor will be completed once the browser is
On Wed, 2003-01-29 at 06:29, Flávio Luiz Mendes wrote:
> I would like to help with the documentation!
> how I can help? he has much thing missed in the documentation
> Thanks !!
> Jonathan Pryor wrote:
> >The better question to ask is what would you like to do?
> >There are lots of things you can do:
> > - Work on the class libraries. See
> > http://www.go-mono.com/class-status.html
> > The classes listed are the classes that need work, are incomplete,
> > etc. Find a namespace that interests you and start implementing.
> > - Documentation. Lots is needed. It's in the monodoc CVS module.
> > See also: http://www.go-mono.com/documentation.html
> > However, you might want to wait on this until the documentation
> > editor is complete.
> > - HOWTOs. These are in the monkeytalk CVS module, and can be seen at:
> > http://www.go-mono.com/tutorial/html/en/index.html
> > - Test Cases: Either implement more, or fix the bugs that they are
> > finding. NUnit is used for test cases, but some are using NUnit,
> > while others are using NUnit2, so I'm not sure what we should be
> > using for new test cases.
> > However, I've heard that there are lots of mono bugs found by the
> > current test cases, and these should be fixed.
> > - Bug Fixes: See http://bugzilla.ximian.com, and look at the bugs for:
> > gtk#
> > Mono/Class Libraries
> > Mono/Debugger
> > Mono/Doctools
> > Mono/mcs
> > Mono/runtime
> >Hope this helps.
> > - Jon
> >On Tue, 2003-01-28 at 09:00, Dushyant Bansal wrote:
> >>I read about your project on SlashDot. I can't commend you guys enough
> >>for making this effort.
> >>I would like to contribute to the code. I've never done any open source
> >>work before though. Please tell me what I need to do to get involved.
> >>Dushyant Bansal
> >>MASc Candidate, Distributed and Mobile Systems,
> >>Computer Engineering,
> >>University of Waterloo,
> >>Mono-list maillist - Monofirstname.lastname@example.org
> >Mono-list maillist - Monoemail@example.com