> Did you take notes as you were running into trouble? Write down what >you think is missing, make sure to include all the bits you had to twiddle, >paths, etc. to get it working, and send it to the list, or to anyone on the >team directly, and we'll add it to the docs directory.
Sheesh, go back and read the messages from me. yes, I've been doing that with exactly that intent AND STATING IT all along. > > As I said, I've been reading up on Python today to try to get a handle on > > the language. And I obviously looked at the sources or I couldn't have > > determined their languages, even of Exploder. These aren't exactly traits > > of a cry baby, Mike. > > I am not a Python guru, but I do know how to code (mostly). My >preferred language is Perl, but I can definately tell where an error comes >from, and zoom in on the part of code that needs to be looked at by someone >more skilled in Python than myself. It's this "zooming-in" that can benefit >the maintainer of those bits with understanding the problem. Now go back and look in the bug-base at the report I entered, and at the two mailed reports since I started... all three have complete reproduction cases, relevant configuration data, etc. You're preaching to the chior here, Mike. Perhaps that's why I responded to your earlier message the way I did - you're lumping me in with AOL-users, for example, when it isn't merited. > Take a breath. Nobody is against you. We all appreciate the effort. >Read your original message again, and see how it could be interpreted a >different way. Initially, I read that as "Hey, your project is great, but it >sucks because you forgot to spoon-feed non-POSIX developers". The comment >that began "Part of this is due to a stunning lack of project setup >documentation.." was a direct slam on our work. I wasn't stating or meaning to imply Plucker sucks; I think it's great and want to help it be even better. But yes, I did slam the dev documentation. I've worked on other opensource projects and never encountered as much setup problem. But then again, that's why I decided to start by fixing that specific issue. And I will fix it, because it annoys me. You can tell I'm annoyed, no? Apparently I'm also a carrier - when annoyed, I cause it in other people. >If you don't like the docs, >you're welcome to correct them. If that means create them where they don't >exist, you're welcome to do that too. Once every single bug is fixed in the >viewer, distiller, and Plucker Desktop, we'll probably all start working on >documentation. Nah. When it's working well and fully feature-laden, it will cease to hold your interest long enough to document the bits-and-bobbled needed to build it. Most developers are that way. I'm not, but I think it was because of a self-inflicted spaghetti-code-disaster back in 1984. Lessons that you learn hard, you learn well. I didn't intend for anyone to feel that I was attacking Plucker itself. And hopefully by the time I'm done with it, I'll consider at least two module-bits better documented plus have contributed a QuickStart Guide. It's a low goal, but one I'm pretty sure I can accomplish before other things pop back up in my life. _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
