08.30.20

Google, Money and Censorship in Free Software Communities

Posted in Finance, Free/Libre Software, Google at 10:02 am by Guest Editorial Team

Reprinted with permission from Debian Community News

T

On 30 June 2019, a Debian Developer sent the email below to the debian-project mailing list.

It never appeared.

Alexander Wirt (formorer) has tried to justify censoring the mailing list in various ways. Wirt has multiple roles, as both Debian mailing list admin and also one of Debian’s GSoC administrators and mentors. Google money pays for interns to do work for him. It appears he has a massive conflict of interest when using the former role to censor posts about Google, which relates to the latter role and its benefits.

Wirt has also made public threats to censor other discussions, for example, the DebConf Israel debate. In that case he has wrongly accused people of antisemitism, leaving people afraid to speak up again. The challenges of holding a successful event in that particular region require a far more mature approach, not a monoculture.

Why are these donations and conflicts of interest hidden from the free software community who rely on, interact with and contribute to Debian in so many ways? Why doesn’t Debian provide a level playing field, why does money from Google get this veil of secrecy?

Is it just coincidence that a number of Google employees who spoke up about harassment are forced to resign and simultaneously, Debian Developers who spoke up about abusive leadership are obstructed from competing in elections? Are these symptoms of corporate influence?

Is it coincidence that the three free software communities censoring a recent blog about human rights from their Planet sites (FSFE, Debian and Mozilla, evidence of censorship) are also the communities where Google money is a disproportionate part of the budget?

Could the reason for secrecy about certain types of donation be motivated by the knowledge that unpleasant parts of the donor’s culture also come along for the ride?

The email the cabal didn’t want you to see

Subject: Re: Realizing Good Ideas with Debian Money
Date: Sun, 30 Jun 2019 23:24:06 +0200
From: a volunteer
To: debian-project@lists.debian.org, debian-devel@lists.debian.org



On 29/05/2019 13:49, Sam Hartman wrote:
> 
> [moving a discussion from -devel to -project where it belongs]
> 
>>>>>> "Mo" == Mo Zhou <lumin@debian.org> writes:
> 
>     Mo> Hi,
>     Mo> On 2019-05-29 08:38, Raphael Hertzog wrote:
>     >> Use the $300,000 on our bank accounts?
> 
> So, there were two $300k donations in the last year.
> One of these was earmarked for a DSA equipment upgrade.


When you write that it was earmarked for a DSA equipment upgrade, do you
mean that was a condition imposed by the donor or it was the intention
of those on the Debian side of the transaction?  I don't see an issue
either way but the comment is ambiguous as it stands.

Debian announced[1] a $300k donation from Handshake foundation.

I couldn't find any public disclosure about other large donations and
the source of the other $300k.

In Bits from the DPL (December 2018), former Debian Project Leader (DPL)
Chris Lamb opaquely refers[2] to a discussion with Cat Allman about a
"significant donation".  Although there is a link to Google later in
Lamb's email, Lamb fails to disclose the following facts:

- Cat Allman is a Google employee (some people would already know that,
others wouldn't)

- the size of the donation

- any conditions attached to the donation

- private emails from Chris Lamb indicated he felt some pressure,
influence or threat from Google shortly before accepting their money

The Debian Social Contract[3] states that Debian does not hide our
problems.  Corporate influence is one of the most serious problems most
people can imagine, why has nothing been disclosed?

Therefore, please tell us,

1. who did the other $300k come from?
2. if it was not Google, then what is the significant donation from Cat
Allman / Google referred[2] to in Bits from the DPL (December 2018)?
3. if it was from Google, why was that hidden?
4. please disclose all conditions, pressure and influence relating to
any of these donations and any other payments received

Regards,

Daniel


1. https://www.debian.org/News/2019/20190329
2. https://lists.debian.org/debian-devel-announce/2018/12/msg00006.html
3. https://www.debian.org/social_contract

Censorship on the Google Summer of Code Mentor’s mailing list

Google also operates a mailing list for mentors in Google Summer of Code. It looks a lot like any other free software community mailing list except for one thing: censorship.

Look through the “Received” headers of messages on the mailing list and you can find examples of messages that were delayed for some hours waiting for approval. It is not clear how many messages were silently censored, never appearing at all.

Recent attempts to discuss the issue on Google’s own mailing list produced an unsurprising result: more censorship.

However, a number of people have since contacted community representatives privately about their negative experiences with Google Summer of Code. Here is one of the messages that Google didn’t want other mentors to see, sent by one of the former Debian GSoC admins:

Subject: [GSoC Mentors] discussions about GSoC interns/students medical status
Date: Sat, 6 Jul 2019 10:56:31 +0200
From: a volunteer
To: Google Summer of Code Mentors List <google-summer-of-code-mentors-list@googlegroups.com>


Hi all,

Just a few months ago, I wrote a blog lamenting the way some mentors
have disclosed details of their interns' medical situations on mailing
lists like this one.  I asked[1] the question: "Regardless of what
support the student received, would Google allow their own employees'
medical histories to be debated by 1,000 random strangers like this?"

Yet it has happened again.  If only my blog hadn't been censored.

If our interns have trusted us with this sensitive information,
especially when it concerns something that may lead to discrimination or
embarrassment, like mental health, then it highlights the enormous trust
and respect they have for us.

Many of us are great at what we do as engineers, in many cases we are
the experts on our subject area in the free software community.  But we
are not doctors.

If an intern goes to work at Google's nearby office in Zurich, then they
are automatically protected by income protection insurance (UVG, KTG and
BVG, available from all major Swiss insurers).  If the intern sends a
doctor's note to the line manager, the manager doesn't have to spend one
second contemplating its legitimacy.  They certainly don't put details
on a public email list.  They simply forward it to HR and the insurance
company steps in to cover the intern's salary.

The cost?  Approximately 1.5% of the payroll.

Listening to what is said in these discussions, many mentors are
obviously uncomfortable with the fact that "failing" an intern means
they will not even be paid for hours worked prior to a genuine accident
or illness.  For 1.5% of the program budget, why doesn't Google simply
take that burden off the mentors and give the interns peace of mind?

On numerous occasions Stephanie Taylor has tried to gloss over this
injustice with her rhetoric about how we have to punish people to make
them try harder next year.  Many of our interns are from developing
countries where they already suffer injustice and discrimination.  You
would have to be pretty heartless to leave these people without pay.
Could that be why Googlespeak clings to words like "fail" and "student"
instead of "not pay" and "employee"?

Many students from disadvantaged backgrounds, including women, have told
me they don't apply at all because of the uncertainty about doing work
that might never be paid.  This is an even bigger tragedy than the time
mentors lose on these situations.

Regards,

Daniel


1.

https://danielpocock.com/google-influence-free-open-source-software-community-threats-sanctions-bullying/

--
Former Debian GSoC administrator

https://danielpocock.com

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. InteLeaks – Part XXII: Bubbles and Buzzwords, No Substance at Intel's Internet of Things (IoT) Group (IOTG)

    The video above is continuation of the previous part about a document full of superficial buzzwords (not technical jargon anywhere), in effect recommending to managers that they blindly follow trends and cargo cults (such as Clown Computing) and not what’s most suitable for technical excellence



  2. IRC Proceedings: Tuesday, January 19, 2021

    IRC logs for Tuesday, January 19, 2021



  3. Links 20/1/2021: WireGuard for pfSense and New US President

    Links for the day



  4. Links 19/1/2021: Krita 4.4.2 Released and JingOS Hype

    Links for the day



  5. Team UPC Keeps Pretending That UPCA Can Still be Resurrected (Even Without the UK, Which is Strictly a Requirement)

    The latest distortion of facts regarding the Unified Patent Court (UPC) Agreement (UPCA) as seen from the lens of people who seek to profit from such distortion



  6. 'Ethical Source' is Not Ethical and Not a Movement But a Misguided Self-Serving PR Stunt

    Something which is neither enforceable nor ethical is being promoted by profoundly unethical media in the pockets of large corporations



  7. InteLeaks – Part XXI: Intel Seeking Advice From a Bunch of Clowns (Harbor 'Research')

    A firm called Harbor 'Research' is making dubious recommendations to Intel; as shown in the above video, there's also an obsession with buzzwords (typically suggestive of a lack of technical grasp/understanding)



  8. IRC Proceedings: Monday, January 18, 2021

    IRC logs for Monday, January 18, 2021



  9. The US Election Was Not Rigged, But the Nomination Process Was (Undermined to Maintain Control by Oligarchy)

    Cheating/driving the left out of the Democratic Party seems like a longstanding tradition and we know who stands to gain from it; moreover, problems remain in the voting process because it's controlled by secret code of companies like Microsoft (in spite of the openwashing)



  10. InteLeaks – Part XX: Redacted (for Names Only) Release of Intel File About Developer eXperience (DX) Meddling in GNU/Linux

    Today (or tonight) we release the first 'phase' of InteLeaks in a sensibly redacted form; coming up next is a surprise from Team Microsoft



  11. Sites in Bed With the EPO and UPC 'Covering' the 'News' Without Mentioning Any of the Overt Abuses

    It is rather sad that blogs like IP Kat have turned into proponents of abusive EPO management and Team UPC increasingly resorts to lying using pseudonyms (to avert criticism and accountability); much of the rebuttal or response that’s hinged on reality/facts can only be found in comments, which are still subjected to a face-saving moderation process (conducted by Team UPC)



  12. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part IV: Stories From the Depths of the Free Software Foundation (FSF)

    To reduce or alleviate suspicions and a potential of mistrust the FSF needs to become more transparent and liberate information (such as the real reason Bradley Kuhn left, as noted in the previous part)



  13. Links 18/1/2021: GNU Radio 3.9, Wikipedia at 20

    Links for the day



  14. InteLeaks – Part XIX: Intel's Web 'Experts' Seen as Microsoft Champions Dealing With the Platform Microsoft is Looking to Destroy

    Things aren't rosy at Intel because the hires aren't suitable for the job of documenting and/or presenting GNU/Linux-centric products (whose target audience is Free software developers)



  15. Adding Images as Characters to the Daily Bulletins of Techrights

    Our daily bulletins now have inside them coarse graphics, depicted using characters alone, and the tool used to generate them announced a new release earlier today; we showcase some of its features (in a new video)



  16. Links 18/1/2021: Weekly Summaries and Linux 5.11 RC4

    Links for the day



  17. IRC Proceedings: Sunday, January 17, 2021

    IRC logs for Sunday, January 17, 2021



  18. The Oligarchs' Parties Will Never Choose the Side of Software Freedom Because Free Software Cannot Bribe Officials

    The tough reality is that next week's (or this coming week's, depending on what Sunday counts as) inauguration ceremony is partly symbolic as all the same and important issues remain largely untouched, for corporations control almost everything of significance



  19. COVID-19 Has Actually Helped Software Freedom Due to Financial and 'Spare Time' Factors

    Developers and users are increasingly exploring what the Free software world has to offer; this is actually measurable and it contradicts claims to the contrary



  20. Future Plans and Using Videos to Complement Text

    Remarks on recent and impending site changes; We are not replacing text with video, we're just trying to enhance the presentation a bit, especially where visuals help make a point or where browsing through Web sites (or leaks) is more suitable than static, linear presentation



  21. InteLeaks – Part XVIII: Intel Does Not Know How to Properly Do Research and It Seems Apparent Unscientific Methods Are Used to Justify Poor Documentation

    There appears to be a severe crisis at Intel; they cannot recruit scientists (or those whom they recruited are walking away) and as a result the company produces bad products with poor documentation (or highly defective chipsets that top-notch marketing cannot compensate for); in this video we walk through some examples of how studies are being conducted (as already noted in Part XVII)



  22. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part III: The Free Software Foundation (FSF) Seems More Like a Victim of Destabilisation Campaigns

    The Free Software Foundation (FSF), which turns 36 later this year, is looking to raise money that helps support the GNU Project, soon 38 years old and likely the most important Free software project to exist (ever)



  23. Links 17/1/2021: EasyOS on Raspberry Pi and GNU libsigsegv 2.13

    Links for the day



  24. InteLeaks – Part XVII: The High Cost of Microsoft Windows Users in GNU/Linux Development Teams

    A look inside Intel explains what holds back the technical team, which bemoans the lesser technical people getting in the way and not even using the product that they are writing about



  25. IRC Proceedings: Saturday, January 16, 2021

    IRC logs for Saturday, January 16, 2021



  26. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part II: Why Bradley Kuhn Left the Free Software Foundation (FSF)

    The founder of the FSF is still at the FSF (albeit not publicly) and the person who lobbied to oust him has basically been 'banished' by the founder



  27. Links 16/1/2021: LibreOffice 7.1 Release Candidate, Zeroshell 3.9.5, FreeBSD Report, and GhostBSD 21.01.15

    Links for the day



  28. Free Speech on the Web Not Respected by Companies That Used to Support Software Freedom

    Mozilla does not have to make its Web browser about politics; it can just make an excellent piece of software that is neutral about the Web pages that it renders, based on the user's personal preferences



  29. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part I: We Are Under Attack by Corporations and Their Salaried Facilitators

    The corporate takeover (taking over the Commons, produced by volunteers who are motivated by altruism) is a subject we must speak about and somehow tackle; this series will highlight uncomfortable or difficult truths



  30. InteLeaks – Part XVI: Intel Cannot Do Command Line, Even When It's Vastly Simpler and More Suitable for Development

    The Developer eXperience (DX) team at Intel seems to be full of Microsoft drones instead of developers and/or mildly technical people; this has not only harmed the quality of documentation but also upset staff, alienating people who actually understand what developers need (more than buzzwords like "DX")


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts