The Compiler That Changed the World Turns 25

Last year, Linux celebrated its 20th anniversary. The kernel that Linus Torvalds started as a hobby project helped the Internet bloom, challenged proprietary operating system dominance, and powers hundreds of millions of devices. From hacker toys like the dirt-cheap Raspberry Pi to most of the Top 500 Supercomputers, Linux dominates the computing industry. But it wouldn't have been possible without GCC, which turns 25 today.

Before Torvalds started hacking away on Linux, Richard Stallman and started the GNU (GNU's Not UNIX) project and part of that was the GNU C Compiler (GCC). Eventually that became the GNU Compiler Collection (also GCC) but we're getting a little ahead of the story.

A Short History of GCC and Linux

The origin of GCC actually started in the free C compiler that Stallman started in 1984, based on a multi-platform compiler developed at Lawrence Livermore Lab. Says Stallman, "It supported, and was written in, an extended version of Pascal, designed to be a system-programming language. I added a C front end, and began porting it to the Motorola 68000 computer. But I had to give that up when I discovered that the compiler needed many megabytes of stack space, and the available 68000 Unix system would only allow 64k.

"I then realized that the Pastel compiler functioned by parsing the entire input file into a syntax tree, converting the whole syntax tree into a chain of "instructions", and then generating the whole output file, without ever freeing any storage. At this point, I concluded I would have to write a new compiler from scratch. That new compiler is now known as GCC; none of the Pastel compiler is used in it, but I managed to adapt and use the C front end that I had written."

For many Linux enthusiasts, GCC has always just been. It's part of the landscape, and kind of taken for granted. But it wasn't always this way. Michael Tiemann, now vice president of open source affairs at Red Hat and the founder of Cygnus Solutions, called GCC's intro in 1987 a "bombshell."

"I downloaded it immediately, and I used all the tricks I'd read about in the Emacs and GDB manuals to quickly learn its 110,000 lines of code. Stallman's compiler supported two platforms in its first release: the venerable VAX and the new Sun3 workstation. It handily generated better code on these platforms than the respective vendors' compilers could muster... Compilers, Debuggers, and Editors are the Big 3 tools that programmers use on a day-to-day basis. GCC, GDB, and Emacs were so profoundly better than the proprietary alternatives, I could not help but think about how much money (not to mention economic benefit) there would be in replacing proprietary technology with technology that was not only better, but also getting better faster."

By the time Torvalds started working on Linux, GCC had quite a history of releases. The first release was 0.9, the first beta release, on March 22, 1987. It had 48 releases between the 0.9 release and 1.40, which came out on June 1, 1991. Torvalds announced that he was working on Linux in July 1991, using Minix and GCC 1.40.

The EGCS Years

As Tiemann notes later, GCC development started falling behind a bit. Some folks got a bit impatient with the GCC development process and speed of getting features to users. GCC had a number of forks in the wild with patches that hadn't made it into GCC. That led to the EGCS project, a fork of a GCC development snapshot from August 1997.

Eventually, in April 1999, EGCS became the official GCC, and GCC took on the "GNU Compiler Collection" moniker.

New in GCC 4.7

I won't try to summarize all of the development and features that have been part of GCC from 1999 to now. Suffice it to say, a lot has happened and GCC has been at the heart of more than Linux.

GCC has also been used by FreeBSD, NetBSD, and OpenBSD as well as part of Apple's XCode tools until very recently. (That's another story for another day...) If it's hard to imagine a world without Linux, it's even harder to imagine a world without the compiler that's been used to build Linux for more than 20 years.

So it's appropriate that the 25th anniversary release of GCC brings quite a bit of goodies for developers. According to Richard Guenther, 4.7 is a "major release, containing substantial new functionality not available in GCC 4.6.x or previous GCC releases."

Says Guenther, GCC 4.7 picks up support for newer standards for C++, C, and Fortran. "The C++ compiler supports a bigger subset of the new ISO C++11 standard such as support for atomics and the C++11 memory model, non-static data member initializers, user-defined literals, alias-declarations, delegating constructors, explicit override and extended friend syntax. The C compiler adds support for more features from the new ISO C11 standard. GCC now supports version 3.1 of the OpenMP specification for C, C++ and Fortran."

GCC also expands its hardware support, with new support for Intel's Haswell and AMD's Piledriver (both x86) architectures. It also adds support for the Cortex-A7 (ARM) line of processors, and for a number of others. Check out the full list of change for 4.7 if you're interested.

