-
Notifications
You must be signed in to change notification settings - Fork 69
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 22nd June 15:00UTC #1027
Comments
Remember to take Monero Standard off the list of newsletters. |
When log? Do better! |
Recanmann has fixed the monerologs repo. Soon(tm) another instance will be online |
Logs
Automated by this |
original monerologs is back. i have an irc bouncer with messages in an sqlite database that can also be called upon in a pinch. |
@plowsof what channels is your bouncer part of? Just curious. |
every channel "plowsof" is in |
Damn, all our dirty secrets are getting logged by plowsof! |
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 - Monero Moon
j-berman 125.3/escapethe3ra 16/selsta 53/ plowsof 53.38 /anhdres 30 or 41/hinto 52.8/v1do 17.4/jeffro256 57/boog900 162/vthor 5.38a. Seraphis General Paper Review
b. New Monero Website
c. How to mine Monero guide
d. I2P SAMv3
e. ofrnxmr feat. BasicSwapDEX - take over the world pt 2
f. Monero Poker Infrastructure Project
g. Mobazha with Monero in Privacy Ecommerce
h. Development of New CCS Proposal Platform
i. Revuo Monero maintenance (2024 Q3)
j. Jeffro256 Full-time 2024 Q3
a. Dev workgroup
b. Localization workgroup
c. Outreach workgroup
d. Events workgroup - MoneroKon 2024
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: