Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post mortem May 25 2021 #520

Merged
merged 1 commit into from May 27, 2021
Merged

Post mortem May 25 2021 #520

merged 1 commit into from May 27, 2021

Conversation

@realrasengan
Copy link
Contributor

@realrasengan realrasengan commented May 27, 2021

No description provided.

@realrasengan realrasengan merged commit ea04f72 into main May 27, 2021
1 of 2 checks passed
1 of 2 checks passed
@travis-ci
Travis CI - Pull Request Build Errored
Details
@travis-ci
Travis CI - Branch Build Passed
Details

In conjunction with yesterday’s events, in retrospect, we should have handled the action of closing down channels slightly differently. Originally, we posted a draft policy revision and solicited feedback in #freenode-policy-feedback. After several days, we discussed various feedback internally that was given.

The intent of doing this was not an attempt of a hostile takeover nor hijack like many people are saying. Since certain projects were disrupting their users' ability to chat on freenode via mass kicks, force closures, spam, we decided to enact this policy in those places which were deemed in violation and could cause an issue later.

This comment has been minimized.

@alyx

alyx May 27, 2021

Perhaps it would be more clear if you updated this to "Since many projects did not want to deal with freenode under my regime and chose to leave, we decided to enact this policy to try as hard as possible to obscure this from our users."?

It may be beneficial in your goal to be open and transparent with your userbase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants