Introducing The ASF’s New Logo Read Now

Board history: Allow product dependencies on LGPL-licensed libraries

ASF Oak Leaf Icon

Allow product dependencies on LGPL-licensed libraries

What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.

These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.

Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.

[raw] the published minutes, which are the record. [main index]

Reports

2005-08-17

WHEREAS, some Project Management Committees (PMCs) within
The Apache Software Foundation (ASF) expect to better serve
their mission through the occasional dependency on existing
LGPL-licensed libraries when no other practical alternative
exists under terms covered by the Apache License, Version 2.0;
and

WHEREAS, research into the impact of distributing ASF products
that depend on the presence of LGPL-licensed libraries
indicates that the product licensing terms are not affected by
such a dependency; and

WHEREAS, the current ASF licensing policy discourages the
distribution of intellectual property by the ASF under terms
beyond those stated in the Apache License, Version 2.0.

NOW, THEREFORE, BE IT RESOLVED, that PMCs may develop and
distribute products that depend on the presence of
LGPL-licensed libraries when no other practical alternative
exists under terms covered by the Apache License, Version 2.0;
and be it further

RESOLVED, that PMCs will register such use of an LGPL-licensed
library with the Vice President of Legal Affairs prior to the
PMC's next regularly scheduled Board report, and in no case
less than two weeks prior to the distribution of the
applicable product(s); and be it further

RESOLVED, that PMCs will continue to reevaluate whether a
practical alternative exists under terms covered by the Apache
License, Version 2.0, which could be substituted in place of
the LGPL-licensed library; and be it further

RESOLVED, that PMCs must continue to ensure that they do not
distribute LGPL-licensed libraries or any other intellectual
property that is only available under licenses with terms
beyond those stated in the Apache License, Version 2.0.

Special Order 6C, Allow product dependencies on LGPL-licensed
libraries, was Tabled. The main discussion points were
whether the permission of dependencies invalidated the
spirit of the ASF and the Apache License. Discussion was
to be continued on the Board mailing list.

2005-07-28

WHEREAS, some Project Management Committees (PMCs) within
The Apache Software Foundation (ASF) expect to better serve
their mission through the use of existing LGPL-licensed
libraries as a product dependency; and

WHEREAS, research into the impact of distributing ASF products
that depend on the presence of LGPL-licensed libraries has
indicated that the product licensing terms are not affected by
such a dependency; and

WHEREAS, the current ASF licensing policy continues to require
all intellectual property distributed by the ASF be licensed
under the Apache License, Version 2.0.

NOW, THEREFORE, BE IT RESOLVED, that PMCs may develop and
distribute products that depend on the presence of
LGPL-licensed libraries; and be it further

RESOLVED, that PMCs will register such use of an LGPL-licensed
library with the Vice President of Legal Affairs prior to the
PMC's next regularly scheduled Board report, and in no case
less than one week prior to the distribution of the applicable
product(s); and be it further

RESOLVED, that PMCs must continue to ensure they do not
distribute LGPL-licensed libraries or any other intellectual
property that cannot be strictly licensed under the Apache
License, Version 2.0.

Discussion occurred that raised questions: Is the FSF position
public?  Will downstream users be comfortable with this?  The
conclusion was to give 3rd parties time to react to this
proposed resolution prior to voting on it.  Resolution 6E
was tabled with general consent.

Subscribe to ASF Plus One, Our Monthly Newsletter

Subscribe Now