For fun and added points, check out this video on YouTube that visualizes 20 years of GCC development. It uses Gource to visualize the history of GCC development.

A big tip of the hat to the GCC team, present, past, and future. Without it, where would we be now?

This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.

The Ever-Changing Linux Skillset

Just because you had what it takes for a good Linux-related job a decade ago, it doesn't mean that you have what it takes today. The Linux landscape has changed a lot, and the only thing that's really stayed constant is that a love of learning is a requirement.

What employers want from Linux job seekers is a topic I've spent a lot of time thinking about, but this post by Dustin Kirkland got me to thinking about just how drastically things have changed in a very short time. The skills that were adequate for a good Linux gig in 2002 may not be enough to scrape by today.

This isn't only true for Linux administrators, of course. If you're in marketing or PR, for example, you probably should know a great deal about social networks that didn't even exist in 2002. Journalists that used to write for print publications are learning to deal with Web-based publications, which often includes expanding to video and audio production. (Not to mention an ever-shrinking number of newspapers to work for...) Very few skilled jobs have the same requirements today as they did 10 years ago.

But if you look back at the skills needed for Linux admins and developers about ten years ago, and now, it's amazing just how much has changed. Kirkland, who's the chief architect at Gazzang, says that he's hired more than a few Linux folks in that time. Kirkland worked at IBM and Canonical before Gazzang, and says that he's interviewed "hundreds" of candidates for dozens of developer, engineer and intern jobs.

Over the years, Kirkland says that the "poking and prodding of a given candidate's Linux skills have changed a bit." What he's mostly looking for is the "candidate's inquisitive nature" but the actual skills he touches on give some insight as well.

Ten years ago, and Kirkland says that he'd want to see candidates who were familiar with the LAMP stack. Nine years ago, and Kirkland says that he'd look for candidates who "regularly compiled their own upstream kernel, maybe tweaked a few configuration options on or off just for fun." (If you've been using Linux this long, odds are you have compiled your own kernels quite a bit.)

Basically, a decade ago, you were looking at folks working with individual machines. In a lot of environments, you could apply what you knew from working with a few machines at home to a work environment. That didn't last.

Six years ago, Kirkland says that he was looking "for someone who had built their own Beowulf cluster, for fun, over the weekend. If not Beowulf, then some sort of cluster computing. Maybe Condor, or MPICH."

Not long after that, Kirkland says that he was looking for experience with open source virtualization – KVM, Xen, QEMU, etc. Three years ago, and Kirkland says that he wanted developers with Launchpad or GitHub accounts. Note that would have required early adopters on behalf of GitHub, since the site had only launched in 2008. Git itself was first released in 2005, but it took a few years before really catching on.

Two years ago? Clustering and social development alone weren't enough. Kirkland says that he was looking for folks using cloud technologies like Eucalyptus. (He also mentions OpenStack, but two years ago the number of people who'd actually been using OpenStack would have been fairly negligible since it was only announced in the summer of 2010..)

Finally, the most recent addition to the list is "cloud-ready service orchestration," which translates to tools like Puppet, Chef, or Juju.

Even that's not enough. What's next? Kirkland says that he's looking for folks who've rooted their phones, tried out big data and thrown together "a map-reduce Hadoop job or two, just for grins."

Naturally, this is just a snapshot of what one interviewer considers important. Kirkland's list of topics may or may not mirror what you'd get in an interview with any other company, but the odds are that you'll see something similar. His post illustrates just how much the landscape has changed in a short time, and the importance of keeping up with the latest technology.

If you're a job seeker, it means a lot of studying. If you're already employed, it means that you should be keeping up with these trends even if you're not using them in your work environment. If you're an employer, it means you should be investing heavily in Linux training and/or finding ways to help your staff stay current.

Even if you're a big data-crunching, cloud computing, GitHub-using candidate, the odds are that next year you'll need to be looking at even newer technology. From the LAMP stack to OpenStack, and beyond, things are not standing still. The one job skill you'll always need is a love of learning.

This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.

As Data Grows, So Grows Linux

IDC recently announced its numbers for 2011 Q4 servers sales: overall server revenues are up for the year 5.8 percent, and shipments are up 4.2 percent. As The Reg reports, these shipment numbers are back to pre-recession levels.

What’s more interesting, though, is the trends that emerge from the very latest reporting quarter, Q4. Linux was the only operating system that saw a revenue increase in servers Q4, with a 2.2 percent rise. Windows lost 1.5 percent and Unix 10.7 percent.

