fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

@corbet @axboe @ljs @brauner

Right or wrong, the feeling I got was that the bar for actions was just raised higher. Now it's not just the CoC committee, you also need a near unanimous vote from the TAB.

lore.kernel.org/workflows/87h6

lore.kernel.orgRe: [PATCH] Documentation/CoC: Spell out the TAB role in enforcement decisions - Jani Nikula

@jani @corbet @axboe @brauner cool, more delays in doing absolutely nothing then!

@ljs @jani @axboe @brauner Again, suggestions for what $SOMETHING should be would be helpful.

Meanwhile, the most recent CoC action got through the TAB in [checking] two hours and 58 minutes. How much faster do you think a process like this should go?
Lorenzo of modest stature

@corbet @axboe @jani @brauner Went over the $SOMETHING on other thread, (and previously - this isn't empty whining).

I am glad it was streamlined from the ~weeks it took to do something about Kent (and case not closed), but can be forgiven for feeling adding more barriers might result in further delay.

If it's on order of hours, fine. But that's something new right?

@ljs @axboe @jani @brauner *All* of this is something new. Everybody involved is still trying to figure this out.

As far as the other thread: you gave some characteristics that you think the process should have, which is fine. But I have not seen a lot of specifics on how such a response could be implemented within our community. I'll say again: suggestions welcome. Nobody feels that they have a real handle on all of this.

(Just to be clear: I'm not involved in the implementation, but I can do my best to ensure that useful ideas are considered.)

@corbet @axboe @jani @brauner There's a character limit on this instance which limits specificity :)

2 simple ones though:

1. Abuse LF staff, get banned from LF events.

2. Refuse to take action requested of you, punishment either extended or escalated.

Surely the community would accept this... Kent refusing to apologise publicly as was asked of him and suffering no consequences for it was to me, very egregious.

@ljs @axboe @jani @brauner I will pass those on. Of course, attendance at LF events is, in the end, up to the LF. Extending the *kernel* CoC to those events is, by Documentation/process/code-of-conduct-interpretation.rst, explicitly out of scope. That could be reconsidered, naturally.

@corbet @axboe @jani @brauner Thanks.

Has the policy changed there? As I know of at least one case in the past where somebody was told if they did not apologise they would not be permitted to attend an LF event, unless I misunderstood the situation.

@ljs @axboe @jani @brauner That policy hasn't changed since the CoC was adopted.