phlawed writes "I've been a Linux user since the previous millennium. I came from OS/2, which I really liked. I quickly felt at home with icewm, using a suitably tweaked config to give me something resembling Presentation Manager. I may have commented on that before. Today, I find myself in a position where my preferred 'environment' is eroding. The only force keeping icewm rolling these days is the distribution package maintainers. I can't code in any meaningful way, nor do I aspire to. I could easily pay for a supported version of icewm, but I can't personally pay someone enough to keep it alive. I'd love it if someone took a personal interest in the code, to ensure that it remains up to date, or to make it run on Wayland or whatever. I want someone to own the code, be proud of it. Is there a general solution for this situation? How do I go about drumming up interest for an old project?"
Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!
theodp writes "Over at Scripting News, Dave Winer has a hobbyist phone on his wish list. Innovative phone manufacturers, Winer suggests, should 'make a smart phone with a really great scripting language, with all kinds of scriptable tools on board. Instead of disallowing scripting, disallow apps that can't be scripted. Make a great simple programming environment that runs on desktops or laptops that plugs right in, but it should also be easy to write scripts on the phone itself. Dave concludes, 'We've already seen the Jobs phone. Now it's time for Woz's.' Having ditched App Inventor, it would appear that Google isn't interested. Microsoft Research has the idea, if not the right implementation, with TouchDevelop (video). Any other existing or in-the-works projects that might fit the bill?"
dp619 writes "Fighting against software patents (New Zealand has banned them) tends to blind FOSS communities to aspects of IP law that actually serve them well. While certainly not perfect, patent, copyright, trademark, and trade secret law each has something to offer FOSS communities. Penn State law professor Clark Asay wrote a guest post for the Outercurve Foundation briefly describing some of the ways in IP law can help open source developers."
An anonymous reader writes "Do you think so called 'rock star' developers are necessary at every company? Personally, I don't think so, and I equate it to not needing a college degree to work at Walmart. If you give every problem a complexity value from 1 to 10, and your problems never get higher than a 6 or 7, do you need people capable of solving the 10s? I work for a large software company and I'd rate myself a 7. There are more technically proficient developers, but I don't have an ego about my work, I work well with coworkers and customers, and I bring people up around me. Most 'rock stars' I've seen have been difficult to work with. Most of them are no longer with the company because they were terminated or quit for more money. Is this usually the case? Is it worth the trouble? (Note to any managers reading this: if you have a rockstar who is a pleasant person, pay them well; they are very rare.)"
jones_supa writes "The sudden death of a solid-state drive in Linus Torvalds' main workstation has led to the work on the 3.12 Linux kernel being temporarily suspended. Torvalds has not been able to recover anything from the drive. Subsystem maintainers who have outstanding pull requests may need to re-submit their requests in the coming days. If the SSD isn't recoverable he will finish out the Linux 3.12 merge window from a laptop."
Esther Schindler writes "You've written some code, you think it would be useful to the world, and you'd like to give back to the open source world. But how do you do it? Andy Lester provides a checksheet for developers for how to release an open source project and get it noticed. For instance: Before you release the project to the wild, write some documentation, create a mailing list, create an issue tracker, and so on. 'Users require releases of your software. It’s a disservice to your users to point at the Git repo and say “Just pull from the master branch and install it.” Users don’t want to have to use version control just to get a release of the code. Create a proper tarball (.tar.gz) that is easily downloadable by anyone. Announce each release. Your announcements should not assume that the reader is familiar with your project.' You think he's missing anything?"
Koookiemonster writes "Our company has many projects, each one with a folder on a Samba drive (Z:\). Our problem is syncing only the programmers' current projects (~30 at any time) between Z:\ and their C:\Projects\-folder on five Windows 7 laptops. If we sync the whole Z:\-drive, our projects folders would be filled with too many subfolders, making it difficult to navigate. The folders contain OpenPCS projects (PLC) and related files (Word, Excel, PDF documents); a common project folder is 50 MB. Is there any easy to use, low-budget sync software with scripting, so that we could e.g. only sync folders that exist locally?" (Read more details, below, of what Koookiemonster is looking for.)
hypnosec writes "Linus Torvalds, in response to a petition on Change.org to remove RdRand from /dev/random, has lambasted the petitioner by called him ignorant for not understanding the code in the Linux Kernel. Kyle Condon from the UK raised a petition on Change.org to get Linus to remove RdRand from /dev/random in a bid 'to improve the overall security of the linux kernel.' In his response, Torvalds asked Condon and the supporters of the petition to gain an understanding of Linux drivers and cryptography, and then 'come back here and admit to the world that you were wrong.' Torvalds stressed that kernel maintainers knew what they were doing and the petitioner didn't. Torvalds, in a similar outburst just yesterday, hoped that 'ARM SoC hardware designers all die in some incredibly painful accident.' This came in response to a message from Kevin Hilman when he noted that there were quite a few conflicts in the ARM SoC pull request for Linux 3.12 which were a result of the platform changes conflicting with driver changes going in to the V4L tree."
New submitter Archie Cobbs writes "Last May I encountered a relatively obscure performance bug present in both MySQL 5.5.x and MariaDB 5.5.x (not surprising since they share the same codebase). This turned out to be a great opportunity to see whether Oracle or the MariaDB project is more responsive to bug reports. On May 31 Oracle got their bug report; within 24 hours they had confirmed the bug — pretty impressive. But since then, it's been radio silence for 3 months and counting. On July 25, MariaDB got their own copy. Within a week, a MariaDB developer had analyzed the bug and committed a patch. The resulting fix will be included in the next release, MariaDB 5.5.33."
An anonymous reader writes "Fed up with piracy and the availability of cracked versions of his software, Cobalt Strike developer Raphael Mudge wrote a blog post telling people how to crack his software. Some gifts are poisoned, and Raphael goes into deep detail about how to backdoor his software and use it to distribute malware. Will this increase piracy of his software, or will it discourage would-be pirates from downloading cracked versions?"
rysiek writes "Remember MailPile, the privacy-focused, community-funded FOSS webmail project with built-in GPG support? The good news is, the funding campaign is a success, with $135k raised (the goal was $100k). The bad news is: PayPal froze MailPile's account, along with $45k that was on it, and will not un-freeze it until MailPile team provides 'an itemized budget and your development goal dates for your project.' One of the team members also noted: 'Communications with PayPal have implied that they would use any excuse available to them to delay delivering as much of our cash as possible for as long as possible.' PayPal doesn't have a great track record as far as fund freezing is concerned — maybe it's high time to stop using PayPal?"
whoever57 writes "On Saturday, Oracle Team USA and Team New Zealand will begin racing for the America's Cup in the amazing AC72 boats. However, the Oracle team starts with a significant handicap. It was recently discovered that members of Oracle Team USA made illegal changes to the boats used in the America's Cup Series (which is sailed in the smaller AC45 boats). After a hearing on Friday, the International Jury has decided on the penalty: Team Oracle will have to pay a fine and sail without some team members. More significantly, they lose two points before starting the America's Cup races against Team New Zealand. A tiny amount of weight had been added to the kingpost, in violation of the measurement rules for the class. This was reported to the measurement committee some weeks ago after its discovery by boatbuilders working for America's Cup Regatta Management (ACRM), not members of Oracle Team USA."
Programmer Steve Losh has written a lengthy explanation of what separates good documentation from bad, and how to go about planning and writing documentation that will actually help people. His overarching point is that documentation should be used to teach, not to dump excessive amounts of unstructured information onto a user. Losh takes many of the common documentation tropes — "read the source," "look at the tests," "read the docstrings" — and makes analogies with learning everyday skills to show how silly they can be. "This is your driving teacher, Ms. Smith. ... If you have any questions about a part of the car while you’re driving, you can ask her and she’ll tell you all about that piece. Here are the keys, good luck!" He has a similar opinion of API strings: "API documentation is like the user’s manual of a car. When something goes wrong and you need to replace a tire it’s a godsend. But if you’re learning to drive it’s not going to help you because people don’t learn by reading alphabetized lists of disconnected information." Losh's advice for wikis is simple and straightforward: "They are bad and terrible. Do not use them."
cold fjord sends news that a study by Coverity has found open-source Python code to contain a lower defect density than any other language. "The 2012 Scan Report found an average defect density of .69 for open source software projects that leverage the Coverity Scan service, as compared to the accepted industry standard defect density for good quality software of 1.0. Python's defect density of .005 significantly surpasses this standard, and introduces a new level of quality for open source software. To date, the Coverity Scan service has analyzed nearly 400,000 lines of Python code and identified 996 new defects — 860 of which have been fixed by the Python community."
theodp writes "Friday saw the launch of Rupert Murdoch's AP Computer Science MOOC. Taught by an AP CS high school teacher, the Java-centric course has students use the DrJava lightweight development environment for the exercises. 'If this MOOC works,' said Amplify CEO Joel Klein, 'we can think of ways to expand and support it.' Only the first week's videos are posted; course content is scheduled to be presented through March, with five weeks thereafter set aside for AP Exam prep. Might as well check it out, you may have helped pay for it — a MOOC-related Amplify job listing notes that 'This position may be funded, in whole or in part, through American Recovery & Reinvestment Act funds.'"
New submitter MeatoBurrito writes "The latest iteration of Mechwarrior was crowdfunded (without Kickstarter) as a free-to-play first-person mech simulator. However, despite promises to the founders, the game has been shifted to a third-person arcade shooter and now the community is rioting. This followed a series of other unpopular decisions; the developers decided to sell an item for real money that had a significant impact on gameplay, crossing the line separating cosmetic/convenience items and 'pay-to-win.' Then they added a confusing game mechanic to limit its use, which had the unfortunate side effect of making some strategies completely useless. From the article: 'PGI’s community practices showcase a fundamental misunderstanding of both freemium development and community management. The developer has never had to deal with such a large player base before, and it has never had to deal with the strains of continuous development before. Rather, PGI seems to be handling Mechwarrior Online in much the same way they might a AAA game: by keeping quiet and only discussing its work in vague terms. ... Mechwarrior Online’s road to launch is a cautionary consumer tale, fraught with anger and betrayal. It shows how a company can take a fan base dedicated to an old IP and completely alienate it through lack of communication, unpopular features, and oathbreaking. It shows how players need to be cautious of supporting a project based solely on the IP backing it.'"
rjmarvin writes "Cities are taking coding to the streets through projects like Code for America and CityNext, working with governments on multiple levels to better serve constituents with mobile and cloud technologies. The 'Peace Corps for geeks' is using technology to make everyday life in cities run more smoothly, providing a way to 'connect technologists and designers with their government to solve important problems and reimagine how government could work.'"
theodp writes "Writing in The Atlantic, Phil Nichols makes a convincing case for why educational technologies should be more like graphing calculators and less like iPads. Just messing around with TI-BASIC on a TI-83 Plus, Nichols recalls, 'helped me cultivate many of the overt and discrete habits of mind necessary for autonomous, self-directed learning.' So, with all those fancy iPads at their schools, today's kids must really be programming up a storm, right? Wrong. Nichols, who's currently pursuing a PhD in education, laments, 'The iPad is among the recent panaceas being peddled to schools, but like those that came before, its ostensibly subversive shell houses a fairly conventional approach to learning. Where Texas Instruments graphing calculators include a programming framework accessible even to amateurs, writing code for an iPad is restricted to those who purchase an Apple developer account, create programs that align with Apple standards, and submit their finished products for Apple's approval prior to distribution.'"