-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I've already started, Mike, but y'all lose yourselves perfectly good
> developers who would be glad to help if not for the predilection to avoid
> anything with a taint of Microsoft on it.
Let me try to put a cork in the mudslining that I see approaching:
A few points:
1.) Plucker is Free Software, built with free tools, on a free OS.
2.) Microsoft is not free, nor are the tools free.
We don't work on that OS, because we don't have the tools, nor do we
have the initiative to go out and get them, since it is not our native
platform. Not to take on another OSS comment, but Open Source and Free
Software exists _only_ because it solves a particular developer's "itch". If
someone else finds it useful, great. If nobody else does, it worked for the
author, and when it comes down to it, that's the bottom line.
Contributions are welcome, encouraged, and appreciated, in all
respects. We can't force people to contribute, we can only make it easier,
if it fits within the confines of the end-goal, to solve an "itch".
If it doesn't work on Windows, in your environment, you are
generally expected to do the additional work to get it working, and then
provide that back to us, so we can include it for others users to benefit
from.
> You're doing just as much crying, wanting people to dive in and fix it but
> not providing docs on what is required in the form of support libraries,
> headers, and tools. (make, gcc, and the Palm SDK we can take as read.)
How do we know what is required, if we don't have the tools or OS to
try it on, and find out where it fails, and then document that tool_x is
needed, or you'll get error_y?
> No, it's the large quantity of dependencies that you aren't noticing
> because you've got them set up.
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.
> 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.
Help us fix the deficiencies, we're willing to help you, but you
have the tools, the OS, and the know-how. You have to do most of the legwork
and help us understand what's missing. It's like doing a surgery over the
telephone. You have to describe what you see, what you don't see, and let us
try to figure it out from here.
> So here I am already trying to fix the problem and you're pissing about
> how "Windows cry babies" don't. Harumph! I -am- trying to fix it, but
> first I have to understand it and verify that, in the face of all logic,
> it really is as it appears. Sheesh!
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. 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. Until then, we have other things that we're focused on.
> My guess is that my initial efforts won't change the actual source code
> much... just make it easier for the next person. But hey, it's something.
It's a good start. March on...
d.
perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.92 (GNU/Linux)
iD8DBQE9j61KkRQERnB1rkoRAsQnAJwLKbe990uRkt6vC7suSxWl+Epw5QCdELKd
eFc6+5oQ1RFCIyOXauSM024=
=E72n
-----END PGP SIGNATURE-----
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
