Hi all,
Please let us know if you have suggestions for agenda items. Here are the agenda items I have collected so far:
* Maarten, Bill, Stefano, Tomas: Brief working group updates
* All: Discuss WR repo of virtio framework port to Zephyr and decide on what to do with OpenAMP code to submit to Zephyr
* All: When/how to begin the master-slave terminology switchover, now that 2021.10 has passed
* All: Discuss contracting possibilities for docs & Zephyr work
The notes and recording from the previous call can be found at https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2021#20211022
Remaining action items from previous call:
* Maarten: Ask Rob Wooley to ask at Zephyr TSC if they know any contractors with solid Zephyr knowledge who might be available for OpenAMP contract
* Bill: Ask Nico about what Yocto Project is doing for documentation
* Nathalie: Publish code of conduct to OpenAMP website with the 3 committee members
If you are missing the meeting invitation, please email me directly, or you can use this link on 11/23/21 at 7am PST (UTC-7) to join the call: https://xilinx.webex.com/xilinx/j.php?MTID=m07ce66710df890f5b1280aeabb1e74c6
For info about the list, link to the archives, to unsubscribe yourself, or for someone to subscribe themselves, visit:
https://lists.openampproject.org/mailman/listinfo/tsc
Thanks & regards,
Nathalie
Hi all,
Checking if anyone has feedback on Bill's checklist.
* (DONE) Forward Bill's System Reference checklist as PDF to TSC list. If anyone wants to discuss, they are invited to join the weekly Wednesday call.
* Here is a link to the PDF<https://drive.google.com/file/d/1oMUUNiVSvKj28ybyAlD70IeItkE0DnAa/view?usp=…>
* Please email Nathalie directly if you need meeting invitation to System Reference call
Thanks & regards,
Nathalie
From: Tsc <tsc-bounces(a)lists.openampproject.org> On Behalf Of Nathalie Chan King Choy via Tsc
Sent: Friday, October 22, 2021 11:38 AM
To: tsc(a)lists.openampproject.org
Subject: [OA-Tsc] 2021-10-22 OpenAMP TSC notes and action items
Hi all,
The notes are posted at:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2021#20211022
The action items are:
* Nathalie:
* (DONE) Move App-services call 1hr earlier
* (DONE) Forward App-services call invitation to Alex Bennee for forwarding to Stratos folks
* (DONE) Forward Bill's System Reference checklist as PDF to TSC list. If anyone wants to discuss, they are invited to join the weekly Wednesday call.
* Here is a link to the PDF<https://drive.google.com/file/d/1oMUUNiVSvKj28ybyAlD70IeItkE0DnAa/view?usp=…>
* Please email Nathalie directly if you need meeting invitation to System Reference call
* (DONE) Check with Vicky how the budget calculation for documentation was done
* Publish code of conduct to OpenAMP website with the 3 committee members
* Topic for next TSC agenda: Discuss WR repo of virtio framework port to Zephyr and decide on what to do with OpenAMP code to submit to Zephyr
* Ioannis:
* See if Carles can join the App-services call
* Maarten:
* Ask WR team to put virtio framework port to Zephyr into a personal repo and send out to OpenAMP TSC for review
* Ask Rob Wooley to ask at Zephyr TSC if they know any contractors with solid Zephyr knowledge who might be available for OpenAMP contract
* Bill:
* Ask Nico about what Yocto Project is doing for documentation
Summary of decisions:
* OpenAMP Code of Conduct committee: Bill (Linaro), Tomas (Xilinx), Jeff (Siemens)
* Review the code for virtio framework port to Zephyr before making decisions on how to handle it
* Bill's proposal (see TSC mailing list<https://lists.openampproject.org/pipermail/tsc/2021-October/000118.html>) was voted on and accepted by TSC members.
* If TSC members or OpenAMP maintainers want to share documents to the mailing list/publicly, they have write access to OpenAMP Steering Committee > FilesToShareWithMailingList<https://drive.google.com/drive/folders/1XQ9RFkP0X_SUIjk85_ncTlWIi17i7Q4Y?us…>. Then can generate a public share link of the document itself for view/comment/edit, as needed.
Thanks & regards,
Nathalie
Hi all,
The notes are posted at:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2021#20211022
The action items are:
* Nathalie:
* (DONE) Move App-services call 1hr earlier
* (DONE) Forward App-services call invitation to Alex Bennee for forwarding to Stratos folks
* (DONE) Forward Bill's System Reference checklist as PDF to TSC list. If anyone wants to discuss, they are invited to join the weekly Wednesday call.
* Here is a link to the PDF<https://drive.google.com/file/d/1oMUUNiVSvKj28ybyAlD70IeItkE0DnAa/view?usp=…>
* Please email Nathalie directly if you need meeting invitation to System Reference call
* (In progress) Check with Vicky how the budget calculation for documentation was done
* Publish code of conduct to OpenAMP website with the 3 committee members
* Topic for next TSC agenda: Discuss WR repo of virtio framework port to Zephyr and decide on what to do with OpenAMP code to submit to Zephyr
* Ioannis:
* See if Carles can join the App-services call
* Maarten:
* Ask WR team to put virtio framework port to Zephyr into a personal repo and send out to OpenAMP TSC for review
* Ask Rob Wooley to ask at Zephyr TSC if they know any contractors with solid Zephyr knowledge who might be available for OpenAMP contract
* Bill:
* Ask Nico about what Yocto Project is doing for documentation
Summary of decisions:
* OpenAMP Code of Conduct committee: Bill (Linaro), Tomas (Xilinx), Jeff (Siemens)
* Review the code for virtio framework port to Zephyr before making decisions on how to handle it
* Bill's proposal (see TSC mailing list<https://lists.openampproject.org/pipermail/tsc/2021-October/000118.html>) was voted on and accepted by TSC members.
* If TSC members or OpenAMP maintainers want to share documents to the mailing list/publicly, they have write access to OpenAMP Steering Committee > FilesToShareWithMailingList<https://drive.google.com/drive/folders/1XQ9RFkP0X_SUIjk85_ncTlWIi17i7Q4Y?us…>. Then can generate a public share link of the document itself for view/comment/edit, as needed.
Thanks & regards,
Nathalie
Hi TSC list members,
In today's OpenAMP TSC, the members voted to accept Bill's proposal with the 1 change shown below.
Thanks & regards,
Nathalie
> -----Original Message-----
> From: Nathalie Chan King Choy <nathalie(a)xilinx.com>
> Sent: Friday, October 22, 2021 10:20 AM
> To: Nathalie Chan King Choy <nathalie(a)xilinx.com>
> Subject: FW: Terminology replacement input
>
>
>
> From: Tsc <tsc-bounces(a)lists.openampproject.org> On Behalf Of Nathalie
> Chan King Choy via Tsc
> Sent: Wednesday, September 22, 2021 2:26 PM
> To: tsc(a)lists.openampproject.org
> Subject: [OA-Tsc] FW: Terminology replacement input
>
> Resending to corrected list address
>
> From: Bill Mills <mailto:bill.mills@linaro.org>
> Sent: Monday, September 20, 2021 7:36 AM
> Subject: Terminology replacement input
>
>
> git context
> replace master with main
> github has special case logic to make this easier:
> https://github.com/github/renaming
>
> remoteproc context:
> "slave" should be "remote processor"
> "master" should be "remoteproc host"
>
> virto context:
> virtio spec uses "device" and "driver"
> suggest we use "virtio device" and "virtio driver"
> Examples of devices:
> vitioblk device
> virtio network interface
> For today's remoteproc rpmsg, LInux is always the driver side
>
> Some virtio "devices" are not very device like and instead are more like
> services.
> Alternative for such cases
> "application service" and "application client"
> Examples:
> vsock: service is the one that creates the socket
vsock: service is the one that calls accept on the socket
> p9fs: service is the side that has the filesystem
> Note that a remote processor can host a service and be a client at the same
> time.
> The terminology is per service.
>
> --
> Bill Mills
> Principal Technical Consultant, Linaro
> +1-240-643-0836
> TZ: US Eastern
> Work Schedule: Tues/Wed/Thur
Hi Nathalie,
You wrote:
> Please let us know if you have any other topics.
I would like us to discuss the creation of a Zephyr repo that we can use for pull requests to zephyr.org that have our reference heterogeneous OpenAMP technologies in it, such as the new virtio framework we are working on.
Thanks,
Maarten
From: Tsc <tsc-bounces(a)lists.openampproject.org> on behalf of OpenAMP TSC <tsc(a)lists.openampproject.org>
Reply-To: Nathalie Chan King Choy <nathalie(a)xilinx.com>
Date: Wednesday, October 20, 2021 at 10:16 PM
To: OpenAMP TSC <tsc(a)lists.openampproject.org>
Cc: "Hancock, Jeffrey" <Jeffrey_Hancock(a)mentor.com>
Subject: [OA-Tsc] Calling for agenda items: OpenAMP TSC - October
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hi all,
Here is the agenda that I have gathered so far. Please let us know if you have any other topics. If you are missing the meeting invitation for Friday, let me know and I can fwd to you directly.
* Nathalie: Calling for volunteers for OpenAMP code of conduct committee
* Maarten/Dan: Pitch for App-services call coming up next week
* Tomas: Summarize latest on System Reference project (formerly known as “end-to-end example”)
* Tomas: Revisit spreadsheet of candidates for spending some of the OpenAMP budget (covers docs, app-services, system reference)
* If quorum, member reps in TSC vote to approve Bill’s proposal from last TSC for master/slave terminology. If no quorum, do the vote by email.
git context
replace master with main
github has special case logic to make this easier:
https://github.com/github/renaming<https://urldefense.com/v3/__https:/github.com/github/renaming__;!!AjveYdw8E…>
remoteproc context:
"slave" should be "remote processor"
"master" should be "remoteproc host"
virto context:
virtio spec uses "device" and "driver"
suggest we use "virtio device" and "virtio driver"
Examples of devices:
vitioblk device
virtio network interface
For today's remoteproc rpmsg, LInux is always the driver side
Some virtio "devices" are not very device like and instead are more like services.
Alternative for such cases
"application service" and "application client"
Examples:
vsock: service is the one that creates the socket
p9fs: service is the side that has the filesystem
Note that a remote processor can host a service and be a client at the same time.
The terminology is per service.
Thanks & regards,
Nathalie
-----Original Appointment-----
From: Nathalie Chan King Choy
Sent: Wednesday, October 6, 2021 3:55 PM
To: Nathalie Chan King Choy; tsc(a)lists.openampproject.org
Cc: Glaropoulos, Ioannis; Robert Oshana; Cufi, Carles; Hancock, Jeffrey; ed.mooring(a)gmail.com; Tanmay Shah; bill.mills(a)linaro.org; Loic PALLARDY; Tomas Evensen
Subject: OpenAMP TSC - October
When: Friday, October 22, 2021 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: webex
Hi all,
The notes and recording from the previous call can be found at https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2021#20210920<https://urldefense.com/v3/__https:/github.com/OpenAMP/open-amp/wiki/TSC-Mee…>
Action items from previous call:
* Maarten will check with the developers about date for: Demo & discussion of implementation & walk through the public repo
* Tomas, Bill, Kumar: Suggest who might be other key people to invite (e.g. Stratos)
* Tomas, Bill, Kumar, Maarten: Send Nathalie who are the "must attend" people for app-services
* Nathalie: Send doodle poll to "must attend" group
* Maarten: Send out invitation to the app-services mailing list and wider audience
* Bill: Check with Linaro if their discussion on inclusive terminology will expand to be public discussion
* Ed/Arnaud: Rename the master branch in OpenAMP GitHub repos.
* Ed/Arnaud: Discuss who of them will to update the master/slave terms in the code.
* Nathalie: Organize sync w/ Kumar and Kate, Bill, Ed, Arnaud, Etsam on MISRA C checking in Zephyr & what can be leveraged for checking OpenAMP.
* Nathalie: Reconvene TSC in 1 month. Agenda to include: TSC to approve Bill's proposal for master/slave terminology
For info about the list, link to the archives, to unsubscribe yourself, or for someone to subscribe themselves, visit:
https://lists.openampproject.org/mailman/listinfo/tsc<https://urldefense.com/v3/__https:/lists.openampproject.org/mailman/listinf…>
Best regards,
Nathalie C. Chan King Choy
Program Manager focused on Open Source and Community
Friday, October 22, 2021
9:00 AM | (UTC-07:00) Pacific Time (US & Canada) | 1 hr
Join meeting<https://urldefense.com/v3/__https:/xilinx.webex.com/xilinx/j.php?MTID=mbd30…>
More ways to join:
Join from the meeting link
https://xilinx.webex.com/xilinx/j.php?MTID=mbd30843cd3e5a94a32db25904f3d5c3f<https://urldefense.com/v3/__https:/xilinx.webex.com/xilinx/j.php?MTID=mbd30…>
Join by meeting number
Meeting number (access code): 2598 019 8901
Meeting password: ggKvnG9t@68
Join by phone
+1-415-655-0001 US Toll
1-844-621-3956 United States Toll Free
Global call-in numbers<https://urldefense.com/v3/__https:/xilinx.webex.com/xilinx/globalcallin.php…> | Toll-free calling restrictions<https://urldefense.com/v3/__https:/www.webex.com/pdf/tollfree_restrictions.…>
Need help? Go to https://help.webex.com<https://urldefense.com/v3/__https:/help.webex.com__;!!AjveYdw8EvQ!InaSEVH16…>
Hi all,
Here is the agenda that I have gathered so far. Please let us know if you have any other topics. If you are missing the meeting invitation for Friday, let me know and I can fwd to you directly.
* Nathalie: Calling for volunteers for OpenAMP code of conduct committee
* Maarten/Dan: Pitch for App-services call coming up next week
* Tomas: Summarize latest on System Reference project (formerly known as "end-to-end example")
* Tomas: Revisit spreadsheet of candidates for spending some of the OpenAMP budget (covers docs, app-services, system reference)
* If quorum, member reps in TSC vote to approve Bill's proposal from last TSC for master/slave terminology. If no quorum, do the vote by email.
git context
replace master with main
github has special case logic to make this easier:
https://github.com/github/renaming
remoteproc context:
"slave" should be "remote processor"
"master" should be "remoteproc host"
virto context:
virtio spec uses "device" and "driver"
suggest we use "virtio device" and "virtio driver"
Examples of devices:
vitioblk device
virtio network interface
For today's remoteproc rpmsg, LInux is always the driver side
Some virtio "devices" are not very device like and instead are more like services.
Alternative for such cases
"application service" and "application client"
Examples:
vsock: service is the one that creates the socket
p9fs: service is the side that has the filesystem
Note that a remote processor can host a service and be a client at the same time.
The terminology is per service.
Thanks & regards,
Nathalie
-----Original Appointment-----
From: Nathalie Chan King Choy
Sent: Wednesday, October 6, 2021 3:55 PM
To: Nathalie Chan King Choy; tsc(a)lists.openampproject.org
Cc: Glaropoulos, Ioannis; Robert Oshana; Cufi, Carles; Hancock, Jeffrey; ed.mooring(a)gmail.com; Tanmay Shah; bill.mills(a)linaro.org; Loic PALLARDY; Tomas Evensen
Subject: OpenAMP TSC - October
When: Friday, October 22, 2021 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: webex
Hi all,
The notes and recording from the previous call can be found at https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2021#20210920
Action items from previous call:
* Maarten will check with the developers about date for: Demo & discussion of implementation & walk through the public repo
* Tomas, Bill, Kumar: Suggest who might be other key people to invite (e.g. Stratos)
* Tomas, Bill, Kumar, Maarten: Send Nathalie who are the "must attend" people for app-services
* Nathalie: Send doodle poll to "must attend" group
* Maarten: Send out invitation to the app-services mailing list and wider audience
* Bill: Check with Linaro if their discussion on inclusive terminology will expand to be public discussion
* Ed/Arnaud: Rename the master branch in OpenAMP GitHub repos.
* Ed/Arnaud: Discuss who of them will to update the master/slave terms in the code.
* Nathalie: Organize sync w/ Kumar and Kate, Bill, Ed, Arnaud, Etsam on MISRA C checking in Zephyr & what can be leveraged for checking OpenAMP.
* Nathalie: Reconvene TSC in 1 month. Agenda to include: TSC to approve Bill's proposal for master/slave terminology
For info about the list, link to the archives, to unsubscribe yourself, or for someone to subscribe themselves, visit:
https://lists.openampproject.org/mailman/listinfo/tsc
Best regards,
Nathalie C. Chan King Choy
Program Manager focused on Open Source and Community
Friday, October 22, 2021
9:00 AM | (UTC-07:00) Pacific Time (US & Canada) | 1 hr
Join meeting<https://xilinx.webex.com/xilinx/j.php?MTID=mbd30843cd3e5a94a32db25904f3d5c3f>
More ways to join:
Join from the meeting link
https://xilinx.webex.com/xilinx/j.php?MTID=mbd30843cd3e5a94a32db25904f3d5c3f
Join by meeting number
Meeting number (access code): 2598 019 8901
Meeting password: ggKvnG9t@68
Join by phone
+1-415-655-0001 US Toll
1-844-621-3956 United States Toll Free
Global call-in numbers<https://xilinx.webex.com/xilinx/globalcallin.php?MTID=mf1b27d18d7f1d1c4967f…> | Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>
Need help? Go to https://help.webex.com
Hi all,
The notes and recording from the previous call can be found at https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2021#20210920
Action items from previous call:
* Maarten will check with the developers about date for: Demo & discussion of implementation & walk through the public repo
* Tomas, Bill, Kumar: Suggest who might be other key people to invite (e.g. Stratos)
* Tomas, Bill, Kumar, Maarten: Send Nathalie who are the "must attend" people for app-services
* Nathalie: Send doodle poll to "must attend" group
* Maarten: Send out invitation to the app-services mailing list and wider audience
* Bill: Check with Linaro if their discussion on inclusive terminology will expand to be public discussion
* Ed/Arnaud: Rename the master branch in OpenAMP GitHub repos.
* Ed/Arnaud: Discuss who of them will to update the master/slave terms in the code.
* Nathalie: Organize sync w/ Kumar and Kate, Bill, Ed, Arnaud, Etsam on MISRA C checking in Zephyr & what can be leveraged for checking OpenAMP.
* Nathalie: Reconvene TSC in 1 month. Agenda to include: TSC to approve Bill's proposal for master/slave terminology
For info about the list, link to the archives, to unsubscribe yourself, or for someone to subscribe themselves, visit:
https://lists.openampproject.org/mailman/listinfo/tsc
Best regards,
Nathalie C. Chan King Choy
Program Manager focused on Open Source and Community
Friday, October 22, 2021
9:00 AM | (UTC-07:00) Pacific Time (US & Canada) | 1 hr
Join meeting<https://xilinx.webex.com/xilinx/j.php?MTID=mbd30843cd3e5a94a32db25904f3d5c3f>
More ways to join:
Join from the meeting link
https://xilinx.webex.com/xilinx/j.php?MTID=mbd30843cd3e5a94a32db25904f3d5c3f
Join by meeting number
Meeting number (access code): 2598 019 8901
Meeting password: ggKvnG9t@68
Join by phone
+1-415-655-0001 US Toll
1-844-621-3956 United States Toll Free
Global call-in numbers<https://xilinx.webex.com/xilinx/globalcallin.php?MTID=mf1b27d18d7f1d1c4967f…> | Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>
Need help? Go to https://help.webex.com
Hi all,
Below is some WR material on terminology that I would like to put forth as draft terminology guidelines for consideration by the group.
Maarten
Guidance
- use inclusive language in documentation to support a diverse audience and to avoid distracting terminology.
- when a biased term in project is encountered, notify the TSC for remediation
- if there is risk that the replacement term is unclear to the audience, you can mention the industry-standard term verbally (for now), but not in writing. E.g.: “Open box testing (also known white-box testing) is a method of software testing that tests internal structures or workings of an application, as opposed to its functionality.”
- do not use the below biased terms in your documentation; use the provided replacement terms.
Biased term
Replacement term
black-box testing
closed box testing
black hat
illegal
blacklist
forbidden list
cripple
slow, break, limit, or alter the functionality
dummy packet
test packet
dummy variable
placeholder variable
female adapter
socket
grandfather
legacy
grey-list
inspect list
male adapter
plug
man hours
labor hours or work hours
man-in-the-middle (MITM)
person-in-the-middle (PITM)
manpower
labor or workforce
master (outside of the master/slave context)
main
master/slave
For high availability: active/standby
For clocks: primary/secondary
For virtualization: host/guest
For services: server/client
For notifications: publisher (or provider) / subscriber
For other scenarios: initiator/responder
middleman
middle person
owner
main
white-box testing
open box testing
white hat
legal
whitelist
allow list
<snip>
Resending to corrected list address
From: Bill Mills <bill.mills(a)linaro.org>
Sent: Monday, September 20, 2021 7:36 AM
Subject: Terminology replacement input
git context
replace master with main
github has special case logic to make this easier:
https://github.com/github/renaming
remoteproc context:
"slave" should be "remote processor"
"master" should be "remoteproc host"
virto context:
virtio spec uses "device" and "driver"
suggest we use "virtio device" and "virtio driver"
Examples of devices:
vitioblk device
virtio network interface
For today's remoteproc rpmsg, LInux is always the driver side
Some virtio "devices" are not very device like and instead are more like services.
Alternative for such cases
"application service" and "application client"
Examples:
vsock: service is the one that creates the socket
p9fs: service is the side that has the filesystem
Note that a remote processor can host a service and be a client at the same time.
The terminology is per service.
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
