1. Cncf-Toc
  2. Messages

Expanded

Topics Messages Polls
   Date   
Re: Real Name Policy for CNCF

Aeva
 

+1 to the concerns here, and +1 to having the appropriate folks discuss this issue, in ways that consider both the legal requirements regarding copyright assignment, and precedent in other organizations, and the societal implications.

Without commenting in any way on the merits of ChrisA's update, I would like to suggest reverting that FAQ change to give time for the conversation to happen and so that the guidance (and its ramifications) can be properly thought out.

Best,
--Aeva


On Wed, Jul 6, 2022 at 3:09 PM Davanum Srinivas <davanum@...> wrote:
Josh,

I would tell folks to NOT change anything that they are doing today. 

ChrisA jumped the gun and pushed the change directly to master. I was looking to have a conversation + debate.

I am waiting for some notes from the original person who asked the questions, so then we could figure out how to get it in front of the GB Legal Committee.

So tell them to hang tight and not change a thing. Let this be a FAQ for *new* project(s) for now.

-- Dims

On Wed, Jul 6, 2022 at 5:27 PM Josh Berkus <jberkus@...> wrote:
Dims,

Can you explain how we reconcile this with the CNCF code of conduct?

Asking because a simple reading of it would require "deadnaming" many of
our trans contributors.  How do we avoid that?


--
-- Josh Berkus
    Kubernetes Community Architect
    OSPO, OCTO



--
Davanum Srinivas :: https://twitter.com/dims
Re: Real Name Policy for CNCF

Josh Berkus
 

On 7/6/22 15:09, Davanum Srinivas wrote:
So tell them to hang tight and not change a thing. Let this be a FAQ for *new* project(s) for now.
Can we get a clarification on "Real Names", please? That could resolve this. I'm sure other LF projects aren't turning away trans contributors ... is there language they use?

--
-- Josh Berkus
Kubernetes Community Architect
OSPO, OCTO
Re: Real Name Policy for CNCF

Davanum Srinivas
 

ChrisA,

Hope you don't mind me talking candidly :) should have cross checked the recipients :)

-- Dims


On Wed, Jul 6, 2022 at 6:09 PM Davanum Srinivas <davanum@...> wrote:
Josh,

I would tell folks to NOT change anything that they are doing today. 

ChrisA jumped the gun and pushed the change directly to master. I was looking to have a conversation + debate.

I am waiting for some notes from the original person who asked the questions, so then we could figure out how to get it in front of the GB Legal Committee.

So tell them to hang tight and not change a thing. Let this be a FAQ for *new* project(s) for now.

-- Dims

On Wed, Jul 6, 2022 at 5:27 PM Josh Berkus <jberkus@...> wrote:
Dims,

Can you explain how we reconcile this with the CNCF code of conduct?

Asking because a simple reading of it would require "deadnaming" many of
our trans contributors.  How do we avoid that?


--
-- Josh Berkus
    Kubernetes Community Architect
    OSPO, OCTO



--
Davanum Srinivas :: https://twitter.com/dims


--
Davanum Srinivas :: https://twitter.com/dims
Re: Real Name Policy for CNCF

Davanum Srinivas
 

Josh,

I would tell folks to NOT change anything that they are doing today. 

ChrisA jumped the gun and pushed the change directly to master. I was looking to have a conversation + debate.

I am waiting for some notes from the original person who asked the questions, so then we could figure out how to get it in front of the GB Legal Committee.

So tell them to hang tight and not change a thing. Let this be a FAQ for *new* project(s) for now.

-- Dims


On Wed, Jul 6, 2022 at 5:27 PM Josh Berkus <jberkus@...> wrote:
Dims,

Can you explain how we reconcile this with the CNCF code of conduct?

Asking because a simple reading of it would require "deadnaming" many of
our trans contributors.  How do we avoid that?


--
-- Josh Berkus
    Kubernetes Community Architect
    OSPO, OCTO



--
Davanum Srinivas :: https://twitter.com/dims
Re: Real Name Policy for CNCF

Josh Berkus
 

Dims,

Can you explain how we reconcile this with the CNCF code of conduct?

