-
Notifications
You must be signed in to change notification settings - Fork 81
ZAP Steering Committee
ZAP steering committee is a group of engineers that meet biweekly and discuss requirements and engineering plans for future features of ZAP tool. As ZAP is a tool used by multiple SDKs and applications, the effort for growing of ZAP needs to be coordinated across these multiple users, and the main purpose of the ZAP steering committee is exactly that.
Members of the steering committee at this point are not "elected" or decided in any formal matter. Until this becomes untenable, the steering committee members are simply people who participate on the biweekly steering committee meeting. Members of steering committee should at all points include all primary contributors to the project, so the nature of the committee is very technical and focuses mostly on technical issues.
Please contact Timotej Ecimovic if you are interested in participating.
Current members of the steering committee, listed in alphabetic order:
- Andrei Litvin
- Boris Zbarsky
- Jerry Johns
- Jiacheng Guo
- Johann Fridriksson
- Jordan Litwin
- Lazar Kovacic
- Song Guo
- Timotej Ecimovic
- Trevor Holbrok
- Vivien Nicolas
- Yufeng Wang
- Jerry Johns presents and discusses his vision for the complex data types and different structure of serializer/codec layers
- Touch on earlier points, we need more structure.
- Move forward with starting to use github for issue tracking and this wiki for keeping documentation.
- Establish need to work together on the issues for needs of the "Matter" SDK.
- First meeting.
- Decide to meet every 2 weeks, Wednesdays at noon, EST.
- Establish need for zap to support structured types.
- Talk about ZCL "feature masks" and the possible need for inclusion into zap.
- Note a problem with electron requiring DISPLAY, even if operation is headless.
- Talk about SDK-specific vs ZCL-specific feature areas.
All documentation on this wiki is to be considered Copyright by the respective authors. The opinions expressed are the opinions of each respective author, and not the opinions of the CSA alliance, their employers or any other organization.
There documents are fully public in nature and are intended as an ongoing documentation for the direction of zap project. They should NOT be used in any binding way as product documentation or commitment to certain features or effort. So it should be considered to be able to change or disappear at any point and should always be considered as "work in progress".