Canonical, Inc. has released many things: ten versions of Ubuntu, the Bazaar revision control system, and now, Launchpad.
The Launchpad collaboration/development platform is home to a host of well-known names in Open Source software, including MySQL, Inkscape, Drizzle, and Zope. Indeed, it houses Canonical's own family of projects, including the vast empire that is Ubuntu development. Despite its cadre of Open Source residents and the value it provides to those project, however, the service has remained under constant fire for not being Open Source itself. Not anymore.
In London yesterday, while Parliament was vacating the city, Canonical was announcing that Launchpad is now an Open Source project. Released under the AGPL, Launchpad is now on par with its Canonical cousins, and has fulfilled — without a day to spare — the commitment Mark Shuttleworth made at OSCON 2008 to release the platform's source code within a year.
According to Canonical, "Launchpad allows developers to host and share code from many different sources using the Bazaar version control system, which is integrated into Launchpad....End-users identify bugs affecting one or more projects so that developers can then triage and resolve those bugs. Contributors can write, propose, and manage software specifications. In addition, Launchpad erases barriers to collaboration by enabling people to support each other’s efforts across different project hosting services, both through its web interface and its APIs."
"Launchpad has everything software projects, open source or not, need to be successful."
While most of Launchpad's famous residents, and now it as well, are Open Source, Launchpad is not limited to the libre licensed. Unlike some of the other collaborative development options, closed-source projects can avail themselves of Launchpad's features without being required to release or license their code in a specific manner. They do, however, forfeit one key perk enjoyed by Open Source residents — while Open Source projects receive free use of the platform, proprietary development comes at a price. There would seem to be a touch of irony that in remaining closed, such projects finance Open Source development.
One of the big name projects housed on Launchpad is Sun's Drizzle. Core Developer Jay Pipes described the project's history with Launchpad:
Since the Drizzle project’s start in April, 2008, its community and contributors have used Launchpad as a platform for managing code and development tasks, and as an efficient method of communication between community members regarding bugs, workflow, code reviews, and more. Launchpad makes it easy to take all the disparate pieces of software development – bug reporting, source control, task management and code reviews – and glue them together with an easy-to-use interface that emphasizes public and open community discourse.
More information on the move, including details about getting the Launchpad source code, are available from the project's development page.
Justin Ryan is a Contributing Editor for Linux Journal.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Interview with Patrick Volkerding
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide