JBP-110 - Add JohnnyD to the reserved list

Contributors with significant responsibilities within Juicebox DAO are encouraged to create a reserved JBX allocation proposal.

Author:

@johnnyD

Proposal date:

February 9, 2022

Summary:

I propose to be added to the reserved rate and receive the same share as the 11 entities currently on the list, bringing each entity’s reserved allocation to 2.08% (25/12).

Risks:

As with any long-term contributor commitment, the risk is in the contributor reneging on their responsibilities and failing to maintain a high work output.

Proposed reserved JBX allocation:

An equal share of the 25% reserved for individual entities, so 2.08%.

How have you contributed to the DAO?

My list of 52 merged PR’s can be found here. I have designed and implemented various features to JB’s frontend and been quick to fix many bugs (see PR’s labeled ‘[BUG]’).

Recent:

• Implement Trending projects sections on homepage. Redesign /#/projects page to include ‘Trending’, ‘Holdings’ and ‘All’ tabs, and added a new filter. https://github.com/jbx-protocol/juice-interface/pull/455
• Design and implement a new ‘Review and Deploy’ modal after project creation https://github.com/jbx-protocol/juice-interface/pull/465
• Improve ‘Burn token’ flow for when project overflow is 0 (e.g. Assange) https://github.com/jbx-protocol/juice-interface/pull/464

Translations:

• I set up and implemented Crowdin to Juicebox, which has massively increased the efficiency in adding translations to the JB site - 5 languages added already with many more on the way.
• Designed and implemented the language selector (‣).

Older UI changes:

• Redesigned and implemented a new top nav for desktop (‣) and mobile (‣).
• Add validations to all JB’s forms Optimize the app's use of reactive forms/
• Added $ value input on distribution forms (https://github.com/jbx-protocol/juice-interface/pull/313).
• Added ‘funding target after JB fee’ input on project creation and reconfig (‣).
• Design and implement a ‘Copy to Clipboard’ icon for ETH addresses (‣)
• Implement button to link feedback form (https://github.com/jbx-protocol/juice-interface/pull/370)
• Can check out the rest of my smaller features and bug fixes in my list of merged PR’s.

How do you want to contribute to the DAO going forward**?**

In the short/medium term:

• Continue to design and implement new features.
• Continue to remain on standby for any bugs that need quick fixing.
• I will play a key role in implementing new interfaces for V2 contracts.
• Continue to participate fully in JB governance.

Long term:

• Implement a Juicebox SDK library.
• Implement custom interfaces for Juicebox projects.

What do you need from the community to accomplish these goals?

Continued amazing work and support from the Peel and Juicebox contributor team. Clear communication and critiques around new features and bugs from the Juicebox community.

What does success look like for someone taking on your role?

Facilitating a continually improving Juicebox user experience.

Under what criteria should the community reassess this allocation?

If I renege on my commitments, fail to maintain a high work output.

Thank you for taking the time to read my proposal 🙌

Sponsors:

Community members who agree to act as spokespeople for this proposal can add themselves here.

---

Note: reserved JBX allocation recipients are required to participate in votes for future reserved JBX allocations. For allocations to non-EOAs, attach an address that will manage voting on the non-EOA address's behalf.

IPFS https://gateway.pinata.cloud/ipfs/Qmd3UcxSyPPqzt4criHhk8SygWKuihDz3Urr49SQxM6KSW

Discord Discussion https://discord.com/channels/775859454780244028/873248745771372584/940804643007651841

Notion Proposal https://www.notion.so/juicebox/685ef9dbbfc04a67b119cc34c29fb4e9?v=660427d3d346451e8def4ff6d6c6ada2&p=f70bd282815945278cc09d31fe49df4f