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>
Hi all,
Notes and link to the recording are available at:
https://github.com/OpenAMP/open-amp/wiki/TSC-Meeting-Notes-2021#20210526
Please download the recording in the next few weeks, if you need to get caught up. Not sure how long before Webex auto-deletes.
Action items
* Stefano & Nathalie: set up next System DT call (aim for mid-June)
* Stefano: Send out slide from today
* Maarten: Send out slide from today
* Maarten: Schedule meeting on the Zephyr work
* Tomas, Bill: discuss resource plan in another meeting soon w/ Kumar (this week)
* Nathalie: Set up follow-up TSC call in a couple weeks
Thanks & regards,
Nathalie
All,
openamp-rp status and roadmap:
Status:
* Keeping the lights on
* Released new open-amp and libmetal lib versions
* this opened the flood gate of pull requests, see below
* Kernel patch activity is slowing down as much of the high
priority backlog has been worked through
* Xilinx R5 is still out standing
Big changes purposed:
* Namespace message enhancement
* know when a client connects and disconnects
* if we are to make a change I think we should cover
more needs than just this so I am working on a NS 2.0
proposal
* Resource table enhancements
* Arnaud is driving but finds that current model needs to
documented first
* message size configuration at startup time
Plans for next 6 months
* Spec document
* start by moving Arnaud's resource table doc to
sphinx / rst
* Infrastructure for documentation in general
* Bill is looking at EBBR for spec focus, and
Zephyr and Yocto Project for whole project
https://arm-software.github.io/ebbr/https://docs.yoctoproject.org/https://docs.zephyrproject.org/latest/
* CI advances
* at least run linux user space to user space tests
* Hopefully QEMU based test also (by any mean necessary)
* Progress on big changes above
* Demo w/ multiple virtques:
* rpmsg and virtio i2c for example
* Our part of whole openamp demo
* SysDT, openamp-rp & openamp app srvs
Bill
On 5/25/21 7:38 PM, Nathalie Chan King Choy via Tsc wrote:
> Wednesday’s agenda:
>
> * 1 min: Maintainer news
> * 10-15 min: Tomas, Kumar: Heterogeneous end-to-end example
> * 3 x 5 min: Stefano, Bill, Maarten: working group updates
> * 5 min: Nathalie: LVC21F CFP - Does OpenAMP Project have topics to
> submit?
> * 10 min: Maarten, Jeff, Tomas: Inclusive terms
> * 10 min: Tomas: OpenAMP resourcing needs for various upcoming initiatives
>
> *From:* Tsc <tsc-bounces(a)lists.openampproject.org> *On Behalf Of
> *Nathalie Chan King Choy via Tsc
> *Sent:* Wednesday, May 19, 2021 3:51 PM
> *To:* tsc(a)lists.openampproject.org
> *Subject:* [OA-Tsc] Calling for agenda items: OpenAMP TSC - May 2021
>
> Hi all,
>
> Please send your requests for agenda items for the 5/26 OpenAMP TSC
> call. Here’s what I have so far:
>
> * Tomas: End-to-end example
> * Maarten, Jeff, Tomas: Inclusive terms
>
> * Nathalie: Are there any OpenAMP topics that would make sense to
> submit for the LVC21F CFP?
>
> Thanks & regards,
>
> Nathalie
>
>
> --
> Tsc mailing list
> Tsc(a)lists.openampproject.org
> https://lists.openampproject.org/mailman/listinfo/tsc
>
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Wednesday's agenda:
* 1 min: Maintainer news
* 10-15 min: Tomas, Kumar: Heterogeneous end-to-end example
* 3 x 5 min: Stefano, Bill, Maarten: working group updates
* 5 min: Nathalie: LVC21F CFP - Does OpenAMP Project have topics to submit?
* 10 min: Maarten, Jeff, Tomas: Inclusive terms
* 10 min: Tomas: OpenAMP resourcing needs for various upcoming initiatives
From: Tsc <tsc-bounces(a)lists.openampproject.org> On Behalf Of Nathalie Chan King Choy via Tsc
Sent: Wednesday, May 19, 2021 3:51 PM
To: tsc(a)lists.openampproject.org
Subject: [OA-Tsc] Calling for agenda items: OpenAMP TSC - May 2021
Hi all,
Please send your requests for agenda items for the 5/26 OpenAMP TSC call. Here's what I have so far:
* Tomas: End-to-end example
* Maarten, Jeff, Tomas: Inclusive terms
* Nathalie: Are there any OpenAMP topics that would make sense to submit for the LVC21F CFP?
Thanks & regards,
Nathalie
Hi all,
Please send your requests for agenda items for the 5/26 OpenAMP TSC call. Here's what I have so far:
* Tomas: End-to-end example
* Maarten, Jeff, Tomas: Inclusive terms
* Nathalie: Are there any OpenAMP topics that would make sense to submit for the LVC21F CFP?
Thanks & regards,
Nathalie