On Jul 15, 2020, at 01:31, Trevor Woerner <twoerner@...> wrote:

Hi,

As most are aware, there are efforts in many open-source/free-software
communities to adjust the language that is used throughout a given project
to be more inclusive.

We discussed this briefly at the most recent YP Technical Team/Engineering
Sync Meeting. Many good points were raised. I'd like to start a discussion on
this topic via email in order to enumerate and keep track of these efforts.

Is there a YP mailing list where the minutes of the YP meeting were posted?

1. As a project we need to decide whether or not to undertake this work. Not
all projects have decided to make any changes. The discussions we had at the
last meeting made it feel as though it was a forgone conclusion by those who
spoke up that we would take on this work. Is that the consensus? Silence
represents agreement?

Also discussed at the June 24th, 2020 OpenEmbedded Happy Hour, where many points were raised without foregone conclusions.

6. Terminology. The Linux kernel project has put out some recommendations:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=49decddd39e5f6132ccd7d9fdc3d7c470b0061bb

From the Linux coding style diff, "avoid introducing new usage", refers to new names, rather than changing existing systems with consequential impact on distributed supply chains for live systems.

To start the discussion, can we please get a consensus on item #1?

It would be helpful to define the work being proposed ("whether or not to undertake this work"), before seeking new funding for the proposed work, from YP or OE stakeholders.

Rich