Our first bi-weekly update of the new year is a more of a monthly update We took some time at our last Team Week in January to discuss and set an intention to open up our communication strategy (Check out Revisiting our communication strategy & style 🦑 for more on this)
As a result, these updates will be a collection of highlights from our team bi-weekly meetings that capture announcements, releases, and highlights of development to provide you with a comprehensive overview of what we’re working on. These updates will be listed under their associated project team (we have four dev teams: Coco, Product, Registry, and Application).
- We’re having a lot of [hard] conversations about identities and code collaboration tools in these topics:
We started this cycle with some spring cleaning before tackling new features. We focused on making file structure and naming more consistent and fleshed out documentation.
- Define file structure · Issue #117 · radicle-dev/radicle-upstream · GitHub
- Unify design system, css and markup · Issue #115 · radicle-dev/radicle-upstream · GitHub
One of our main goals was to make it easier for other teams and outside contributors to collaborate on the Upstream codebase. The best entry point to start contributing is
In the proxy which powers the UIs data sources we improved separation of concerns, isolated domain logic from incidental API implementation. All of this was to maintain velocity down the road and provide a safe landing pad for protocol teams to make upstream (badumdish) contributions to reflect and put protocol changes to test swiftly. Improve separation of concerns in proxy · Issue #125 · radicle-dev/radicle-upstream · GitHub
We also started the work to a more controlled test environment where the high-level integration tests can more easily drive the state and setup needed for them to be able to assert correctly. Ideally paving the way to model more complex network constillations. Integration test strategy · Issue #133 · radicle-dev/radicle-upstream · GitHub
Orgsfeature is completed and integrated in the upstream
- Switched from PoA to a dummy PoW consensus PoW consensus by CodeSandwich · Pull Request #223 · radicle-dev/radicle-registry · GitHub
- We’re researching transaction fees and different proof-of-work & difficulty adjustment algorithms.
- We’ll be writing more about the Registry soon - stay tuned!
That’s it for now!
the radicle team