diff options
| -rw-r--r-- | site/git/index.php | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/site/git/index.php b/site/git/index.php index a3e3cc8..f86af09 100644 --- a/site/git/index.php +++ b/site/git/index.php @@ -80,7 +80,8 @@ <h2 id="guidelines">General guidelines for submitting patches <span class="r"><a href="#guidelines">#guidelines</a></span></h2> <p> Using your legal name is <b>not</b> required. For reasons why we have this policy, read <a href='http://geekfeminism.org/2012/09/29/quick-hit-how-git-shows-the-patriarchal-nature-of-the-software-industry/'>this article</a>. You can use an assumed name, or your company name (if you have a company), if you want. Also, read <a href='http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/'>this article</a>. Unfortunately, git appears to be stuck with these problems, when an author changes their name, and we don't have a concrete answer to it. - As far as we know, publishing your legal name isn't even required for copyright purposes; in fact, "pen names" are common in literature. + As far as we know, publishing your legal name isn't even required for copyright purposes; in fact, "pen names" are common in literature. You can also + submit patches without a name, if you want (instructions are detailed on this page). </p> <p> When submitting any kind of documentation, try not to use the terms him/her, she/he, his/her, or anything that is gender biased. <b>Use their, they, them, those people, that person, and so on.</b> <a href="https://gist.githubusercontent.com/0xabad1dea/8870b192fd1758743f66/raw/a230fa3438ce60c538dba31830fa88143245b719/singularthey.md">You are making a huge difference</a>. |