PODSHL PublishRegister ProjectsLog SecurityNotice

Notice and action

We mirror files that projects publish in their own repositories. If something we mirror should not be there, tell us here.

What a notice does, and does not do

It reaches the mirror, never the source. Our copy is withdrawn and the project returns to unknown — the state of one that never registered. Everything in the developer's own repository is untouched, because it was never ours.

It degrades; it does not delete. Not death, un-enrolment. We do not mark anyone as revoked, because somebody who published something contested has not necessarily done anything wrong.

Every removal is logged with a public reason code, and the affected party is told why. That log entry is the statement of reasons — if we could remove things quietly, the transparency would be decorative.

A notice aimed at a problem class is refused. There is no such path. Otherwise whoever owns a name could forbid anyone from saying it out loud, and naming other people's software is the whole open-source branch.

File one

Your name and how to reach you are stored with the notice and read by the operator, who decides on it. They are not published — the public statement of reasons carries neither — and nothing passes them on automatically; if the affected party has to be told who objected in order to answer, the operator does that by hand. A notice is not anonymous, because somebody has to be able to answer it. See privacy.