[#radicle_biweekly] 27.3.20

[abbey]

Hello Community!

We’re trying to make it easier to contribute to the Radicle project! We’ve started tagging issues in our different repos. If you’re interested in getting involved in Radicle development check out this post for more details!

Radicle [Surf] Contributions

I’ve seen that there is some interest in contributing to radicle. radicle-surf is at a stable stage but still needs some love and additions. That’s why I’ve made an attempt to organise some work items for ourselves AND YOU to help polish this library into the shining beauty it deserves to be! There’s a ticket for that gathers some easy pickings: Survey surf · Issue #69 · radicle-dev/radicle-surf · GitHub But you can also view the tickets with the “help wanted” tag Issues · radicle-dev/radicle-…

And here’s our team updates:

@coco:

• CoCo has been iterating internally on discussions and code. A lot of this is work-in-progress and will likely lead to updates next week. Stay tuned!

  • To give an insight into what this is: code for managing [general] identities has been worked on by @mmassi , who plans to have code ready for review. @kim has provided radicle-link with some initial peer-gossip functionality. @fintohaps has merged the issue tracking model and is thinking about the [CRDT] operation-based semantics.

@application:

• We continued our work on the first big feature deliverable Identities I. Check the milestone for a comprehensive overview.

• The identity creation & handle registration flows have been merged, along with their integration with the @registry. Now, we’re working on visualizing transactions.

• Besides implementing new features, we’re discussing changes in the codebase that will make future developments easier to implement:

  • New navigation and storage handling https://github.com/radicle-dev/radicle-upstream/pull/232
  • Alternatives to GraphQL https://github.com/radicle-dev/radicle-upstream/issues/165

@registry:

• We have implemented block rewards! How it works: Miners will now add an inherent transaction to a block that sets the block author account. When a block is finalized the block author account receives some funds (#270). The block author also receives a share of the transaction fees with the rest just being burned (#276). The block author account is controlled with a CLI option (#272).

@product:

• We’re excited to welcome @brandonhaslegs to the Product team! He’ll be working on all things design alongside @Julien.

• We’ve started pushing more of our work to Discourse. Keep an eye on the product category for discussions on design & product development - like this post on colors

We hope everyone is staying healthy and safe during these troubling times

Best,
Abbey