<flame on> I've seen several comments go across with valid concerns, and a few that perplex me.
Guys, look at the facts. We have a very small number of internals hackers here, and only one who actually gets paid for it. Most of us have jobs and families, and we slip in this stuff in little slices in hopes that little by little we are gaining ground. This is nothing new to people like Larry, but I think many other people take it for granted. We are not an army. If you have concerns about Parrot's pace (as do I), quality, or design, then grab a bat and step up. I can tell you from past open source projects, things do not happen unless you: 1) Offer specifics, numbers, helpful snippets 2) Offer patches (cliche, but still best bet) 3) Take a personal interest in an area and try to learn it and improve it Simon Glover is a good example. He has countless doc/test/comment patches in because he follows the pace, and pitches in when he sees a small problem. I can't ever think of a time I've heard him gripe. But, since he is a regular contributor, if he did gripe, I'd listen politely. Here are two final suggestions... -Subscribe to the cvs-parrot list; you might get a clue of how thin we are spread and who is responsible for what. You also get to read patches as they go in, and comment on them. -Visit the IRC channel from time to time. There is more going on than what goes across the list. <flame off> -Melvin
