Dev Committee Q3 Reform Funding Proposal

Introduction

We believe the failing of the previous Dev Committee Funding proposals show the community’s desire for a reform of the committee. We agree with many of the criticisms that were brought up. We believe that the way forward is to reform the committee in order to continue the good work that the previous committee was doing and fix the bad. This is why the we wrote this proposal. This proposal aims to achieve the following:

  • Show the dev committee’s benefits to the community and clearly define its goals.
  • Clearly define the roles of each member in the committee and identify the work they would be doing.
  • Propose a reasonable budget reflecting the market conditions and the amount/type of work the members would be doing.
  • Show that the team members are capable of achieving the goals of the committee.

The Proposed Goals of the Dev Committee

As the dev committee, our goals would be the following:

  1. Provide new devs with opportunities to prove/improve themselves while getting compensated. (Previously the dev committee had been achieving this with CCRs and mentorship programs. Some notable devs onboarded this way include Srdtrk, Kent, and kromsten)
  2. Play an active role in the creation and maintaining of templates and other types of demonstrative code examples (including articles/documentation). The download data from https://crates.io/ shows that most secret contracts still use outdated versions of secret-toolkit that don’t have proper compatibility with many of the current standards. This is likely due to the fact that many code examples and templates are outdated. (In the past, Trivium node has produced templates pro-bono to help fix this. In particular, srdtrk has been producing up to date code examples, fixing issues in secret-toolkit, writing documentation pro-bono, and making presentations on the latest features. We believe that this has lead to a measurable increase in the downloads of the latest secret-toolkit-incubator)
  3. Update the community on recent updates to the tools used in development.
  4. Develop new dev tools for quality of life improvements.
  5. Provide specialized developers the opportunity to present their work to the other developers on the network.
  6. Encourage collaboration among developers. And help other committees to satisfy their dev needs.
  7. Provide limited front-end + smart contract support to devs in need.
  8. Help answering other dev’s technical questions.
  9. Represent our community of developers in crypto events.

The proposed dev committee would NOT be tackling the following:

  • Development of the core protocol.
  • Development of any specific dapp.
  • Validator support.
  • Testnet support.

Action Plan

In this section, we will describe exactly how our committee plans to realize the goals written above. This is some (but not all) of what the dev team would be compensated for. We will also talk about some of the previous achievements these programs made.

Mentorship Program & Community Code Repositories (CCRs)

CCRs are small bounties for simple development tasks. The dev committee often uses these to create/maintain demonstrative code examples and provide quality of life improvements. A list of the completed CCRs can be found here, we plan to move them if this proposal passes. Mentorship program is when a new developer (that has some knowledge of cosmwasm and/or frontend) on the network is assigned a mentor to accomplish a certain task. This task can often be something the student wants or a CCR, in which case they get compensated. The early compensation is often very rewarding and encourages the developers to stay in the network becoming long time creators. Kent, srdtrk, and kromsten have started out this way.

Weekly Dev Calls

This is supposed to be the time when:

  • New developers are introduced.
  • New/old CCRs and their proposals are discussed.
  • Tooling version changes are discussed.
  • Community members give updates on how their work is going.
  • Developers can be asked questions by the broader community.
  • Community feedback can be taken.
  • Specialized presentations are made.
  • New connections and collaborations among devs are made.

A well written summary of past meetings and the agenda of the next meeting must be provided. The planning and writing of weekly calls is one of the areas where we’re planning to improve on the previous committee.

Written Content and Presentations

The goal here is to have well written meeting notes/agendas. Also maintain up to date documents on where to find most up to date resources and code examples (i.e. when a new template/example shows up, Secret University and others should be made aware), this is why we have been working closely with the documentation overhaul project, and contributed to it extensively. We will also update the dev community on minor updates in secret-toolkit and secretjs.

We will also be actively seeking presenters with specialized knowledge that might be interesting to know for other people in the dev community. Srdtrk also likes to give presentations whenever possible.

Initiatives

