After a trial period of 1-3 cycles, contributors are encouraged to propose a recurring role for themselves. Recurring payouts should be renewed/updated every 90 days.
Author:
Proposal date:
2022-01-09
Summary:
I propose that I become a front-end engineer for Juicebox and receive a recurring payment of 2900USD in ETH per FC. If this proposal passes I’ll be quitting my Web2 job and working on Juicebox full time.
Risks:
- I stop making consistent contributions to Juicebox’s front-end. If this occurs my payout should be reduced or removed.
Payout recipient:
johnnyd.eth
Payout amount:
2900USD in ETH per FC
How have you contributed to the DAO?
I have made various improvements to Juicebox’s front-end, mostly in the areas of forms and translations.
Form optimization:
- Scoped out bugs (mostly with failing validations) and other style optimizations for all Juicebox’s forms, fixed them all and they have all been merged (Untitled).
- Added an input in individual payout forms for a ‘$ (or ETH) value of the payout’ which links to the already existing ‘percentage of the funding target’ slider (https://github.com/jbx-protocol/juice-interface/pull/313).
- Added an input on funding forms for ‘funding target after fee’ which links to the already existing ‘funding target’ field (https://github.com/jbx-protocol/juice-interface/pull/313).
Translations:
- Mark the whole codebase for translations (https://github.com/jbx-protocol/juice-interface/pull/308, https://github.com/jbx-protocol/juice-interface/pull/359)
- Implemented a translation tool called Crowdin (used by Uniswap, Gitlab and other big projects) to improve the efficiency of translating the JB site. I set up Github actions to automatically upload and download translations to and from Crowdin (https://github.com/jbx-protocol/juice-interface/pull/329), setup the Juicebox project in the Crowdin interface and created instructions on Notion for translators and managers in using the new system. Crowdin has already seen massive amounts of new translations added to the site.
- Designed and implemented a language selector as seen in the top nav and footer (https://github.com/jbx-protocol/juice-interface/pull/309).
- Configured site for Turkish and Russian languages (https://github.com/jbx-protocol/juice-interface/pull/348)
Other UI changes:
- Redesigned and implemented a new top nav for desktop (https://github.com/jbx-protocol/juice-interface/pull/317) and mobile (https://github.com/jbx-protocol/juice-interface/pull/340).
- Design and implement a ‘Copy to Clipboard’ icon for ETH addresses (https://github.com/jbx-protocol/juice-interface/pull/346)
- Implement a ‘Share to Twitter’ modal when user donates to a project (https://github.com/jbx-protocol/juice-interface/pull/345)
- Implement button to link to @Zhou Jason’s new feedback form (https://github.com/jbx-protocol/juice-interface/pull/370)
- Small bug fixes: https://github.com/jbx-protocol/juice-interface/pull/369, https://github.com/jbx-protocol/juice-interface/pull/368
How do you want to contribute to the DAO going forward**?**
If this proposal passes, I’ll be quitting my current Web2 job and working on Juicebox’s front-end full time.
Continue improving Juicebox’s front-end
The front-end workload of Juicebox is only going to increase and the front-end team will need all the help it can get. I want to keep improving Juicebox’s UX however it can be done. New components, bug fixes, upgrading existing designs, and any other way we can make our app the smoothest damn user experience on Web3.
What does success look like for someone taking on your role?
- Making consistent contributions to improving Juicebox’s UI and UX.
- Timely bug fixes
Under what criteria should the community reassess this payout?
- If I fail to make consistent contributions to Juicebox’s front-end.
@aeolian
Note: recurring payout recipients are required to participate in votes for future payout allocations. For payouts to non-EOAs, attach an address that will manage voting on the non-EOA address's behalf.