42 Members
For meta-discussion about the MSC proposal process | https://matrix.org/blog/2018/06/20/towards-open-governance-for-matrix-org/ | https://github.com/matrix-org/matrix-doc/issues/131820 Servers

Load older messages

Timestamp Message
4 Jan 2019
16:51:38@travis:t2l.ioTravisRalthough that document is pending an update
In reply to @adam:thebeckmeyers.xyz
Have people from the core team read Graydon's thoughts as an outsider on Rust? He talks about both the language proposal process as well as some ideas about limiting scope creep (keeping Rust from becoming C++). https://graydon2.dreamwidth.org/263429.html
yup, i read it
17:40:59@matthew:matrix.orgMatthewthe stuff about “managing emotional burden” resonated most
17:41:06@matthew:matrix.orgMatthewor whatever expression he used
17:41:22@matthew:matrix.orgMatthewto describe the soul destroying onus of trying to wrangle people to consensus
17:42:56@adam:thebeckmeyers.xyz&AdamUnfortunately his advice on that point didn't seem very actionable to me. :/
21:50:53@uhoreg:matrix.orguhoreg changed their display name from uhoreg to horeg.
21:52:03@uhoreg:matrix.orguhoreg changed their display name from horeg to ühoreg.
21:54:12@matthew:matrix.orgMatthew &Adam: yeah, there seemed to be two suggestions - to rate-limit activity based on personal-time-budgeting
21:54:15@matthew:matrix.orgMatthewand to have cooling off periods
21:54:31@matthew:matrix.orgMatthewboth of which end up slowing everything down and making it grind to a halt
21:54:55@matthew:matrix.orgMatthewand both of which we do today, and all that happens is that some jerk wades into a discussion and craps all over it, at which point everyone says "ugh, i'll come back to this 3 weeks"
21:54:59@matthew:matrix.orgMatthewand hey presto we lose 3 weeks
21:55:10@matthew:matrix.orgMatthewand lose all the momentum
21:55:31@matthew:matrix.orgMatthewso yup, it didn't seem that actionable to me too.
21:55:47@matthew:matrix.orgMatthewi suspect the mitigation is more to be ruthless on expecting constructive behaviour from folks
21:56:00@matthew:matrix.orgMatthewas anathema as it might feel to some (like me, at least)
23:18:05@kitsune:matrix.orgkitsuneI'm surprised that there's no mention about splitting areas of responsibility/interest among people, imposing structure in the team. You don't have to have everybody in the architecture team being equally involved in all parts and required to read all the scrollbacks of everything. Yes, that means delegating to someone to represent/defend your opinion on some topics which, even though you are pretty much qualified to discuss, are not your designated areas.
23:25:15@kitsune:matrix.orgkitsune It doesn't need to lay responsibility on a single person. But if more than N people are expected to "read everything" on a certain wider subject and be ready to give their authoritative position on anything that happens on the subject, then probably some hierarchy should be set up with respective delegation/escalation paths. Yes it's a move away from direct democracy but it's a price to pay for the system's complexity.
5 Jan 2019
00:53:08@matthew:matrix.orgMatthewwell, rust does have it with subteams?
00:53:14@matthew:matrix.orgMatthewand i suspect we'll sprout it to in good time
00:53:48@matthew:matrix.orgMatthew(also worth noting that i believe graydon stepped away from rust due to not wanting to deal with the scaling/community process, so he certainly may lack the answers :)
02:21:33@kitsune:matrix.orgkitsuneWell, /shrug then
7 Jan 2019
20:18:27@andrewm:amorgan.xyzanoa changed their profile picture.
15 Jan 2019
13:13:29@benpa:matrix.orgbenpa changed their profile picture.
20 Jan 2019
23:19:07@tom:lant.uktoml changed their profile picture.
21 Jan 2019
16:18:30@uhoreg:matrix.orguhoreg changed their display name from ühoreg to uhoreg.
28 Jan 2019
07:35:48@jan.christian:gruenhage.xyzjcgruenhage changed their profile picture.
6 Feb 2019
11:51:44@tom:lant.uktoml changed their profile picture.
15:59:10@tom:lant.uktoml changed their profile picture.

There are no newer messages yet.

Back to Room List