Slashdot Mirror

An anonymous reader writes: Jono Bacon explains that in the same way open source spawned millions of careers and thousands of companies, the same openness has massive potential when applied to products. It could potentially jumpstart a revolution in how we conceptualize, build, and share things and how we experiment and innovate to push the boundaries of science and technology. He outlines some steps for adapting open source principles to physical creations: "...we will need to create a premise of a blueprint bundle. In much the same way I can download a branch from Git or a tarball with some code, complete with build system, we will want to be able to download a single branch or tarball with the full software, hardware designs, and more for how to create an open product. ... we will need to figure out how we collaborate and improve different pieces of these projects. For example, if someone refines a 3D printed piece of a drone, how do they fork the blueprints, submit their changes, have them reviewed, and get them merged into the project? Another question could relate to automated testing: when building physical products we can't always afford to build and test new physical hardware for it to then crash and burn, so how can we have unit tests for hardware or test in a virtual setting?"

An anonymous reader writes: As open source started booming, more people joined. Opinionated people. People who listened to the "we welcome everyone!" message and felt that their opinion could be their primary contribution. For some, they felt showing up at the gig gave them the right to dictate what the band played. From a leadership perspective, this was a tough spot to be in. On one hand, you want to foster an open, welcoming, and empowered community. You want that diversity of skills, but you also want value and quality. Low-quality contributors don't bring much other than noise: they are a net drain on resources because other good contributors have to take time away to support them.

In addition to this, those entitled, special-snowflakes who felt they deserved to be listened to would invariably start whining on their blogs about what they considered to be poor decisions. This caused heat in a community, heat causes sweating, sweating causes irritability, and irritability causes more angry blog posts. Critical blog posts were not the problem; un-constructive, critical blog posts were the problem. So what's the best way to foster a welcoming environment while still being able to remove the destructive elements?

An anonymous reader writes: The Bike Kitchen started WhiteBikes in Bratislava after a failed attempt by the city to finance a similar program. At first users shared donated bikes with the same lock code. They needed a system that would work somewhat automatically without the need for manual rentals (e.g. somebody giving out bicycles). From there, smsBikeShare was born. Users registered with a mobile phone number and could send basic SMS commands (RENT, RETURN, FREE, WHERE, etc.). The system used an inexpensive SMS gateway API and a local message-back number to receive and respond to messages. Shared bicycles have a coded U-lock with a four-digit number, and upon renting a bike, users receive a code to unlock the bicycle and another to reset it to once they are done. Send a message, receive the answer, unlock the bike, reset the lock, and you're off pedaling.

An anonymous reader writes: As Congress gears up again to seriously consider patent litigation abuse—starting with the introduction of H.R. 9 (the "Innovation Act") last month—opponents of reform are arguing that recent Supreme Court cases have addressed concerns. Give the decisions time to work their way through the system, they assert. A recent hearing on the subject before a U.S. House Judiciary Committee (HJC) Subcommittee shined some light on the matter. And, as HJC Chairman Bob Goodlatte, a long-time leader in Internet and intellectual property issues, put it succinctly in his opening remarks: "We've heard this before, and though I believe that the Court has taken several positive steps in the right direction, their decisions can't take the place of a clear, updated and modernized statute. In fact, many of the provisions in the Innovation Act do not necessarily lend themselves to being solved by case law, but by actual law—Congressional legislation."

An anonymous reader writes with this interview with John Sullivan, Executive Director of The Free Software Foundation. "There is a growing concern about government surveillance. At the same time, those of us who live and breathe technology do so because it provides us with a service and freedom to share our lives with others. There is a tacit assumption that once we leave the store, the device we have in our pocket, backpack, or desk is ours. We buy a computer, a tablet, a smartphone, and we use applications and apps without even thinking about who really owns the tools and whether we truly own any of it. You purchase a device, yet you are not free to modify it or the software on it in any way. It begs the question of who really owns the device and the software?"

An anonymous reader writes: Industry knows open source software has an immense value, but how valuable is an open hardware design? To answer that question, Dr. Joshua Pearce, an associate professor at Michigan Tech University, analyzed three methods to quantify the value of open hardware design in the latest issue of the journal Modern Economy. The methods are summarized in an article at opensource.com.

