Any other concerns aside, I would agree that Drupal.org should not point people to any service that requires a user to create an account in order to view vital information like system status.
jpoesen's suggestion to update this error page (and any others like it) to point to an open platform or service like Mastodon sounds reasonable to me.
As the person who created and set up the @drupalcommunity Twitter account for the Drupal Community Working Group back in 2016, I would be favor of deprecating that account in lieu of other channels that are more aligned with the project’s values and principles and code of conduct.
As for @drupal, @drupalcon, and other accounts, I believe those are run by the Drupal Association, and they would be the ones to make the decision whether to stop using them or not. I think there probably is value in keeping those accounts active at some level to protect the trademark and avoid having bad actors take over the namespace, but would in general agree that they should not be primary communications channels for the project or community.
volkswagenchick → credited gdemet → .
tekNorah → credited gdemet → .
volkswagenchick → credited gdemet → .
volkswagenchick → credited gdemet → .
volkswagenchick → credited gdemet → .
Thanks again! You can read the announcement of the updated Code of Conduct here: https://www.drupal.org/community/blog/introducing-the-updated-drupal-com... →
volkswagenchick → credited gdemet → .
volkswagenchick → credited gdemet → .
Closing this meta issue, as all child issues have now been marked fixed or closed.
Making this issue as fixed as the Code of Conduct has been reviewed and updated with community feedback provided in https://www.drupal.org/project/drupal_cwg/issues/3320237 →
The finalized draft has been submitted to the CWG for final review and approval.
Closing out this issue, as work has moved to this ticket and associated sub-tickets: https://www.drupal.org/project/drupal_cwg/issues/3313322 →
Closing out this very old and long-ago fixed issue.
Closing out this very old and long-ago fixed issue. The issue queue etiquette page at https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett... → addresses the concerns that prompted this issue.
Closing out this old issue. To summarize, the CWG does not maintain a list of individuals who have been banned from events, instead situations involving banned individuals are handled on a case-by-case basis. If you are an event organizer and are concerned that someone who is scheduled to attend or speak at your event might be doing so in violation of a ban, you are welcome to reach out to the CWG for guidance.
volkswagenchick → credited gdemet → .
With regard to speakers, my personal view is that if there is a HEPA filter near the podium, we should not require speakers to mask while they are presenting. Studies published by the CDC and others have demonstrated the efficacy of HEPA filters used in a conference room setting, especially when accompanied by masking. Many other conferences use HEPA filters to improve safety for speakers and attendees, including the recent meeting of the World Economic Forum in Davos.
If the venue does not have HEPA filters available, they can be easily constructed using a box fan and furnace filters.