From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Unilaterally blocking people on Github without any proper procedures or authority
Date: Wed, 10 May 2017 10:49:18 -0400 [thread overview]
Message-ID: <assp.030364a0b3.20170510104918.1db18460@o-sinc.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2575 bytes --]
This is really amazing and a new low for Gentoo all around. Many likely
have no knowledge. This side steps Comrel, and any other Gentoo
entities. There are no open bugs, there is no record or any mention....
Yesterday I noticed my history of past commits to Gentoo disappeared
from my Github account. I went to watch/star/fork Gentoo repos and I
could not. Having contacted Github over such. It turns out I was
blocked from Gentoo organization on Github.
That is entirely unacceptable, and without any reason. At best it is
over comments on this PR. Which I have mentioned several times on this
mailing list and -dev. The submitter was VERY upset to see it closed.
https://github.com/gentoo/gentoo/pull/1721#issuecomment-299942259
My comments there HARDLY justify any action be taken....
There is another open for over a year I just discussed with
fordfrog/Miroslav Šulc. Which he was requesting my help to test
address. Why it has not been committed to tree. I used to maintain
Tomcat. Other than me, Miroslav/fordfrog is the only other with such
experience to be able to test out such changes, etc.
https://github.com/gentoo/gentoo/pull/1358
I can only assume this was mgorny/Michał Górny. He recently showed up
in #gentoo-java IRC asking about those PRs. I responded to him, and he
ignored me, no surprise. Thus I am not to shocked at the blocking on
Github.
Though this goes entirely against any Gentoo policy on taking any such
action against a developer. Much less a member of the community. Even
after stuff in December. I was not blocked, banned, indefinitely from
any Gentoo resource. At it seems I am now from Github.
Even worse, a repo Miroslav Šulc/fordfrog created on a project I had
direct commit access to I am now blocked from. I know neither Miroslav
Šulc/fordfrog or Benda XU/heroxbd would want me restricted from
that respository.
https://github.com/gentoo/java-ebuilder
This is really unacceptable and needs to be reversed immediately.
Anyone including myself that has been blocked from Gentoo github should
have that block removed.
Someone needs to start paying attention to the people who are managing
Gentoo on Github. They are clearly doing what ever they want. Not
following any Gentoo policies. Not filing any bugs, or any records of
their actions. This is not how organizations of any form should operate.
This could never happen within Gentoo. This is abuse of a 3rd party
resource a limited few have administrative control over, without
oversight.
--
William L. Thomson Jr.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2017-05-10 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 14:49 William L. Thomson Jr. [this message]
2017-05-13 21:07 ` [gentoo-project] Unilaterally blocking people on Github without any proper procedures or authority Kristian Fiskerstrand
2017-05-14 3:53 ` Raymond Jennings
2017-05-14 5:15 ` Matthias Maier
2017-05-14 5:34 ` William L. Thomson Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=assp.030364a0b3.20170510104918.1db18460@o-sinc.com \
--to=wlt-ml@o-sinc.com \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox