Closed skmp closed 2 years ago
Archiving here, as at this point censorship wouldn't be out of the question
I think there should be a formal inquiry, into who exactly has 'maintainer voting powers' within fex, how many were present in the voting, what exactly were the reasons for the decision, as well as the final vote tally (support/oppose/absent).
Looks like my name has censored from the past contributors github page, https://github.com/FEX-Emu/FEX/graphs/contributors.
The Pulse page and Contributors widgets are still uncensored it seems.
Widget in main page
Pulse Page
Contributors page
An intriguing fact to archive here is that https://emulation.gametechwiki.com/index.php/FEX-Emu, the only independent information about FEX, as far as I can tell, doesn't actually mention @phire, but only @sonicadvance1 and @skmp.
(I wasn't aware of this before the capture)
Taking note of recent events, phire has lost privilege of communication and have to speak to me through intermidieries from now on, and namely through Petros Korelas (+30 6936 126 336), petros@korelas.law, https://www.korelas.law/, +30 211 013 0613
The notice is still not in the homepage of https://fex-emu.com, so there's clearly no consensus of the so-called fex-emu.com team.
I'm still backchanneling with Sonicadvance1.
fex-emu.com has private whois, https://uk.godaddy.com/whois/results.aspx?checkAvail=1&tmskey=&domain=fex-emu.com
fex-emu.com capture
fex-emu.com capture
https://github.com/FEX-Emu/fex-emu.com/commit/db20ba7c5f75a9f9a877823d3bd518a450ba7d7b was made by SA1, though there's no signed-off or commit message? not sure what to make of this.
The message claims to be coming from both Ryan & Scott, though, there's actually no verifiable information linking this to SA1?
Who composed this?
What organizational claim does this 'Ryan & Scott` group over so called fex-emu.com's administrative assets?
Was there voting? Was due process followed?
And how does the group named 'Ryan & Scott` from so-called fex-emu.com relate exactly to the discord linked from the original fex-emu.org page, and github repo?
Based in which authority was https://github.com/FEX-Emu/FEX/issues/1965 marked as 'unplanned' (?) and was closed?
Who used the FEX-Emu organization to mark the ticket as locked?
Was there due process wrt decision making and audit trail there?
Apparently, someone has quietly and behind the scenes blocked me from either creating an issue in fex-emu, or forking the repo (github errors in both cases).
I assume this to be a side effect of @phire's evident power tirp
email forwarding established to ryan.houdek@fex-emu.com, for all destinations except skmp@fex-emu.org
In addition, access has been granted to sonicadvance1@gmail.com to modify email forwarding and renew the domain. I expect my mailbox will not be tampered with.
I think this is the best choice for now, before further steps on Monday.
Removed privacy protection from fex-emu.org, and updated the contact records (will take a moment to refresh) https://www.namecheap.com/domains/whois/result?domain=fex-emu.org
Initial reports have been filed against github (for directly hosting), namecheap (as a registar to the domain) and twitter (for posting a link to) wrt the unauthorized public disclosure of private, medical data and relating it with my full name.
This is a clear, severe violation of GDPR as well as medical records acts.
Reported urls:
Taking note of recent events, sonicadvance1 has lost privilege of communication and have to speak to me through intermediaries from now on, and namely through Petros Korelas (+30 6936 126 336), petros@korelas.law, https://www.korelas.law/, +30 211 013 0613
(this marks the end of public archival for now, and I'll be handing over to Petros Korelas (+30 6936 126 336), petros@korelas.law, https://www.korelas.law/, +30 211 013 0613)
After discussing with several people, I've decided the best resolution at this point is to focus on the code/tech - that's what we're here for, anyway - and let time pass so that everyone involved gets their cool back.
I also think, at this point, everyone involved (including me) owers everyone else involved (including me) and apology.
This ticket might disappear at some point.
Write up details, release redacted documentation from chats with sonicadvance1, phire, as well as of the discussion that generated in #contributor-discuss in the days leading up to the incident.
Follow up from https://github.com/FEX-Emu/FEX/issues/1965 as that issue was closed as 'unplanned' by phire and then locked by some 'abstract' FEX-Emu entity. I guess the rest of it was 'planned' in some way or another by some?