An anonymous reader writes: The VFX industry has for most of the last 30 years been reliant on Macs and Windows machines for video editing, primarily because all of the Linux-based FOSS tools have been less than great. This is a shame, because all of the best 3D and 2D tools, other than video, are entrenched in the Linux environment and perform best there. The lack of decent video editing tools on Linux prevents every VFX studio from becoming a Linux-only shop. That being said, there are some strides being made to bridge this gap. What setup do you use? What's still missing?

Jason Baker writes Despite its importance, the GPLv2 has been the subject of very few court decisions, and virtually all of the most important terms of the GPLv2 have not been interpreted by courts. This lack of court decisions is about to change due to the five interrelated cases arising from a dispute between Versata Software, Inc. and Ameriprise Financial, Inc.. These cases are dealing with four important terms in the GPLv2: 1) What are the remedies for breach of the terms of the GPLv2? 2) What is a "distribution" under the GPLv2 that triggers the obligations under the GPLv2? 3) Does the GPLv2 include a patent license? 4) What type of integration between proprietary code and GPLv2 licensed code will result in creating a "derivative work" and subject such proprietary code to the terms of the GPLv2?

Home automation is a recurring topic around here; we've had stories about X-10-based home-brewed systems, a protocol designed for automation, and more than a few Ask Slashdots. Now, an anonymous reader writes OpenMotics is an open source home automation hardware and software system that offers features like switching lights and outputs, multi-zone heating and cooling, power measurements, and automated actions. The system encompasses both open source software and hardware. For interoperability with other systems, the OpenMotics Gateway provides an API through which various actions can be executed. The project was open sourced 2 years ago and was started about 10 years. The choice to open source the project was very conscious: we want to offer a system where users are in full control over their home automation system.

Jason Baker writes Can you really trust your email provider? And even if you self-host your email server, can you really trust its security if you can't see the code? Over on Opensource.com, Olivier Thierry makes three cases for using open source to power your email solution: The power of numbers, the value of trust, and the importance of leverage.

Jason Hibbets writes Jiri Folta was looking for an easy way to have all of his online storage services, such as Google Drive and Dropbox, integrated with his Linux desktop without using any nasty hacks. He shares this solution in this short tutorial, and shows you how to integrate ownCloud with the Gnome desktop and then add your favorite cloud providers to use all of your cloud accounts in one place just as easily as if they were local drives.

jenwike writes: With the success of open source software today, we are seeing organizations undertake more egregious marketing and promotion schemes that exaggerate their participation in, contributions to, and/or licensing of open source software. Their hope is to capitalize on the label of 'open source' and the success that goes along with it. The reality is that the responsibility is on the end-users to review the software and accompanying license to ensure it meets your expectations.

Jason Baker writes: Most everyone is using an open source tool somewhere in their workflow, but relatively few are contributing back their time to sustaining the projects they use. But these days, there are plenty of ways to contribute to an open source project without submitting code. Projects like OpenHatch will even help you match your skill set to a project in need. So what's holding you back? Time? Lack of interest? Difficulty getting started?

Jason Hibbets writes An open source craft brewery in Saint Paul, Minnesota is taking open source beyond sharing recipes. The goal for Tin Whiskers Brewing Company is to "engage and give back to the community by sharing an inside look at opening and operating a craft brewery." In this interview with co-founder George Kellerman, we learn a little more about why the trio of hobbyists who started the brewing company took the path to becoming professional brewers and why they decided to be more open. "The brewery community was extremely helpful and open, so being open ourselves seemed like a great way to honor that," Kellerman said.

Jason Hibbets writes Sharing is winning. In 2015, Creative Commons is expected to pass one billion licensed works under the commons. Millions of creators around the world use CC licenses to give others permission to use their work in ways that they wouldn't otherwise be allowed to. Those millions of users are the proof that Creative Commons works. But measuring the size of the commons has always been a challenge. Until now...

jenwike writes The Open Source Seed Initiative is a passionate group that wants to ensure their seeds are never patented, but making sure seeds are free for use and distribution by anyone isn't as easy as you might think. Part of the equation are plant characteristics, like an extended head on lettuce — is that an invention? Or, would you argue that it is the product of the collective sharing of material that improves the whole crop over time? In this report, one farmer says, "If you're not exchanging germplasm, you're cutting your own throat."

blottsie writes: The Federal Communications Commission will abandon its earlier promise to make a decision on new net neutrality rules this year. Instead, FCC Press Secretary Kim Hart said, "there will not be a vote on open internet rules on the December meeting agenda. That would mean rules would now be finalized in 2015." The FCC's confirmation of the delay came just as President Barack Obama launched a campaign to persuade the agency to reclassify broadband Internet service as a public utility. Opensource.com is also running an interview with a legal advisor at the FCC. He says, "There will be a burden on providers. The question is, 'Is that burden justified?' And I think our answer is 'Yes.'"