IDC attributes some of that Linux success to its role in what the analyst firm calls “density-optimized” machines, which are really just white box servers, and are responsible for a lot of the growth in the server market. These machines have gained popularity in a space still squeezed on budget and that continues to be commoditized. But there are other factors at play for Linux’s success over its rivals.

Coming out of the recession, Linux is in a very different position than it was 10 years ago when we emerged from the last bubble. Today it's mature, tried, tested and supported by a global community that makes up the largest collaborative development project in the history of computing.

Our latest survey of the world’s largest enterprise Linux users found that Total Cost of Ownership, technical superiority and security were the top three drivers for Linux adoption. These points support Linux’s maturity and recent success. Everyone is running their data centers with Linux. Stock exchanges, supercomputers, transportation systems and much more are using Linux for mission-critical workloads.

Also helping Linux’s success here is the accelerated pace by which companies are migrating to the cloud. Long a buzzword, the cloud is getting real, right now. While there is still work to do for Linux and the cloud, there is no denying its dominant role in today’s biggest cloud companies: Amazon and Google to name just two.

The mass migration to cloud computing has been quickened due, in part, to the rising level of data: both the amount of data enterprises are dealing with but the also how fast that data is growing. IDC this week predicted that the “Big Data” business will be worth $16.9B in three years. There is a huge opportunity here for Linux vendors. Our Linux Adoption Trends report, shows that 72 percent of the world’s largest Linux users are planning to add more Linux servers in the next 12 months to support the rising level of data in the enterprise. Only 36 percent said they would be adding more Windows servers to support this trend.

The enterprise server market is a strong area for Linux, but it’s an incredibly competitive market. Together we’ll continue to advance Linux to win here. In fact, we’ll be meeting at the NYSE offices in April at our Annual Linux Foundation Enterprise End User Summit where some of the world’s largest companies will talk in depth about exactly the things I’ve touched on here.

Yet again we are seeing market winners are born from collaboration. And we have the numbers to back it up.

This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.

Dream Studio 11.10: Upgrade or Hands Off?

Many Linux distributions specialized for multimedia distributions have come and gone. Some were pretty good, but Dream Studio has outshone them all. Musician and maintainer Dick Macinnis has just released Dream Studio 11.10, based on Ubuntu Oneiric Ocelot. Dream Studio 11.04 is a tough act to follow – is it worth upgrading to 11.10?

Chasing Ubuntu

Basing a custom distribution on Ubuntu has a lot of advantages, but it also means chasing a fast-moving target. There are ways to minimize the pain, as Macinnis explains. "The decision to create different versions of Dream Studio is one I had made quite a while ago, and is one of the reasons I decided to get all my packages into PPAs rather than on a personally hosted repo."

PPAs are Personal Package Archives hosted on Canonical's Launchpad. This is a slick way to make third-party package repositories available in a central location. Ever wonder what goes into making your own Linux distribution? Even when you base it on another distro like Ubuntu it's still work.

"When I build the Dream Studio each release cycle, I basically install Ubuntu on a VM, make sure all the packages will install properly, and run a script to add my personal optimizations and such. Then I use Ubuntu Customization Kit to unpack the stock Ubuntu liveCD, run the script I've made on it via chroot, and pack it up again," says Macinnis. "Dealing with changes in Ubuntu from one release to the next is the biggest issue and takes the most time, which is why I don't begin until Ubuntu has been released (as chasing a moving target was driving me nuts a couple releases ago). However, since almost all my packages are now desktop independent (except artwork), making derivatives with different DEs is quite easy."

Sure, it's easy when you know how. Vote for your favorite desktop environment in Macinnis' poll, and be sure to vote for LXDE because that is my favorite. Or E17, which is beautiful and kind to system resources. Or maybe Xfce.

System Requirements

Dream Studio 11.10 is a 2GB ISO that expands to 5.6GB after installation. You can run it from a live CD or USB stick, but given the higher performance requirements of audio and video production you really want to run it from a hard disk. While we're on the subject of hard drives, don't get excited over 6Gb/s SATA hard disk drives. They're not much faster than old-fashioned 3Gb/s or 1.5Gb/s SATA HDDs, and you need a compatible motherboard or PCI-e controller. Put your extra money into a good CPU instead. Audio and video production, and editing photo and image files are CPU-intensive. Bales of RAM never hurts, and a discrete video card, even a lower-end one, gives better performance than cheapo onboard video that uses shared system memory.