Asking because a simple reading of it would require "deadnaming" many of our trans contributors. How do we avoid that?


--
-- Josh Berkus
Kubernetes Community Architect
OSPO, OCTO
Fluid 2022 Annual Review submitted

顾荣 <gurongwalker@...>
 

Dear CNCF TOC members,

I am Rong Gu, a maintainer of Fluid project (CNCF sandbox). We have submitted the Fluid 2022 Annual Review. The PR is here：https://github.com/cncf/toc/pull/870.  Please kindly review it. Thanks.

Best,
Rong
Re: Mentoring WG for Approval

Katie Gamanji
 

Reviewed too! LGTM


On Fri, 1 Jul 2022, 17:06 Davanum Srinivas, <davanum@...> wrote:
Just reviewed. LGTM Josh. Thanks for wrapping it up.

-- Dims

On Fri, Jul 1, 2022 at 11:59 AM Josh Berkus <jberkus@...> wrote:
Dims, Kate, Matt, all:

Here's the final on the charter for the Mentoring WG:

https://github.com/cncf/tag-contributor-strategy/pull/188

Once you approve this, I'll update references elsewhere.

--
-- Josh Berkus
    Kubernetes Community Architect
    OSPO, OCTO








--
Davanum Srinivas :: https://twitter.com/dims
Re: Real Name Policy for CNCF

Gareth Rushgrove
 

Worth noting the policy doesn't define "real name".

