-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monero Community Workgroup Meeting: Saturday 11th November 2023 @ 15:00 UTC #920
Comments
Any suggestion containing the word "multisig" is purely hypothetical/fantasy until it is proven to be "known secure". Following that, drastic UX improvements are needed. |
a summary was created by monero.observer Logs
Automated by this |
Can we close this issue and open up the next meeting issue please. Thanks. |
Location: Libera.chat, #monero-community | Matrix
Instructions for joining the monero.social Matrix server.
Time
15:00 UTC Check your timezone
Moderator: plowsof
Please reach out in advance of the meeting if you would like to propose an agenda item.
Proposed Meeting Items:
News: Monero Observer - Revuo Monero - The Monero Standard - Monero Moon
a. Add retroactive funding proposal for FCMPs
b. dangerousfreedom - wallet work
c. Core Monero Concepts
d. escapethe3RA Monero Observer maintenance (2023 Q4)
e. Form Nonprofit Assocation for MoneroKon
f. erc: ccs for getmonero and weblate
g. Monero Selfhosted View-only Web Wallet (with received transaction Telegram/Email/SMS/Discord/Webhook alerts)
h. CCS Coordinator
i. v1docq47 - monerotopia 2023 (part 2) and monerokon 2023 voiceovers and working on xmr.ru
j. jeffro256 full-time dev 2023Q4
k. hinto-janai - full-time work on Cuprate (3 months)
l. selsta part-time monero development (3 months)
a. Dev workgroup
b. Localization workgroup
c. Outreach workgroup
d. Events workgroup - MoneroKon 2023
e. Website workgroup
f. Policy workgroup
g. Research workgroup
h. Seraphis Migration workgroup
Previous meeting including logs
Meeting logs will be posted here afterwards.
The text was updated successfully, but these errors were encountered: