Great document. I have a couple of comments.
1.) The beginning talks a lot about people doing this "on the job". A lot
of developers on open source projects are students, you might wish to
mention something just to acknowledge that they do exist. I know it is
petty, but it never hurts to feed someone's ego by recognizing them.
2.) You mention getting a Perl distribution for Windows, but don't metnion
getting a C compiler.
I would recommend saying something about CygWin (www.cygwin.com) or
perhaps a dos based C compiler. cvs, perl, and make all become non-issues
when CygWin is added to the mix; although performance does suffer quite a
bit.
3.) If anyone plans to work on imcc, then they will need YACC or Bison.
They don't need it to compile imcc, but if they want to develop for it they
will.
4.) Before submitting a patch it would be nice if they could do cvs update.
If not, that is ok, but at least they would know the patch will apply
cleanly.
A really great document...keep up the good work!
Tanton
----- Original Message -----
From: "Erik Lechak" <[EMAIL PROTECTED]>
To: "perl6-internals" <[EMAIL PROTECTED]>
Sent: Tuesday, October 08, 2002 11:28 PM
Subject: the getting started guide
>
> Hi,
>
> Well here it is, my first attempt at a "getting started" guide. It's
> not ready for public consumption, but I would like to hear some
> feedback. The later sections are blank or contain notes in a not nice
> format. As time moves on and I learn more, I expect the guide to fill
> up. It's taking me a lot longer to get up to speed on Parrot due to the
> fact that I am documenting my learning process. I hope this effort
> helps others ramp up more rapidly.
>
> If you find any mistakes (boy, am I opening myself up with this one) or
> anything you would like to add to the first few sections, I'd like to
> hear them.
>
> I plan to have a lot more diagrams in the document. I am using 'dia' to
> create them. Is there a better tool for the job?
>
> I started writing the guide in a textbook format, but I was putting
> myself to sleep. So I am writing it in a more friendly style. I hope
> this doesn't bother anyone. If so, let's hear it.
>
> This version is in html. I almost have the pod version ready.
>
> I am on a windows machine. But I also have a linux box sitting right
> next to me. I used winzip to zip it up. Do you guys have a prefered
> compression format that I should use in the future?
>
> Here is my last question. Recently, when I try to login to cvs, I get
> this (see below). It worked in the past. Is it me, or did something
> else happen?
>
> set CVSROOT=:pserver:[EMAIL PROTECTED]:/cvs/public
> cvs login
>
> (Logging in to [EMAIL PROTECTED])
> CVS password: ***I JUST HIT RETURN HERE***
> cvs [login aborted]: could not open %USERPROFILE%/.cvspass: No such file
> or directory
>
>
> Thanks,
> Erik
>
>
