Via the H comes a report that the Simon Phipps, current President of the Open Source Initiative, thinks that the VP8 patent Cross-license agreeement Google brokered with the MPEG-LA is incompatible with the Open Source definition. The primary problems are that the license is not sub-licensable and only covers certain uses, leading to conflict with OSD clauses five, six, and seven. Phipps concludes: "As a consequence, I suggest the license is flawed when considered in relation to open source projects and is likely to be negatively received by many communities that value software freedom. Doubtless a case can be made that the patent license is optional, but I suspect the community issues may remain. Once again we're left with our fingers crossed. Google's making the right noises, but this draft agreement seems like a particularly unworkable approach for free and open source software. Its failure to allow sublicensing seems like a major flaw. Even if this doesn't result in a requirement for all end-users to sign the agreement, the discrepancies between this document and the OSD leave it disruptive to open source adoption of VP8."

Read more of this story at Slashdot.

Via the H comes a report that the Simon Phipps, current President of the Open Source Initiative, thinks that the VP8 patent Cross-license agreeement Google brokered with the MPEG-LA is incompatible with the Open Source definition. The primary problems are that the license is not sub-licensable and only covers certain uses, leading to conflict with OSD clauses five, six, and seven. Phipps concludes: "As a consequence, I suggest the license is flawed when considered in relation to open source projects and is likely to be negatively received by many communities that value software freedom. Doubtless a case can be made that the patent license is optional, but I suspect the community issues may remain. Once again we're left with our fingers crossed. Google's making the right noises, but this draft agreement seems like a particularly unworkable approach for free and open source software. Its failure to allow sublicensing seems like a major flaw. Even if this doesn't result in a requirement for all end-users to sign the agreement, the discrepancies between this document and the OSD leave it disruptive to open source adoption of VP8."

Read more of this story at Slashdot.

Via the H comes a report that the Simon Phipps, current President of the Open Source Initiative, thinks that the VP8 patent Cross-license agreeement Google brokered with the MPEG-LA is incompatible with the Open Source definition. The primary problems are that the license is not sub-licensable and only covers certain uses, leading to conflict with OSD clauses five, six, and seven. Phipps concludes: "As a consequence, I suggest the license is flawed when considered in relation to open source projects and is likely to be negatively received by many communities that value software freedom. Doubtless a case can be made that the patent license is optional, but I suspect the community issues may remain. Once again we're left with our fingers crossed. Google's making the right noises, but this draft agreement seems like a particularly unworkable approach for free and open source software. Its failure to allow sublicensing seems like a major flaw. Even if this doesn't result in a requirement for all end-users to sign the agreement, the discrepancies between this document and the OSD leave it disruptive to open source adoption of VP8."

Read more of this story at Slashdot.

Via the H comes a report that the Simon Phipps, current President of the Open Source Initiative, thinks that the VP8 patent Cross-license agreeement Google brokered with the MPEG-LA is incompatible with the Open Source definition. The primary problems are that the license is not sub-licensable and only covers certain uses, leading to conflict with OSD clauses five, six, and seven. Phipps concludes: "As a consequence, I suggest the license is flawed when considered in relation to open source projects and is likely to be negatively received by many communities that value software freedom. Doubtless a case can be made that the patent license is optional, but I suspect the community issues may remain. Once again we're left with our fingers crossed. Google's making the right noises, but this draft agreement seems like a particularly unworkable approach for free and open source software. Its failure to allow sublicensing seems like a major flaw. Even if this doesn't result in a requirement for all end-users to sign the agreement, the discrepancies between this document and the OSD leave it disruptive to open source adoption of VP8."

Read more of this story at Slashdot.

Via the H comes a report that the Simon Phipps, current President of the Open Source Initiative, thinks that the VP8 patent Cross-license agreeement Google brokered with the MPEG-LA is incompatible with the Open Source definition. The primary problems are that the license is not sub-licensable and only covers certain uses, leading to conflict with OSD clauses five, six, and seven. Phipps concludes: "As a consequence, I suggest the license is flawed when considered in relation to open source projects and is likely to be negatively received by many communities that value software freedom. Doubtless a case can be made that the patent license is optional, but I suspect the community issues may remain. Once again we're left with our fingers crossed. Google's making the right noises, but this draft agreement seems like a particularly unworkable approach for free and open source software. Its failure to allow sublicensing seems like a major flaw. Even if this doesn't result in a requirement for all end-users to sign the agreement, the discrepancies between this document and the OSD leave it disruptive to open source adoption of VP8."

Read more of this story at Slashdot.

Via the H comes a report that the Simon Phipps, current President of the Open Source Initiative, thinks that the VP8 patent Cross-license agreeement Google brokered with the MPEG-LA is incompatible with the Open Source definition. The primary problems are that the license is not sub-licensable and only covers certain uses, leading to conflict with OSD clauses five, six, and seven. Phipps concludes: "As a consequence, I suggest the license is flawed when considered in relation to open source projects and is likely to be negatively received by many communities that value software freedom. Doubtless a case can be made that the patent license is optional, but I suspect the community issues may remain. Once again we're left with our fingers crossed. Google's making the right noises, but this draft agreement seems like a particularly unworkable approach for free and open source software. Its failure to allow sublicensing seems like a major flaw. Even if this doesn't result in a requirement for all end-users to sign the agreement, the discrepancies between this document and the OSD leave it disruptive to open source adoption of VP8."

