CCS Coordinator

changed the description

I think it goes without saying what an excellent job plowsof has been doing.

Without plowsof reaching a consensus on CCS ideas would be CHAOS to be honest!

I agree with this proposal

I must agree with Lovera

@plowof has been great at organizing CCS discussions and meetings, increasing communication in the commnuity, and generally keeping things running smoothly

While the CCS system isn't always perfect, plowsof does a remarkable job of keeping the community together. He is reliable, honest, impartial - a perfect fit for the role. Thank you for your service!

mentioned in commit 087b31e2

merged

After 8 meetings:

During this period:

The following proposals have went to funding and been graciously funded by the community: (some overfunded)

All of the issues being resolved in my last update, have been completed/repurposed, apart from the following:

Maintaining FlatPak package - BigMenPixel has been maintaining the GUI flatpak and has all but finished his own tasks for obtaining the verified status (with issues out of his control delaying it). If this can not be resolved then shortly then i would ask the community to discuss the next steps (possibly paying out for the maintenance instead)
BP++ peer review - the new scope / funds have been secured and CypherStacks review is now unerway. Jberman has now taken the reigns for putting together scope(s) for Seraphis audits / working closely with researchers from auditing firms. I continue to help where required such as keeping the communication lines open / providing updates to e.g. ZKSecurity especially during the CCS wallet incident.

Some highlights from https://bounties.monero.social/ include BCH-XMR Atomic swaps, Bitmessage rival/rewrite, background view-key based syncing, Nostr client for monero

Now, when you have volunteers who are banned from community channels like danbob getting me to increase my organisational skills by setting up (and secretly updating) focal boards / ofrnxmr taking the initiative for solving monero-meta issues (after midipoet brought the problem to the forefront) I definitely have to do better. In the short term i'll be:

chasing up the onion URL for the CCS and bringing the weblate server back online so translations can resume.
Discussion around the multisig signers will need to conclude before tobotht has finished his multisig UX improvements.
And with the departure of our monero-site maintainer, extra attention will be required there.

Thank you to those who support me (and the 1 whale who keeps me awake at night wondering when it'll all be over after i dissapoint them). I am replaceable, and the CCS lives on! Closing out M1 + M2.

After 4 meetings:

These proposals moved to funding and where graciously funded by the community!

Besides existing and generally trying to be helpful some things i wanted to note:

I need to use / update the focal board more often provided by Dan !
Maintaining FlatPak package - I will shortly ask the community to approve payout for the entire* proposal. Verified status on flathub / other options need to be discussed again in a follow-up maintenance proposal, as i feel consensus isnt so clear on the "verified" issue.
BulletProof++ Peer review - MRL/Community has recently approved an early 50% payout. CypherStack has found several issues in the original paper, offered fixes, and is working closely with the author to resolve them. Liaising with CS / discussing details of the scope for this proposal has been handed off to J-berman who is qualified for the role and is pushing other tasks forward (Seraphis related) but i am always available if emails have to be sent again.
Weblate / site - it seems the weblate server not being functional for over a year is coming to an end now. credits to pigeons our volunteer sysadmin and contributors who have been pushing this forward. All i have done is ask how its going. The CCS onion url is still on the sysadmins to-do list. I've put some pull requests / issues up for site but its been mostly a group effort, so again thanks for people raising these.
Been keeping things running as smoothly as can be with payouts/issues @ bounties.monero.social. thank you to the bounty hunters and the donors!

There was a complaint of sorts questioning my impartiality for this role in a github comment. in the full context of that issue i am definitely not impartial and siding with devs/researchers / pushing back on use-cases which can harm privacy / be abused. CCS proposers who interact with me can be the judge if they wish to escalate.

To be continued...?

Hash: SHA256

89cjBhX6sGujbCoKr8n71CasxXVKeCcLEUZvCxwQCCGB1svqeoQ9Pm9bVKPf14b1LuipfXkwqtV2BEE8kJAC1KK726CcFqk

=== monero info ===
[ height ] 3123422
[  time  ] Tue  9 Apr 08:50:35 UTC 2024
[  hash  ] c684df8a1fa75e3953b9e9a04a9bf53fda6ae6e9ee94ff5f347bafbf80e34d92
-----BEGIN PGP SIGNATURE-----

iI0EARMIADUWIQTci88MUIPyAweCgD5OipEtQO0FLAUCZhUBhRcccGxvd3NvZkBw
cm90b25tYWlsLmNvbQAKCRBOipEtQO0FLKjbAP91LV+8L/eShJZkXc4oLLHG6rAg
vwpxxAR14eF2IRq+dQD+KTLGkyF9pH0KnmB2+WqVv+az0f87yS4HFL6jmay5nhI=
=VCrO
-----END PGP SIGNATURE-----

mentioned in merge request !440 (merged)

mentioned in merge request !503 (merged)

mentioned in merge request !560 (merged)

CCS Coordinator

Who?

What?

Funding

Activity

CCS Coordinator

Who?

What?

Funding

Merge request reports

Activity