This is a list of books currently on my To Read shelf... literally. I do not suggest or anti-suggest any of them at this time as I haven't read them yet.
Current Efforts:
Blue Parabola, LLC
HubAustin
web2Project
PHP'ers:
Cal Evans
Eli White
Elizabeth Naramore
Joe LeBlanc
Matthew Turland
Matthew Weier O'Phinney
Planet PHP
Tony Bibbs
Business/mISV:
Bob Walsh
Eric Sink
Joel Spolsky
Micah Baldwin
Paul Graham
Past Projects:
CodeSnipers
HOBY
Judicial Watch
mobile FoxNews.com
NRTW
Great Tools I use:
Drupal
GitHub
NetBeans for PHP
phpUnit
Subversion
Zend Framework
This is not the home of dotProject or web2project. It is the home of CaseySoftware, LLC. Any dotProject support questions should be referred to their support forums.
Update: To be fair, a great deal of inspiration for this post came from Ed "Funkatron" Finkler and his session at phpWorks 2008 Picachu pitch-at-ya peek-at-you lightning talk called "Users are Assholes" and later by Matthew Weier O'Phinney's lightning talk called "How to get kicked off my Project." Thanks for the fodder guys!
On all sides of software development, there are annoyances. Some of them go beyond annoyances and into pet peeves. Some of them go beyond pet peeves and incite open war within projects and communities. After witnessing a number of these rants - from developers and non-developers - and even sharing a few myself, I thought maybe I could make the situation better.
Therefore, I present here for comment:
The Ten Commandments of Open Source Software.
0. Thou shalt not ask questions without basic research including documentation and the Google.
I. Thou shalt realize that most developers work on passion and freetime. Thou are not paying them.
II. Thou shalt not criticize code and architectures before seeking understanding.
III. Thou shalt not use the phrase "this should be simple" unless thou has confirmed it as such.
IV. Thou shalt apply patches and updates in a timely manner. Further, thou shalt have a vague idea of when the next release is due-eth.
V. Honor thy developers and designers.
VI. Thou shalt include specific error messages and screenshots when thou hast problems. Thou stating "thy software sucks" is not helpful and angers the Funkatron.
VII. Thou shalt not murder.*
VIII. Thou shalt not copy without respecting both the license and the terms within.
IX. Thou shalt not covet the features and functionality in thy neighbor's software.
Did I miss any?
* No, I'm not kidding.
Awesome
That covers it all! Excellent commandments to live by- though, I think the murder may be a little flexible in times of a launch ;)
Great, on target and damn funny
Keith:
Great job...thanks for adding a little more humor to the day
Paul
IX
I think coveting features of thy neighbor's software is normal, and actually a pretty good way to grow your project. Like the list.
zero
BTW, Romans did not have a number 0. Bad monkey logic for trying to use base zero array and roman numerals. Thou must go hindu-aribic for base 0
Thy Grammar? :P
How about:
X. Thou shalt use the proper conjugation of verbs after "thou", such as "hast" and "art" instead of "has" and "are", at all times when using "thou" instead of "you".
XI. Thou shalt not randomly append the archaic -eth verb suffix on adjectives.
*ducks*
Nice article, but I think coveting thy neighbors' features is a good thing, especially if thou art motivated to add them to the software via a patch. I will guess, however, that thou was talking about whiners wondering "why can't thou add such and such, waaah!"
Coveting thy neighbor's features
I was torn on this one. I thought it was the weakest point but left it in anyway hoping people would read what they wanted from it. It looks like that mostly worked.
And I would have gotten away with it too if it wasn't for you kids and that dog!
That is you _meddling_ kids,
That is you _meddling_ kids, get it right ;)
Point Taken
Ah, that's right. My apologies.
On the first one
In a perfect world, we like people who do their own research but this world isn't perfect. And the more adoption your open source project receives the more likely it is that the end user is not aware of RTFM and STFW. ;)
RTFM & STFW
Here's what gets me..
Quite often they're not willing/able to do a basic search but figured out enough to find the forums, mailing lists, or developers' email addresses.
While it may be simple ignorance, quite often it appears to be laziness too. It's like the guy in your office who refuses to look anything up and prefers to ask the guy next to him instead of doing it himself.. At minimum, it's disruptive..
Fantastic
I might need to send this out over some mailing lists. "Consult Commandment ___ and amend your behavior." :-)
A good example!?
It's nice to be used as an good example for once. ;)
Post new comment