Loading...
 
Skip to main content

No Food for Thought

Food is something you should provide to your brain long before coming to this blog. You will find no food recipes here, only raw, serious, non-fake news for mature minds.

Resigning from Debian's Publicity team (sort of), and the status of our public relations

admin Tuesday January 1, 2019

When I joined Debian, Debian Weekly News was an important tool for me to follow the project. I must have read each issue until, during the Dunc-Tank controversy, I read the following in the introduction of the 2006-09-26 issue:

Debian Weekly News - September 26th, 2006 wrote:
As Debian experiments with funding, the author of DWN is going to experiment with spending less time on Debian. Please understand that due to this there may be no future issues of DWN in the current form or that they will only be released less frequently.


This was horrific not just from a public relations standpoint, but from a manpower standpoint. Having someone replace Joey would be extremely difficult. And indeed, at that point, Debian Weekly News did stop being weekly, before its last issue came out on 2007-07-03.

I cannot blame Joey for what he did. He must have been burnt out at the time, and if it wasn't for the fact that Dunc-Tank was unofficial, it would have been a good reason to leave. I felt compelled to take over from Joey, but that would have been too much work, and I never thought weekly news was a good format anyway.

But when I saw Alexandr Schmehl's call to resurrect DWN inside the Publicity team, I felt it was my duty to help. And that wasn't hard - the first issues had very poor quality, and I quickly started reviewing them.

A lot has happened since. Many people joined the team. Many people left. A few people got quite involved. Unfortunately, no one got involved as much and for as long as Joey did. And the news never regained their former frequency, nor did they approach their former quality. Few contributors officially resigned, but I guess I am the last one from the initial crew to quit. Over time, my involvement expanded to review all public communications.

Publicity team delegated

Fast forward to September 2015. Many of those in charge of Debian's public relations, including myself, were probably surprised to read Updating delegation - Press/Publicity/Bits. There were good news there. Despite the title, this was essentially making the publicity team delegated, which had never been done before. For the first time, the publicity team was officially recognized. Merging the previous teams was perhaps a good idea. But most members of the previous teams were no longer part of the new team, without any explanation. On 2015-10-04, I contacted the DPL asking what this was all about. As the mailing list has been broken for many months, only one of these mails has been archived. I am making these mails public by including them below.

Filipus Klutiero wrote:

> - Team members must word articles in a way that reflects the Debian project's stance on issues rather than their own personal opinion.

This is not an actual task. I do not think delegations should try telling teams how to do their job, and I do not think neutrality should only be requested from the publicity team... if there is such a thing as neutrality.

> - Finally, the Publicity Team is the official Debian contact point for press inquiries and media people outside Debian. When acting in such capacity, members of the team act as a spokesperson of the Debian Project.


I have never been part of the bits team, nor intensively involved in the others. I have no strong opinion on whether merging is a good idea, though it seems reasonable.
That being said, I really think such a cut would be detrimental. I have been focused on project news, but ever since Joey left, "the team" (we did not talk about a team back then) has been understaffed. Removing most members will certainly push quality and timeliness even lower.

Were members removed because you did not want to grant them press privileges? If so, I think this should be canceled, or the team structure should be complexified to support different accesses for different members. I do not think members would be offended. In fact, this was already the case, and I for one have zero desire to get more accesses.

If you confirm your decision, I will let you be the one to officially remove members from the list.


Neil's answer came the next day. The next day, I replied:

Filipus Klutiero wrote:

> Delegations are not only about tasks, and this doesn't tell them how to fulfil the role. It's a limiting on the scope of the delegation though.

I do not see the neutrality item as a limitation of scope. I do see it as a rule on how the role must be or must not be fulfilled.

If there is concern about releases being controversial or otherwise low in quality, what we need is better reviewing, and this has been discussed before, unfortunately without results so far: https://lists.debian.org/debian-publicity/2011/08/msg00020.html

> I should point out that this text was the one proposed by the team itself: https://lists.debian.org/debian-publicity/2015/08/msg00032.html

I recognize I have not been following closely lately, and I could have reacted earlier, but I did not propose that text, and I see no sign on the mailing list that this text was proposed to project leadership.

