| 00:30 | <devsnek> | jridgewell: https://github.com/engine262/engine262/commit/a38a19dca496fcad78951fd6d8e89246c01223b0 |
| 00:35 | <jridgewell> | Looks right |
| 18:01 | <shu> | how do i transfer a repo out of tc39-transfers? do i transfer it to "tc39"? |
| 18:10 | <ljharb> | shu: only the chairs can do that |
| 18:11 | <ljharb> | (there's instructions at the bottom of the readme on https://github.com/tc39/proposals) |
| 18:11 | <Bakkot> | specifically, my understanding is that only the chairs can accept the transfer, and there's a time limit for accepting the transfers, so the chairs just do the whole process once it's in tc39-transfer |
| 18:12 | <Bakkot> | sidebar: we should update tc39/proposals to list the new editors |
| 18:12 | <Bakkot> | how-we-work maybe needs a new section for how to do chair/editor handover which lists this sort of thing |
| 18:12 | <ljharb> | nah that's not how it works |
| 18:12 | <Bakkot> | no? |
| 18:12 | <ljharb> | to transfer to tc39-transfer, the owner of the repo is added to tc39-transfer, and then they can just summarily move it in |
| 18:12 | <Bakkot> | right yes |
| 18:13 | <Bakkot> | I was describing the process following that point |
| 18:13 | <ljharb> | and since the chairs are owners in both tc39-transfer and tc39, they just summarily move it over when they get to it |
| 18:13 | <ljharb> | i'm not aware of any "request transfer" feature in github |
| 18:13 | <Bakkot> | https://help.github.com/en/github/administering-a-repository/transferring-a-repository |
| 18:14 | <Bakkot> | > When you transfer a repository that you own to another user account, the new owner will receive a confirmation email. The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire. |
| 18:14 | <ljharb> | that's to a user account, not to an org |
| 18:14 | <ljharb> | but fair |
| 18:14 | <Bakkot> | ahh, ok |
| 18:15 | <Bakkot> | I didn't realize that the process was different for transferring to users vs orgs |
| 18:17 | <akirose> | it's v different |
| 18:18 | <akirose> | to a degree that it's an annoying problem for me in my other job |
| 18:18 | <ljharb> | i've continually complained to github that users and orgs aren't equally privileged in the majority of workflows/features |
| 18:23 | <shu> | i continue to be mostly ignorant of how GH works |
| 18:26 | <rkirsling> | is this like, gitizens united |
| 18:26 | <rkirsling> | (I'll see myself out) |
| 18:29 | <shu> | is that a soft g, like gente |
| 18:34 | <ljharb> | it's a g like in gif |
| 18:35 | <ljharb> | jitizens |
| 20:19 | <devsnek> | MylesBorins: should I add import.meta to the agenda |
| 20:19 | <MylesBorins> | yeah probs |
| 20:19 | <devsnek> | cooleo will do |
| 21:07 | <devsnek> | akirose: there are some odd formatting issues in the welcome email, should i message you a screenshot? |
| 21:12 | <devsnek> | MylesBorins: i assume 15m is enough time? |
| 21:13 | <MylesBorins> | maybe 30 |
| 21:13 | <MylesBorins> | since it is a stage 4 |
| 21:13 | <MylesBorins> | we can take time back later if we don't think we need it |
| 21:13 | <devsnek> | 👍🏻 |
| 21:13 | <ljharb> | don't tempt fate |
| 21:15 | <devsnek> | oh god i have write perms to agenda repo now |
| 21:16 | <devsnek> | i'm not in front of a git atm would someone mind deleting that commit out |
| 21:16 | <ljharb> | sure |
| 21:16 | <devsnek> | i'm so used to that creating a branch by default oops |
| 21:17 | <ljharb> | devsnek: also "stage" is "current stage" in that table |
| 21:17 | <devsnek> | oh oops |
| 21:28 | <akirose> | oops |