First time accepted submitter jenwike writes As Neelie Kroes leaves the office of the European Commission's VP of the Digital Agenda, we need to take a look the new, incoming leadership and ask where they stand on open source software and open standards. The Public Policy Director for Red Hat, Paul Brownell, gives thoughts on the two politicians that President-Elect Junker has named to lead on ICT for the new Commission: former Estonian Prime Minister Andrus Ansip has been named as Vice President for Digital Single Market; and incumbent European Commissioner for Energy Gunther Oettinger (a German politician and lawyer) has been named as Commissioner for Digital Economy and Society.

Czech37 writes Facebook may be among the world's most well-known tech companies, but it's not renowned for being at the forefront of open source. In reality, they have over 200 open source projects on GitHub and they've recently partnered with Google, Dropbox, and Twitter (among others) to create the TODO group, an organization committed to furthering the open source cause. In an interview with Opensource.com, Facebook's James Pearce talks about the progress the company has made in rebooting their open source approach and what's on the horizon for the social media network.

An anonymous reader writes Writing on Opensource.com, Matt Micene shares his thoughts on getting started with an open source project. "I came back from OSCON this year with a new fire to contribute to an open source project. I've been involved in open source for years, but lately I've been more of an enthusiast-evangelist than a hands-on-contributor to an open source community. So, I started some thinking about what to do next. When I was involved in projects before, it was due to a clear progression from user to forum guru to contributor. It's a great path to take but what do you do if you just want to jump into something?" Matt goes on to lay out several steps to help new contributors get started.

Jason Hibbets writes: "There are many solved problems in open source. Groupware is not one of them," Georg Greve, co-founder and CEO of Kolab System starts off his post highlighting recent features of the latest release of the Kolab groupware project. He calls out a few newly elected politicians that don't like the current set-up, but says that thousands of users don't have the same experience. "Until today, the city of Munich is using the same stand-alone calendaring and email systems it had used when it was still fully operating on Windows. Updating these systems had a lower priority than the migration to LiMux then. But an upgrade is underway now. And, the solution they chose is agnostic to the desktop platform and will service LiMux and Windows alike. The primary difference made by another migration would likely be due to the perils that come with any migration, such as additional costs and delays. In other words: The very problem used to criticize the LiMux desktop is already being solved."

Czech37 writes SELinux lead Dan Walsh wrote last month that Docker "containers do not contain" and that the host system isn't completely protected. Today, Walsh details the steps that Docker, Red Hat, and the open source community are taking to make Docker more secure: "Basically, we want to put in as many security barriers to break out as possible. If a privileged process can break out of one containment tool, we want to block them with the next. With Docker, we are want to take advantage of as many security components of Linux as possible. If "Docker" isn't a familiar word, the project's website is informative; the very short version is that it's a Linux-based "open platform for developers and sysadmins to build, ship, and run distributed applications"; Wikipedia has a good explanation, too.

Czech37 writes SELinux lead Dan Walsh wrote last month that Docker "containers do not contain" and that the host system isn't completely protected. Today, Walsh details the steps that Docker, Red Hat, and the open source community are taking to make Docker more secure: "Basically, we want to put in as many security barriers to break out as possible. If a privileged process can break out of one containment tool, we want to block them with the next. With Docker, we are want to take advantage of as many security components of Linux as possible. If "Docker" isn't a familiar word, the project's website is informative; the very short version is that it's a Linux-based "open platform for developers and sysadmins to build, ship, and run distributed applications"; Wikipedia has a good explanation, too.

New submitter Jason Baker writes: With the rise of Docker containers as an alternative for deploying complex server-based applications, one might wonder, does the operating system even matter anymore? Certainly the question gets asked periodically. Gordon Haff makes the argument on Opensource.com that the operating system is still very much alive and kicking, and that a hardened, tuned, reliable operating system is just as important to the success of applications as it was in the pre-container data center.

