Coming from #2067721-3: Amend code of conduct: We won't tolerate bullying or harassment and following.

For core changes, we have a policy that certain large changes should be notified via the g.d.o/core group, which gets blasted out on RSS, twitter, and a few other places, before they actually happen. That's because some changes are far-reaching enough that the general community deserves to have it flagged rather than being buried in an issue queue that 99.3% of all core developers don't see. Most issues don't reach that level of significance, but for those that do it behooves us to make sure everyone has a chance to weigh in, even if they wouldn't otherwise have noticed it.

The same applies to community policies. In the case linked above, a change to the Drupal.org social contract (the COC) was made without the knowledge of 99.965% of the people it would affect. I only found out about it at all because KatteKrab posted a courtesy link to an old g.d.o thread after-the fact. Based on the issue, it looks like Lee Hunter had some concerns about the wording, too.

I don't know if the same channel (/core) should be used, but there should be some way to raise selected issues to whole-community attention so that people not subscribed to this group have an opportunity to weigh in, just as we do with core itself. Not all issues need that level of flag waving, of course, but IMO any changes to the COC do.

Comments

kattekrab’s picture

kattekrab commented

I'd say we need a different channel to /core - coz there's a helluva lot more people in this community that DON'T follow the machinations of core either.

As far as I know we don't currently have a way to really reach "the community" short of an ad-hoc program of blogging so that it hits planet, tweeting... and posting to groups.drupal.org

Suggestions on how we could do this would be welcome... although I do feel that this issue languished in the relevant places for a while... I certainly didn't engage in any kind of active outreach - and I agree that would have been useful to attract more eyeballs.

Crell’s picture

Crell commented

Simple answer: Make another g.d.o group that's announce-only like /core, but not called /core. /community? There's probably plenty of "if you're engaged the community you really ought to know about..." announcements besides COC change proposals that could go out there.

kattekrab’s picture

kattekrab commented

hmmm I like.

Simplicity++

Might be a good thing to discuss at the summit in a couple of weeks too.

dddave’s picture

dddave commented

#2 sounds like a good, easily achievable solution guaranteeing enough reach (coupled with usage of the Planet feed).

kattekrab’s picture

kattekrab commented

@dddave thanks for weighing in on this! :)

Given this is about communication and outreach should we invite a few more eyeballs to engage with this?

I'm inviting Roel, George, Webchick and Dries as the comm-wg, just for courtesy really...

But do we want to blog, tweet, etc?

Next - how might one go about creating an announce only GDO group?

:)

Crell’s picture

Crell commented

I think the way to do it is "ask webchick". :-)

kattekrab’s picture

kattekrab commented
Status: Active » Needs review
kattekrab’s picture

kattekrab commented

https://groups.drupal.org/community already exists - and would not suit this purpose.

tvn’s picture

tvn commented

There is now https://groups.drupal.org/governance restricted to Working Group members only. Posts go on Drupal Planet, https://twitter.com/drupalwgs and https://twitter.com/drupal.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Needs review » Fixed

Yep, I think that means this is fixed. It's one place for folks to look and messages that get broadcast here should now reach a *far* wider audience than in the past, and extra bonus, all of the WGs can use it, not just ours.

kattekrab’s picture

kattekrab commented

win!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.