20190627 TSC Meeting Notes - 830AM Pacific / 2100 IST Minutes
Recording of call
Note that recording was started late, partially through old business.
Roll call of TSC members
x Erik Nordmark x Kalyan Nidumolu Rob Woolley | x Greg Chase x Srinibas Maharana x Avi Deitcher | x GopiKrishna Kodali Vijay Tapaskar | x Harihara Subhramanian CS Roman Shaposhnik |
|---|
Introductions of other attendees
Sankar - works for Zededa. Committer to EVE. Interested in joining TSC
Acceptance of prior minutes -
No disagreement
TSC Decisions via Email list
Additional TSC volunteers - no new volunteers. Early committers are not on TSC unless they volunteered.
Nominees for TSC Chair - Erik Nordmark
Nominees for TSC Vice Chair - Greg Chase
Old Business
Vote on composition of TSC - no dissent
Vote on TSC Chair - Erik Nordmark
Vote on TSC Vice Chair - Greg Chase
Vote to adopt mail-list business & decision making - no dissent
Vote to adopt The Apache Way as default decision making process in addition to Project EVE Charter - no dissent
Discuss & vote on Project EVE release process - need to have explicit document for this proposal, process and cadence - both emergency releases & major & minor release - adoption of fixes from pull releases ← Greg to work with Roman and Erik to write a first draft, and will be shared in email for comment and possible decision to adopt.
Weekly office hours & monthly TSC meetings - how's it going so far? ← no comments, will continue as is next month. Note July 4 is a week off.
New Business
Proposed contribution of "Adam", EVE device API reference implementation | Github repo | Demo ← no dissent about accepting Adam into Project EVE, subject to proper licensing and IP contribution agreements. Github needs to have a license applied. Erik to administer the contribution
Topics for email discussion:
Do we need to put Adam into a separate repository?
What do we call this new feature?
Further user education programs? ← finish core documentation first. Greg has some content under development
EVE API discussion
1) full REST compliance - current design is "REST-ish". - leave adhoc for now, evolving on release by release basis
2) return codes for various operations - API call by API call discussion, will be evolved release by release ← we need to make sure that return codes are correctly documented ← Sankar
How to change future TSC composition ← How long does officers last, how do we add new TSC members, how do we end TSC tenures in case of lack of participation (project ability to gain quorum), how can we make a pipeline for grooming new members ← Greg to study charter, make some proposals in email for discussion