[DISCUSSION] [RGP - 23] - Start the Radicle Integrations & Tooling Org - 2024

[yorgos]

Thanks for the feedback and additional thoughts here folks!

@fintohaps

I would say that a higher budget is worth keeping these good developers working alongside us, and also encouraging them to work on some heavier lifting within the heartwood code base itself too.

Thanks for the kind words! I do want to say in return - and for the record - that we are very appreciative of the support and encouragement we’re getting from the core team members ! Happy to get more involved, as required!

@fintohaps

I played around with the numbers in a spreadsheet here – you can edit the Total Budget value to see expected compensation outcomes. Perhaps 524,250, is rather high but it seems like 250,000 is quite low, imo. 350,000 seems like a more fair number. I think it’s important to note that this budget is only for 3 quarters as well, unless I’ve miscalculated

It seems to me that playing around with the numbers in this spreadsheet only helps show how much less each individual contributor would be making with this reduced budget. I don’t see how this helps us decide on the overall budget to spend, which is the real point of discussion here. If there are concerns that our team’s contributors are highly paid, I’d expect a comparison of average rates across orgs to help highlight whether that is the case or not.

@cloudhead

In time, I think it’ll make sense to invest more in integrations (as well as web, protocol etc.), but right now, accepting this proposal would feel off-balance.

I think this is the main point of disagreement here. We believe the additional budget would make sense now, whereas you see it further in the future. I don’t think we disagree on the value of the work, it’s more a matter of timing.

So, even though we clearly see things differently here, and after our offline discussions and negotiations since yesterday, we will “disagree and commit” [1], requesting a reduced budget of 350K USDC in total.

For posterity, I will state here our reasons of disagreement, more as food for thought for the evaluation of future proposals:

• I don’t think “10% of the core team” is enough investment. We see integrations as a core value proposition of a code collaboration platform and I think we should be investing more (to be clear: regardless of whether that investment ends up in our own team or not).

• We did not structure our budget as a % of the core team (and after the RSN proposal it didn’t seem necessary to do so) - we structured it up from the existing contributors, trying to convert some of them to full-time engagement. With the new budget, we will all keep contributing in a part-time fashion.

• Even if Radicle 1.0 is not fully launched yet, we are already seeing validation from early potential users about the value of this tooling. Just some examples:

  • CI Integrations:

    • being mentioned in the hackernews post - I wonder how discoverable (for normal people) these repositories are. It looks l... | Hacker News
    • requested in 3/9 Radicle Org User Interviews ran by @dnlklmn: julien, spencer, daniel
    • asked about in zulip, a lot(!!)

  • Planning Boards:

    • being mentioned in the hackernews post as one of the important features in GitHub - It is if you don't care about any of the other things that Git brings to the tab... | Hacker News
    • came up in 1/9 Radicle Org User Interviews ran by @dnlklmn: daniel
    • Original request for this feature in zulip, from internal team members

  • IDE Plugins:

    • already used by radicle org team devs,
    • appreciation for VS Code extension - Can’t scroll the page · Issue #1 · maninak/maninak.github.io · GitHub
    • requested in 1/9 Radicle Org User Interviews ran by @dnlklmn: spencer

Finally, one of the hottest leads that is now preparing to run a public Radicle node for their Open Source Software (OSS) projects (Dogecoin Foundation), after being prodded by @bordumb , requested CI Integrations and VS Code support [see tweet].

---

With that said, and despite our disagreement on the overall amount, we remain committed to Radicle’s success and want to continue contributing towards that. I will proceed to edit the formal review post and adjust the requested amounts to the reduced budget, hoping that this will be enough to reach quorum and get this proposal passed in the current voting cycle.

@shelb_ee I’d appreciate your help and guidance on any additional actions that may be required from our side with regards to moving this proposal forward.

Thank you all again for your time and support!