Bonum Certa Men Certa

Sirius Open Source: Buy Your Own Desk, Bring/Buy Your Own Device (BYOD), Repair and Maintain Your Computer at Your Own Expense and Time

Desk for Sirius? Who owns what?

Sirius Open Source desk



Summary: The previous part in the Sirius ‘Open Source’ series showed the financial issues at Sirius; to make matters worse, the company does not provide any means for work to its NOC staff (except an ancient Cisco phone, about 20 years old and bought second hand through eBay)

THE articles that we published about the EPO showed that as horrible and autocratic António Campinos has been, at least the Office chipped in and covered expenses for home working, such as ergonomic chairs. At Sirius, however, the company pays for nothing of that sort. Not for desk, chair, computer, and so on. Workers are on their own; technical problems with a work device? That's your problem. That's your device. The company won't cover it. Then they impose bloatware on staff -- software that ordinary machines cannot run (yes, staff did complain; it was a common problem) or can barely run. Does the company help procure suitable hardware? No. Was it asked about it? Yes.



Here is an internal report circulated in the company earlier this month (a day prior to departure):


Remote Workers' Procurement and Other Costs



Equipping staff with suitable assets is a basic, very basic, requirement. Roy has covered the legal aspects of that for many years in his Web sites. In Sirius, the company failed to equip home workers ("work-from-home" staff) with any computers or chairs or anything required to do the work. The managers expect staff to pay for purchasing and maintenance of all work equipment at their own expense in their own time. There's no IT department to help with computer issues or even issue a replacement.

To make matters worse, bloated software which requires very powerful and expensive computers was introduced some years ago. Roy and colleagues also complained about this bloat, but that fell on deaf ears (Roy internally suggested the company can purchase suitable equipment or cover the costs of that). That's aside from the very low (by market standards) salary, adding further burden. More on financial aspects shall be discussed later.

In recent months workers began observing that Sirius had customers with no way to access their systems. So how are workers supposed to deal with tickets they receive? There was expectation of dealing with queries by using "Google" to throw some answer at a client (as if the client cannot access Google), otherwise find an associate or escalate. It was starting to get hard to even tell apart clients and non-clients, as documentation was scarce and outdated to the point where clients were vaguely described and their status was unclear. Sentences like "Google is your friend" were said inside the company (Google is surveillance, it's not a friend) and our skillset ought not rely on using search engines, following a textual script (like clerical staff in a call centre), or mere escalation to some other company. As noted before, many associates are at best loosely connected to the company and are in effect third parties.

About a year ago Roy faced disciplinary action over something unjust (to him). Instead of an independent, impartial tribunal acting as arbitrator it was likely the culprits judging the incident, then resorting to cover-up/distortion over the sequence of events to pass to the blame to 'low-level' staff. This started to become a typical modus operandi, which dated back several years, as a later section will explain in detail.

These issues turned out to be more widespread as staff managed to communicate with one another. For instance, lots of people were having phone issues. The company did not admit this; individual people reported it, then there was blaming of the people unable to use a defective "service" that keeps changing and breaking things that previously worked. Instead of admitting this migration was a mistake and acknowledging prior warning were given, there was only further entrenchment. More details will be given in the last section.

Recent Techrights' Posts

Maria Glukhova, Dmitry Bogatov & Debian Russia, Google, debian-private leaks
Reprinted with permission from disguised.work
Who really owns Debian: Ubuntu or Google?
Reprinted with permission from disguised.work
Keeping Computers at the Hands of Their Owners
There's a reason why this site's name (or introduction) does not obsess over trademarks and such
In May 2024 (So Far) statCounter's Measure of Linux 'Market Share' is Back at 7% (ChromeOS Included)
for several months in a row ChromeOS (that would be Chromebooks) is growing
Links 03/05/2024: Microsoft Shutting Down Xbox 360 Store and the 360 Marketplace
Links for the day
Evidence: Ireland, European Parliament 2024 election interference, fake news, Wikipedia, Google, WIPO, FSFE & Debian
Reprinted with permission from Daniel Pocock
Enforcing the Debian Social Contract with Uncensored.Deb.Ian.Community
Reprinted with permission from Daniel Pocock
Gemini Links 03/05/2024: Antenna Needs Your Gemlog, a Look at Gemini Get
Links for the day
IRC Proceedings: Thursday, May 02, 2024
IRC logs for Thursday, May 02, 2024
Over at Tux Machines...
GNU/Linux news for the past day
Jonathan Carter & Debian: fascism hiding in broad daylight
Reprinted with permission from disguised.work
Gunnar Wolf & Debian: fascism, anti-semitism and crucifixion
Reprinted with permission from disguised.work
Links 01/05/2024: Take-Two Interactive Layoffs and Post Office (Horizon System, Proprietary) Scandal Not Over
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, May 01, 2024
IRC logs for Wednesday, May 01, 2024
Embrace, Extend, Replace the Original (Or Just Hijack the Word 'Sudo')
First comment? A Microsoft employee
Gemini Links 02/05/2024: Firewall Rules Etiquette and Self Host All The Things
Links for the day
Red Hat/IBM Crybullies, GNOME Foundation Bankruptcy, and Microsoft Moles (Operatives) Inside Debian
reminder of the dangers of Microsoft moles inside Debian
PsyOps 007: Paul Tagliamonte wanted Debian Press Team to have license to kill
Reprinted with permission from disguised.work
IBM Culling Workers or Pushing Them Out (So That It's Not Framed as Layoffs), Red Hat Mentioned Repeatedly Only Hours Ago
We all know what "reorg" means in the C-suite
IBM Raleigh Layoffs (Home of Red Hat)
The former CEO left the company exactly a month ago
Paul R. Tagliamonte, the Pentagon and backstabbing Jacob Appelbaum, part B
Reprinted with permission from disguised.work
Links 01/05/2024: Surveillance and Hadopi, Russia Clones Wikipedia
Links for the day
Links 01/05/2024: FCC Takes on Illegal Data Sharing, Google Layoffs Expand
Links for the day
Links 01/05/2024: Calendaring, Spring Idleness, and Ads
Links for the day
Paul Tagliamonte & Debian: White House, Pentagon, USDS and anti-RMS mob ringleader
Reprinted with permission from disguised.work
Jacob Appelbaum character assassination was pushed from the White House
Reprinted with permission from disguised.work
Why We Revisit the Jacob Appelbaum Story (Demonised and Punished Behind the Scenes by Pentagon Contractor Inside Debian)
If people who got raped are reporting to Twitter instead of reporting to cops, then there's something deeply flawed
Free Software Foundation Subpoenaed by Serial GPL Infringers
These attacks on software freedom are subsidised by serial GPL infringers
Red Hat's Official Web Site is Promoting Microsoft
we're seeing similar things at Canonical's Ubuntu.com
Enrico Zini & Debian: falsified harassment claims
Reprinted with permission from disguised.work
European Parliament Elections 2024: Daniel Pocock Running as an Independent Candidate
I became aware that Daniel Pocock had decided to enter politics
Publicly Posting in Social Control Media About Oneself Makes It Public Information
sheer hypocrisy on privacy is evident in the Debian mailing lists
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, April 30, 2024
IRC logs for Tuesday, April 30, 2024