goldcd writes "A while back I wrote some pretty reasonable forum code, a PHPBB alternative. A few years down the line it's pretty stable, I've stopped tinkering with it, and it's standing up by itself. I have neither the time, inclination, nor inspiration to do anything more with it, but would very much like to give the code to the world to use and expand upon. Now I could just upload it as it is onto SourceForge, but currently it's very specific in its usage and I'd be ashamed of what 'proper' coders would think of my amateur offering — I'm afraid it would be laughed at and ignored. On the other hand, I don't want to waste hours of my own time perfecting it for people just to 'rip off' as is, and never contribute anything. My question is, what do you have to do to make your code 'OSS appealing?'"

Marcy writes "Microsoft has just announced the final release of the IIS FastCGI module for IIS 5.1 (XP), 6 (2003), and 7 (2008). This FastCGI module was built with collaboration from Zend, the creators of PHP, and is intended to solve the CGI on Windows problem." It's free as in beer.

Elektroschock writes "The two core developers of Thunderbird have left Mozilla. Scott McGregor made a brief statement: 'I wanted to let the Thunderbird community know that Friday October 12th will be my last day as an employee of the Mozilla Corporation.' Meanwhile, David Bienvenu blogged: 'Just wanted to let everyone know that my last day at The Mozilla Corporation will be Oct. 12. I intend to stay involved with Thunderbird... I've enjoyed working at Mozilla a lot, and I wish Mozilla Co and the new Mail Co all the best.' A few month ago Mozilla management considered abandoning their second product and setting up a special corporation just for the mail client. Scott was more or less supportive. David joined in. While Sunbird just released a new version no appropriate resources were dedicated to the missing component. And while Thunderbird became the most used Linux mail client it has been abandoned by Mozilla for 'popularity reasons'. Both messages from David and Scott do not sound as if the founders will play any role in the Thunderbird Mail Corporation. What happened to Mozilla? Is it a case of pauperization through donations?"

dalektcalum writes "Dr. Ann Cavoukian, Canada's Information and Privacy Commissioner, recently gave a talk entitled Privacy by Design. The talk starts off by covering the basics of privacy, and privacy law, and then moves onto the important component: how to design software that properly protects users privacy. The majority of the talk is spent on design principles, but also examines specific technologies (such as Elliptical Curve Cryptography)." The site includes a flash video of the talk, but there are also several torrents for folks who want to avoid hammering their servers.

scott3778 writes to recommend a post by Timothy Mattson over at Intel's Research Blog. He argues, convincingly, that the most important paper for programming language designers to read today is one written by two social psychology professors in 2000. This is the well-known academic study, "When Choice is Demotivating: Can One Desire too Much of a Good Thing?" "And then we show them the parallel programming environments they can work with: MPI, OpenMP, Ct, HPF, TBB, Erlang, Shmemm, Portals, ZPL, BSP, CHARM++, Cilk, Co-array Fortran, PVM, Pthreads, windows threads, Tstreams, GA, Java, UPC, Titanium, Parlog, NESL,Split-C... and the list goes on and on. If we aren't careful, the result could very well be a 'choice overload' experience with software vendors running away in frustration."

ElvaWSJ writes "Several networking pioneers are dissatisfied with the Internet's underpinnings, and some are offering remedies to ease the strain that bandwidth-hungry services put on technology networks. Along with other projects here in the US and around the world, numerous companies and organizations are looking to rewrite the underpinnings of the internet. This piece looks at new concerns from old hands at networking, with comments from folks like Larry Roberts and Len Bosack. 'Mr. Roberts's concern over the Internet's infrastructure stretches back years. Even while at ARPAnet, he says he was unsure how long the technology could work, especially since the system didn't ensure that information packets would arrive at their destination. His fears crystallized in the late 1990s when he saw companies begin to use the Internet to make phone calls and consumers begin to dabble in online video.'"

