*** Draft ***
Item | Description |
---|---|
LTS releases | the long term support releases |
LFN | Linux Foundation Networking |
SDN | Software-Defined Network |
CNCF | Cloud Network Computing Foundation |
Contributor | Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project |
Committer | Committers are Contributors who have earned the ability to modify (“commit”) source code, documentation or other technical artifacts in a project’s repository |
PTL | Project Technical Lead - a technical individual responsible for the project, provides direction for a sub-project. Check also Ownership & Responsibilities |
NFV | Network Function Virtualization |
TSC | Technical Steering Committee. The main TF governance body |
TWS | Technical Work Stream - Community call to deep dive on technical issues |
TF | Tungsten Fabric Community. This community. |
IRC | Internet Relay Chat |
VPG | Virtual Port Group |
CLA | Contributor Licence Agreement |
Module/sub-system | The bigger area of the Tungsten Fabric functionality logically separated (eg. Configuration System, Fabric Management System, Control System, vRouter etc.). Modules may be composed of components. Modules and components may or may not align with source code repositories.
|
| |
TL/SME | Technical Leader/Subject Matter Expert - a technical individual assigned to anything of significance, module, component, project, support activity with a deep knowledge and understanding of assigned part. Should be consulted and treated as a decision-maker for the respective area. |
Project | Collection of work undertaken to deliver a well-defined goal. The goal can be anything, it could be a feature enhancement or a big bug, support activity. Anything of significance that requires a well-defined goal can be a project. Projects transcend modules and components. A project is generally associated with a timeframe, a plan, and a collection of people. A technical leader/manager for a project should be defined |
Categories | Any meaningful distinction to enhance understanding. Categories may apply to modules, components, projects, anything useful |
Ownership & Responsibilities | A project, activity, module or component has only one leader, it may have many participants |
Supporting Activities | Any body of work in support of TF processes, development or release activities e.g. CI, infrastructure, documentation, deployment. Each supporting activity has a technical leader |
Source Code Repositories | Individual git repository that house TF code, names may not map directly to modules and components |