--- Log opened Sat Apr 15 00:00:33 2023
10:38 < ariard> BlueMatt[m]: matt, can you tell me why i have been removed from the LDK GH org during the night ? is that a technical mistake?
10:38 < ariard> if block inc is doing corporate capture of this open-source project please be transparent about it at last
10:39 < ariard> moneyball___: ^^
10:39 < BlueMatt[m]> I didn’t think that team did anything, honestly. As we’d discussed previously since you haven’t done much work on ldk in a while and I don’t believe every merged I removed that a while ago. The “people” team I don’t even know what it does, the reviewers team has had non spiral folks for a while and that’s not changing.
10:40 < BlueMatt[m]> Errr don’t think that team does anything
10:40 < BlueMatt[m]> Or doesn’t have access to anything in particular, it’s just a random team in the org
10:40 < ariard> Sorry i've not done any work on LDK since a while? like last review is last evening iirc
10:41 < BlueMatt[m]> A few reviews here or there but never (?) via the approved button
10:41 < ariard> so what do you mean, you're the one taking all the project admin decisions in the background without any public communication?
10:41 < BlueMatt[m]> Of course any review you want to do I appreciate!
10:41 < BlueMatt[m]> The team I removed you from isn’t…a thing?
10:42 < BlueMatt[m]> Like it doesn’t have any particular access to anything
10:42 < ariard> the approved button is not part of the CONTRIBUTING.md guidelines iirc and not bitcoin core or libsecp256k1 practice?
10:42 < BlueMatt[m]> I was planning on deleting it
10:43 < ariard> I don't remember the exact scope of GH org and capabiities though if it exists it let you do things?
10:43 < BlueMatt[m]> ariard: The GitHub flow requires it (and has for quite some time). The teams/access on GitHub are around the approve button “counting” and merging. Anything besides that is just nonsense
10:43 < ariard> and in the past it has been a source of discussion for the Core one, like when the bips drama around Taproot
10:44 < BlueMatt[m]> I don’t think so but if you can no longer like assign issue tags or whatever let me know and I’ll figure out how to add that back
10:44 < ariard> BlueMatt[m]: would you prefer to move from approve button to GPG-signed approvals of the PR?
10:44 < ariard> like distrust GH infrastructure
10:44 < BlueMatt[m]> I don’t want drama, but mostly I literally do not understand GitHub permissions, they’re unreadable indecipherable crap
10:45 < BlueMatt[m]> Yes we should, just haven’t yet. Up to now I’ve still reviewed every line merged locally and not trusted GitHub specifically
10:45 < BlueMatt[m]> But before I can’t keep up we have to shift :)
10:45 < ariard> BlueMatt[m]: okay i'm just happy if i can tag issues, that's helpful we start to have far more PR to review
10:46 < ariard> I'll open an issue on the repository on how we move from "trust-GH" to trust GPG and script like Core is doing.
10:48 < ariard> BlueMatt[m]: https://github.com/lightningdevkit/rust-lightning/pull/2089
10:48 < ariard> Like said I prefer to focus on the long-term context-rich stuff and beyond that i think i'm still quite active that matters for LDK
10:49 < ariard> Like vls, jamming, mempool and eltoo even if if concede i'm least active on the repository itself, lightning has grown
10:50 < ariard> And sorry for being late on my two open PRs #1841 and #1884, back on it soon
10:51 < BlueMatt[m]> Hey no pressure. You do what you feel like you can add the most value with
10:51 < BlueMatt[m]> I’m not your boss
12:33 -!- darosior [~darosior@194.36.189.246] has quit [Remote host closed the connection]
12:36 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-rust
12:38 < ariard> Yeah I know you're not my boss. Still the way the maintenance of an open-source project is done is no neutral on the contribution culture
12:39 < ariard> I think laawnj had some consistent thoughts here from his years of maintenance with Core.
12:39 < ariard> I remember talking with him publicly when he merged a bit too fast a glozow PR, without real review end of 2022
12:40 < ariard> BlueMatt[m]: see https://github.com/lightningdevkit/rust-lightning/issues/2186, we can pursue the conversation there
12:40 < ariard> Or at next LDK meeting, dunno which week it's happening
12:55 -!- greypw25460021 [~greypw254@grey.pw] has quit [Quit: I'll be back!]
12:56 -!- greypw25460021 [~greypw254@grey.pw] has joined #bitcoin-rust
13:12 -!- darosior [~darosior@194.36.189.246] has quit [Ping timeout: 276 seconds]
13:40 < ariard> I confirm as block #785567 - hash 00000000000000000003b79170d0dfb9cd12d3aee10a0f337bbb586310184f6d I've been re-added to the LDK org
13:40 < ariard> With the same level of privileges (at least what matters for my area of contributions) - So the technical mistake sounds to have be corrected
13:40 < BlueMatt[m]> I'm kinda confused....(a) I haven't touched anything in the past hour?
13:40 < BlueMatt[m]> and (b) whats the actual issue here?
13:41 < BlueMatt[m]> "org member" has never been a thing, either in core or in ldk
13:41 < BlueMatt[m]> various teams may show up on github as "org member" but its meaningless
13:41 < BlueMatt[m]> the only meaning is "can assign tags" and I _think_ I didnt remove you from that
13:41 < BlueMatt[m]> i removed you from a team that, as far as I can tell, isn't actually used for anything
13:58 < ariard> BlueMatt[m]: okay do you confirm you remove me from a team that plausibly have trigger this mail notification: https://github.com/ariard/rust-lightning/commit/9b17593833b5b2d8fb3a9afe4eb81f315cbc4229 ?
13:58 < ariard> s/remove/removed/g
13:58 < ariard> sorry for the latency, had to figure out how to convert the mail as a pdf
13:59 < ariard> I concede the GH mail notification are very unclear as they don't tell you which rights have been removed...
14:18 < BlueMatt[m]> Yea there’s a team just called “people” or something like that (not at a computer rn) that I don’t think is used that I did remove you from
14:19 < BlueMatt[m]> I didn’t intend to remove you from anything that matters
16:25 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-rust
21:47 -!- angusp [9e8eed9774@2604:bf00:561:2000::1048] has quit [Ping timeout: 252 seconds]
21:51 -!- angusp [9e8eed9774@2604:bf00:561:2000::1048] has joined #bitcoin-rust
--- Log closed Sun Apr 16 00:00:34 2023