Software Pages
Software Projects
Software projects are projects that have software deliverables. These are the currently active software projects, organized by software deliverable type. Links are as follows:
| Column | Site | Link |
|---|---|---|
| WA | Wiki | Work Area wiki page |
| PS Name | Wiki | Project Stream wiki page |
| PS Code | Code | Bitbucket project |
| Project | Wiki | Project wiki page |
| Issues | Issues | JIRA project |
| Code: Project Name | Code | Bitbucket repository |
The Forum's software activities span many areas and are stored for the membership on the Forum's code repository and publicly on GitHub.
A critical area of the BBF's work is the development of software models, specifically the development of both data and information models that accelerate the implementation of agile services. This key area of work is led by BBF Software Architect William Lupton, who also leads the Software Advisory Group.
Table of Contents
Used for existing report tool Shares with SD-354 Includes protocol schema WT-104: Provisioning Parameters for VoIP CPE WT-135: Data Model for a TR-069 Enabled STB Not started ... ... Type WA PS Name PS Code Project Issues Code: Project Name IPR Notes Code Test Plans BUS Network Measurement NETMEAS WT-382HNSTACKWT-382: Test Plan for 1905.1/1aBSD3 RANDIncludes stackSoftware Tools
BUS Software Tools TOOLS SD-354 DMR SD-354: New BBF CWMP Report Tool BSD3 RAND xCONF SD-376 DM2YM SD-376: CWMP Data Model/YANG Translation Rules and Tools BSD3 RAND Interfaces APIs BUS USP USP WT-369 USP WT-369: User Services Platform BSD3 RAND Data Models TR-069 and USP Data Models BUS Data Modeling CWMP WT-069 CWMP WT-069: CPE WAN Management Protocol BSD3 RAND WT-106 DMSUPP WT-106: Data Model Template for TR-069-Enabled Devices BSD3 RAND WT-181 DEV2DM WT-181: Device Data Model for TR-069 BSD3 RAND WT-104 VOIPDM BSD3 RAND WT-135 STBDM BSD3 RAND WT-140 NASDM WT-140: TR-069 Data Model for Storage Service Enabled Devices BSD3 RAND WT-196 FAPDM WT-196: Femto Access Point Service Data Model BSD3 RAND YANG Data Models Common YANG YANG Modules YANG WT-383 YMCMN WT-383: Common YANG Modules BSD3 RAND FTTDP WT-355 YMDPU WT-355: YANG Modules for FTTdp Management BSD3 RAND WT-374 YMGHN WT-374: YANG Models for Management of G.hn Systems BSD3 RAND WT-393 WT-393: PMAA Management Model BSD3 RAND FAN PON Management PON WT-385 YMOLT WT-385: YANG model for management of ITU-T PON BSD3 RAND WT-394 YMONU WT-394: YANG Models for Management of PON ONUs BSD3 RAND SDN / NFV SDN for MSBN SDN WT-368YMANWT-368: YANG Models for access nodes in SDNBSD3 RANDFixed Access Network Sharing FANS WT-386 YMFANS WT-386: Fixed Access Network Sharing Interfaces BSD3 RAND
Creating Software Projects
As already stated, a software project is a project that has software deliverables. This is determined when the project is created: the NPIF indicates whether there will be software deliverables and, if so, lists the expected software deliverable types. The Software Project Guidelines explain how an NPIF for a software project should be completed.
Contributing to Software Projects
All contributors of software to a software project must have completed a software submission form that covers the project's software deliverable types. The Software Project Guidelines explain how the software submission form is used and how it should be completed. All completed Software Submission Forms are available for review.
A software contribution proposes software for inclusion in a project. Software can be contributed via an attachment (e.g. a ZIP file) or via a "pull request". The Bitbucket Guidelines page explains how software projects use Bitbucket and how to create pull requests.
If software is contributed via an attachment, the editor may offer to edit and re-contribute it (on behalf of the original contributor) via a pull request. In this case, the original contributor is responsible for checking that the editor has incorporated their contribution correctly.
The "software contributor" is the person who uploaded the software contribution. A software contribution has one or more "software authors" (one of which is the software contributor) and zero or more "non-software authors" (who support the contribution but did not contribute to the software). Unlike software authors, non-software authors do not need to have completed a software contribution agreement.