My studio PC is powered by a three-core AMD CPU, 4GB RAM, an Nvidia GPU, and a couple of 2TB SATA 3Gb/s hard drives. It's plenty good enough, though someday I'm sure I'm going to muscle it up more. Why? Why not?

You want your hardware running your applications and not getting weighed down driving your operating system. Dream Studio ships with GNOME 2, GNOME 2 with no effects, Unity, and Unity 2D. Just for giggles I compared how each one looked in top, freshly booted and no applications running:

GNOME 2: 440,204k memory, 6% CPUGNOME 2, no effects: 453,640k memory, 3.7% CPUUnity: 592,432k memory, 4.8% CPUUnity 2D: 569,936 1.0% CPU

It's not a big difference, measuring memory usage is not precise in Linux, and your mileage may vary, so use what makes you happy.

What's Inside

Dream Studio installs with a vast array of audio, movie, photography, and graphics applications. It's a great showcase for the richness of multimedia production software on Linux. Audio is probably the biggest pain in the behind, as the Linux audio subsystem can be a real joy^* to get sorted out. One of the best things Dream Studio does is box it all up sanely, and on most systems you just fire up your audio apps and get to work. It comes with a low-latency kernel, the JACK (JACK Audio Connection Kit) low-latency sound server and device router, and the pulseaudio-module-jack for integrating PulseAudio with JACK. If you have a single sound card this doesn't give you anything extra, so you're probably better off disabling PulseAudio while JACK is running. This is easy: in Qjackctrl go to Setup -> Options and un-check "Execute script after startup: pulsejack" and "Execute script after shutdown: pulsejackdisconnect". Leave "Execute script on startup: pausepulse" and "Execute script after shutdown: killall jackd" checked.

If you have more than one audio interface PulseAudio gives you some extra device routing options that you don't have with JACK alone. Once upon a time PulseAudio was buggy and annoying because it was new, and it introduced latency. It's stable and reliable now, but it still introduces some latency which is not good for audio production. But when you're capturing and recording audio streams, as long as everything is in sync then latency doesn't matter. Try it for yourself; it is easy and fun.

The creative applications are nicely-organized in both Unity and GNOME 2. Some notable audio apps are Audacity, Ardour, Hydrogen drum kit, DJ Tools, Tuxguitar, batches of special effects, and the excellent Linux Multimedia Studio (LMMS). On the graphics and video side you get FontForge, Luminance HDR, Scribus, Hugin, Stopmotion, Openshot, Blender, Agave, and a whole lot more.

There are a few of the usual productivity apps like Firefox, Libreoffice, Empathy, and Gwibber. And of course you may install anything in Linux-land that your heart desires.

Upgrade or No?

The problems I've run into are mostly Ubuntu glitches. During installation, the partitioning tool only gives a teeny tiny bit of room to show your existing partitions, and it does not resize, so you can't see all of your partitions without figuring out how to make it scroll. (Click on any visible partition and navigate with the arrow keys.) Ubuntu wants to you play audio CDs with Banshee; it wants this so badly it does not have a "play CD with" option. But Banshee doesn't work — it doesn't see the CD. My cure for this was to install VLC. There were some other nits I forget so they couldn't have been all that serious.

The one significant issue I ran into was with mass xruns in JACK. A xrun is a buffer underrun; an interruption or dropout in throughput. This can cause noticeable dropouts in your sound recordings. xruns should not be a problem on a system as powerful as mine, and they never have been. Until now. It could be a kernel problem, or a bug in JACK, it's hard to say. So before you upgrade a good working system test this new release well first.

*If you define joy as head-banging aggravation.

This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.

Can Linux Win in Cloud Computing?

Gerrit Huizenga is Cloud Architect at IBM (and fellow Portland-er) and will be speaking at the upcoming Linux Foundation Collaboration Summit in a keynote session titled "The Clouds Are Coming: Are We Ready?" Linux is often heralded as the platform for the cloud, but Huizenga warns that while it is in the best technical position to warrant this title, there is work to do to make this a reality.

Huizenga took a few moments earlier this week to chat with us as he prepares for his controversial presentation at the Summit.

You will be speaking at The Linux Foundation Collaboration Summit about Linux and the cloud. Can you give us a teaser on what we can expect from your talk?

