On Oct 12, my funding from the previous campaign will expire.
This is a request for an extension in order for me to continue to be able to support Grin with the type of contributions I’ve been doing over the past six months.
As part of this request, I’m proposing:
- The rate to be increased to a 1/4th of a Yeastunit, or $2,500/month. This, as the workload has been greater than originally anticipated.
- The time period to be reduced from 6 months to 3 months. This, to make the review check points more frequent in order to evaluate whether it makes sense for this to continue.
I’m adding this request to the agenda for Tuesday’s Governance meeting.
The original motivation still holds true today:
Beyond work on the main grin (node/wallet/miner) repositories, work on the admin side of the project has evolved over the past year. The /grin-pm repo is now a place where we track general project management issues, meeting notes, event presentations, financial data, and more.
I think this work adds value and is important for the project’s health, for it’s good governance, and for progress to be made faster.
Grin would get reliable and consistent support for the non-development related tasks, that would help achieve its potential quicker.
With Igno’s departure the need for good governance and a push for decentralization of work and decision making has become even more important. Ultimately the goal is to have several independent sub-teams with their own processes and governance, but we’re not quite there yet. The bootstrapping process takes time and effort, and benefits from having people dedicated to laying the groundwork for it.
Evaluation of previous period
My own assessment
- I believe the weekly progress update thread covers my detailed contributions well.
Some of the past period’s efforts worth calling out in particular:
- Two quarterly transparency reports published (3rd report due in October).
- /grin-security repo created, putting everything security related under one roof, under the stewardship of @j01tz.
- Thorough rewrite and update of the dandelion documentation, inspiring some ideas for further improvement of the implementation (still tbc).
- Exploring more structured forms of release planning, with v2.1.0 being an example.
- Been taking an active role as focal point for donor and ecosystem relations.
What went well?
- All the scope as outlined in the original funding request was carried out as intended.
- There’s been consistency in quality and delivery - meeting notes, newsletters, etc have all been delivered in a timely manner, only missing an issue when I took a brief break for the birth of my son.
- Adapting to Igno’s absence and helping the project move forward despite this. I feel we are in better shape than ever to respond to disruptions.
What could have been improved?
- Planning process for v1.1.0 and the v2.0.0 hard fork could have been much better. It was in the middle of Igno disappearing, but nevertheless. Our approach to slate versioning was a mistake, and we should have handled it better.
- The findings from the security audit have still not been published. On the bright side, @j01tz is now lead on this, and is doing a great job: All issues have been resolved, and a publication is now being co-ordinated. But it still feels like something I could have done more to progress.
- Some of the discussions in the community have recently been filled with contention, perhaps most recently around transaction building. In hindsight, I could have been less contentious, and better focused on the bigger picture.
- Turnaround time of meeting notes could be improved.
What have I learned?
- It’s a marathon, not a sprint. Keep a long term view.
- Manage time more efficiently, set tighter limits and avoid spending too much time each week on things that will not make a difference in the longer term.
- There’s no point for me to get consumed by too much of the technical details early on. I should focus more on achieving actionable outcomes, and spend less time debating.
- Community building does not happen over night, and cannot be forced. Patience.
Feel free to raise feedback and/or suggestions in the thread below, or in private, my DMs are open.
Specific tasks in-scope
Same as last:
- Meeting related admin
- Financials / book keeping
- Keep grin-pm/financials/ up do date: income / spending / misc_support logs
- Publish quarterly transparency reports
- News reporting
- Media relations
- Focal point for media enquiries
- Weekly status report to keep track of progress.
In addition, also:
- Manage the newly created /grin-rfcs and /grin-security repos and the related processes.
- Focal point for corporate donors and ecosystem requests.
- 3 months.
- Ring-fenced around admin tasks
The intention is to raise this as a discussion point in the next Governance meeting and ask for the request to be approved.
Edit Oct 3: Clarification in lessons learned.