This was extracted (@ 2025-01-15 21:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
There has been too much confusion over what may be included in a source code or binary distribution of an Apache release from apache.org. Below is a proposed policy to be publicly posted to address this confusion. The board would also need to set a date for conformance to this policy. 1. If anything is unclear or in doubt, bring your questions to licensing@apache.org. Better to ask early than late or never. 2. Source distributions must be under the terms of the Apache License. Source distributions may include third-party software under other licenses, but those licenses must not place requirements or restrictions on the code, even those subsets of code, that go beyond those of the Apache license. 3. Binary distributions may include third-party libraries that allow for redistribution in combination with code under the Apache License. The existance of any library whose copyright terms go beyond that of the Apache License *must* be prominently mentioned in the LICENSE file accompaning the binary distribution (appended after the Apache License), and all requirements of the licenses of the third party code must be followed with respect to attribution, labelling, et cetera. 4. It is the responsibility of all developers to be aware of the licenses on included code, to follow those requirements, and make those requirements clear to the recipients of their code. The board approved the above "talking points" regarding third-party code in Apache releases. Notice will be sent to members@.