Procedures for making draft software publicly available for comment. |
This license and the specified additional information has now been used for several draft releases, which are listed at https://www.broadband-forum.org/software (a permalink that re-directs to the Software Release Registry public wiki page). |
BBF wishes to be able to make publicly-available draft software releases.
Reasons to make draft software releases:
Additional rationale for making draft software releases:
Additional notes about draft software releases:
The draft specification document, if any, may be placed on a BBF web site or may also be placed on a public GitHub site (or similar).
BBF staff and members may at their discretion view public comments and incorporate (or not) ideas or feedback reflected in those comments in the same manner as normal BBF contributions.
Public comments are given with no assurance that they are original, or that the commenter has the necessary legal rights to contribute any included intellectual property. BBF staff and members should therefore exercise caution before including in a contribution any text or code received in a public comment.
This license will be included in each file that is part of the draft software release.
Copyright (c) <YEAR>, Broadband Forum This is draft software, is subject to change, and has not been approved by members of the Broadband Forum. It is made available to non-members for internal study purposes only. For such study purposes, you have the right to make copies and modifications only for distributing this software internally within your organization among those who are working on it (redistribution outside of your organization for other than study purposes of the original or modified works is not permitted). For the avoidance of doubt, no patent rights are conferred by this license. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Unless a different date is specified upon issuance of a draft software release, all member and non-member license rights under the draft software release will expire on the earliest to occur of (i) nine months from the date of issuance, (ii) the issuance of another version of the same software release, or (iii) the adoption of the draft software release as final. |
Members are responsible for adding their own copyright statements, where appropriate. The BBF copyright will be separated from the member copyright as shown below (this actually applies to all releases, not just to draft releases):
Copyright (c) <YEAR>, Broadband Forum The undersigned members have elected to grant the copyright to their contributed material used in this software: Copyright (c) <YEAR>, <MEMBER> <LICENSE TEXT AS SHOWN ABOVE> |
This additional information will be included in each file that is part of the draft software release.
<DRAFT> | Draft software release unique identifier. |
<NAME> | Software project name. |
<LINK> | Link to public web page that provides access to details of all draft and final versions of this software project. |
Some of these rules are derived from similar rules in the YANG Publication page. All the rules need to be defined more rigorously. The whole topic of how the draft software release should be pushed to GitHub is a separate topic and is not addressed here. One important consideration is whether to collapse the internal commit history before pushing to GitHub (this has implications for how the release will be prepared, e.g. it may make sense to prepare it in a temporary branch, or even in the master branch). |