)]}'
{
  "commit": "1f0fed312a40620b9f33f712d180a3c649e91e27",
  "tree": "403430dcb9d3a74f4eedea7622b745d8c5d78553",
  "parents": [
    "16bd9f20a403117f2e0d9bcda6c6e621d3763e77"
  ],
  "author": {
    "name": "brian m. carlson",
    "email": "sandals@crustytoothpaste.net",
    "time": "Wed Jul 16 00:25:23 2025 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Jul 16 07:35:45 2025 -0700"
  },
  "message": "SubmittingPatches: allow non-real name contributions\n\nOur submission guidelines require people to use their real name, but\nthis is not always suitable for various reasons.\n\nFor people who are transgender or non-binary and are transitioning or\nwho think they might want to transition, it can be a major obstacle and\ncause major discomfort to require the use of their real name.  This is\nmade worse by the fact that Git provides no way to change names built\ninto history, so the use of a deadname is forever.  Our code of conduct\nstates that we \"pledge to act and interact in ways that contribute to an\nopen, welcoming, diverse, inclusive, and healthy community,\" and\nchanging this policy is one way we can improve things for contributors.\n\nIn addition, there are some developers who are so widely known\npseudonymously that they have a Wikipedia page with their handle and no\nreal name.  It would seem silly to reject patches from people who are\nknown and respected in their open-source community just because they\ndon\u0027t wish to share a real name.\n\nThere are also other good reasons why people might operate\npseudonymously: because they or their family members are well known and\nthey wish to protect their privacy, because of current or past\nharassment or retaliation or fear of that happening in the future, or\nbecause of concerns about unwanted attention from government officials\nor other authority figures.  As much as possible, we want to welcome\ncontributions from anyone who is willing to participate positively in\nour community without having them worry about their safety or privacy.\n\nIn all of these cases, we should allow people to proceed using a\npreferred name or pseudonymously if, in their best judgment, that\u0027s the\nright thing to do.  State that it is common to use a real name but\nexplicitly mention that contributors who are not comfortable doing so or\nprefer to operate pseudonymously or under a preferred name can proceed\notherwise, provided the name is distinctive, identifying, and not\nmisleading.  For instance, using U+2060 (WORD JOINER) as one\u0027s ID would\nlikely be distinctive but not identifying, since most people would have\ntrouble reading it due to its zero-width nature.\n\nWe prohibit identities which are misleading, since our goal is to create\na community which works together with a common goal, and misleading or\ndeceiving others is not conducive to good community or compatible with\nour code of conduct, nor is it compatible with making a legal assertion\nabout the provenance of one\u0027s code.\n\nExplicitly prohibit anonymous contributions to ensure that we have some\nline of provenance to a known (if pseudonymous) author who might be able\nto respond to questions about it.  Explain that this is the reason we\nhave this policy to help contributors understand the rationale better.\n\nUse \"some form of your real name\" since some current contributors use\nshortened forms of their name or use initials, which have always been\nconsidered acceptable.  This helps guide people who would be fine using\ntheir real name but have misconfigured `user.name` thinking it is\nintended to be a username or is used for authentication (despite our\ndocumentation to the contrary), but also allows for a variety of\ncircumstances where the contributor would feel more comfortable not\ndoing so.\n\nNote that this policy is the same as that of the Linux kernel[0] and the\nCNCF[1], as well as many smaller projects.  The Linux kernel patch was\nAcked-by one of the Linux Foundation\u0027s lawyers, Michael Dolan, so it\nappears these changes have had legal review.\n\nAdditionally, retain the section header ID for ease of linking across\nversions.\n\n[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id\u003dd4563201f33a022fc0353033d9dfeb1606a88330\n[1] https://github.com/cncf/foundation/blob/659fd32c86dc/dco-guidelines.md\n\nSigned-off-by: brian m. carlson \u003csandals@crustytoothpaste.net\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "958e3cc3d54741261902123dd832619047d51819",
      "old_mode": 33188,
      "old_path": "Documentation/SubmittingPatches",
      "new_id": "86ca7f6a78a9b69294eb97bbbc1138376f40198b",
      "new_mode": 33188,
      "new_path": "Documentation/SubmittingPatches"
    }
  ]
}