Right now we're in the discussion phase. As far as I'm concerned, if most people who speak up decide that's what we should do, then that's what I'll work towards; although (from the feedback so far)

On 7/15/20 10:45 AM, Trevor Woerner wrote: "Master" has been used in commit headers, so do we intend on re-writing git history? -armin

To be really clear, whilst you keep saying this, I have heard of no such plans from the LF and I have asked. Yes, the LF is a strong believer in diversity and does take these issues seriously but as

<pidge@...> wrote: If people find the terms whitelist/blacklist offensive I encourage them to communicate this to the community. Other than the obvious (which seems may be a coincidence?) I

This is a good question. Some projects are replacing "master" in isolation; such as when used as a branch name. Other projects are only replacing "master" when paired with "slave".

If the word "master" alone is considered non-inclusive for people in the US then CVs are also affected, like speaker bios at conferences. What replacement term are US universities using for their

A note here, as I was talking with Paul Barker about this last week. We've already done this in part of YP, in the now retired autobuilder code base (about 6 years ago), removing master/slave

On 7/14/20 10:31 PM, Trevor Woerner wrote: Well, as I see it, the LF will make a ruling and then the Yocto Project with have to follow. If OE decides not to change then this

Thank you Rich, Am Mi., 15. Juli 2020 um 16:00 Uhr schrieb Rich Persaud <persaur@...>: This is exactly what I wanted to convey. Couldn't word it any better way.

"Trunk" also has the advantage of describing a physical object ("tree") which overlaps with the functional role of the digital object being named. Here's the etymology of "main", which does not

In comparison to Github (hundreds of employees, sold for billions) or the Linux kernel with contributors from large commercial ecosystems (e.g. RedHat/IBM and Google/Android), OE was architected by a

<jester@...> wrote: This is actually the most interesting point to me. In anything we undertake, the higher level goals should be stated (not just a technical document with rename

I'm old we should rename "master" to "trunk". Philip

https://civs.cs.cornell.edu/ Is what we use now. Philip

Just focusing on points that are prominent to me. Comments inline. Am Mi., 15. Juli 2020 um 11:12 Uhr schrieb Richard Purdie <richard.purdie@...>: Fully agreed. One of the things I

Thanks for bringing this up and writing a summary. The OE and YP TSCs are aware of this and are starting to have discussions about it. I have also been looking at what other projects and the Linux

Review comments will likely appear when patches are submitted. On that note, I recommend we move the coding style documentation from the wiki into the oe-core git repository so that changes can

Hi Jacob, Good point. I wonder where we are on the topic of anonymous voting? I think someone was working on this for various other purposes (electing TSC members, various voting for OE

Hi Josef, Not at all, your opinion is very much appreciated! Thank you for your input. I think, as a project, we need to have a position on this, and you've contributed to the discussion in a

I post them on the yocto mailing list in plain text with formatting, or you can see them all collected here in google