OpenMandriva contributor denies sabotage claim after repo deletions

OpenMandriva’s dispute with contributor Davide Beatrici has moved from an incident report to a public disagreement over intent and governance. Beatrici told The Register that he did delete GitHub repositories and publish a package that removed desktop environment packages from the project’s Cooker development branch, but denied OpenMandriva’s claim that the actions amounted to attempted distribution sabotage.

The case matters beyond one Linux distribution because it exposes a familiar operational risk in volunteer-run software projects: maintainers with broad access can make changes faster than governance processes can respond. OpenMandriva said last week that Beatrici misused administrative permissions to delete parts of its GitHub presence and to ship an empty package in Cooker that obsoleted GNOME and COSMIC packages. The project said it had considered legal action.

Beatrici acknowledged the technical actions described by OpenMandriva. He told The Register he removed the GNOME and COSMIC repositories from GitHub, took the related packages out of Cooker, and uploaded a package that marked them obsolete. His dispute is with OpenMandriva’s account of why he did it and what his status was inside the project at the time.

According to Beatrici, the changes were a protest after other maintainers removed OneDev configuration files from several repositories without discussing the move with him. He said that change effectively shut off work he had been doing on replacement build and mirroring infrastructure for the distribution. Beatrici told The Register that his action was intended to send a message, and argued that the deleted repositories and removed packages could be restored without unusual difficulty.

OpenMandriva’s original statement framed the incident as a contributor retaining and abusing administrative rights after a break with the project. Beatrici rejected that characterization, telling The Register he had not intended to leave OpenMandriva and had continued working on his tasks despite conflict in the project’s Matrix rooms.

He also disputed the implication that the internal split was straightforward. Beatrici said OpenMandriva president Bernhard Rosenkränzer had repeatedly tried to mediate between contributors before the relationship deteriorated. OpenMandriva has not provided The Register with a response to Beatrici’s account, despite questions sent to the project and Rosenkränzer on Friday, according to the publication.

Beatrici’s comments also broaden the issue from one set of deletions to the state of OpenMandriva’s release infrastructure. He told The Register that parts of the project’s build system were outdated and said he had spent time contributing patches to OneDev while building a new package pipeline. OpenMandriva has not answered whether it stands by its sabotage description or how it assesses those infrastructure claims.

The practical outcome is less ambiguous than the motive. OpenMandriva had to restore affected repositories and deal with package changes in its development branch. For open source projects that depend on a small group of high-trust maintainers, the episode is another reminder that access control, offboarding, and technical governance are production concerns, even when no company balance sheet is attached.

This story draws on original reporting from The Register.