!VyoUhyWvlhSpFWWxHL:matrix.org

Zulip setup coordination

85 Members
Coordination to setup https://nixpkgs.zulipchat.com/, see https://github.com/NixOS/foundation/issues/14330 Servers

Load older messages


SenderMessageTime
2 May 2024
@zimbatm:numtide.com@zimbatm:numtide.comDifferent angle19:38:03
@infinisil:matrix.orginfinisilI think the manual invite process should work out just fine really19:38:27
@infinisil:matrix.orginfinisil

Tasks:

  • Get https://github.com/NixOS/foundation/pull/144 merged
  • Link these documents everywhere
  • Open participation for everybody, and maybe create some streams for different topics
  • Invite everybody
19:39:53
@infinisil:matrix.orginfinisil *

Tasks (in this order)

  • Get https://github.com/NixOS/foundation/pull/144 merged
  • Link these documents everywhere
  • Open participation for everybody, and maybe create some streams for different topics
  • Invite everybody
19:40:01
@edef1c:matrix.orgedefimage.png
Download image.png
19:40:06
@edef1c:matrix.orgedefthis could be the welcome intro, and people can sub to the other streams after they've read the message19:40:29
@edef1c:matrix.orgedefjust join people to one read-only thing by default, basically19:40:45
@edef1c:matrix.orgedef(not trying to hammer on this, and not insistent on this particular approach, just making sure my earlier suggestion is conveyed effectively)19:41:23
@edef1c:matrix.orgedefanyway, that's my proposed colour for the bikeshed, onwards19:41:33
@7c6f434c:nitro.chat7c6f434c Technical post about the welcome message: has there been enough changing things around to start the welcome message with «Attention: this CoC is not the same as Nixpkgs main CoC, and not the same as some earlier versions mistakenly posted (before the invitations were sent).»? 19:41:51
@7c6f434c:nitro.chat7c6f434c * Technical question about the welcome message: has there been enough changing things around to start the welcome message with «Attention: this CoC is not the same as Nixpkgs main CoC, and not the same as some earlier versions mistakenly posted (before the invitations were sent).»? 19:41:58
@edef1c:matrix.orgedefyeah19:42:14
@edef1c:matrix.orgedefthat seems fair19:42:17
@7c6f434c:nitro.chat7c6f434cHopefully this will do some click-baiting…19:43:00
@edef1c:matrix.orgedefoh, yeah, it'd help the actually-reading-it funnel19:43:32
@edef1c:matrix.orgedeflooks like we have some suggestions on the CoC PR19:43:52
@edef1c:matrix.orgedefi feel like i understand where shlevy is coming from but i'm not sure how to accommodate his concerns19:44:59
@joepie91:pixie.townjoepie91 🏳️‍🌈if you are referring to the thread I commented on, I do not think it can be accommodated without violating the spirit of the document - it is a fundamental mismatch in thinking about harms19:47:01
@edef1c:matrix.orgedefmm, okay19:47:18
@danielle:fairydust.spacedanielleConstructive collaboration involves assuming the injured party was genuinely hurt, and assuming good intent on both sides means you apologize and avoid doing the same thing (knowingly hurting someone)19:48:40
@joepie91:pixie.townjoepie91 🏳️‍🌈 this is an issue I run into very frequently when discussing conduct discussions; a lot of people, especially from "apolitical" tech background, have an interpretation of "misconduct" that centers entirely around intent and understanding... where a complaint is only deemed valid if the person being complained about fully understands and agrees with the accusation. this is a frequent source of persistent harassment of marginalized folks, because this is where the whole marginalized vs. privilege perspective comes into play. so if you want effective moderation, you just cannot have "the person understands and agrees with it being wrong" as a prerequisite 19:49:26
@edef1c:matrix.orgedef
In reply to @danielle:fairydust.space
Constructive collaboration involves assuming the injured party was genuinely hurt, and assuming good intent on both sides means you apologize and avoid doing the same thing (knowingly hurting someone)
what i understand shlevy's worry as, is that people might weaponise feigned injury to steer conversations or coerce others
19:49:29
@danielle:fairydust.spacedanielleThat would be disruptive behavior19:49:38
@danielle:fairydust.spacedanielleand is already not in the spirit of the document19:49:46
@joepie91:pixie.townjoepie91 🏳️‍🌈
In reply to @edef1c:matrix.org
what i understand shlevy's worry as, is that people might weaponise feigned injury to steer conversations or coerce others
(I mentioned resolution by a moderator for this reason)
19:49:55
@joepie91:pixie.townjoepie91 🏳️‍🌈
In reply to @edef1c:matrix.org
what i understand shlevy's worry as, is that people might weaponise feigned injury to steer conversations or coerce others
* (I mentioned resolution by a moderator for this reason, but it did not seem to assauge the concerns)
19:50:04
@infinisil:matrix.orginfinisilI'll step away for a bit, but let's try to make https://github.com/NixOS/foundation/pull/144 work, you can also send PRs against my branch with suggestions. After that we should be Zulip-unblocked19:50:14
@danielle:fairydust.spacedaniellei left comments on Valentin's suggestions, i'm a mix of soft +1s and hard "do not reword this"19:50:57
@edef1c:matrix.orgedefi'll also step away for a bit, since i feel i've been a bit too engaged and would like to make some space instead19:51:21
@danielle:fairydust.spacedanielle
In reply to @infinisil:matrix.org
I'll step away for a bit, but let's try to make https://github.com/NixOS/foundation/pull/144 work, you can also send PRs against my branch with suggestions. After that we should be Zulip-unblocked
fwiw the only things there are minor rewordings rather than things that change actual meaning, so I think it can land relatively easily.
19:56:33

Show newer messages


Back to Room ListRoom Version: 10