Ric, if you get this, please reply - my ISP kept giving me "Email ACCEPTED" and then sending it into a black hole it seems. Perhaps I used the word "sn0wfl4ke" too many times? cheers zen ----- Forwarded message from Zenaan Harkness ----- From: Zenaan Harkness To: CypherPunks Cc: wayward4now@gmail.com, andrewanglin84@gmail.com, rms@gnu.org, inspector_rikati@yahoo.com.au Date: Sun, 3 Nov 2019 10:15:18 +1100 Subject: Re: Git falls to the giant swinging CoCs! -- [gitrevnews@gmail.com: Git Rev News edition 56] Anyone know A Better Way for such emails as below? Email is broken in some ways it seems - the below email evidently had a few trip words or repetitions such that the ISP, despite its mail server saying to me "ACCEPTED" for each (of 5) recipient, has not sent the email through. No error, no warning, just "Email ACCEPTED" and then into a black hole! This is disappointing of course. And I guess if they (Telstra's SMTP server in this case) lower their SPAM scoring, then too much spam gets through and folks get annoyed - looks like this is a "broken" in email? Anyway, may be this one will similarly be black holed ... let's see... On Sun, Nov 03, 2019 at 09:50:16AM +1100, Zenaan Harkness wrote:

Those with limp and dodgy feelz, are inevitably compelled to seek "safety" in numbers, introducing CoCs (code of conduct aka "community stasi policing"), raging inflamed discussions, and censorship "safety first" committees to make damnably sure their snow CoC is obeyed!

Sadly, Git is the latest project to fall (see below).

Perhaps we ought begin to consider anti-dotes to such snowflakery?

- separation of man and snowflake

have the place (e.g. mailing list) for adults to get on with work

have the snowflake hall, say snowflakes@$MY_PROJECT.$TLD

As we see recently with the FSF and Richard Stallman, those who contribute over a long period of time, and have deceived the group by successfully hiding their snowflakery and huge swinging CoC demands, tend towards the public lynch mob, the coup, and the crucifixion of good men, including the founder.

Such deception, where folks instead of finding or creating their own space like a man, they simmer and seethe in anger, plotting their evil for the day the leader takes a public hit from morons, are deceivers and back stabbers, cowards of the first order.

- never surrender to terrorists

name evil behaviour, and handle the evil behaviour first and foremost, at all times, as the first evil, even in the face of a lynch mob

blackmail should be the first evil, the first "illegal" crime punishable by severe punishments, even where the perpetrator of the blackmail is a spook or deep CoC

deception and hiding of snowflakery is a ground for dismissal - sure, the flake might chuck an Amway retard programming spaz and try to fuck over the group by "leave a big hole" (what do we expect from CoCs anyway?) - but let's just be thankful for the work they did do, and get on with being men - in the long run, we'll be better off without that undermining shit!

(for those who missed the memo, leave a big hole means "make my pathetic self really valuable and then leave a huge hole in the group by leaving" - well, men don't give a firetruck, we learn the lesson of the CoC and move on, filling that hole, spoon by bloody spoon if we have to!)

- always immediately (or as soon as possible) name a terrorist act

e.g. the Koch brothers come to your Think Pad Update Services Association (TP-USA) offering "a million fiats for your CoC"

make immediate public announcement "Koch brothers seek CoC, attempt to corrupt men@list with limp fiats and demanding censorship"

e.g. snowflake seeks to censor men@list with large swinging CoC, even though snowflakes@list is offered and actively CoCing around

make public announcement "apparently snowflakes like CoC so bad, they seek to ram CoC in face of men@list"

Yes, we should (probably, presumably, duty of care etc)

- make an up front, open and honest declaration of intent for the men@list list

"are you a man or a f*#!& meme, if the former you may join the primary list, if anything else, join the snowflakes and/ or seek a mentor willing to personally tutor you; if reading this message was overly stressful to your feelz, get some firetrucking help already!"

if your project is so fortunate as to have at least one contributor who is willing to be on both the men@list list, and the snowjobs@list, all the better - in fact there are plenty of mediator types out there, so it's usually only a very short matter of time before a White Knight steps up to vigorously seize the CoC obeying kudos creds on the snowjobs list

Make such declarations so folks know what they're getting into from the get go.

After that, it's open season muffas :D

"Oh PLEASE muh little snowflake, pleease step into the ring!

Yes my precious, you know you wanna be a man, so join, don't hesitate, join the list of men and leave your tissues outside. "

Of course, if everyone, or everyone of any authority in a project, is a censorship craving CoC nut, and you happen to be a man, or at least a man in training, we suggest you join another project, or start yer own, such as NoMoreAnalCommittees@for.men.only

Hopefully there are further decisive CoC-flake slaying ideas and approaches out there - experiment and report back, so we can share the winning to all men of good character and high ideals.

Peace,

----- Forwarded message from Git Rev News Team -----

From: Git Rev News Team To: git-rev-news@freedbms.net Date: Sat, 2 Nov 2019 19:38:22 +0000 Subject: Git Rev News edition 56 List-ID: 318f078aaef2e75d94c2bf757mc list <318f078aaef2e75d94c2bf757.118053.list-id.mcsv.net>

View this email in your browser (https://mailchi.mp/5e0c777b9b30/git-rev-news-edition-56?e=2778fe651d)

** Git Rev News: Edition 56 (October 26th, 2019) ------------------------------------------------------------

Welcome to the 56th edition of Git Rev News (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=a628f14a1e&e=2778fe651d) , a digest of all things Git. For our goals, the archives, the way we work, and how to contribute or to subscribe, see the Git Rev News page (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=bce39d838b&e=2778fe651d) on git.github.io.

This edition covers what happened during the month of September 2019.

** Discussions ------------------------------------------------------------

** General ------------------------------------------------------------ * Growing the Git community (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=ba7d757500&e=2778fe651d) Derrick Stolee, who prefers to be called Stolee, emailed the mailing list after the Virtual Contributor Summit (see previous edition (/rev_news/2019/09/25/edition-55/#general) ) saying he wanted to further discuss some ideas, that had been shared during the Summit, about “Inclusion & Diversity” with the goal of making the community more welcoming to new contributors of all kinds. He listed some possible problems that could prevent new contributors entering the community: 1. Discovering how to contribute to Git is non-obvious. 2. Submitting to a mailing list is a new experience for most developers. This includes the full review and discussion process. 3. The high standards for patch quality are intimidating to new contributors. 4. Some people do not feel comfortable engaging in a community without a clear Code of Conduct. This discomfort is significant and based on real experiences throughout society. 5. Since Git development happens in a different place than where users acquire the end product, some are not aware that they can contribute. Then Stolee proposed actions to address the problems: 1. Improve the documentation for contributing to Git. 2. Add more pointers to GitGitGadget. 3. Introduce a new “mentors” mailing list. 4. Add an official Code of Conduct. 5. Advertise that Git wants new contributors. Each action was explained and justified, sometimes pointing to interesting research like the recent paper "”We Don’t Do That Here”: How Collaborative Editing With Mentors Improves Engagement in Social Q&A Communities” (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=328cea8906&e=2778fe651d) . Stolee also proposed some metrics to be measured between releases to monitor how the community are doing: 1. How many first-time contributors sent a patch? 2. How many contributors had their first commit accepted into the release? 3. How many contributors started reviewing? 4. How many total patches/reviews did the list receive? His email was very detailed with many suggestions about how to implement the actions, and he asked interesting questions to gather peoples’ opinion. Denton Liu replied to Stolee sharing some thoughts as a “relatively new contributor (just less than a year)”. He said that from his experience to get more contributors, we should try to answer the “how do we make it more fun to contribute to Git?” question. He recalled that most of his time learning to contribute to Git “stemmed from the fact that there’s a lot of tribal knowledge that’s not really written down anywhere”. As Stolee had mentioned the “My First Contribution” document (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=5aed1d5401&e=2778fe651d) , which was recently contributed by Emily Shaffer, Denton said that it would have really helped him get started. Denton also suggested improving transparency about what happens to patches sent to the mailing list. Mike Hommey replied to Stolee suggesting an additional problem which is that newcomers don’t really have any idea what they could contribute. Johannes Schindelin, alias Dscho, replied to Mike that newcomers need experienced developers to validate the ideas they would like to implement in Git, before they can be confident enough to work on them. And they also need to be shown ideas they could implement. Dscho then talked about the GitGitGadget issue list (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=9697445ccf&e=2778fe651d) which is open and “intended to accumulate possible project ideas”. Dscho also acknowledged the Chromium Git issue list (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=53416a7f8f&e=2778fe651d) which is another issue tracker with a similar purpose. Replying to Stolee, Jeff King, alias Peff, who is responsible for the main Git web site (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=ebec6f87b0&e=2778fe651d) , suggested improving the community page (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=17d8d30313&e=2778fe651d) to add more information for beginners. He said he was open to accepting patches or pull requests (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=b6fa76a1f5&e=2778fe651d) . Elijah Newren mostly agreed with Stolee’s email, but suggested a less strongly worded tone when talking about goals and existing problems. Junio Hamano, the Git maintainer, replied to Stolee about the goal of the project and the metrics that we could use with the following:

We first should make sure that we serve existing users and existing community members well. So well that other people who are not yet our “existing” users and members would want to become part of us, in order to join the fun and share the benefit. If we cannot serve even the existing members well, we shouldn’t be talking about acquiring new members. He then proposed to measure “community-member happiness” with metrics like “This many percent of total community member population have been active this month”. The discussion involved a number of other Git developers like Jakub Narębski, Emily Shaffer, Garima Singh, Pierre Tardy, Philip Oakley and Randall S. Becker. A number of people commented especially on the subject of adding an official Code of Conduct, which will be reported on in a separate article below. Otherwise it remains to be seen if many actions will be taken to make the project more welcoming to new contributors. * [PATCH] add a Code of Conduct document (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=787a6de364&e=2778fe651d) Following the Virtual Contributor Summit (see previous edition (/rev_news/2019/09/25/edition-55/#general) ) and the discussions about growing the Git community (see the article above), Jeff King, alias Peff, decided to send a patch to add a code of conduct. In his patch he says that “it may be a good time to cement our expectations when things are quiet, since it gives everybody some distance rather than focusing on a current contentious issue”. Many people indeed agreed in the previous discussions with that point of view, and the idea of a Code of Conduct in the first place. Peff says that his patch adapts the Contributor Covenant Code of Conduct from https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=5adf127071&e=2778fe651d and that “it’s also the same document used by the Git for Windows project”. One of the changes is that for dealing with community issues, the document spreads the responsibility to the Project Leadership Committee (git@sfconservancy.org) instead of the only maintainer, Junio C Hamano. Peff also mentioned a commit (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=15b456f01f&e=2778fe651d) by Michael Haggerty from June 2013 that he found in a previous discussion and that has nice set of guidelines about how to review code. A number of the replies were about the Project Leadership Committee as it’s not easy to know who is part of it. This was acknowledged by Peff who sent a follow-up patch (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=421fab31ff&e=2778fe651d) to address the issue by listing the Project Leadership Committee members with their email addresses and by saying that they can also be contacted individually. Even though there was some disagreement, in general most of the people taking part in the discussion agreed with Peff’s patches. Junio later sent a follow-up email (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=74ca410bff&e=2778fe651d) with the subject “Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks” to get more developers to formally agree with the final patch, which then several did. The commit adding the Code of Conduct has since been merged into the master branch.

** Releases ------------------------------------------------------------ * Git 2.24.0-rc0 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=3d6cc12fce&e=2778fe651d) * Git for Windows 2.24.0-rc0 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=b2b288861c&e=2778fe651d) * GitHub Enterprise 2.18.4 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=f172a41e58&e=2778fe651d) , 2.17.10 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=240e998cc2&e=2778fe651d) , 2.16.19 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=dfe2501cc4&e=2778fe651d) , 2.15.24 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=22a0742454&e=2778fe651d) , 2.18.3 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=202657f31e&e=2778fe651d) , 2.17.9 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=b4d16f290a&e=2778fe651d) , 2.16.18 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=e0ac42fc84&e=2778fe651d) , 2.15.23 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=a904fc55ab&e=2778fe651d) * GitLab 12.4 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=e304454b99&e=2778fe651d) , 12.3.5, 12.2.8, and 12.1.14 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=fb97541979&e=2778fe651d) , 12.3.4 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=57eab5184a&e=2778fe651d) , 12.3.3, 12.2.7, and 12.1.13 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=23cb7e2aae&e=2778fe651d) , 12.3.2, 12.2.6, and 12.1.12 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=b918415d3c&e=2778fe651d) , 12.3.1 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=54bc2dbc3a&e=2778fe651d) , 12.3 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=d98959ffd6&e=2778fe651d) * Bitbucket Server 6.7 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=4f05b964e2&e=2778fe651d) * Gerrit Code Review 3.0.3 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=5fd9d0e5c5&e=2778fe651d) * GitKraken 6.3.0 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=058872013d&e=2778fe651d) , 6.2.1 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=5891df2357&e=2778fe651d) * GitHub Desktop 2.2.1 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=c0ad13552e&e=2778fe651d) , 2.2.0 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=37ac140db2&e=2778fe651d)

