# Q2 Team Call

14.06.2023

## Agenda

### Progress

* Patches & Issues
* Issues not used much
* A little annoying to comment
* "Logged in" experience
* Lower friction in starting up httpd/node + authenticating
* Lack of ability to attach screenshots to issues
* Patches going good
* Web UI "authenticated" state
* Mostly working
* Notifications missing
* Error handling missing
* TUI (issue browsing)
* Tree-like widget
* Prototype stage
* Network
* More robust
* Fetch V2
* In-process
* Gitoxide? (https://github.com/Byron/gitoxide)
* Inspiration from link-replication
* Rollout?
* More than one node?
* "Where do I push my code?"
* Wireguard network overlay?
* Each person is behind a NAT, can't directly serve repos
* Solved by hole-punching
* Doesn't necessarily provide static addresses for users
* Solved by wireguard
* Gives user static address that they can share
* IPv6
* Derive network addr from public key
* Centralization issue: wireguard router
* Tor
* Code review
* CI/CD
* Web
* Router/pre-loading
* Architectural change to make code more readable
* UX aspect: loading bar
* Still some pages that work with the "old" spinner
* Patches
* Patch creation?
* Reviewing?
* Merging requires CLI
* How to connect workflows?
* Docs
* Prompt?
* Syntax highlighting in diffs
* Was using textmate grammars
* Move to treesitter?
* Down the rabbit hole
* Performance
* Expensive to materialize all COBs
* Have to materialize to know if patch is open or closed
* Mostly down to crypto verification
* Initial thought: trust what's local, don't re-verify
* Make write expensive, but read cheap
* Middleware doesn't work out well with axum
* Caddy caching requires external plugins
* Eventually settled on per-handler cache on slow routes
* /projects
* /projects/:rid/tree
* /projects/:rid/patches
* Reduced latency quite a bit: 200ms -> 10ms
* Reviewing radicle-interface code to optimize requests
* Eventually proper SQL layer on top of Git
* TUI
* Design wireframing session
* Work on patch view / code review
* Widgets are work in progress
* CLI
* Move to git-push for patch open/update
* Community
* Help potential users/contributors as much as possible
* Create welcoming vibe
* Social
* Twitter updates ~1/week
* Blog?
* Mastodon?
* Nostr?

### Priorities

* Start using radicle issues
* Build milestones feature?
* +1 from IDE plugins
* Move code review off of Zulip
* CLI: `rad review -p`
* In-progress
* Semi-blocked on git-range-diff support
* Useful for revision-to-revision diffs
* Currently not useful after rebases
* Progress
* Focus on implementing git-range-diff as is
* Concern is in API design / integrating with codebase
* Putting a prototype up that can be integrated with codebase
* Latest EOW
* TUI?
* In the works on the TUI
* At least display stuff
* Diffs
* Conversations
* Web?
* At least view code reviews
* Viewing inline comments
* Viewing review verdicts
* See in side-bar who accepted/rejected a revision/patch
* Syntax highlighting for diffs
* Etc.
* Move CI/CD off of GitHub
* New CI team
* User onboarding
* Docs
* Hand-holding
* Zulip
* DevRel?
* Glossary?
* In the past, we've had people join too early
* Hiring
* Image embedding so that interface can dogfood

### Growing users

* How ready are we?
* How comfortable would we be as a team, to promote Radicle to the big guys?
* To Debian?
* Etc.
* How stable are the protocols?
* Versioning?
* We're doing much better than 6 months ago
* Dogfooding
* Requests from IDE team are fulfilled with 1-2 days
* Get 2-3 more teams using Radicle
* Drips?
* IDE plugins
* radicle-interface
* Intermediate step
* Talk to friends
* Regular internal feedback on product, by team

### Conferences

* CCC
* EthCC
* July
* Radicle talk at satellite event
* Autonomous Ecologies (https://autonomousecologies.xyz/)
* ProtocolBerg
* Sept 15th, 2023

* https://socrates-crete.org/
* https://jcrete.org/