Developer's guide: let's get started!

[Todd Graham Lewis <tlewis mindspring net>]

I am ready to get started on the developer's guide.  Have we figured
out how we're going to manage chunks of this baby?  Should I just
start writing and figure out how to submit/reconcile them later?
(HINT: the answer is no.)  What parts should I do?  I think that I
can handle the following:

i18n
DnD
language bindings (pointers to various projects; nothing other than
	C and scheme is close to stable enough)
sound (don't know much, but it looks easy)

I have never written a GNOME program, and so I would not feel comfortable
telling people how to do it.  I am, however, generally familiar with what
is going on, and I would be more than happy to proofread other people's
parts and/or offer suggestions.  Consider me an alpha user of the guide.

When can we get started?  Who is going to do Parts 1, 2 and 3?

--
Todd Graham Lewis      MindSpring Enterprises    tlewis@mindspring.net
 The Windows 2000 name was obviously created over a glass of root beer
  in the company cafeteria by a couple of executives looking for a way
   out of the Windows NT delays.                     -- John C. Dvorak