An anonymous reader writes "Apple's reasoning for keeping the iPhone a closed platform is that they don't want to 'potentially gum up the provider's network'. An article in the New York Times, though, points out that there are hundreds of phones out there working on open platforms that don't seem to be causing network interference. AT&T and Palm, in fact, welcome experimentation on their platforms. In AT&T's case ... on every phone but the iPhone. 'Hackers who have explored the workings of the phone say it uses the frameworks and structures that Apple uses on its other platforms to enable development; it just hasn't been documented. So if Apple is going to allow applications later, is there any reason -- other than vindictiveness or obsessive interest in control -- that it would want to cut off those developed by the pioneers who figured things out ahead of the official launch?'"

An anonymous reader notes a blog entry, possibly his own, comparing and evaluating 8 mobile platforms from the point of view of their suitability for a hobbyist programmer. Covered are iPhone, Java ME, Windows Mobile, Linux, Palm, Brew, Symbian, and Blackberry. The writer seems open-minded and is a strong fan of free software, but he gives the edge to Windows Mobile for this class of developer.

David Gerard invites to read Carla Schroeder from Enterprise Networking Planet, who gets down to the real reason why companies want to keep their code proprietary, with examples. Quoting: "We are drowned in tides of twaddle about precious IP, Trade Sekkrits, Sooper Original Algorithms that must not be exposed to eyes of mere mortals, and all manner of silly excuses. But what's the real reason for closed, proprietary code? Embarrassment."

willdavid writes in to note a survey of open source developers conducted by Evans Data that indicates a real rift in the community over GPLv3. The survey was based on in-depth interviews with 380 open source developers and no estimated margin of error was given. "Just 6 percent of developers working with open-source software have adopted the new GNU General Public License version 3... Also, two-thirds say they will not adopt GPLv3 anytime in the next year, and 43 percent say they will never implement the new license. Almost twice as many would be less likely to join a project that uses GPLv3 than would be likely to join... [Evans Data's CEO said] 'Developers are confused and divided about [the restrictions GPLv3 imposes], with fairly equal numbers agreeing with the restrictions, disagreeing with them, or thinking they will be unenforceable.'"

An anonymous reader writes "Now that XML is the de facto standard (for good or ill) for doing message passing, I find that I need to give XML examples in the documentation that we produce. We're stuck with Word and up till now I've just been doing the examples as cut and paste from the log files. We include schemas in the appendix but it seems that the clients like the 'readability' of the raw XML over other approaches we've tried. I'm wondering what everyone else is doing in the world of XML documentation."

Maximum Prophet writes "Programmers and System Administrators typically don't get overtime. A law firm based in Nevada is looking to stand up for white-collar workers around the country, trying to reverse decades-old (and incorrect) thinking about what it means to work in an office. 'Computer workers of various stripes, for example, have commonly not been paid for their extra hours ... But under California law, the exemption applies only for workers whose primary function involves "the exercise of discretion and independent judgment." In numerous lawsuits, Thierman and other plaintiffs' attorneys have alleged that legions of systems engineers, help desk staff, and customer service personnel do no such thing. Of programmers, Thierman says, "Yes, they get to pick whatever code they want to write, but they don't tell you what the program does ... All they do is implement someone else's desires.'"

wolfeon writes "In 2005, Derek Sivers of CD Baby wanted to scrap his site and perform a rewrite in Rails. He hired Jeremy Kemper, also known as bitsweat on Freenode, to help on the project. Two years later, through blood and sweat, the project was then canceled because of limitations of Rails. Rails just wasn't meant to do everything since it is very much "canned" project. Mr. Sivers has written an entry in the O'Reilly blog: 7 reasons I switched back to PHP."

twoblackeyes writes "PopSci delves into the 10 greatest technical challenges faced by game developers today, and the technology that will hopefully make them a thing of the past. At the top of every dev's wish list is increased realism: realisitic fire, water, enemy AI, material physics, etc. Here directly from the developers where the tech stands today, and where it will likely be tomorrow. '4. Artificial Intelligence - Problem: Once upon a time, the bad guys in videogames wandered around mindlessly, shooting at you while they waited to die. That doesn't cut it anymore. Players demand sophisticated enemies to fight and reliable in-game allies with which to fight them. Thing is, it's freaking complicated, and it eats up processor speed. "We're faking just enough smarts to make it work," says Mathieu Mazerole, lead engineer on Ubisoft's Assassin's Creed. Status: Imbuing characters in a game with lifelike decision-making ability involves employing the kind of high-level logic theories--learning decision trees, mobile navigation, finite-state machine models--used by top robotics engineers.'"

eldavojohn writes "What's the biggest threat to the success of OpenOffice.org? Is it Microsoft Office? Is it the simple fact that Dell doesn't offer it with computers? Not according to some participants in the 'open' source project itself, they say the biggest problem with OO.o is the fact that Sun codes, owns & makes all key decisions for the project when it should be more community oriented. A professor who participates in the project itself said 'enough developers are frustrated by both the technical and the organizational infrastructure at OpenOffice.org' and cites this as 'a real problem that is weighing on the project.' Other members of the community agree like Michael Meeks who asked 'At what fraction of the community will Sun reconsider its demand for ownership of the entirety of OpenOffice.org?' Hopefully with IBM's entrance into OO.o participation we will see the product become more community controlled & accessible. Has anyone else experienced this when developing for OO.o or another 'open' source project? Is it a good idea to criticize a company when they've put so much effort into a project that is technically open source and completely free? Is Sun trying to control OO.o like Java? Do they have good reasons or evil underlying intentions?"

Joe Barr writes "Fork the kernel? Are you crazy? A blog entry on InfoWorld.com urged the Linux community to fork the kernel into desktop and server versions because, according to the author, all Linus Torvalds cares about is big iron. Sorry, but that's both wrong and stupid."

Sunnz writes "The leaner, lighter, faster, and most importantly, BSD Licensed, Compiler PCC has been imported into OpenBSD's CVS and NetBSD's pkgsrc. The compiler is based on the original Portable C Compiler by S. C. Johnson, written in the late 70's. Even though much of the compiler has been rewritten, some of the basics still remain. It is currently not bug-free, but it compiles on x86 platform, and work is being done on it to take on GCC's job."

An anonymous reader writes "In a recent public posting to the Linux Kernel mailing list the founder of the Software Freedom Law Center, Eben Moglen, lashed back at OpenBSD creator Theo de Raadt without actually mentioning his name. 'What has happened is that people who do not have full possession of the facts and have no legal expertise — people whom from the very beginning we have been trying to help — have made irresponsible charges and threatened lawsuits, thus slowing down our efforts to help them.' Moglen pointed out that they have and continue to help all open source projects, including OpenBSD, but the process takes time. 'The required work has been made more arduous because some people have chosen not to cooperate in good faith. But we will complete the work as soon as we can, and we will follow the community's practice of complete publication, so everyone can see all the evidence.'"

Phoe6 writes "Leading author and programmer, Bruce Eckel, posted some of his concerns on Python 3000 stating that the Python community is failing to address some of the important issues with this major, backward incompatible release. Problems he mentions are concurrency support on multi-core CPUs, easy deployment support, and a standardized user interface, amongst others. He expresses his dissatisfaction at the post titled "Python 3K or Python 2.9?. Guido van Rossum addresses the concerns in a very pragmatic way with his response to Bruce Eckel and calls for more developers to contribute to Python to improve it further. Bruce Eckel concludes with his thoughts that he wants his favorite language to be better with his reply to Guido's reply."

An anonymous reader writes "OOXML is already Microsoft's "de facto" standard as implemented in Office 2007, so when would any changes arising from the Comments Resolution meeting in February 2008 be put in place? According to Jeremy Allison's latest column, when last minute changes were suggested for the CIFS standard, which Samba exists to disentangle, "the response came back from Microsoft that although the fixes were valid, unfortunately the code was already written and was going to be shipped in the next service pack. End of discussion. It wasn't even in a shipping product yet, but the specification was determined to be unchangeable as they didn't want to change their existing code.""