Page tree
Skip to end of metadata
Go to start of metadata

This page is here to capture and memorialize voting resolutions from the Community.  This page will not be used for Elections.

How to create votes.

Details on how to create votes can be found here.

However, we recommend the following options:

  • Changeable votes - Disabled
  • showComments - Enable only if you would like to have community members provide context on the vote.  This space should not be used for discussion.  That should be done in the mailing lists or in Meetings with a recording and minutes.
  • List of voters and viewers can generally be left blank.
  • Always show the results - Enabled
  • Show the list of already voted users? - Enabled.
  • Username Visualization - set to "Linked User Name"
  • Locked - Set after the voting period has concluded.

Other 

  • Separate resolutions by date, most recent at the top.
  • Link to the Minutes where the resolution was discussed.
  • Link to any necessary documentation or files



 

RESOLVED: The TF Community will migrate from Jira to GitHub Issues

Choices Your Vote Current Result: (4 Total Votes)
Yes RESOLVED: The TF Community will migrate from Jira to GitHub Issues
4 Votes , 100%
No RESOLVED: The TF Community will migrate from Jira to GitHub Issues
0 Votes , 0%
Abstain RESOLVED: The TF Community will migrate from Jira to GitHub Issues
0 Votes , 0%



 

RESOLVED: The TSC approves the role of Community Release Manager as defined in v3 of the Proposal https://wiki.tungsten.io/x/GYFdAQ

Choices Your Vote Current Result: (6 Total Votes)
Yes RESOLVED: The TSC approves the role of Community Release Manager as defined in v3 of the Proposal https://wiki.tungsten.io/x/GYFdAQ
6 Votes , 100%
No RESOLVED: The TSC approves the role of Community Release Manager as defined in v3 of the Proposal https://wiki.tungsten.io/x/GYFdAQ
0 Votes , 0%
Abstain RESOLVED: The TSC approves the role of Community Release Manager as defined in v3 of the Proposal https://wiki.tungsten.io/x/GYFdAQ
0 Votes , 0%


 

RESOLVED: Tungsten Fabric will leverage git.dpdk.org upstream builds for all future Tungsten Fabric Releases

Choices Your Vote Current Result: (6 Total Votes)
Yes RESOLVED: Tungsten Fabric will leverage git.dpdk.org upstream builds for all future Tungsten Fabric Releases
6 Votes , 100%
No RESOLVED: Tungsten Fabric will leverage git.dpdk.org upstream builds for all future Tungsten Fabric Releases
0 Votes , 0%
Abstain RESOLVED: Tungsten Fabric will leverage git.dpdk.org upstream builds for all future Tungsten Fabric Releases
0 Votes , 0%


 

RESOLVED: The TSC has agreed to adopt a 6-month release cadence for Tungsten Fabric.

Choices Your Vote Current Result: (7 Total Votes)
Yes RESOLVED: The TSC has agreed to adopt a 6-month release cadence for Tungsten Fabric.
7 Votes , 100%
No RESOLVED: The TSC has agreed to adopt a 6-month release cadence for Tungsten Fabric.
0 Votes , 0%
Abstain RESOLVED: The TSC has agreed to adopt a 6-month release cadence for Tungsten Fabric.
0 Votes , 0%

RESOLVED: The TSC has agreed to adopt GitHub toolchain to develop a Review workflow for the Documentation Repository.

Choices Your Vote Current Result: (7 Total Votes)
Yes RESOLVED: The TSC has agreed to adopt GitHub toolchain to develop a Review workflow for the Documentation Repository.
7 Votes , 100%
No RESOLVED: The TSC has agreed to adopt GitHub toolchain to develop a Review workflow for the Documentation Repository.
0 Votes , 0%
Abstain RESOLVED: The TSC has agreed to adopt GitHub toolchain to develop a Review workflow for the Documentation Repository.
0 Votes , 0%

RESOLVED: The TSC will adopt the Release Distribution(v2)  and Milestones Proposals(v1) as a part of the official Tungsten Fabric Release Plan. 

Choices Your Vote Current Result: (6 Total Votes)
Yes RESOLVED: The TSC will adopt the Release Distribution(v2)  and Milestones Proposals(v1) as a part of the official Tungsten Fabric Release Plan. 
6 Votes , 100%
No RESOLVED: The TSC will adopt the Release Distribution(v2)  and Milestones Proposals(v1) as a part of the official Tungsten Fabric Release Plan. 
0 Votes , 0%
Abstain RESOLVED: The TSC will adopt the Release Distribution(v2)  and Milestones Proposals(v1) as a part of the official Tungsten Fabric Release Plan. 
0 Votes , 0%


  - Tungsten Fabric Technical Seat Allocation

RESOLVED, The TSC agrees to reduce the number of TSC Technical Representatives from 5 to 4 for the 2020 TSC Election.

Choices Your Vote Current Result: (7 Total Votes)
Yes RESOLVED, The TSC agrees to reduce the number of TSC Technical Representatives from 5 to 4 for the 2020 TSC Election.
7 Votes , 100%
No RESOLVED, The TSC agrees to reduce the number of TSC Technical Representatives from 5 to 4 for the 2020 TSC Election.
0 Votes , 0%
Abstain RESOLVED, The TSC agrees to reduce the number of TSC Technical Representatives from 5 to 4 for the 2020 TSC Election.
0 Votes , 0%


 - Tungsten Fabric TSC Seat Allocations

There has been an ongoing discussion in the community for some time about adjusting the size of the TSC to more appropriately reflect the Tungsten Fabric Community.  This resolution will reduce the number of Community Representatives from 5 to 3 and eliminate the (unfilled) seat reserved by the ARB.

Note that this resolution is only for the 2020 TSC Election period.  The 2020 TSC will need to review and propose an updated governance model prior to the 2021 Election period. 


 - LFN Developer Events

Information on LFN Technical Events

  • No labels