Often times, dev committee members will start working on a small initiative to benefit the network without expecting further funding. For example Srdtrk likes improving secret-toolkit. These will often be small CCR level initiatives. This is certainly the case for the current proposed dev team. We will list some of our individual contributions in the next section.

Miscellaneous

  • Represent SN in Crypto events. (We are all inherently enthusiastic about SN)
  • Create “leads” with companies/crypto projects based on technical capabilities of SN.
  • Code peer review systems. And connections with auditing firms. (started by Lumi)
  • Transparency tools for the dev committee and other committees to use. (started by the previous dev committee)

The Team

  • Lumi is a member of the previous dev committee. He has worked in the development of blackbox & cloak, and many NFT projects. He is most famously the author of secret-random-minting-snip721-impl, which was the template many NFT project used to do random minting before Stashh. Some of his past initiatives are:

    • Public endpoints provided by Trivium.
    • Publishing public templates used by many. You can find one of the more recent ones here.
    • Helping & reviewing community code.

    His proposed roles in this dev committee are the following. The times below are an estimation:

    1. Dev call & leads call (2 hr/week)
    2. Community asks (1 hr/week)
    3. Assess CCRs, and assess candidate mentees (1 hrs/week)
    4. Dev support (1 hr/week)
  • Xiphiar has been an active developer for a long time, and he is a member of the previous dev committee. Many of the tools people use to view their liquidity and transaction history are built by him. He has also developed frontends for many NFT projects, and maintains Trivium’s public API node cluster. His proposed roles in this dev committee are the following:

    1. Dev call & leads call (2 hr/week)
    2. Dev support in mostly js related issues (1.5 hr/week)
    3. Assess front-end related CCRs, and assess front-end related candidate mentees (1.5 hrs/week)
  • Srdtrk. His background is in research in pure mathematics, running simulations in python, matlab and etc. Became interested in cosmwasm about 1 year ago and transitioned to secret network with the help of the mentorship program. The developer of Cover. In the past 2 months, Worked on the following initiatives:

    • Write the documentation on secret network storage.
    • Regularly update CCRs to make sure they are using the most up to date code/storage patterns.
    • Produce the first template using Cashmaps. Meant to replace other factory contract templates.
    • Give a talk in the dev call about cashmaps
    • Contribute to secret-toolkit, one of which produced a minor subpackage release.
    • Review community code.

    His proposed roles are the following:

    1. Dev call & leads call (2 hrs/week)
    2. Produce most of the written content for the committee (meeting summaries, articles, meeting agendas, etc.). Written content will be an important part of the new committee. This also includes planning the dev calls. (2 hrs/week)
    3. Keeping track of latest tooling updates, and initiatives (1 hrs/week). Srdtrk likes improving storage features and giving presentations.

Funding

The leads will be asking for $85/hr.

  • Lumi: 5 hrs/week @$85/hr
  • Xiphiar: 5 hrs/week @$85/hr
  • Srdtrk: 5 hrs/week @$85/hr

Total lead ask: $15,300.

The mentorship program will continue as before at 2hr/week x5 mentors at $85/hr. (Any budget left over will be carried to the next funding period)

Total Mentorship program ask: $10,200.

The CCRs will continue. We expect 7 CCRs based on the previous funding periods, the max reward for CCRs will be set at $2500. (Any budget left over will be carried to the next funding period).

Total CCR ask: $17,500.

For a total ask of $43,000

2 Likes

Note: This proposal has nothing to do with why the Bizdev collab is not happening

hey, did you guys intend to change the hours for attending the leads call to doing other stuff like mentoring devs or is the hours breakdown the same as before?

1 Like

hours and cost seem reasonable at this time.

The total number of hs and rates seem fine to me. It’s making a bit of noise for me that 40% of the paid hours will be spent on calls… I think the distribution should be revisited to make better use of the teams dev skills

2 Likes

Would like the answer to the same question as @ertemann and @votor133t is asking. I remember listening on gov talk that these will be adjusted

Hi! Sorry for the late reply. Yep, we’ll all be adding some extra hours to make up for the meeting time. It will be spent on tooling and developer assistance.

2 Likes