Community Action Planning

This page was created at the request of the TSC to provide a list of areas where the Tungsten Fabric Community needs support.

The community needs to Address the following category of issues.

Repo Migration:

Repo migration to Tungsten Fabric needs to be completed, allowing the community to establish processes and procedures as per LFN guidelines.

This is also one of the important parts for the community to come out of the incubation phase.

The community needs to have a better track of repo move and challenges, which will enable the community to establish better transparency and collaboration

Trade Mark:

Repos have a very large context of references to Juniper's Trademark Contrail, which limits participating community members to do their version of distribution for Tungsten Fabric.

Hence limiting the participation in the Tungsten Fabric community.

This needs to be addressed on an urgent basis or a stop-gap solution needs to be achieved, which will help to attract more community members to participate.

Segregation of private information from technology:

Many of the commits messages in repo have vague comments or references to URLs private to organizations, participating organizations need to ensure segregation of private information from the technology/architecture/gist of the commit made, allow commit message to be complete in itself.

This allows and encourages community members to review and comment on changes if they have any objections.

Discussion of Release planning, Blueprints and feature development:

development of new features have to follow a process and needs to be transparent with other participating members, giving a chance to have a discussion and to be able to arrive at a better, toughened architecture or solution for the feature proposed.

Participating in Community discussions:

All the Active committers are expected to participate in a community discussion on various channels established for the community.

Unblocking pending commits:

Many of the commits were blocked due to non-technical reasons, which have forced submitters to either abandon or take their code changes downstream.

Technical

• Repo Migration 
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Code development not being done on gerrit.tungsten.io  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Not all developers are set up to use gerrit.tungsten.io
• Not all repos from GitHub mirrored in gerrit yet.
• CI needs to be integrated with gerrit.tungsten.io
• Carry forward PTLs and Committers to new platform
• .gitreview update
• • wiki content from old repos not being updated by either migration to the new wiki or pointers in the new repositories
    • ansible deployer repo
• Commits not being merged
  • Repos that have not yet migrated are having commits being ignored or rejected for non-technical reasons.
• Use of Tungsten Jira instead of the Juniper Jira for upstream code. -  need comments and feedback happening on the TF Jira  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Trademark issues in the Codebase - Casey to work with Prabhjot to develop a list of all trademark references in the code. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Developer Onboarding Guide - A new Developer Onboarding Guide is in the works, however, additional resources would be very helpful.  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Gerrit to GitHub migration
  
  • docs repo is almost finished migrating
  • Currently building documentation on the migration process to look at migrating codebase from gerrit.tungsten.io

Organizational

• Project Definitions → Marek Chwal, Casey Cain
  • List of currently existing projects needed projects and PTLs responsible for them or vacates
  • Projects need clear definitions (charter) so that we can assign PTLs to those projects.
  • Project Expectations not defined
    • Community communication
    • Project Release Participation
    • Feature / Project Documentation
    • Election mechanics for PTLs
    • Project decision-making process
    • Committer Lifecycle
  • PTL Definitions & Expectations
• Release Process → Marek Chwal, Casey Cain
  • Marek Chwal, the new Community Release Manager will be working with the community to improve our release planning.
    (Discussion on Release planning will be conducted during Virtual LFN Developer & Testing Forum - moderated by Marek Chwal  and Casey Cain)
• CNF Integrations → Casey Cain