1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

LLVM Offered Into The Software Freedom Conservancy

Free Software

Published on 19 September 2012 03:12 AM EDT
Written by Michael Larabel in Free Software
13 Comments

The LLVM project applied to be part of the Software Freedom Conservancy and the Conservancy's Project Evaluation Committee has approved of accepting the increasingly popular open-source compiler infrastructure.

Bradley Kuhn announced that the evaluation committee has approved of accepting LLVM for the Software Freedom Conservancy. As described from their website, "The Software Freedom Conservancy is a not-for-profit organization that helps promote, improve, develop, and defend Free, Libre, and Open Source Software (FLOSS) projects. Conservancy provides a non-profit home and infrastructure for FLOSS projects. This allows FLOSS developers to focus on what they do best — writing and improving FLOSS for the general public — while Conservancy takes care of the projects' needs that do not relate directly to software development and documentation."

Bradley's message was sent to the LLVM developers' list but is not appearing at the moment within the public archives at the moment, so it's been embedded below.
I'm sorry for the intrusion of a project policy discussion onto the developer list, but there may be many here who may have thoughts, input, or question regarding Conservancy's offer for LLVM's membership, discussed below. If you're not interested in that topic, please feel free to ignore this message.

TL;DR: LLVM applied to the Conservancy and has been offered membership. The FSA template should be reviewed by all interested parties.

Full Details:

I am excited to inform you that Conservancy's Project Evaluation Committee has approved LLVM for membership in the Software Freedom Conservancy.

If LLVM proceeds to accept membership, the next step is to negotiate a formal agreement between the project and the Conservancy, which is called
a fiscal sponsorship agreement (FSA). You can find a template of the agreement available on Conservancy's website at:
http://sfconservancy.org/members/apply/ConservancyFSATemplate.pdf
http://sfconservancy.org/members/apply/conservancy-fsa-template.tex

Generally, Conservancy leaves it for the LLVM community to decide how you'd like to discuss the document internally. Note that signing such an agreement is a big step for the project and you should consider the agreement carefully, in whatever forum is most appropriate for your community.
Conservancy strongly suggests that a public discussion of the FSA occur on the general discussion list for developers of your project, which is why I've posted this information here on your public list.

Conservancy representatives would be glad to answer questions from the community as you consider the document, and you should feel comfortable cc'ing us on any discussion threads. Meanwhile, you are also welcome to batch questions into one group as well and email them to us directly, and just repost the responses. Basically, whatever works well for you works fine for us.

Also cc'ed is Conservancy's "Project Intake group", which can be reached by the alias project-intake@sfconservancy.org and is comprised of the
following people: Bradley M. Kuhn, Tony Sebro, Jeremy Allison, Tom Callaway, Martin Michlmayr

All of us are members of Conservancy's Project Evaluation Committee and will be happy to answer questions and you should also feel free to cc that address, too, if you'd like, when asking questions.

Meanwhile, Conservancy's detailed discussion will mostly be with the application leads, Chris Lattner and Tanya M. Lattner. Ultimately, Conservancy will rely on the application leads to coordinate the final details of the FSA with Conservancy.

Specifically, note that the FSA template is in fact, just that, a template. Most notably, we'll need to figure out together two key terms of the agreement:

(a) who the initial signatories should be (ideally it should include anyone who has ever made substantial contributions to the project),

(b) who the Project Leadership Committee (PLC) should be, how it should govern itself, and what it should be called. Note there are a few examples in the FSA template of how other projects have done this, but they are just guidelines, not choices. The most important thing is to write something that describes the natural and existing leadership structure of your project.

Meanwhile, there are a few other minor issues that we've raised in a private thread with the application leads.

We look forward to LLVM joining Conservancy. But, Conservancy does realize that you are also talking to other potential fiscal sponsors, and we definitely encourage this. We want LLVM to find the right home; perhaps that is Conservancy, but if not, we understand!

--
Bradley M. Kuhn, Executive Director, Software Freedom Conservancy

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  2. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
  3. AMD Radeon R9 285 Tonga Performance On Linux
  4. Apotop Wi-Copy
Latest Linux Articles
  1. AMD Moves Forward With Unified Linux Driver Strategy, New Kernel Driver
  2. MSI: Update Your BIOS From The Linux Desktop
  3. NVIDIA vs. AMD 2D Linux Drivers: Catalyst Is Getting Quite Good At 2D
  4. 15-Way GPU Comparison With Mesa 10.3 + Linux 3.17
Latest Linux News
  1. Linux 3.18-rc1 Released One Week Early With Many Changes
  2. The VC4 Gallium3D Driver Is Still Moving Along For The Raspberry Pi
  3. Direct3D 9 Support Might Land Within Mainline Mesa 3D Drivers
  4. OpenGL Preview Benchmarks For NVIDIA's GeForce GTX 970
  5. HOPE: The Ease Of Python With The Speed Of C++
  6. Vitesse: Using LLVM To Speed Up Databases
  7. AMD Is Restructuring Again, Losing 7% Of Employees
  8. Linux Testing Of The NVIDIA GeForce GTX 970
  9. Qt 5.4 Now In Beta With Web, Bluetooth LE, Graphics Improvements
  10. AMD's Radeon R9 285 On Linux Offers Good OpenCL Performance
Latest Forum Discussions
  1. AMD Is Restructuring Again, Losing 7% Of Employees
  2. Bye bye BSD, Hello Linux: A Sys Admin's Story
  3. NVIDIA Presents Its Driver Plans To Support Mir/Wayland & KMS On Linux
  4. Open-Source AMD Fusion E-350 Support Takes A Dive
  5. Upgrade to Kaveri, very slow VDPAU performance
  6. ChromeOS Drops Support For EXT2/EXT3/EXT4 File-Systems
  7. Lennart Poettering On The Open-Source Community: A Sick Place To Be In
  8. The Slides Announcing The New "AMDGPU" Kernel Driver