Restrict push permissions for Rene. Hopefully this is a temporary measure.
Concern Raised0dbab55b62e4

Authored by bcooksley on Feb 9 2018, 10:26 PM.

Description

Restrict push permissions for Rene. Hopefully this is a temporary measure.

Fixes T7934

Details

Auditors
rjvbb
Committed
bcooksleyFeb 9 2018, 10:30 PM
Parents
R248:5374265bfa59: Revert "skip eol and author name check for plasma-mobile.org"
Branches
Unknown
Tags
Unknown
Tasks
Restricted Maniphest Task
bcooksley added a task: Restricted Maniphest Task.Feb 9 2018, 11:27 PM
rjvbb raised a concern with this commit.EditedFeb 10 2018, 11:11 AM
rjvbb added a subscriber: rjvbb.

This is hardly acceptable.

The prior behaviourin question makes it sound like I have a record of proven misconduct in pushing (tags), with demonstrable record of refusal to cease and desist the behaviour in question. Neither record exists in my knowledge; I was NEVER asked or told NOT to push tags.

In reality, this can only refer to a single tag I applied for personal use to my personal working copy and of which was I don't know how it ended up on the server. No one realised this had happened, including me. Instead, this just slumbered until I cited my local commit - in a context that clearly showed my intention to keep it private. It is hard imagine this tag can have messed anything up significantly in the almost 3 months it was out in the wild.

I did push a tag to the Konsole repo once before, intentionally; after a proper review (here on phab IIRC) which was accepted by the project maintainer who agreed with my explanation why the tag was useful.

What makes this measure so hard to accept is that it was done in response to a single request of a single other user who seems to have developed a personal beef against me (which could well be due to cultural differences), without given me a chance to explain myself. Worse, the measure introduces a *defamatory* text in the explanatory message. And above all, it's a global measure that also affects my own repositories of which I am the sole and only release manager. This is of course completely unacceptable:

> git push -v
Pushing to ssh://git@git.kde.org/osx-integration
Counting objects: 1, done.
Writing objects: 100% (1/1), 214 bytes | 214.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0)
remote: FATAL: VREF/kde-update-checks: helper program exit status 256
remote: Pushing tags without the consent of the release managers for a repository is not permitted.
remote: As a consequence of prior behaviour, your privileges to push tags has been globally restricted.
remote: Push declined - please contact sysadmin@kde.org for further information
remote: error: hook declined to update refs/tags/qt59-plugins
To ssh://git.kde.org/osx-integration
 = [up to date]      qt590 -> qt590
 ! [remote rejected] qt59-plugins -> qt59-plugins (hook declined)
updating local tracking ref 'refs/remotes/origin/qt590'
error: failed to push some refs to 'ssh://git@git.kde.org/osx-integration'

Those last two things must change. The explanatory message can refer to the fact I indicated myself that I have no use for tagging repositories of projects that aren't mine. And I should regain full control over my own repositories (repository, to be exact).

(Also please check the grammar while you're rewriting the message...)

Edit: And use the proper form if you have to use my real name, i.e. include the acute accent.

This commit now has outstanding concerns.Feb 10 2018, 11:11 AM