| 4 Jan 2019 |
 TravisR | although that document is pending an update | 16:51:38 |
 Matthew | 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:27 |
| Matthew | the stuff about “managing emotional burden” resonated most | 17:40:59 |
| Matthew | or whatever expression he used | 17:41:06 |
| Matthew | to describe the soul destroying onus of trying to wrangle people to consensus | 17:41:22 |
 @adam:thebeckmeyers.xyz | Unfortunately his advice on that point didn't seem very actionable to me. :/ | 17:42:56 |
|  [uhoreg] changed their display name from uhoreg to horeg. | 21:50:53 |
| [uhoreg] changed their display name from horeg to ühoreg. | 21:52:03 |
| Matthew | &Adam: yeah, there seemed to be two suggestions - to rate-limit activity based on personal-time-budgeting | 21:54:12 |
| Matthew | and to have cooling off periods | 21:54:15 |
| Matthew | both of which end up slowing everything down and making it grind to a halt | 21:54:31 |
| Matthew | and 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:55 |
| Matthew | and hey presto we lose 3 weeks | 21:54:59 |
| Matthew | and lose all the momentum | 21:55:10 |
| Matthew | so yup, it didn't seem that actionable to me too. | 21:55:31 |
| Matthew | i suspect the mitigation is more to be ruthless on expecting constructive behaviour from folks | 21:55:47 |
| Matthew | as anathema as it might feel to some (like me, at least) | 21:56:00 |
 kitsune | I'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:18:05 |
| kitsune | 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. | 23:25:15 |
| 5 Jan 2019 |
| Matthew | well, rust does have it with subteams? | 00:53:08 |
| Matthew | and i suspect we'll sprout it to in good time | 00:53:14 |
| Matthew | (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 :) | 00:53:48 |
| kitsune | Well, /shrug then | 02:21:33 |
| 7 Jan 2019 |
|  anoa changed their profile picture. | 20:18:27 |
| 15 Jan 2019 |
|  benpa-matrix changed their profile picture. | 13:13:29 |
| 20 Jan 2019 |
|  tom changed their profile picture. | 23:19:07 |
| 21 Jan 2019 |
| [uhoreg] changed their display name from ühoreg to uhoreg. | 16:18:30 |
| 28 Jan 2019 |
|  JC changed their profile picture. | 07:35:48 |
| 6 Feb 2019 |
| tom changed their profile picture. | 11:51:44 |
| tom changed their profile picture. | 15:59:10 |