** Other News ------------------------------------------------------------

Various * A new maintainer for Git-Gui, Pratyush Yadav (@prati0100), came forward (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=f7e91a5b66&e=2778fe651d) . Let’s praise and thank him for volunteering. * The Gerrit User Summit 2019 is going to be broadcasted on live.gerritforge.com (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=7d32ecc592&e=2778fe651d) and will include talks about JGit and Gerrit Code Review, including major members of the Git Community, like Jonathan Nieder and Terry Parker.

Light reading * Commit graph drawing algorithms (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=16eead2ddf&e=2778fe651d) by pvigier (Pierre Vigier), describes algorithms used by various tools including one in pvigier’s prototype git client called gitamine (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=3e6cd7d290&e=2778fe651d) . * Git Pathspecs and How to Use Them (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=948cc4a0f4&e=2778fe651d) by Adam Giese. * GitHub Actions, the missing notes: CMake, Qt and IFW (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=6882f6ab56&e=2778fe651d) by Michele ‘skypjack’ Caini, shows how he uses GitHub Actions (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=30ceb11ca7&e=2778fe651d) in his project. (GitHub Actions, still in public beta, were first covered in Git Rev News #44 (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=e1d7c5807f&e=2778fe651d) ) * An Unintentionally Comprehensive Introduction to GitHub Actions CI (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=c873584d45&e=2778fe651d) by Tierney Cyren – with example of an application build on top of Node.js. * Scheduling Jekyll posts with Netlify and GitHub Actions (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=7563b22cfa&e=2778fe651d) by Nicholas C. Zakas on his Human Who Codes blog: using a GitHub Action cron job to schedule Netlify builds for static site generated blog posts (which was previously done using Netlify and AWS Lambda (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=85e6f286c0&e=2778fe651d) ). * “git request-pull” and confusing diffstats [LWN.net] (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=67ee31b35b&e=2778fe651d) by Jonathan Corbet talks about what to do if the history to be pulled includes merges from outside (e.g. to obtain the dependencies for a fix), and why it happens. * How Bash completion works (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=4c7865de8d&e=2778fe651d) and Adding Bash completion to my tool (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=8698000b35&e=2778fe651d) by Chris Patuzzo; Git’s Bash completion can be found in contrib/completion/git-completion.bash (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=a6105a03a8&e=2778fe651d) .

Git tools and sites * Gollum (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=09d03338b0&e=2778fe651d) is a simple, Git-powered wiki written in Ruby with a sweet API and local frontend. * git_examples.sh (https://github.us10.list-manage.com/track/click?u=318f078aaef2e75d94c2bf757&id=9bc246366f&e=2778fe651d) – 99% of the Git commands you’ll need at work, demonstrated in a single script.

** Credits ------------------------------------------------------------

This edition of Git Rev News was curated by Christian Couder , Jakub Narębski , Markus Jansen and Gabriel Alcaras with help from Emily Shaffer, Luca Milanesio and George Espinoza.

============================================================ You are receiving this email because you signed up to receive the Git Rev News newsletter.

Our mailing address is: Software Freedom Conservancy - Git Project 137 Montague ST STE 380 New York, NY 11201 USA ** unsubscribe from this list (https://github.us10.list-manage.com/unsubscribe?u=318f078aaef2e75d94c2bf757&id=bfcffa5321&e=2778fe651d&c=0f7ca31000) ** update subscription preferences (https://github.us10.list-manage.com/profile?u=318f078aaef2e75d94c2bf757&id=bfcffa5321&e=2778fe651d) Email Marketing Powered by Mailchimp http://www.mailchimp.com/monkey-rewards/?utm_source=freemium_newsletter&utm_medium=email&utm_campaign=monkey_rewards&aid=318f078aaef2e75d94c2bf757&afl=1

----- End forwarded message -----

----- End forwarded message -----