Read more of this story at Slashdot.

beaverdownunder writes "I recently attended a 'hackathon' that was really just another pitching contest, and out of frustration am tempted to organize an event myself that is better suited to developers and far less entrepreneur-centric than some of the latest offerings. What I'd like to know from the /. community is, what would you like to see in a hackathon? What are some good hackathons you've attended that weren't just thinly-veiled pitch-development workshops? I have an idea around assigning attendees to quasi-random teams based on their skill sets, then giving them 48 hours to complete a serious coding / engineering challenge (probably in the not-for-profit space) — but maybe you've got some better ideas?"

Read more of this story at Slashdot.

First time accepted submitter fezzzz writes "Anonymous performed a data dump of hundreds of whistle blowers' private details in an attempt to show their unhappiness with the SAPS (South African Police Service) for the Marikana shooting. In so doing, the identities of nearly 16,000 South Africans who lodged a complaint with police on their website, provided tip-offs, or reported crimes are now publicly available." Reader krunster also submitted a slightly more in depth article on the breach.

Read more of this story at Slashdot.

gbrumfiel writes "Last week, Google and NASA announced a partnership to buy a new quantum computer from Canadian firm D-Wave Systems. But NPR news reports that many scientists are still questioning whether new machine really is quantum. Long-time critic and computer scientist Scott Aaronson has a long post detailing the current state of affairs. At issue is whether the 512 quantum bits at the processor's core are 'entangled' together. Measuring that entanglement directly destroys it, so D-Wave has had a hard time convincing skeptics. As with all things quantum mechanical, the devil is in the details. Still it may not matter: D-Wave's machine appears to be far faster at solving certain kinds of problems (PDF), regardless of how it works."

Read more of this story at Slashdot.

jrepin writes "The GNU Hurd is the GNU project's replacement for the Unix kernel. It is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other features that are implemented by the Unix kernel or similar kernels (such as Linux). The Debian GNU/Hurd team announces the release of Debian GNU/Hurd 2013. This is a snapshot of Debian 'sid' at the time of the Debian 'wheezy' release (May 2013), so it is mostly based on the same sources. Debian GNU/Hurd is currently available for the i386 architecture with more than 10,000 software packages available (more than 75% of the Debian archive)."

Read more of this story at Slashdot.

An anonymous reader writes "The Xbox One was revealed earlier, and Kotaku was able to get some answers about the always-online rumors that plagued the console before its announcement. Microsoft VP Phil Harrison said Xbox One doesn't need a constant connection in order to play games, and you won't be dropped from single-player games if your connection cuts out. However, it does require check-ins with Microsoft servers. This echoes the Xbox One FAQ, which cryptically says, "No, it does not have to be always connected, but Xbox One does require a connection to the Internet." The number Harrison gave was once every 24 hours, but Microsoft's PR department was quick to say that was just one potential scenario, not a certainty. Microsoft also provided half-answers about how used games and game sharing would work. Players will be able to take a game to a friend's house and play it (using their profile, at least). Players will also have some mechanism to trade and sell used games, but it's not yet clear exactly how it would work. If one player uses a disc to install a game on their Xbox One, then gives the disc to a friend, the friend will be able to install it, but needs to pay full price to play it. That scenario, however, assumes both players want to own the game — the second one would essentially be a unique copy. Microsoft said they have a plan for trading used games, which would involve deactivating the game on the original owner's console, but they aren't willing to elaborate yet." Several publications have hands-on reports with the new hardware: Engadget, Ars Technica, Gizmodo.

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.

An anonymous reader writes "I run a small software consulting company who outsources most of its work to contractors. I market myself as being able to handle any technical project, but only really take the fun ones, then shop it around to developers who are interested. I write excellent product specs, provide bug tracking & source control and in general am a programming project manager with empathy for developers. I don't ask them to work weekends and I provide detailed, reproducible bug reports and I pay on time. The only 'rule' (if you can call it that) is: I do not pay for bugs. Developers can make more work for themselves by causing bugs, and with the specifications I write there is no excuse for not testing their code. Developers are always fine with it until we get toward the end of a project and the customer is complaining about bugs. Then all of a sudden I am asking my contractors to work for 'free' and they can make more money elsewhere. Ugh. Every project ends up being a battle, so, I think the solution is to finally hire someone full-time and pay for everything (bugs or not) and just keep them busy. But how can I make that transition? The guy I'd need to hire would have to know a lot of languages and be proficient in all of them. Plus, I can't afford to pay someone $100k/year right now. Ideas?"

Read more of this story at Slashdot.