| 29 Oct 2022 | |||
| vrurg | Google Calendar does it in a weird way. :( | 19:35 | |
| lizmat | hehe | 19:41 | |
| japhb | Good on ya for perservering. :-) | 19:45 | |
| Geth | Raku-Steering-Council/main: 1fc4e21cd5 | (Nick Logan)++ (committed using GitHub Web editor) | minutes/20221029.md Add RSC meeting minutes for 2022-10-29 |
22:20 | |
| 11 Nov 2022 | |||
| Raku-Steering-Council: codesections++ created pull request #51: Add response option: ≤ 48hr ban by one CAT member |
16:56 | ||
| Raku-Steering-Council: codesections++ created pull request #52: Add CAT membership & update ToC |
17:32 | ||
| Raku-Steering-Council/main: ec465c0ecb | (Daniel Sockwell)++ | 4 files Add CAT membership & update ToC This adds a list of current CAT members and updates the ./papers README's ToC. It also deletes the CoC.md, which was added for rendering purposes but (I believe) isn't needed anymore. |
|||
| Raku-Steering-Council/main: 3babdea3ba | (Daniel Sockwell)++ (committed using GitHub Web editor) | 4 files Merge pull request #52 from codesections-forks/Papers Add CAT membership & update ToC |
|||
| Raku-Steering-Council/main: fad631df4f | (Daniel Sockwell)++ (committed using GitHub Web editor) | README.md Add link to Papers |
18:38 | ||
| Raku-Steering-Council/main: 6a511f1d92 | (Daniel Sockwell)++ (committed using GitHub Web editor) | papers/code_of_conduct.md redeploy |
18:44 | ||
| Raku-Steering-Council: codesections++ created pull request #53: Fix links to CoC |
19:08 | ||
| Raku-Steering-Council/main: ebcd4ebcca | (Daniel Sockwell)++ | 4 files Fix links to CoC Previous links were not rendering; I believe because they were conflicting with the *theme*'s Code of Conduct file. |
19:09 | ||
| Raku-Steering-Council/main: d1217017f3 | (Daniel Sockwell)++ (committed using GitHub Web editor) | 4 files Merge pull request #53 from codesections-forks/CoC-link Fix links to CoC |
|||
| Raku-Steering-Council/main: 2100d0640d | (Daniel Sockwell)++ (committed using GitHub Web editor) | papers/code_of_conduct.md Prevent broken links to prior page |
19:36 | ||
| 12 Nov 2022 | |||
| Raku-Steering-Council/main: 79b20ea75d | (Juan Julián Merelo Guervós)++ (committed using GitHub Web editor) | README.md :bug: :memo: Thanks @MasterDuke17 ! |
09:08 | ||
| 14 Nov 2022 | |||
| Raku-Steering-Council/main: abb7e0fee4 | (Elizabeth Mattijsen)++ | minutes/20221112.md Minutes of 12 Nov 2022 |
12:36 | ||
| 16 Nov 2022 | |||
| Raku-Steering-Council/Add-new-spaces: f522acf17a | (Daniel Sockwell)++ (committed using GitHub Web editor) | papers/Raku_Code_of_Conduct.md Explicitly list newly created digital spaces This adds three newly created Raku digital spaces (dev.to, YouTube, & Mastodon) to the explicit list of covered spaces. This change is non-substantive: these spaces were already covered by the "any other digital spaces Raku may establish" clause. But it's good to be explicit. |
16:13 | ||
| Raku-Steering-Council/main: f522acf17a | (Daniel Sockwell)++ (committed using GitHub Web editor) | papers/Raku_Code_of_Conduct.md Explicitly list newly created digital spaces This adds three newly created Raku digital spaces (dev.to, YouTube, & Mastodon) to the explicit list of covered spaces. This change is non-substantive: these spaces were already covered by the "any other digital spaces Raku may establish" clause. But it's good to be explicit. |
16:16 | ||
| Raku-Steering-Council/main: d24ebfca36 | (Daniel Sockwell)++ (committed using GitHub Web editor) | papers/Raku_Code_of_Conduct.md Merge pull request #54 from Raku/Add-new-spaces Explicitly list newly created digital spaces |
|||
| japhb | codesections++ | 16:19 | |
| 26 Nov 2022 | |||
| vrurg | Trying to chose best option for creating YouTube account. One way is to request for a non-profit organization account. It requires EIN, physical address, online contact information. I wonder if it makes sense to go this way since EIN would only be taken from The Raku Foundation DBA and I expect it to be the same as for YAS. | 22:23 | |
| Hm, looks more like something for asked via email. | 22:25 | ||
| Am I the only one receiving mail delivery returns from gmail with "this message does not meet IPv6 sending guidelines regarding PTR" message? | 22:35 | ||
| japhb | Nah, that's been going for a while. Two of the RSC members are behind gmail, I think, and so they don't get emails from the mailing list. | 23:05 | |
| (Or at least, we see errors for it -- dunno if gmail forwards the message on anyway) | |||
| vrurg | 5xx are fatal codes in SMTP. No, they are not delivered. | 23:08 | |
| japhb | (I was speaking from memory. I didn't have one of the errors in front of me. :-) ) | 23:14 | |
| 27 Nov 2022 | |||
| lizmat | yeah. we're still figuring out what the issue is :-( | 11:54 | |
| as far as I know, all of the right knobs have been turned into the correct setting :-( | |||
| 28 Nov 2022 | |||
| Geth | Raku-Steering-Council/main: 0cd59d38ef | (Elizabeth Mattijsen)++ | minutes/20221126.md Minutes of 26 Nov 2022 |
13:55 | |
| Raku-Steering-Council/main: 62ffde3331 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | papers/README.md Add extensions |
14:40 | ||
| 30 Nov 2022 | |||
| Raku-Steering-Council/main: 9637c1b47d | (Daniel Sockwell)++ | papers/coc_incident_response_guide.md Add response option: ≤ 48hr ban by one CAT member This commit adds the points discussed at a previous RSC meeting: * CAT should share passwords needed to ban someone * CAT members should exchange phone #s * CAT can treat someone as abstaining if they don't respond in 48hrs * Any CAT member can issue a 48 hr ban without needing to discuss with the full group. |
21:55 | ||
| Raku-Steering-Council/main: 9ccb0d4554 | (Daniel Sockwell)++ (committed using GitHub Web editor) | papers/coc_incident_response_guide.md Merge pull request #51 from codesections-forks/Incident-Response Add response option: ≤ 48hr ban by one CAT member |
|||