From a consumer perspective, I'd like open source to be ubiquitous to the point of invisibility. Using recent Ubuntu distros, I'm always shocked at how professional the environment feels. Just five years ago, you'd need to hunt down drivers and do a bunch of fiddling to get basic things like a sound card working. Now there are so many pushbutton ways to deploy open source tech, from OSes to CMS distros on Pantheon to buying an Android-powered mobile phone.
We're not quite to the point where CMS users can feel like open source is transparent; there's still a huge investment in vendors to give you the expertise to manage your Drupal or WordPress site, for example. But we're closer than we were a decade ago, and that's pretty exciting.
Dustin Kirkland, from Canonical's Ubuntu Product and Strategy team, told me in a long interview at LinuxCon, "We are really steamrolling towards a GA release of Ubuntu on z Systems. Users of z Series systems are the types that buy hardware for 5 and 10 years and that lines up very well with our LTS of Ubuntu.” He also said they need to do some work on tool chain to ensure they have components like gclib libraries on all of the compilers, including other bits such as Perl, PHP, Ruby, Python, etc., which are needed to build the Ubuntu universe. Users will start seeing that work coming out later this year and alpha/beta builds of Ubuntu in early 2016.
LinuxCon exclusive: Mark Shuttleworth says Snappy was born long before CoreOS and the Atomic ProjectSubmitted by Roy Schestowitz on Friday 21st of August 2015 10:21:12 PM Filed under
That guy is a Chicagoan named Kevin Barry. Barry got started doing indie-level Android development while still working for someone else as a software developer during the day. He eventually started making more money with his early Android efforts than he was making with his "real" job -- and thus, TeslaCoil Software was born. (Little known fact: TeslaCoil is named after Barry's cat, Tesla -- who was named after a certain Nikola who also bore that name.)
It has never even been a serious contender in the race. In my opinion, most TTS applications in Linux have remained in hobbyist mode since inception. And I'm sure that statement will chap the ass of many, but a simple comparison between all of the Linux programs using TTS vs. Mac, Windows, and even the mobile market will bear me out. Hopefully we can raise enough awareness to at least see some forward movement on TTS in Linux. Hopefully.
We had the chance to interview Lance Albertson, the director of Open Source Lab (OSL) at Oregon State University (OSU), who is at LinuxCon this year to speak about what they do to help their students bridge this skill gap and how they work with open source projects to train the next generation of people who will keep the Internet running.
Open source communities have been paving the way for innovation for years, and recently they've been paving the way for diversity in the IT fields, too. For some women, the way into technology was clear and well-lit. Others faced harsh criticism from their families, friends, and society. Thankfully, open source communities are creating a level playing field, enabling women from all over the world to learn, contribute, and make their mark in technology.
Alicia Gibb has a passion for hardware hacking—she founded and is currently running the Open Source Hardware Association (OSHWA). Also a member of the ADA Initiative Board, Defensive Patent License Board, and the Open Source Ecology Board, she got her start as a technologist from a combination of backgrounds: informatics and library science.
Alicia formerly worked as a researcher and prototyper at Bug Labs where she ran the academic research program and the R&D lab. Her work is fascinating and she graciously agreed to this interview.
The second part is of this question is why these issues are especially important for the open source community. Accessibility gets to the vary core of what open source means. If we really want to make software that is freely available for people to use, share, improve and modify, we have to make sure that that software doesn't exclude some people because it is inaccessible. That defeats the core purpose of open source. As a side benefit, accessible software is software more people can use, and if you can have more people working on your project, your project will be better for it.