Karel Kulhavy wrote:
Welcome to the concept of human languages. If things couldn't ever be interpreted two ways then puns wouldn't exist and lawyers would be starving.If you write a specification in a way that permits two different interpretations, isn't it wrong?
changes they will figure out new things to do with the application (law of unanticipated consequences) which will break the code again. I suggest, the only "Bug Free" programs are very very simplistic.
Finally, I suggest you drop your usage of the word criminal. The developers here are pretty much not payed for their time. Every request
This is a mantra I hear every time I report a bug and is absolutely irrelevant to anything. I am also doing things that can be freely downloaded from web and don't use this mantra against people helping me doing my job by sending bugreports.
I don't use your stuff so I have no comment about it. But rudness isn't excusable. It tends to convince others that working with you is not only a waste of time but an agrevation.
I am reminded by a scene in the movie Office Space where a manager is yelling at the top of his lungs...that the engineers "DON"T HAVE PEOPLE SKILLS!" Reading what you have written leaves me to conclude.... in some cases he might be right.for a feature, Every Bug report, Every request for an explination or documentation should be made with the most polite thanks for your efforts could you explain, fix, repair... did you notice.... how can I help.
Polite thanks are just a waste of bandwidth. When you do something for free, polite thanks are a default by principle. Should I put them into mail footer? I don't expect polite thanks in bugreports. I always have to skip them to get to the technical details that interest me.
For example, if someone writes me polite thanks for Ronja, it doesn't move the project any forward. When someone writes "The download script for wget doesn't work this way", I go, fix it, Ronja becomes better, the benefit for the general public gets bigger (because not every single builder is pestered by the bug in the script) and I become more happy.
If someone writes "Hey Clock, you are idiot, your script is wrong", the net
result is the same, and the impact on my happiness should be (theoretically)
the same.
Obviously, someone can also contribute a code or design, but contributing a
bugreport is already a pretty valid forward movement.
Bug reports are legitimate.
And - can I download the source for the board anywhere?
Nope, not the schematics or the board design. I am planning on publishing the Land Patterns and Symbols as well as I am working to release my modifications to gschem and gnetlist which provide a level of hierchical bus support.
