Upstream May 2022 Community Update

:tada: Key Achievements :tada:

What we worked on and achieved in the last month. These include some of the key decisions we’ve made about our product direction.

Release 0.3.1 (Patch Statuses)

Our focus last month was to improve our patches feature. One of the common problems we’ve seen from both users and ourselves was the inability to manually close open patches. The only way for a patch to be closed was to merge it. As you can imagine, there are a myriad of reasons why a patch may not be merged, leaving a lot of open patch clutter. With our 0.3.1 release, we’ve implemented the ability for project delegates and patch creators to manually close their patches!

More details on our 0.3.1 release here:

Initial User Feedback

We’ve begun to have multiple feedback and onboarding sessions with various DAOs. This has been a great opportunity for us to gather feedback, and help prioritize key issues that are affecting our ability to activate users and teams. Although this will be an ongoing process, we’ve already been able to identify a few blocking issues as users set up both the CLI and Upstream to start with code collaboration.

More details here:

Comment Discovery

We’ve successfully mapped out the user flow and needs for our patch commenting system. This work was required to understand how we expect users to interact with our patch commenting, and what user needs our solution needs to help solve. Along with patch comments, we believe the commenting primitives built for this system will allow us to implement comments wherever applicable, further delivering value to our users.

More details here:

:face_with_monocle: Our Focus

What we’re currently focusing on in the immediate and short term. Expect to see some of these conclude very soon!

Commenting (Carryover)

The next step to further improve the code collaboration experience is commenting. The first area that we’ll be implementing a commenting system is with patches. This will allow users to communicate with their team members within the context of the project that they’re collaborating on. Further, the commenting system built here will lay the groundwork for commenting on various features, including Issues.

More details here:

Issue Management Discovery

Teams currently still rely on external tools for things like project management and communication. We’ll be expanding our use of the commenting system (which we will have for Patches) as well as key issue management features so teams can progressively rely on Radicle for larger parts of their workflow. The goal for this next month is to determine the user flow and MVP needs for Issue Management.

More details here:

Market / User Research

To better understand what we need to prioritize to maximize value delivery to our users, we need to continue synthesizing the user feedback we’re gathering to ensure users can successfully utilize Radicle. Further, we need to look at the market as a whole to understand how to position our product(s). Our goal is to use this data to create a comprehensive product strategy for code collaboration.

More details here:

:crystal_ball: What’s Next

Core initiatives and features that we’ll be focusing on in the longer term. Just some of the exciting things we have in store!

Cross-Team Collaboration

This past month, we’ve identified a few core cross-team collaboration issues that we need to solve as an organization. Specifically, our lack of coordination across teams, along with our dependencies on each other, result in a disjointed code collaboration user experience. Analyzing and solving these issues will ultimately allow us to create a seamless product offering, giving us the ability to compete in the marketplace.

Core Task: Work with team leaders and create structures to ensure effective cross team collaboration.

More details here:

Ethereum Integration (carryover)

DAOs intrinsically are web3 native teams, and most utilize the Ethereum blockchain. Although we do have some features around this already, we’ve decided to remove them to focus on the MVP as they were problematic. Moving forward, we need to better identify and understand how users and teams want Radicle to integrate with the blockchain, and what aspects of Radicle should be integrated with on-chain data.

Core Task: Define user needs, problems and jobs to be done with the Ethereum integration. Identify technical implementation and design needs.

Competitive Landscape / Roadmap

This past month, we’ve defined the vision and high-level strategic priorities for Upstream. That said, additional work needs to be done to put together the roadmap for the product. The roadmap will be critical for prioritization once we establish a feedback pipeline. Further, diving deep into the competitor landscape will help us inform our priority features.

Core Task: Documentation created and shared via

1 Like