Huizenga: Clouds are on the top of every IT departments list of new and key technologies to invest in. Obviously high on those lists are things like VMware and Amazon EC2. But where is the open source community in terms of comparable solutions which can be easily set up and deployed? Is it possible to build a cloud with just open source technologies? Would that cloud be a "meets min" sort of cloud, or can you build a full fledged, enterprise-grade cloud with open source today? What about using a hybrid of open source and proprietary solutions? Is that possible, or are we locked in to purely proprietary solutions today? Will Open Standards help us? What are some recommendations today for building clouds?

Linux is often applauded as the "platform for the cloud." Do you think this is accurate? If not, what still needs to be done? If so, what is it about Linux that gives it this reputation?

Huizenga: Linux definitely has the potential to be a key platform for the cloud. However, it isn't there yet. There are a few technology inhibitors with respect to Linux as the primary cloud platform, as well as a number of market place challenges. Those challenges can be addressed but there is definitely some work to do in that space.

What are the advantages of Linux for both public and private clouds?

Huizenga: It depends a bit about whether you consider Linux as a guest or virtual server in a cloud, or whether it is the hosting platform of the cloud. The more we enable Linux as a guest within the various hypervisors, and enable Linux to be managed within the cloud, the greater the chance of standardizing on Linux as the "packaging format" for applications.

This increases the overall presence of Linux in the market place and in some ways simplifies ISV's lives in porting applications to clouds. As a hosting platform, one of the biggest advantages for cloud operators is the potential cost/pricing model for Linux and the overall impact on the cost of operating a cloud. And, the level of openness that Linux provides should simplify the ability to support the cloud infrastructure and over time increase the number of services that can be provided by a cloud. But we still have quite a bit of work to do to make Linux a ubiquitous cloud platform.

What is happening at the Linux development level to support the rapidly maturing cloud opportunity? What does the community need from other Linux users and developers to help accelerate its development and address these challenges?

Huizenga: I'll talk about some of the KVM technologies that we need to continue to develop to enable cloud, as well as some of the work on virtual server building & packaging, DevOps, Deployment, and Management. There are plenty of places for the open source community to contribute and several talks at the Collaboration Summit should dive further into the details as well.

What do you make of Microsoft running Linux on Azure?

Huizenga: Anything that lets us run Linux in more places must be good!

More information about Huizenga's talk can be found on The Linux Foundation Collaboration Summit schedule. If you're interested in joining us, you can also request an invitation to attend.

This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.

A Peek Behind the Curtain at Puppet Labs

In this interview, Luke Kanies, CEO and founder of Puppet Labs, explains why the Puppet configuration management tool is a huge hit with sys admins, and tells us what to expect next from the popular open source project.

Linux.com: Puppet was picked by Linux Questions members as the 2011 Configuration Management Tool of the Year. What do you think it is about Puppet that helped make it the winner?

Luke Kanies: Primarily, it's that people who use Puppet love Puppet. The 4,000 people on our mailing list, 500 IRC members, and hundreds of customers don't just use the software to make their lives better; they actually like using it. I've been consistently surprised by how many people seem to be emotionally fond of Puppet, and I get thanked all the time by people for just helping them by having created Puppet.

Linux.com: What makes Puppet different than other configuration management tools?

Luke Kanies: The biggest difference between Puppet and other tools is our focus on great design and user experience. It's obviously not perfect, and there's still a lot of work to do before it's got as good a design as we want, but relative to other configuration management tools, it's easy to set up, easy to use, and easy to train other people on.

Other tools are happy to sacrifice usability for more power, more configurability, or easy access to global unstructured data. These all help make the tools more powerful, but they also make them harder to understand, harder to learn, and harder to spread through your whole organization.

Note, though, that Puppet has not by any means been dumbed down – we just resist adding features until we are confident that the features will actually make the product more useful, not just more powerful.

Linux.com: Are there any new features or improvements in the works for Puppet right now?

Luke Kanies: Yes, quite a lot is being worked on. We're always working on making our open source projects faster, more capable, and easier to use, so you'll see a lot of work from us on that in the near future. For instance, our central databases will be heavily upgraded, supporting far better scalability and really exposing all of the great data Puppet has about your infrastructure. Puppet has seen orders of magnitude increases in performance in the last few years to support the dramatic scaling needs of our customers, like Zynga, who are using the public cloud, and that trend will continue. We're also building more of our infrastructure around MCollective, which provides real-time access to your infrastructure and is becoming our infrastructure middleware for orchestration and communication.

We're also working on a lot of great partnerships with our new investors – VMware, Cisco, and Google Ventures – along with some other interesting projects, like OpenStack.

In our commercial product, Puppet Enterprise is going to take great advantage of that new central database with enhanced reporting, and we're building workflows around it that make the lives of our users a lot easier.

Linux.com: There are several Puppet Camps scheduled for this year. What are those like? Who should attend, sponsor, or host these camps?

Luke Kanies: Puppet Camps are by our community, for our community. We only run them where there is enough of a presence on the ground to really have a great conference, and our regional Puppet Camps are seeing larger attendance than our competitors' worldwide conferences.

You should attend Puppet Camp if you want to learn about configuration management in general or Puppet in particular, work with other Puppet users, and meet other great sys admins in your region. We always provide training at the camps, in addition to all the great talks and open sessions, and opportunities to just hang out with Puppet people. They're also great events if you're a company looking to reach the best sys admins and the most advanced devops practitioners out there.

Anyone interested in sponsoring or attending a Puppet Camp you can find more information on our Community page.

Linux.com: PuppetConf 2011 was held in September. Has planning started for PuppetConf 2012?

Luke Kanies: Yes, PuppetConf 2012 is set for September 27th and 28th in San Francisco, California. A call for participation, location information, and ticket sales will start around the end of March. 2011 had over 1,200 participants in person and streaming. We're aiming to triple that number this year. In the works are the first administered Puppet Certification tests, The Puppet Labs, which are large-scale demo environments for attendees to play with. You'll also see a new product release, a great speaker and attendee list, and much, much more.

Linux.com: Anything else we should know about Puppet or Puppet Labs?

Luke Kanies: Puppet Labs is fundamentally about enhancing sys admin productivity, as a means of enhancing organizational agility, increasing adoption of technology, and converting operations from a cost center to a competitive advantage. Our software is by sys admins, for sys admins.

Linux.com: Thanks to Luke Kanies for taking the time to update us on Puppet.

This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.

Patents, Legal Collaboration and our Legal Summit

Unfortunately legal issues, specially patents lawsuits, are much in the news. From Yahoo suing Facebook to the ongoing battles surrounding Apple and other mobile device providers, my RSS and social media feeds seem to have more and more articles about legal issues everyday.

Wired published a great article today from an ex-Yahoo developer on how his work was weaponized for a patent war.

He writes: "I thought I was giving them a shield, but turns out I gave them a missile with my name permanently engraved on it." This case, among other similar ones, points out the need quite urgently for reform of our software patent system. When companies struggle, especially large ones, it's often easier to litigate than innovate.

But amid the patent wars there has been some good news. OIN last week announced they are expanding their patent pool to cover other important projects such as KVM, Git and others projects.

As SVN writes: "Patents owned by Open Invention Network are available royalty-free to any company, institution or individual that agrees not to assert its patents against the OIN’s broad Linux Definitions." Keith Bergelt of OIN will be speaking at our upcoming CollaborationSummit on this Linux definition. Keith will take people through the changes in the definitions, as well as the updating of the 1000s of packages already included in their coverage. This is important stuff and I'm very happy to feature Keith as a speaker.

We are continuing our active role in the legal landscape by marshaling the power of collaboration with our members. Before next month's Linux Foundation Collaboration Summit, we will be holding our Linux Foundation Legal Summit, where counsels and attorneys from our members come together with our legal experts and others from around the industry to plot the best defense for Linux and free software. There is power in collaboration; certainly with software but also with legal issues. It's a core part of our mission to enable this legal collaboration and spear head programs, like our Open Compliance program, that simplify and improve legal matters in our community. And as mentioned above, we also have a track on legal and compliance issues at the Collaboration Summit. This year Bradley Kuhn was kind enough to assist me in creating the track and I'm happy to say we have a who's who of leaders in the open source legal industry.

We are featuring
-- Aaron Williamson of the SFLC on the Evolving Form of Free Software Organization
-- Bradley from the Software Freedom Conservancy on GPL Compliance
-- Richard Fontana from REd Hat will talk about the Decline of the GPL and what to do about it
-- Karen Sandler from the GNOME Foundation will talk about real world trademark management for free software projects

And on day one of Collaboration Summit we will have a keynote on the SPDX project, one of the best examples of collaborative legal issues. You can read details about full the schedule of Collab Summit.

I hope to see many of you there.

This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.