[Discussion] Drips Org Proposal 2023

[ange]

Hi @lftherios and team - this proposal gets me excited for where Drips is headed this year. Thank you for putting this together.

A few questions and pieces of feedback:

@lftherios

problem of FOSS sustainability / funding public goods

Can you include another couple sentences defining this problem (since it’s been something we’ve talked about so much in the past)?

@lftherios

Continue to iterate on core experiences based on user feedback.

What are “core experiences”? Are these separate from or do they include “CDF” and “Awesome Lists”?

@lftherios

Q3&Q4 23

1. Continue to iterate on core experiences based on user feedback.
2. Integrate the Radicle code collaboration protocol, with the assumption that it has a stable release.
3. Conduct an additional audit.
4. Potentially deploy Drips v2 contracts on more relevant EVM networks (Optimism, Arbitrum, Polygon)

Because it’s harder to know at this point what the roadmap will be in Q3 and Q4 2023, can we expect an updated roadmap as we get closer to Q3 and Q4, to understand how funds will continue to be used? If yes, where could we find such a document? My assumption is that the roadmap will become clearer as you listen to users and define what product market fit would mean/require.

@lftherios

Metrics

Firstly, what will be done to engage more developers to build on the Drips protocols? I could imagine that implementations of the SDK is also a measure of success? Secondly, I know you plan on having a dashboard for hosting/tracking the metrics - but how would these metrics be contextualized to indicate success or how much closer you are the product market fit? In what format, what version of reporting, will the metrics be analyzed to answer this? How can the community access this additional context? I’m just thinking, numbers are great - but I’m not sure I know when a number crosses a threshold to signify “success” of a feature or product.

@lftherios

We are establishing a non-for-profit association in CH, where all core contributors can become members. Decision making is based on one member one vote.

I’m excited for you all to test out this structure and how it can be morphed over time to support the development of Drips and the needs of its team.

@lftherios

Reasoning & Analysis

I’m wondering if this section would be better suited to move up to follow the “Purpose” section.

@lftherios

Timeline & Budget

To @sllyllyd 's point, I agree that April should be removed from this budget. But I do agree with @lftherios that “Legal support fees” should be covered by the Foundation Org for 2023 - see the “Responsibilities - Org Support Services” under the “Operations” section [Temperature Check] Start the Foundation Org. Secondly, are we assuming all contributors being paid in fiat? Is that what the Skyline fees represent?