Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.

Atlassian cookies and tracking notice, (opens new window)

Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)

LF Decentralized Trust

LF Decentralized Trust

Technical Oversight Committee

Results will update as you type.

End requirement to use Repolinter
Extend labs sponsors to SIG chairs
Forgo Active state requirement for First Major Release
Forgo the Project Lifecycle Incubation state
Governing Docs to be consolidated into a git repo
Hyperledger Explorer major release v1.0.0
Hyperledger Explorer Promoted release v1.0.0
Inactive Projects
Introduce a mechanism for regular review of a project
Long Term Agenda - Framing
MAINTAINERS file content
Management of quarterly reports to the TSC
Move Besu from Incubation to Active status
Move Composer to End of Life
Move HIP process to GitHub
Move Hyperledger Aries from Incubation to Active status
Move Hyperledger Explorer from incubation to active status
Move Hyperledger Lab Firefly into a Project in Incubation
Move Hyperledger Quilt to Dormant state
Move the Blockchain Integration Framework (BIF) lab to a Project
Move TSC issues / decision log to GitHub
Moving a Project to EOL
Process for new projects that already have a history
Project maturity metrics / Badging
Projects have two quarters to comply with common repo structure
Projects not required to start as a lab
Rename Active status and call it Graduated
Replace "Major Releases" with "Promoted Releases"
Restructure the Greenhouse to avoid confusion
Rollover of projects tied to a single other project
Security reporting policy on GH repos
Should the TSC have a secretary role?
Should we have a different chat platform?
Solang project proposal
Steps/Criteria/Policies for Releases after First Major Release
Subprojects and project proposals
Subprojects house keeping
Subprojects not formally defined
Table consideration of the FireFly proposal for two months
Task-force extension
Task-force formalization
Task-force launch
Task-force reporting
TSC Co-chair/Vice-chair
TSC Election 2020-2021 Plan
TSC Election nominations
TSC Election observers
TSC Election process approval
TSC Election timing
TSC Election voters selection
TSC Membership Diversity
TSC Quorum
TSC Size
TSC Term length
TSC Term limits
Unlimited Incubation period
WGs' purpose set to information exchange rather than production of deliverables
WGs product
WGs scope
WGs shall be dropped
WGs transition to TSIGs
What if a top level project does not meet its charter goal?
When to name a Project
Working Group Quarterly Reports

You‘re viewing this with anonymous access, so some content might be blocked.

/

Task-force formalization

Updated Dec 04, 2019

Task-force formalization

Dec 04, 2019

Status

RESOLVED

Outcome

Unanimously approved

Minutes Link

2019 11 07 TSC Minutes

Overview of Proposal

See Working Group Task Force: WGTF_Proposal4

Formal Proposal(s)

Formalize "task-force" as a task-specific group with limited scope and fixed time to complete.

Action Items

Type your task here, using "@" to assign to a user and "//" to select a due date

Reviewed By

Angelo de Caro

Arnaud J LE HORS

Christopher Ferris

Dan Middleton

Gari Singh

Hart Montgomery

Mark Wagner (Deactivated)

Nathan George

Swetha Repakula

Tracy Kuhrt (Deactivated)

Troy Ronda

Comments

Nov 7, 2019

What sort of resources does a TF require?

wiki space?
mail list?
chat channel?

Assume nothing and create any of the above on demand?
Is the difference from a WG just the explicit end date?

{"serverDuration": 33, "requestCorrelationId": "49bc0282309a406baa03d402ca07243b"}