lrosen (attorney Lawrence Rosen) writes with a response to an article that appeared on Opensource.com late last month, detailing a court case that arose between Versata Software and Ameriprise Financial Services; part of the resulting dispute hinges on Versata's use of GPL'd software (parsing utility VTD-X, from Ximpleware), though without acknowledging the license. According to the article's author, attorney Aaron Williamson (former staff attorney for the Software Freedom Law Center), "Lawyers for commercial software vendors have feared a claim like this for essentially the entire 20-odd-year lifetime of the GPL: a vendor incorporates some GPL-licensed code into a product—maybe naively, maybe willfully—and could be compelled to freely license the entire product as a result. The documents filed by Amerprise in the case reflect this fearful atmosphere, adopting the classically fear-mongering characterization of the GPL as a 'viral' license that 'infects' its host and 'requires it to become open source, too.'" Rosen writes: I want to acknowledge Aaron's main points: This lawsuit challenges certain assumptions about GPLv2 licensing, and it also emphasizes the effects of patents on the FOSS (and commercial) software ecosystem. I also want to acknowledge that I have been consulted as an expert by the plaintiff in this litigation (Ximpleware vs. Versata, et al.) and so some of what I say below they may also say in court. Read on for the rest (and Williamson's article, too, for a better understanding of this reaction to it). An important take-away: it's not just the license that matters.

Let's be open about the facts here. Ximpleware worked diligently over many years to create certain valuable software. The author posted his source code on SourceForge. He offered the software under GPLv2. He also offered that software under commercial licenses. And he sought and received and provided notice of United States patent claims related to that software.

Unbeknownst to Ximpleware, Versata took that GPLv2 software and incorporated it into Versata products – without disclosing that GPLv2 software or in any other way honoring the terms of the GPLv2 license. The reason Ximpleware became aware of that GPLv2 breach is because some months ago Versata and one of its customers, Ameriprise, became embroiled in their own litigation. The breach of GPLv2 came out during discovery.

Ximpleware has terminated that license as to Versata. This is exactly what the Software Freedom Conservancy and others do when confronted by GPL breaches.

That earlier litigation is between two (or more) commercial companies; it is not a FOSS problem. These are mature, sophisticated, profitable companies that have the wherewithal to protect themselves. I know in my own law practice, whether I represent software vendors or their commercial customers, we typically provide for some level of indemnification. Perhaps Ameriprise and the other customer-defendants can count on Versata defending them against Ximpleware. Such a commercial dispute between big companies – even if it involves the GPLv2 software of a small company and separate indemnification for copyright or patent infringement – is between them alone.

But as to Ximpleware and its GPLv2 copyrighted and patented software, there are a few misunderstandings reflected in Aaron Williamson's article:

1. The notion of "implied patent licensing" has no clear legal precedent in any software licensing. While it is true that goods one purchases include a patent license under what is known as the "exhaustion doctrine," there is no exhaustion of patented software when copies are made (even though copying of the software itself is authorized by GPLv2). For example, a typical commercial patent license nowadays might include a royalty for each Android phone manufactured and sold. Companies that distribute Android phones and its FOSS software acquire patent licenses so recipients of their phones are indeed free to use those phones. But that isn't because of some implied patent licenses that come with Android software, but because commercial companies who distribute phones pay for those patent rights, directly or indirectly. I think it is entirely reasonable to require commercial companies to get their patent licenses in writing.

2. Versata's customers who received the (in breach!) GPLv2 software all moved to dismiss Ximpleware's infringement claims against them, pointing to Section 0 of GPLv2, which says, "[t]he act of running the Program is not restricted." What that sentence actually means is just what it says: The GPLv2 copyright grant itself (which is all there is in GPLv2) does not restrict the act of running the program. Nor could it; that is a true statement because running a program is not one of the enumerated copyright rights subject to a copyright license (17 USC 106). The authors of the GPL licenses have themselves made that argument repeatedly: The use of software is simply not a copyright issue.

3. Because there are U.S. patent claims on this Ximpleware software, Section 7 of GPLv2 prohibits its distribution under that license in the United States (or any jurisdictions where patent claims restrict its use). If Ameriprise and the other defendants were outside the U.S. where the Ximpleware patents don't apply, then GPLv2 would indeed be sufficient for that use. But inside the U.S. those customers are not authorized and they cannot rely on an assumed patent grant in GPLv2. Otherwise GPLv2 Section 7 would be an irrelevant provision. Reread it carefully if you doubt this.

The Versata customers certainly cannot depend on an implied patent license received indirectly through a vendor who was in breach of GPLv2 since the beginning – and still is! Versata ignored and failed to disclose to its own customers Ximpleware's patent notices concerning that GPLv2 software, but those patents are nevertheless infringed.

Should we forgive commercial companies who fail to undertake honest compliance with the GPL? Should we forgive their customers who aren't diligent in acquiring their software from diligent vendors?

As Aaron Williamson suggests, we shouldn't ignore the implications of this case. After all, the creator of Ximpleware software made his source code freely available under GPLv2 and posted clear notices to potential commercial customers of his U.S. patents and of his commercial licensing options. Lots of small (and large!) open source commercial companies do that. Although it is ultimately up to the courts to decide this case, from a FOSS point of view Ximpleware is the good guy here!

There is rich detail about this matter that will come out during litigation. Please don't criticize until you understand all the facts.

------------------------------------------

Lawrence Rosen
Rosenlaw & Einschlag (lrosen@rosenlaw.com)"

ectoman (594315) writes Opensource.com has a summary of an interview with Michael Tiemann, co-founder of Cygnus Solutions and one of the world's first open source entrepreneurs. Now VP of Open Source Affairs at Red Hat, Tiemann offers an historical perspective on what makes open source businesses successful, and shares how he dealt with the open source movement's early skeptics. "A lot of the skepticism is a response to the abstract; it's a response to the unknown," Tiemann says, "And when you bring a concrete success story with just absolutely stellar credentials that doesn't just outperform the field, but embarrasses the field, then the skeptics begin to look like they're on the wrong side." The full audio interview on Hacker Public radio (~1 hour).

ectoman writes: Opensource.com is running an interview with Jennifer Davidson of ChickTech, a non-profit organization whose mission is to create communities of support for women and girls pursuing (or interested in pursuing) careers in tech. "In the United States, many girls are brought up to believe that 'girls can't do math' and that science and other 'geeky' topics are for boys," Davidson said. "We break down that idea." Portland, OR-based ChickTech is quickly expanding throughout the United States—to cities like Corvallis and San Francisco—thanks to the "ChickTech: High School" initiative, which gathers hundreds of young women for two-day workshops featuring open source technologies. "We fill a university engineering department with 100 high school girls—more girls than many engineering departments have ever seen," Davidson said. "The participants can look around the building and see that girls from all backgrounds are just as excited about tech as they are."

ectoman (594315) writes The U.S. Supreme Court issued a groundbreaking decision concerning software patents, claiming that abstract ideas are not by themselves patentable. The ruling was a cause for celebration among those opposed to software patent abuse, like Red Hat's Vice President and Assistant General Counsel, Rob Tiller. Here, Tiller analyzes and offers some context for the Court's ruling, which "uses the traditional common law methodology of comparing one case to previous similar cases and harmonizing with those most similar."

ectoman (594315) writes Proponents of patent reform in the United States glimpsed a potential victory late last year, when the House of Representatives passed H.R. 3309, the Innovation Act, designed to significantly mitigate patent abuse. Just months ago, however, the Senate pulled consideration of the bill. And since then, patent reform has been at a standstill. In a new analysis for Opensource.com, Mark Bohannon, Vice President of Corporate affairs and Global Public Policy at Red Hat, explains three reasons why. "For this year, at least," he writes, "the prospect of addressing abusive patent litigation through Congressional action is on ice"—despite the unavoidable case for reform.

ectoman (594315) writes Proponents of patent reform in the United States glimpsed a potential victory late last year, when the House of Representatives passed H.R. 3309, the Innovation Act, designed to significantly mitigate patent abuse. Just months ago, however, the Senate pulled consideration of the bill. And since then, patent reform has been at a standstill. In a new analysis for Opensource.com, Mark Bohannon, Vice President of Corporate affairs and Global Public Policy at Red Hat, explains three reasons why. "For this year, at least," he writes, "the prospect of addressing abusive patent litigation through Congressional action is on ice"—despite the unavoidable case for reform.

New submitter Czech37 (918252) writes "If you work in an organization that isn't focused on development, where computer systems are used to support other core business functions, getting management buy-in for the use of open source can be tricky. Here's how an academic librarian negotiated with his management to get them to give open source software a try, and the four phrases he recommends you avoid using." "Open Source," "Free [Software]," "Contribute," and "Development" appear to scare managers away.

Phil Shapiro often loans his Chromebook to patrons of the public library where he works. He says people he loans it to are happily suprised at how fast it is. He wrote an article earlier this month titled Teachers unite to influence computer manufacturing that was a call to action; he says that if 20,000 teachers demand a simple, low-cost Chromebook appliance -- something like a Chrome-powered Mac mini with a small SSD instead of a hard drive, and of course without the high Mac mini price -- some computer manufacturer will bite on the idea. Monitors? There are plenty of used ones available. Ditto speakers and keyboards, not that they cost much new. The bottom line is that Phil believes Chromebooks, both in their current form factor and in a simpler one, could be "the" computer for schools and students. Maybe so, not that Android tablets are expensive or hard to use. And wait! Isn't there already a Chromebox? And even a Chromebase all-in-one Chrome-based desktop? In any case, Chrome-based computers look pretty good for schools and libraries, especially if and when prices for the simplest members of the family get down to where Phil thinks they should be. (Alternate video link)

Phil Shapiro often loans his Chromebook to patrons of the public library where he works. He says people he loans it to are happily suprised at how fast it is. He wrote an article earlier this month titled Teachers unite to influence computer manufacturing that was a call to action; he says that if 20,000 teachers demand a simple, low-cost Chromebook appliance -- something like a Chrome-powered Mac mini with a small SSD instead of a hard drive, and of course without the high Mac mini price -- some computer manufacturer will bite on the idea. Monitors? There are plenty of used ones available. Ditto speakers and keyboards, not that they cost much new. The bottom line is that Phil believes Chromebooks, both in their current form factor and in a simpler one, could be "the" computer for schools and students. Maybe so, not that Android tablets are expensive or hard to use. And wait! Isn't there already a Chromebox? And even a Chromebase all-in-one Chrome-based desktop? In any case, Chrome-based computers look pretty good for schools and libraries, especially if and when prices for the simplest members of the family get down to where Phil thinks they should be. (Alternate video link)

Lemeowski (3017099) writes "In a time where there's a 'gold rush' for 3D printing patents, there's one company that's doing everything it can to keep its 3D printers as open as possible. Jeff Moe, CEO of Aleph Objects, said in an interview with Opensource.com that his company's strategy is 'to not patent anything, but to establish prior art as soon as we can. So when we develop things we try to push it out there as soon as possible and hope to establish prior art if there isn't prior art already. That allows us to develop a lot more quickly.' The company makes the Lulzbot 3D printers, and goes to the extreme of publishing every last detail about its printers, Moe said, including syncing its internal file system that it uses to share files on the development of the machine to the public every hour so you can see what they're doing."

An anonymous reader writes "Following one of the best descriptions ever of a hacker I've ever seen, Pete Herzog, creator of the 'security testing' (professional hacking) manual OSSTMM outlines compelling reasons why the traits of the hacker should be taught in school to make better students and better people. It starts out with 'Whatever you may have heard about hackers, the truth is they do something really, really well: discover.' and it covers open education, teaching kids to think for themselves, and promoting hacking as a tool for progress." A good read, despite confusing hacker and hacker a bit. I remember getting to set up Debian on a scrap machine in high school, only to have county IT kill the project because of the horrible danger experimentation could have proven to the network...

Do you remember the worries about getting different health care software systems to work with each other as health care providers starting moving away from paper? It's still a problem, but Joanne Rohde's company, Axial Exchange, is working to cure that problem not only as an entrepreneur but also because she has personal reasons to see health care providers communicate better with each other. In a 2012 interview for Huffington Post, she said, "While I was working for Red Hat, I got very sick... I ultimately had to go to 10 doctors to be diagnosed. Going from doctor to doctor, I could not believe I had to start over each time. No one actually talks to each other I became convinced that if I had had all the information, I probably would have been able to figure it out faster." In fact, Joanne got so sick that she quit her job as Red Hat COO after four years with the company. Once she started getting decent treatment for her Fybromyalgia and started getting better, she decided to apply open source principles to health care IT -- and to start a new company to do it. Opensource.com talked with Joanne in September 2013, and in January 2014 she talked with Health Care Finance News for an article titled Patients key to reducing readmissions. A phrase Joanne seems to be using a lot lately is "patient engagement," which has become a major part of Axial Exchange's work to improve communications not only between different health care providers but also between those providers and their patients. Update: 02/05 20:16 GMT by T : If you're seeing this post on beta.slashdot.org, note that we're still ironing out the details of video display here. You can view the video on tv.slashdot.org, instead. Please pardon our dust.

New submitter Jason Baker writes "It seems like a perennial question: 'How do we get more women involved in tech?' The open source community, like any other part of the technology industry, is grappling with finding solutions that are more than just talking the talk of diversity, but actually make some demonstrable difference in the numbers. While there have been numerous success stories, the gender gap is still rampant. The answer, at least to one freelance entrepreneur, is providing strong role models of women using open source to have fun and make money. But is that enough to make a difference?"

New submitter Jason Baker writes "It seems like a perennial question: 'How do we get more women involved in tech?' The open source community, like any other part of the technology industry, is grappling with finding solutions that are more than just talking the talk of diversity, but actually make some demonstrable difference in the numbers. While there have been numerous success stories, the gender gap is still rampant. The answer, at least to one freelance entrepreneur, is providing strong role models of women using open source to have fun and make money. But is that enough to make a difference?"

Lemeowski writes "Honeybees are disappearing at an alarming rate, with a third of U.S. honeybees vanishing last year. Since bees pollinate many fruits and vegetables, the disappearance of honeybees could cause the United States to lose $15 billion worth of crops, and even change the American diet. The honey bee disappearance is called Colony Collapse Disorder, a serious problem of bees abruptly leaving their hives. A new open source effort called the Open Source Beehives project hopes to help by creating "a mesh network of data-generating honey bee colonies for local, national, and international study of the causes and effects of Colony Collapse Disorder." Collaborators have created two beehive designs that can be downloaded for free and milled using a CNC machine, then filled with sensors to track bee colony health."

Lemeowski writes "Time has been good to Linux and the kernel community, with the level of participation and volume of activity reaching unprecedented levels. But as core Linux kernel developers grow older, there's a very real concern about ensuring younger generations are getting involved. In this post, Open Access supporter Luis Ibanez shares some exciting stats about recent releases of the Linux kernel, but also warns that 'Maintaining the vitality of this large community does not happen spontaneously. On the contrary, it requires dedication and attention by community members on how to bring new contributors on board, and how to train them and integrate them alongside the well-established developers.'"

Lemeowski writes "Open source software projects are seeing some success on fundraising sites like Kickstarter and Indiegogo. But Warren Konkel believes open source software needs a better funding model that's more aligned with how software is built. So Konkel, who was the first hire at LivingSocial, teamed up with his friend David Rappo, a producer for games including Guitar Hero and Skylander, and founded Bountysource, a crowdfunding and bounty site specifically designed to help developers raise money for their OSS projects, bug fixes and feature requests. In this interview, Konkel talks about how he recently snagged a $1.1 million investment in Bountysource, gives developers tips on launching a fundraising effort for their OSS project, and more."

Lemeowski writes "Game studios go to great lengths to protect their IP. But board game designer Daniel Solis doesn't subscribe to that philosophy. He has spent the past ten years blogging his game design process, posting all of his concepts and prototypes on his blog. Daniel shares four things he's learned after designing games in public, saying paranoia about your ideas being stolen "is just an excuse not to do the work." His article provides a solid gut check for game designers and other creatives who may let pride give them weird expectations."

Lemeowski writes "Cygnus Solutions co-founder Michael Tiemann takes an in-depth look at whether music can truly ever be open source. Leaning on his personal experiences of trying to convince the market that a company that provided commercial support for free software could be successful, Tiemann argues that similar to how 'the future of software was actually waiting for the fuller participation of users ... so, too, is the future of the art of music.' In his essay, Tiemann makes a case for open source music, from licensing for quality recordings to sheet music with notes from the original composer in an easy-to-reuse format, and he offers ways to get involved in making music open source." Apropos open source music, reader rDouglass adds a link to the Open Goldberg Variations project, last mentioned on Slashdot in 2012.

New submitter Lemeowski writes "Critics have been pounding GitHub recently, claiming it is hosting tons of code with no explicit software license. The debate was thrust into the limelight last year when James Governor of RedMonk issued an acclaimed tweet about young developers being 'about POSS — post open source software,' meaning they disliked or avoided licensing and governance. Red Hat's IP attorney Richard Fontana explores the complaint saying there is a positive aspect of the POSS and GitHub phenomenon: Developers are, for the first time in the history of free software, helping inform each other about licensing and aiding in the selection process. The result is that it's becoming easier to suggest legal improvements to GitHub-hosted repositories."

ectoman writes "This week, a coalition of more than 40 companies sent a letter to Congress asking for legislation that expands the Covered Business Method (CBM) program, a move some feel would stem patent abuse in the United States. Expanding the scope of CBM—a program that grants the Patent and Trademark Office the power to challenge the validity of certain business methods patents—would expedite the patent review process and significantly cut litigation costs, they say. "The vague and sweeping scope of many business method claims covering straight forward, common sense steps has led to an explosion of patent claims against processes used every day in common technologies by thousands of businesses and millions of Americans," says the letter, signed by companies like Amazon, Netflix, Red Hat, Macy's, and Kroger)."

jrepin writes "Around a year ago, a school in the southeast of England, Westcliff High School for Girls Academy (WHSG), began switching its student-facing computers to Linux, with KDE providing the desktop software. The school's Network Manager, Malcolm Moore, contacted us at the time. Now, a year on, he got in touch again to let us know how he and the students find life in a world without Windows." And they didn't even meet much resistance: "Younger students accept it as normal. Older students can be a little less flexible. There are still a few that are of the view that I can get rid of Microsoft Word when I can pry it from them. Staff are the same (although it is surprisingly not age-related). Some are OK and some hate it. Having said that, an equal number hate Windows 7 and nobody liked Windows 8. I think the basic problem is that Windows XP is a victim of its own success. It works fairly well from a user point of view, it's been around practically forever, and people don't like change, even some students, oddly."

ectoman writes "Are firms responsible for GPL violations on code they receive from third parties? A German court thinks so. The Regional Court of Hamburg recently ruled that Fantec, a European media player maker, failed to distribute 'complete corresponding source code' for firmware found in some of its products. Fantec claims its third-party firmware supplier provided the company with appropriate source code, which Fantext made available online. But a hackathon organized by the Free Software Foundation Europe discovered that this source code was incomplete, and programmer Harald Welte filed suit. He won. Mark Radcliffe, an IP expert and senior partner at DLA Piper who specializes in open source licensing issues, has analyzed the case—and argued that it underscores the need for companies to implement internal GPL compliance processes. 'Fantec is a reminder that companies should adopt a formal FOSS use policy which should be integrated into the software development process,' he writes. 'These standards should include an understanding of the FOSS management processes of such third-party suppliers. The development of a network of trusted third-party suppliers is critical part of any FOSS compliance strategy.'"

ectoman writes "Are firms responsible for GPL violations on code they receive from third parties? A German court thinks so. The Regional Court of Hamburg recently ruled that Fantec, a European media player maker, failed to distribute 'complete corresponding source code' for firmware found in some of its products. Fantec claims its third-party firmware supplier provided the company with appropriate source code, which Fantext made available online. But a hackathon organized by the Free Software Foundation Europe discovered that this source code was incomplete, and programmer Harald Welte filed suit. He won. Mark Radcliffe, an IP expert and senior partner at DLA Piper who specializes in open source licensing issues, has analyzed the case—and argued that it underscores the need for companies to implement internal GPL compliance processes. 'Fantec is a reminder that companies should adopt a formal FOSS use policy which should be integrated into the software development process,' he writes. 'These standards should include an understanding of the FOSS management processes of such third-party suppliers. The development of a network of trusted third-party suppliers is critical part of any FOSS compliance strategy.'"

ectoman writes "In a recent policy speech, Federal Trade Commission Chairwoman Edith Ramirez indicated that the FTC might be preparing to seriously address patent abuse in the United States. Mark Bohannon, Vice President of Corporate Affairs and Global Public Policy at Red Hat, has reviewed Ramirez's remarks, calling them 'some of the most direct and specific to date from a senior U.S. Government official regarding "harmful PAE [patent assertion entities] activities."' Bohannon writes that the FTC's proposed roadmap for patent reform 'is both ambitious and doable,' and he discusses how the agency could make its potential contributions to reforms most effective. The piece arrives one week after Bohannon analyzed other patent reform efforts currently ongoing in Washington—in a piece Slashdot readers have been discussing."

ectoman writes "In a recent policy speech, Federal Trade Commission Chairwoman Edith Ramirez indicated that the FTC might be preparing to seriously address patent abuse in the United States. Mark Bohannon, Vice President of Corporate Affairs and Global Public Policy at Red Hat, has reviewed Ramirez's remarks, calling them 'some of the most direct and specific to date from a senior U.S. Government official regarding "harmful PAE [patent assertion entities] activities."' Bohannon writes that the FTC's proposed roadmap for patent reform 'is both ambitious and doable,' and he discusses how the agency could make its potential contributions to reforms most effective. The piece arrives one week after Bohannon analyzed other patent reform efforts currently ongoing in Washington—in a piece Slashdot readers have been discussing."