| 22 Jun 2019 |
 Matthew | we deliberately didn't include a clause like that in the governance docs | 22:04:23 |
| Matthew | just because some random decides to build a project on Matrix doesn't mean they automatically get to define how the protocol evolves | 22:04:54 |
 CalcatriX | You're alluding to two contradicting things. | 22:05:31 |
| CalcatriX | On the one hand, you have totally open policies for participation, and next you immediately say it's more closed than that... | 22:05:49 |
| Matthew | they're not contradictory. | 22:06:06 |
| CalcatriX | I think you need to codify something more real than this... | 22:06:12 |
| CalcatriX | This ambiguity is just a weak spot, as I see it. | 22:06:21 |
| Matthew | anyone is welcome to participate & contribute, whether they have a project or not, as long as they follow the bylaws/values/mission whatever | 22:06:28 |
| CalcatriX | In reply to @matthew:matrix.org
anyone is welcome to participate & contribute, whether they have a project or not, as long as they follow the bylaws/values/mission whatever And the result of this is noise. | 22:06:44 |
| Matthew | i guess we could add something to make that explicit in the governance docs, though - thanks for pointing it out. | 22:06:45 |
| CalcatriX | I'm not saying I have all the answers here, this is an extremely difficult issue for you to contemplate... | 22:07:04 |
| Matthew invited  Github. | 22:07:11 |
| Github joined the room. | 22:07:26 |
| CalcatriX | Check this out for contrast, I'm not saying they have it all correct, but they felt a need to include these clauses: https://ircv3.net/charter | 22:09:16 |
| CalcatriX |
In general, candidates who meet any of the following criteria will be given more consideration
- Developers of widely used IRC software
- Administrators of widely used IRC networks
- People who have otherwise contributed materially to the specifications
| 22:09:47 |
| Matthew | !github create "governance docs should spell out that building a project on matrix doesn't automatically mean you get to define the protocol" "i.e. there is no claim-of-stake. instead, anyone can participate, as long as they are aligned with the project's mission and following the governance rules" | 22:10:09 |
| Github | Need to specify repo. Usage: !github create [owner/repo] "issue title" "description" | 22:10:12 |
| Matthew | bah | 22:10:16 |
| Matthew | !github create matrix-org/matrix-doc "governance docs should spell out that building a project on matrix doesn't automatically mean you get to define the protocol" "i.e. there is no claim-of-stake. instead, anyone can participate, as long as they are aligned with the project's mission and following the governance rules" | 22:10:42 |
| Github | Created issue: https://github.com/matrix-org/matrix-doc/issues/2142 | 22:10:44 |
| CalcatriX | I'm not sure that solves the issue. I totally agree with the principal of that position. Anyone can contribute. Nobody should be locked out from the bottom line | 22:10:51 |
| CalcatriX | But it doesn't help the immediate noise issue. | 22:11:02 |
| CalcatriX | I shouldn't have to battle randoms like Jamie and Kytheria to finally reach a substantive discussion with Travis | 22:11:37 |
| CalcatriX | I believe this may be a cultural problem | 22:11:55 |
| Matthew | !github create matrix-org/matrix-doc "governance docs should spell out that contributors should be competent" "i don't think we have anything that says 'before you make a proposal, try not to be out of your depth'. it might be worth gently adding" | 22:12:09 |
| Github | Created issue: https://github.com/matrix-org/matrix-doc/issues/2143 | 22:12:10 |
| Matthew | perhaps ^ helps balance it slightly. | 22:12:23 |
| CalcatriX |
try not to be out of your depth
Totally on point.
| 22:12:30 |
| CalcatriX | For example, why is Half-Shot responding to Frislie's federation canonical JSON MSC with nonsense? | 22:12:51 |
| Matthew | you sure seem to know a lot about the matrix community for someone who claims
I'm new. I don't know what's going on.
| 22:13:43 |