This could be implied to mean full legal name (not a lawyer, but I
think that's the common usage term in law). Or you could imply it to
mean "the name literally everyone calls me in the real world". Those
two names for lots of people could be different.

That I think makes it clearer how this can be exclusionary and open to
being weaponised against marginalised folks.

Gareth

On Mon, 4 Jul 2022 at 07:26, Frederick Kautz <frederick@...> wrote:

This policy is going to exclude a lot of people who are at risk from harassment. A significant number of people use pseudonyms today. We should consider revising this policy. Perhaps there is a path where we can allow people to register their pseudonym to help balance privacy and legal protection of the projects.

On Sun, Jul 3, 2022 at 2:23 PM Christoph Blecker <cblecker@...> wrote:

This isn't so much a question, as it is a request for the CNCF/TOC to review and possibly reverse this policy. While I and many others choose to use their legal name when contributing to projects, there are many reasons why someone might choose to use a pseudonym while contributing. Examples of some of those reasons and the harm that a "real names" policy can create are discussed in the EFF's open letter to Facebook, when Facebook introduced their real name policy in 2015 [1].

Pseudonyms are also used regularly when publishing copyrighted works. When used in the book publishing industry, they are commonly known as "pen names". The U.S. Copyright Office [2] (where the CNCF is based) and the Canadian Intellectual Property Office [3] (where I am personally based) both affirm that use of a pseudonym is permitted.

I'm sure there are others who have more expertise in the subject who could provide more reasons and context, but I personally feel like this is an unnecessary barrier to contribution and may exclude talented contributors from our projects.

Cheers,
Christoph Blecker

[1]: https://www.eff.org/document/open-letter-facebook-about-its-real-names-policy
[2]: https://www.copyright.gov/circs/circ32.pdf
[3]: https://www.ic.gc.ca/eic/site/cipointernet-internetopic.nsf/eng/h_wr02281.html?Open&wt_src=cipo-cpyrght-main&wt_cxt=learn#copyrightInformation


On Sat, Jul 2, 2022 at 3:04 PM Davanum Srinivas <davanum@...> wrote:

Hi Folks,

There was a query from one of the projects about Pseudonyms for DCO and CLA. The CNCF staff has clarified the current policy:
- https://github.com/cncf/foundation/issues/379
- https://github.com/cncf/toc/commit/4b5d5049bce9719bff4b10939389204bc0493557

If you have any questions related to this policy, please chime in.

thanks,
Dims

--
Davanum Srinivas :: https://twitter.com/dims
--
Gareth Rushgrove
@garethr

garethr.dev
devopsweekly.com
Re: Real Name Policy for CNCF

Frederick Kautz
 

This policy is going to exclude a lot of people who are at risk from harassment. A significant number of people use pseudonyms today. We should consider revising this policy. Perhaps there is a path where we can allow people to register their pseudonym to help balance privacy and legal protection of the projects.

On Sun, Jul 3, 2022 at 2:23 PM Christoph Blecker <cblecker@...> wrote:
This isn't so much a question, as it is a request for the CNCF/TOC to review and possibly reverse this policy. While I and many others choose to use their legal name when contributing to projects, there are many reasons why someone might choose to use a pseudonym while contributing. Examples of some of those reasons and the harm that a "real names" policy can create are discussed in the EFF's open letter to Facebook, when Facebook introduced their real name policy in 2015 [1].

Pseudonyms are also used regularly when publishing copyrighted works. When used in the book publishing industry, they are commonly known as "pen names". The U.S. Copyright Office [2] (where the CNCF is based) and the Canadian Intellectual Property Office [3] (where I am personally based) both affirm that use of a pseudonym is permitted.

I'm sure there are others who have more expertise in the subject who could provide more reasons and context, but I personally feel like this is an unnecessary barrier to contribution and may exclude talented contributors from our projects.

Cheers,

On Sat, Jul 2, 2022 at 3:04 PM Davanum Srinivas <davanum@...> wrote:
Hi Folks,

There was a query from one of the projects about Pseudonyms for DCO and CLA. The CNCF staff has clarified the current policy:
- https://github.com/cncf/toc/commit/4b5d5049bce9719bff4b10939389204bc0493557

If you have any questions related to this policy, please chime in.

thanks,
Dims

--
Davanum Srinivas :: https://twitter.com/dims
[RESULT] CubeFS (formerly known as ChubaoFS) passed for incubation

Amye Scavarda Perrin
 

Re: Real Name Policy for CNCF

Christoph Blecker
 

This isn't so much a question, as it is a request for the CNCF/TOC to review and possibly reverse this policy. While I and many others choose to use their legal name when contributing to projects, there are many reasons why someone might choose to use a pseudonym while contributing. Examples of some of those reasons and the harm that a "real names" policy can create are discussed in the EFF's open letter to Facebook, when Facebook introduced their real name policy in 2015 [1].

Pseudonyms are also used regularly when publishing copyrighted works. When used in the book publishing industry, they are commonly known as "pen names". The U.S. Copyright Office [2] (where the CNCF is based) and the Canadian Intellectual Property Office [3] (where I am personally based) both affirm that use of a pseudonym is permitted.

I'm sure there are others who have more expertise in the subject who could provide more reasons and context, but I personally feel like this is an unnecessary barrier to contribution and may exclude talented contributors from our projects.

Cheers,

On Sat, Jul 2, 2022 at 3:04 PM Davanum Srinivas <davanum@...> wrote:
Hi Folks,

There was a query from one of the projects about Pseudonyms for DCO and CLA. The CNCF staff has clarified the current policy:
- https://github.com/cncf/toc/commit/4b5d5049bce9719bff4b10939389204bc0493557

If you have any questions related to this policy, please chime in.

thanks,
Dims

--
Davanum Srinivas :: https://twitter.com/dims
Real Name Policy for CNCF

Davanum Srinivas
 

Hi Folks,

There was a query from one of the projects about Pseudonyms for DCO and CLA. The CNCF staff has clarified the current policy:
- https://github.com/cncf/toc/commit/4b5d5049bce9719bff4b10939389204bc0493557

If you have any questions related to this policy, please chime in.

thanks,
Dims

--
Davanum Srinivas :: https://twitter.com/dims
Re: Mentoring WG for Approval

Davanum Srinivas
 

Just reviewed. LGTM Josh. Thanks for wrapping it up.

-- Dims


On Fri, Jul 1, 2022 at 11:59 AM Josh Berkus <jberkus@...> wrote:
Dims, Kate, Matt, all:

Here's the final on the charter for the Mentoring WG:

https://github.com/cncf/tag-contributor-strategy/pull/188

Once you approve this, I'll update references elsewhere.

--
-- Josh Berkus
    Kubernetes Community Architect
    OSPO, OCTO








--
Davanum Srinivas :: https://twitter.com/dims
Mentoring WG for Approval

Josh Berkus
 

Dims, Kate, Matt, all:

Here's the final on the charter for the Mentoring WG:

https://github.com/cncf/tag-contributor-strategy/pull/188

Once you approve this, I'll update references elsewhere.

--
-- Josh Berkus
Kubernetes Community Architect
OSPO, OCTO
Re: Comment period for Interim Code of Conduct documentation

Davanum Srinivas
 

Josh,

Thanks, Kudos go to Joanna and the interim CoCC team!.


On Thu, Jun 30, 2022 at 8:46 PM Josh Berkus <jberkus@...> wrote:
On 6/29/22 13:50, Erin Boyd wrote:
>
> As announced in today’s blog post
> <https://www.cncf.io/blog/2022/06/29/comment-period-for-interim-code-of-conduct-draft-documentation/>,
> the Interim CNCF Code of Conduct Committee has posted drafts of the
> following Code of Conduct documentation to the CNCF website for public
> review and comment:

These are really excellent ... and complicated!

Had some minor feedback around wording in just a couple of places
(submitted).

--
-- Josh Berkus
    Kubernetes Community Architect
    OSPO, OCTO








--
Davanum Srinivas :: https://twitter.com/dims
Re: Comment period for Interim Code of Conduct documentation

Josh Berkus
 

On 6/29/22 13:50, Erin Boyd wrote:
As announced in today’s blog post <https://www.cncf.io/blog/2022/06/29/comment-period-for-interim-code-of-conduct-draft-documentation/>, the Interim CNCF Code of Conduct Committee has posted drafts of the following Code of Conduct documentation to the CNCF website for public review and comment:
These are really excellent ... and complicated!

Had some minor feedback around wording in just a couple of places (submitted).

--
-- Josh Berkus
Kubernetes Community Architect
OSPO, OCTO
Comment period for Interim Code of Conduct documentation

Erin Boyd
 

CNCF Community Members,


As announced in today’s blog post, the Interim CNCF Code of Conduct Committee has posted drafts of the following Code of Conduct documentation to the CNCF website for public review and comment:


We welcome your feedback.  If you have comments, please share them with us using our Feedback Form on or before July 15, 2022 (in any time zone).


Thank you.


Erin A. Boyd

Chairperson, Interim CNCF Code of Conduct Committee



--

Erin A. Boyd

Director of Emerging Technologies OCTO

Distinguished Engineer

Red Hat

eboyd@...   

Re: [cncf-gb] TOC Election Results for GB Special Election

Katie Gamanji
 

Massage congrats and welcome on the TOCs!


On Wed, 29 Jun 2022, 12:08 Stephen Augustus, <hey@...> wrote:
Congrats Cathy!!!

On Tue, Jun 28, 2022, 17:32 Richard Hartmann <richih@...> wrote:
(Replying to both lists at once and adding Cathy directly, moving Jeffrey to CC)

Congrats, Cathy. Welcome aboard!

On Tue, Jun 28, 2022 at 11:05 PM Jeffrey Sica <jsica@...> wrote:
>
> Many thanks to all who participated in this process, I’m pleased to announce the results of the special election.
>
>
> GB appointed seat:
>
> Cathy Zhang
>
>
>
>





Locked [CNCF] Greetings from Singapore

Turritopsis Dohrnii Teo En Ming
 

Subject: [CNCF] Greetings from Singapore

Hi!

My name is Mr. Turritopsis Dohrnii Teo En Ming.

I am a Targeted Individual (TI) living in Singapore.

Just a short intro :)
Re: [cncf-gb] TOC Election Results for GB Special Election

Stephen Augustus
 

Congrats Cathy!!!


On Tue, Jun 28, 2022, 17:32 Richard Hartmann <richih@...> wrote:
(Replying to both lists at once and adding Cathy directly, moving Jeffrey to CC)

Congrats, Cathy. Welcome aboard!

On Tue, Jun 28, 2022 at 11:05 PM Jeffrey Sica <jsica@...> wrote:
>
> Many thanks to all who participated in this process, I’m pleased to announce the results of the special election.
>
>
> GB appointed seat:
>
> Cathy Zhang
>
>
>
>





821 - 840 of 8023