Hi Daniel, Daniel Ouellet wrote on Fri, Oct 29, 2010 at 03:30:47PM -0400:
> No one SADLY really thank you Actually, there were quite a few mails recently saying "thank you". > YOU give us We also do it for ourselves. :) But yes, publishing code and getting feedback from people using it is necessary for making it better, and keeping good code to yourself is stupid (excepting dirty quickhacks, of course). Its usefulness isn't diminished when others use it, too. Besides, you can help to keep the project going * by buying CDs (remember, Theo is working full time on OpenBSD, and needs a salary, and without his dedication, all this would work much less smoothly, if at all), * by donating (remember, without donations, there is no way to get developers together for hackathons; many devs pay for their own travelling and hotel costs, but not all are able to do so), * and by sending patches (remeber, without people sending patches, we can't recruit new developers). > your beliefs! The groff case is not so much about beliefs as about practicability. Did you ever try to write mdoc(7) manuals for groff, working around the various bugs? It was not fun. Did you ever try to fix bugs in groff? I wasn't very successful, for sure, even though i spent some time trying to read some chunks of that code. Now we perhaps even get a chance to install manual sources because mandoc(1) is fast enough to format them on the fly, even on the slow architectures. Let's see. Simplicity, correctness, functionality and maintainability are key. And having completely free code, of course. Yours, Ingo P.S. The p2k10 hackathon in Budapest (hmm, in Pest, to be precise :) was really nice. Thanks to robert@ for a perfect organization!
