# Maintenance Proposal: go-ssb (@decentral1se)

23 November 2022 (drafted)
24 November 2022 (approved)

## Status

:heart: Supported by several SSBC members and approved by @mix :heart:

### Proposed Work

- Issue triage
- PR review
- Bug fixes
- Test coverage
- CI improvements
- Binary build automation

Work would spillover into related repos (ie. margaret, muxrpc etc.) when required, but the focus is very-much on go-ssb.

### Source of Funds

[Scuttlebutt Maintenance Fund](https://opencollective.com/scuttlebutt-maintenance)

### Hourly Rate

Work to be invoiced at $50 NZD.

### Scope of Work

Initial proposal is 40 hours of work spanning approximately one month ($2000 NZD).

### Starting

Soonish. There will be downtime in December.

-----

## Call Notes

(rough notes...

time boxing is useful

maintenance fund open to new folks, informal processes so far

some clients brewing on d1 / trav side
some existing go-ssb "maintenance" work has supported hermes/golgi/kuska/etc.
is there an overlap?

what is "appropriate maintenance"?

tasks that are engaging are important to keep going on it

**maybe easy to do:**
- (done) backporting the memory fixes from planetary (good example)
- reverse flag for tangles.thread, seems "nice to have but not deal breaker"

**maybe hard** / needs cryptix + is still fix territory, could be dragons
- fixing ebt replication (how broken is it!? we don't know, we're not planetary)
- fixing the test suite, 20 skipped tests, 1-5/10 timeout / flaky tests
- outgoing connection handler

time to co-brain with cryptix
sync call, we could probably fund this
turbo-charge progress that could be made, beans spill

**possibility for co-funding**:
- outside of maintenance fund might be possible: peachcloud, maintenance, ssbc (3-way split)
- peachcloud oc could help fund relevant fixes (ie. ebt)

sunrise-choir gave remaining OC funding to peachcloud to support ssb rust development

EOF)