| 2 May 2024 |
 joepie91 🏳️🌈 | people generally do not read pinned things, is the proble | 17:44:49 |
| joepie91 🏳️🌈 | * people generally do not read pinned things, is the problem | 17:44:50 |
 edef | so some flavour of "i solemnly swear i have read and will abide by these rules" seems important | 17:44:53 |
| joepie91 🏳️🌈 | they need to actually be addressed to people | 17:44:59 |
| joepie91 🏳️🌈 | they need to clearly and unambiguously register as "this is meant for you, not other people" in some manner | 17:45:24 |
| edef | and i think it's too subtle to tell whether people have or have not read + it's annoying to go "read pinned" | 17:45:33 |
| joepie91 🏳️🌈 | the exact manner does not matter as long as that is satisfied | 17:45:38 |
 infinisil | Who can give me an estimate on how long this takes to implement? And who actually has the time and experience to implement this? | 17:46:43 |
| edef | okay, i think i can make a clickthrough fairly fast, few hours tops | 17:47:14 |
| edef | https://zulip.com/api/send-invites | 17:47:28 |
| edef | i can throw together a lil flask app real fast, basically | 17:47:53 |
| joepie91 🏳️🌈 | infinisil: if "sending an e-mail to users is acceptable" then plan B is "create a shared e-mail account for all mods and contact people from there", which is jank but is guaranteed to be completable in a short timeframe (if the clickthrough does not work out) | 17:48:06 |
| joepie91 🏳️🌈 | * infinisil: if "sending an e-mail to users manually" is acceptable then plan B is "create a shared e-mail account for all mods and contact people from there", which is jank but is guaranteed to be completable in a short timeframe (if the clickthrough does not work out) | 17:48:15 |
| infinisil | We can't send invite links | 17:48:43 |
| joepie91 🏳️🌈 | the clickthrough is a bit nicer in that it requires less mod work | 17:48:44 |
| joepie91 🏳️🌈 | we don't need to, we just need to get acknowledgment and then mark e-mails as 'handled' | 17:49:03 |
| edef | API invites seem practical and Python lib is easy to use, will have a prototype in ~15m | 17:49:14 |
| edef | API invites send emails | 17:49:17 |
| infinisil | edef: Neat! Can you briefly describe the process you're imagining a https://pad.lassul.us/? | 17:49:50 |
 lovesegfault | Are y'all figuring out how to invite everyone who comments on the issue? | 17:51:48 |
| edef | yes, along with ensuring they have read the rules of engagement | 17:52:04 |
| lovesegfault | How are the contributions validated? Are we going to check it manually? | 17:52:23 |
| edef | i believe so | 17:52:42 |
| lovesegfault | Also, is one merged PR enough? Or is there a stricter requirement to participate | 17:52:45 |
| lovesegfault | (Might help reduce spam) | 17:52:51 |
| infinisil | Manually, one PR is enough yes :) | 17:52:54 |
| edef | what has been ratified is 1 PR from yesterday at the earliest | 17:53:06 |
| edef | i have my feelings about this particular choice, but will abide by what is ratified | 17:53:20 |
| lovesegfault | 1 PR requirement feels like a mistake to me | 17:53:32 |
| lovesegfault | Alas, if it's been decided, then what's done is done | 17:53:52 |
