| 2 May 2024 |
 edef | In reply to @raitobezarius:matrix.org
I am sure this is a 5 line fix * yes, but we cannot get it written, tested, and deployed in the timespan we have, and we are not self-hosting aiui | 17:06:21 |
 @hexa:lossy.network | 
Download image.png | 17:06:26 |
| @hexa:lossy.network | basically, edit the organization description | 17:06:40 |
| @hexa:lossy.network | supports markdown | 17:06:43 |
| edef | does this show for signup by invitation? | 17:06:59 |
| edef | and maybe emphasise that you really need to have read it | 17:07:17 |
| edef | i'd almost put a small canary in to get speaking privs | 17:07:30 |
| edef | but, going to bias for less new complexity, more speed i think | 17:07:48 |
 infinisil | edef: Oh you're not invited yet, let's try it out, sending.. | 17:07:49 |
| edef | * but going to bias towards less new complexity, more speed i think | 17:07:59 |
 raitobezarius | In reply to @edef1c:matrix.org
yes, but we cannot get it written, tested, and deployed in the timespan we have, and we are not self-hosting aiui (i want to say: is this a challenge) | 17:08:11 |
| raitobezarius | but let's roll out, yes! | 17:08:16 |
| edef | In reply to @raitobezarius:matrix.org
(i want to say: is this a challenge) if you want it to be :p | 17:08:25 |
| raitobezarius | i will do a data export to test things | 17:08:33 |
| infinisil | Sent, let us know how it looks edef | 17:08:40 |
| @hexa:lossy.network | feel free to suggest a more to the point description | 17:09:12 |
| edef | my mail is not as fast as it promises, so gimme a sec | 17:09:14 |
 ronef | Side comment/ask - To be super transparent, I'm having a hard time tracking the stream of messages here. So if there's a critical item or proposal lets find a way to surface it in a more async method. | 17:09:25 |
| @hexa:lossy.network | if they don't show the org description for invites I'll consider this a bug | 17:09:26 |
| @hexa:lossy.network | because they tell you to reference the coc there | 17:09:31 |
| edef | In reply to @ronef:matrix.org
Side comment/ask - To be super transparent, I'm having a hard time tracking the stream of messages here. So if there's a critical item or proposal lets find a way to surface it in a more async method. we're focusing on "fast" so we can transition to Zulip, where this will be easier | 17:09:46 |
| infinisil | ronef: I like the async workflow of sending a PR to the foundation repo when something needs to be decided | 17:10:08 |
| edef | it tries to subscribe me to the Zulip newsletter by default, egh | 17:10:37 |
 joepie91 🏳️🌈 | In reply to @edef1c:matrix.org
and maybe emphasise that you really need to have read it I would strongly suggest using a wording like "Read these carefully; they are different from what you are used to" | 17:10:43 |
| joepie91 🏳️🌈 | In reply to @edef1c:matrix.org
and maybe emphasise that you really need to have read it * I would strongly suggest using a wording like "Read these carefully; they are different from what you are used to" directly in the signup flow | 17:10:57 |
| edef | i get punted straight to the welcome bot | 17:11:02 |
| raitobezarius | does someone want a copy of the export tarball? | 17:11:18 |
| edef | is the welcome bot programmable at all? | 17:11:19 |
| raitobezarius | to take a look and reassure themselves | 17:11:23 |
| raitobezarius | In reply to @edef1c:matrix.org
is the welcome bot programmable at all? not yet, there's an issue on that | 17:11:31 |
