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. AMD Launches New FX CPUs, Cuts Prices On Existing Processors
  2. Preview: AMD's FX-9590 Eight-Core At Up To 5.0GHz On Linux
  3. Intel Launches The Core i7 5960X, Mighty Powerful Haswell-E CPUs
  4. AMD Radeon R9 290: Gallium3D vs. Catalyst Drivers
Latest Linux Articles
  1. Ondemand vs. Performance CPU Governing For AMD FX CPUs On Linux 3.17
  2. How Intel Graphics On Linux Compare To Open-Source AMD/NVIDIA Drivers
  3. The Fastest NVIDIA GPUs For Open-Source Nouveau With Steam Linux Gaming
  4. Testing For The Latest Linux Kernel Power Regression
Latest Linux News
  1. The Witcher 2 Ups The Performance More & Works Around Catalyst Bug
  2. Running Gallium3D's LLVMpipe On The Eight-Core 5GHz CPU
  3. Trying Intel OpenCL On Linux For Video Encoding
  4. GSoC 2014 Yielded Some Improvements For Mesa/X.Org This Year
  5. webOS Lives On As LuneOS With New Release
  6. Marek Lands Radeon Gallium3D HyperZ Improvements
  7. Mozilla Firefox 32 Surfaces With HTML5, Developer Changes
  8. Nouveau X.Org Driver Released With DRI3+Present, Maxwell, GLAMOR
  9. Microsoft & AMD Release C++ AMP Compiler With Linux Support
  10. AMD, Wine & Valve Dominated August For Linux Users
Latest Forum Discussions
  1. Lennart Poettering Talks Up His New Linux Vision That Involves Btrfs
  2. nv and xorg.conf under Debian PPC
  3. AMD graphics doesn't work with AMD Catalyst drivers
  4. Best Radeon for a Power Mac G5?
  5. The dangers of Linux kernel development
  6. Updated and Optimized Ubuntu Free Graphics Drivers
  7. AMD Releases UVD Video Decode Support For R600 GPUs
  8. SSD seems slow