Compiz Comes Together

Compiz — the compositing window manager responsible for more than a few dropped-jaws — has a long history of ins and outs, not the least of which includes more forks than at a garden club lunch. It seems, however, that things always come back together, and such was the case on Tuesday, as the Compiz community announced the imminent re-merger of several well known forks.

According to the newly-minted Compiz Council, the future of Compiz is in mergers and acquisitions: Mergers with its forks, and acquisition of their code. The first to be announced involves the C++-based Compiz++ and the remote-desktop-oriented Nomad branch, which the project plans to merge in by early Fall 2009. Compiz++ is planned to merge first as Compiz 0.9.0, with a 0.9.2 release to follow shortly thereafter as a "cleanup" measure. Following Compiz 0.9.2, the project will then review the Nomad code: if it is considered ready to merge, it will merge into Compiz 0.9.4, with its own 0.9.6 cleanup release. If it is found to not be ready, the project will focus on option handling for Compiz 0.9.4, with the Nomad merger remaining on hold as long as necessary.

As though the merger of two forks back into the mothercode wasn't achievement enough, the project will also be merging in Compiz Fusion, the configuration and plugin system formed in early 2007 by the merger of Beryl — an earlier Compiz fork — back into the main Compiz community. The news came after the Compiz Council, composed of five longstanding Compiz community members, issued an official statement announcing its formation and setting out a roadmap for future development — with the code described as "expected to be quite volatile."

The council also announced that the project would be parting ways with freedesktop.org, an interoperability-focused organization which provides hosting for a number of similar projects, including the X.Org Server, GStreamer multimedia framework, and the GTK-Qt engine. Details of the move, and of the Compiz-Fusion merger, are said to be still under development, and should be forthcoming in the near future.

______________________

Justin Ryan is a Contributing Editor for Linux Journal.

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Documentation

El Perro Loco's picture

A lot of good things can come from the "reunited" Compiz. I certainly hope one of those things is better documentation - for the techie, the power user and the newbie alike. I would like to have everything spelled out - including the dependencies and, if everything else fails, cake-recipe-style instructions to completely *remove* Compiz-whatever from my installation!

If somebody out there has already seen such documentation, please post the address. So far, my googlings (!) have not been fruitful.

White Paper
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions