Skip to content

Instantly share code, notes, and snippets.

@edwardoliveira
edwardoliveira / dbsky.csv
Created February 6, 2025 15:20
Database people
We can make this file beautiful and searchable if this error is corrected: It looks like row 2 should actually have 5 columns, instead of 3 in line 1.
displayName,handle,didLiz 👩🏿‍💻,lizzyrandom.bsky.social,did:plc:xl7yjujygm5f2rwfyu2fm3kd
Bijil Subhash,bijilsubhash.bsky.social,did:plc:r6zilu37epcssryqcdu4xctk
Anders,dataders.bsky.social,did:plc:kh4tjxyrlleosqn3l4mxw3a6
Mark Needham,markhneedham.com,did:plc:dad7mxkikrer53hclo3iykhb
Max Gabrielsson,maxxen.bsky.social,did:plc:ockajdxbicx77v3kaotzfl2j
Elad Leev,leevs.dev,did:plc:bsoo3s2r7hw7f33tf3agvbw3
Wan Shen Lim,wslim.bsky.social,did:plc:opd45mp3v32xcwcr3illkawd
shikhar,schmizz.net,did:plc:mycpt6nuh2isf7pcyuftiqes
materialize.com,materialize.com,did:plc:cl4gcjbc5hfgpgyyt2hhfcgv
Ryan Marcus,ryanmarcus.bsky.social,did:plc:pqrsfv7j63esjfeg6j6jqsd3
Hi,
The patch attached on ZOOKEEPER-2597 is a straightforward adaptation of Kafka's one. It takes care of merging Github PR into Apache git repo and a subsequent closing of the PR on the GH side, among other things (rewriting of commit messages, etc). The current status is: the script needs to be reviewed/validated by a committer. It has been some time since I uploaded the patch, so I gonna do another pass through it in the meantime.
There are some workflow issues beyond the scope of ZOOKEEPER-2597 that need to be sorted out (IMO):
1. The normal workflow is to open a JIRA ticket before doing any GH PR, that is, no JIRA-less PRs. The PR should have a title of the form "ZOOKEEPER-xxxx: Title". This will trigger the Apache JIRA-Github integration and it's opening show up in the JIRA ticket.
2. OTOH, not every Kafka PR needs a corresponding JIRA ticket. There are a class of PRs with "MINOR" title that represent trivial code changes and "HOT-FIX" title that fix urgent, but simple bugs. Both bypass the JIRA cre