On Fri, Aug 24, 2012 at 1:00 PM, Rob Weir <robw...@apache.org> wrote: > Or if someone who cared sufficiently about this policy area took > ownership and proposed a wording of the policy, either as a Board > resolution, or on legal-discuss, and had that policy approved and > recorded via the ordinary means.
As a member of the Incubator PMC, I am willing to submit the following question via <https://issues.apache.org/jira/browse/LEGAL>: "AOO official binary artifacts" May the Apache Open Office podling consider binary artifacts prepared as described in this passage "official", in the sense that their sense that their release is an "act of the corporation" and their contributors are indemnified? http://www.apache.org/dev/release.html#what The Apache Software Foundation produces open source software. All releases are in the form of the source materials needed to make changes to the software being released. In some cases, binary/bytecode packages are also produced as a convenience to users that might not have the appropriate tools to build a compiled version of the source. In all such cases, the binary/bytecode package must have the same version number as the source release and may only add binary/bytecode files that are the result of compiling that version of the source code release. My preference would be to have someone more invested in AOO serve as advocate, but I will do it if no one else steps forward. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