>> That being said, I really think such a cut would be detrimental. I have been focused on project news, but ever since Joey left, "the team" (we did not talk about a team back then) has been understaffed. Removing most members will certainly push quality and timeliness even lower.
> This isn't to stop anyone doing any work - I believe that the only actual people who I expect to be 'removed' are Joey, and myself.

First, it would be most useful to have a list of delegations. Failing that, I will guess, since I do not remember seeing a publicity delegation, that you are saying this is the first delegation for the publicity team.

I understand your point - the publicity team has never been delegated, so your delegation does not remove delegates.
On the other hand, the publicity team did exist as a de facto team, as other Debian teams start. I have no problem with turning it into a delegation, nor with removing current members which are determined as undesirable, but delegating omitting existing members effectively removes them. If a decision is taken to remove most of the team, an explanation would help everyone ensure there were no alternative solutions to the problem.

If anyone doubts manpower is an issue, just look at these 3 pages I just consulted - they are *all* outdated, more than 2 weeks after the delegation:
https://wiki.debian.org/Teams/Publicity/#Usual_roles
https://wiki.debian.org/Teams/Press
https://www.debian.org/intro/organization.en.html

And if some think email should suffice, notice the delegation does not even show in our team's mail archive.


Neil was then quiet for weeks. On 2015-10-24, I told him:

Filipus Klutiero wrote:

A new DPN issue has been released. While one longstanding problem appears to be finally gone (only 4 years after https://lists.debian.org/debian-publicity/2011/12/msg00019.html ), the reviewing issue is certainly not. And this is despite half of the persons listed as having contributed to that issue not even being part of the team according to the delegation (this issue has taken a long time to release - I have not verified whether their contributions predate the delegation, or if they chose to contribute despite it).

The situation described in my last mail seems to persist. I do not wish to remain associated in any way with the publicity team in its current state when reasonable efforts are not being done to go forward. Insofar as this makes sense given the current context, I intend to offer my resignation if the situation has not evolved in a month.


His last message came on 2015-10-26:

Neil McGovern wrote:

On Sat, Oct 24, 2015 at 10:58:43AM -0400, Filipus Klutiero wrote:
> A new DPN issue has been released. While one longstanding problem appears to be finally gone (only 4 years after https://lists.debian.org/debian-publicity/2011/12/msg00019.html ), the reviewing issue is certainly not. And this is despite half of the persons listed as having contributed to that issue not even being part of the team according to the delegation (this issue has taken a long time to release - I have not verified whether their contributions predate the delegation, or if they chose to contribute despite it).

I believe it's the latter - you keep insisting that the fact that they're not delegated means they've been banned from doing any work.
This is not the case.

> The situation described in my last mail seems to persist. I do not wish to remain associated in any way with the publicity team in its current state when reasonable efforts are not being done to go forward. Insofar as this makes sense given the current context, I intend to offer my resignation if the situation has not evolved in a month.

I intend to make no further efforts here, you are free to make your own choice on where you work.


I immediately asked Neil to explain:

On 2015-10-26, Filipus Klutiero wrote:

On 2015-10-26 11:46, Neil McGovern wrote:
>I believe it's the latter - you keep insisting that the fact that they're not delegated means they've been banned from doing any work.

What? Did I even claim such a thing once?

In any case, I have tried verifying your belief, but gave up due to the team VCS's breakage... which - ahem - predates the team's halving.


More than 2 months later, my questions remain unanswered. And therefore, as I warned I would do, I hereby resign from the Debian Publicity team (or whatever the team is called now, since that delegation apparently also stripped us from an official name).

Where are we?

A few weeks after this, Laura Arjona finally updated the team's wiki page. The page now lists what it calls "DPL-Delegated members". Unfortunately, things are still far from clear. The page now lists "DPL-Delegated members" and then "Current members". Some of the "DPL-delegated members" are not current members. Most of the current members are not DPL-delegated members. Even Neil, which is expected to be removed by his own account, still figures as a current member.

What happened?

According to Ana Guerrero Lopez's mail, this initiative came from at least Cédric Boutillier and herself. I have not worked much with these, but I would doubt Cédric Boutillier would have intentionally hijacked the publicity team. Considering Laura's edits, I would guess this was an unfortunate accident.

If so, by accepting to delegate without fixing and without verifying, the DPL may have simply done an error. Carelessness would be the only thing he could be blamed for. However, by spreading misinformation and disappearing from the discussion, the DPL has now also failed to fix damage he is (at least in large part) responsible for.

Unless we have a cabal trying to slowly perform a discreet coup, those indirectly kicked out can probably consider that they remain in the team. It remains to be determined how they now differ from "DPL-Delegated members".

Conclusion

2 DPN issues in the last 5 months is not much. There are surely problems for redactors. Solving these may help on the quantity side. Unfortunately, since I can count on my fingers the number of times I contributed content to the news, I cannot say what will help the most.

In general though, the team does extremely bad in recruiting and maintaining its members (either redactors or reviewers). I am not sure I have seen a single DPN issue with proper credits (despite a 2011 discussion of the problem). On the reviewing side, of the hundred issues for which I performed a final review, I could not find any issue or any significant error in about 10. This is not as much as I wish, but it seems the situation had improved with years. I hope whoever picks up this task can keep directing their remarks to the redaction side and eventually make reviewing less necessary. I also wish the team knows how to maintain these recruits for as long as I stayed, or longer. And I hope these will finally benefit from reviewing guidelines.

Other general issues having priority are of course fixing the mailing list and the VCS.

Debian has disappointed me in the last years. In a sense, this delegation is a good thing for me, since I probably no longer have the dedication to the project necessary to care about public relations. I am far from being as involved in Debian as I was when I started reviews, but I may keep reading DPN. Thanks in advance to those who stay… and good luck.

Update 2016-08-21

In his A year in the life of a DPL talk about his DPL term, Neil mentioned his delegation (at 17:45). Since it must have been harder to fix its problems, he seems to have found easier to congratulate this "fantastic" team, since it was "incredibly active and the amount of stuff we're getting now is absolutely wonderful"… even though the team had published merely 6 news issues in the previous year rather than the 52 published a full decade earlier.

Update 2018-05-27

Chris Lamb has updated the team's delegation to reflect the departure of Ana Guerrero Lopez and Cédric Boutillier, which leaves 2 people in the team. Even looking at the year before, the (yearly) number of issues had already dropped to 4 😑

Update 2022-07-17

The team has just published a news issue… its first this year. In fact, in the last 3 years, the team which Neil calls "incredibly active" has struggled to publish even 1 issue per year. One thing hasn't changed though: it still uses the term "weekly"!

Congratulations, Neil McGovern. Your carelessness, but most importantly, your pride and unwillingness to show modesty after being told about your mistakes has managed to kill what was left of Debian's public relations - and in doing so, to largely kill Debian itself.

Update 2024-09

Is Debian waking up? According to its new DPL, whoever is left in the "incredibly active" team which published exactly 4 issues of its "weekly" news during the last 5 years now "wants us".🙄

Smart technology makers, dumb technology users

admin Sunday December 16, 2018

With the advent of smart TVs, smartphones and other computers, humans need to be a lot smarter about their usage of technology. Unfortunately, we are quite dumb - in particular the underprivileged. And unfortunately, even the smartest have apparently gotten dumber, even when they control their use of their smartphones.
Good thing at least technology is getting smarter and smarter! Well, perhaps

Car thieves are bad, but much wiser than car makers

admin Saturday December 15, 2018

Thieves have a new way to steal cars. A method for clean thefts, served on a silver platter by car manufacturers who sell cars equipped with key fobs instead of traditional keys, without any protection against a simple attack. Even Toyota!

If I had had such a vulnerable car stolen from me, I would be happy to discover that flaw. I would just sue the manufacturer for selling such a product. When you create such a vulnerability, you are guilty of gross negligence. The onus isn't on the customer to prove that this flaw was exploited, but on you to prove the theft was made with different means.

When manufacturers will have lost tens of millions of euros in damages, perhaps they will consider paying for security responsibles who have a clue or two about security.

An Apple Brainwash a Day Keeps Bugs Away

admin Monday December 10, 2018

Computer maker Apple has found the recipe to avoid having to acknowledge any defect in its products: to instruct its technicians - I mean, its geniuses (of deception) - to avoid usage of the words "crash", "bug" or "problem".

Unfortunately, joining that cult is quite costly, given the sacrifices required by its gurus. Well, I guess that's just like any other sect, when it has managed to enslave enough fools.

A Week at Club Med Cancun - Technically not so Greatly Organized

admin Sunday October 14, 2018

I took a week of vacation and on a friend's suggestion, decided to spend it at Club Med's village in Cancun, Mexico. I had never tried Club Med, but I needed to relax and thought that by paying for quality, I would take a break from bugs, as well as from problems in general.

Bugs

Short version

I saw surprisingly few biological bugs in the village. A lot less than I expected. Unfortunately, I stayed in familiar ground as for computer bugs. At least 2 major bugs before my stay, at least 2 issues during my stay, and 1 bug after. I wish I was looking for an IT Manager job.

Long version

Even before I confirmed my choice, I hit a major bug in Club Med's website - the booking calendar was showing me the wrong prices (I believe it ignored my departure city). I still found the booking procedure impressive and tried to create an account. I hit another major bug right there, unable to create an account for days! I had to call an agent to book.

WiFi

Before you book, Club Med advertises the following:

clubmed.ca wrote:

What's included in your stay
Children Clubs for ages 4-17 + All-day gourmet dining & open bar + Unlimited water & land sports + Day & Night Entertainment + Wi-Fi & Gratuities = all inclusive


After you booked though, the formula gets more complicated:

Final voucher wrote:
As of November 1, 2016 basic WIFI access is included in your Club Med package. Premium WIFI is also available at an additional cost and can be purchased on site. Subject to change.

Of course, there is no useful description of each access type. So since I wasn't travelling for business, I didn't purchase premium WiFi.

The reception staff told me to install the Club Med Villages app on my cellphone. Over 24 hours after my arrival, and despite multiple attempts, I still hadn't managed to download the ~ 70 MB application on my cellphone. Plus, network was really bad on my laptop. So I went back to the reception, asked if that was normal, and since I couldn't get a useful answer, I gave in despite the feeling of deception and paid for the damn Premium WiFi access. I then tried to setup the Premium access on the cellphone - and was greeted by a DNS error. 2 young employees at the reception failed to help. After rebooting and multiple attempts, I gave up.

Over 2 days after my arrival, after I had given up, I noticed the installation had finally ended. I then tried to access my village, but that turned out even harder. A scrollbar stayed stuck at 100%. I gave up on that too a day later. Only after I came back home did I realize that the application was finally usable.

Salvaging the Unsalvageable?

Nevertheless, I liked many aspects of Club Med and felt compelled to help them improve. I was disappointed that no one asked me how my stay went when I left (probably because I left early). So when I saw an email asking for feedback, I decided to set aside my reluctance to waste time with surveys and took at least 20 minutes to fill it. Here's what I wrote at the last step:

Unexpected technical difficulties; 2 important issues booking (wrong prices, prolonged failure to create account), big issues with standard wifi even without trying to view any video, inability to use premium wifi on cellphone. Unable to use Club Med app on fresh cellphone during whole stay. Lost at least 4 hours due to technical issues overall. Made me wonder if I chose the right brand for a worry-free vacation, and would hesitate to recommend consequently

Exceptional welcome videos; poor TV

Sunday cocktail is a great idea

Great resort location, great architecture, great choice of activities

Great buffet

Was expecting to have bicycles for rent. Disappointed that reception staff couldn't even tell me where to go to rent one


I was 98% into the survey then. I hit Next... and all I got was an image. No confirmation that my feedback was submitted. I tried to go back, but the document had expired.
Gah - apparently half an hour more wasted. All of that on my main desktop, with Mozilla Firefox 60 (ESR).

Other types of bugs, other life forms and Beyond

Other than technical issues, there is wildlife at Club Med, as my photos show.

This was my first time at Club Med, but I learned that it was bought by a Chinese company. Does Club Med still offer the best all inclusive resorts in the concept it created, or is there now a better option for those looking for real quality? I don't mind paying some more (my whole week was around 1800 CAD, direct flight from Quebec City included).

Julbo photochromatic cycling glasses

admin Saturday October 13, 2018

This summer I looked for cycling glasses which would not only protect my eyes from the Sun, but also minimize the airflow. After careful research, I chose Julbo's Aerospeed, even though I couldn't find a local retailer to buy them from. I bought online from trekkINN for 173 CAD and thankfully, the glasses fit well. Just a couple disappointments:

  1. It wasn't clear whether these came with a single glass or several. In the end, there is one glass (and it cannot be removed).
  2. At night, there is important reflection. You get used to it, but it requires some more attention.