On Sat, May 24, 2008 at 6:29 PM, Tony Yu <[EMAIL PROTECTED]> wrote:

> I think this is what you're asking for, but I may have done the diff from
> the wrong directory.

I think the last one was a plain-ol-diff and this one is a svn diff so
it is better. I have applied it and committed it.  FYI, I  normally do
the svn diff at the same level that the setup.py resides in, but it is
easy enough to correct for,

> One last thing: is there some sort of tutorial for beginners who *may* want
> to contribute. Like a "Getting Started" page for developers. I have tons of
> questions, but I don't want to spam this list. For example: I checked out
> the maintenance version of MPL but the build and install set everything up
> in a new/separate directory. This means my subversion working copy is
> separate from the installed copy (what actually gets imported).

In the svn trunk, there are a few documents in docs/devel (you need a
fesh checkout to find it) that contain coding style guidelines, but
they are rather incomplete.  We are in the process of a documentation
push, so we hope to add to these.  Your questions are welcome, just
batch them into just one or a few emails rather than a ton of
individual ones.  Perhaps one of your first projects can to write the
"getting_started.rst"  for the developer's guide as you learn the
ropes.  We can all pitch in with answers to your questions...  In my
experience, one of the best time to write introductory documentation
is when you are learning something he first time, because the more
seasoned developers have trouble approaching the subject from the
perspective of a beginner.

JDH

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to