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:
@aeolian
Proposal date:
2022-01-11
Summary:
Compensate aeolian.eth US$3,000 (in ETH) per funding cycle for frontend engineering.
Risks:
If my circumstances change, my lack of availability might pose the following risks:
- Unable to provide timely bug fixes.
- Contributions I’m leading may go stale.
- Unable to provide timely code reviews.
Payout recipient:
aeolian.eth
Payout amount:
US$3,000 (paid in ETH)
How have you contributed to the DAO?
A (mostly) complete list of my contributions can be found here: @Anonymous ‘s contributions
Since my first contribution to Juicebox app ~2 months ago, I felt I have become well-integrated into frontend team and JuiceboxDAO generally. As a frontend engineer, I’ve consistently made impactful contributions to the Juicebox app and added value to discussions across multiple domains.
Notable code contributions include:
- Added Uniswap price to Juicebox projects (design and implementation) [1]
- Added multi-language (internationalization) support to the Juicebox app and Juicebox documentation [2, 3]
- Site performance and technical debt improvements [4]
- UI/UX improvements [5]
- Contributor experience and documentation improvements [6]
- Project page redesign (in progress) [7]
- Juicebox terminology audit (in progress) [8]
How do you want to contribute to the DAO going forward**?**
I’m committed to making the Juicebox app the best it can possibly be. This means continuing to add features and fix bugs, as well as continuing to improve the maintainability of Juicebox by cleaning up technical debt.
Short-term goals include:
- Adding Sushiswap price to the interface [9]
- Project page redesign (design and implementation) [7]
- Various maintainability improvements [10]
Medium term goals include:
-
Improve usability of Juicebox.
I’m most interested in making Juicebox easier to use and understand. Simplifying Juicebox may be one of the most critical factors to continued adoption of the Juicebox platform. This requires a broad skillset that spans copywriting, technical writing, UI/UX design and programming; I believe I’ve demonstrated these skills in my contributions thus far.
-
Contribute to the launch of Juicebox V2.
-
Become a maintainer of the Juicebox frontend.
Currently, the Juicebox app codebase only has one maintainer - Peri. A lot of Peri’s time is spent reviewing contributions (which is very much appreciated), but continuous context-switching can take a toll and shift focus away from other high-leverage work (like the v1.1 migration). As I become more familiar with the codebase and trusted by the DAO, I believe I could join Peri as a maintainer of the Juicebox frontend codebase. Having maintained a few popular open source projects, I’m aware of the responsibility this entails - baby steps!
What does success look like for someone taking on your role?
- Shipping features, bug fixes and UI improvements.
- Reviewing code contributions.
- Maturing the contribution and workflow processes for design and dev.
Under what criteria should the community reassess this payout?
There are three scenarios where my payout may need to be reassessed:
- My personal circumstances change such that I am unable to contribute at an acceptable level. In this case, my payout should be reduced or removed.
- My responsibility grows within the DAO, and more of my time is required. In this case, I would propose an increase to my payout.
- I become available to the DAO full-time. In this case, I would propose an increase to my payout.
[1] - https://github.com/jbx-protocol/juice-interface/pull/311
[2] - https://github.com/jbx-protocol/juice-interface/pull/236
[3] - Untitled
[7] - Untitled
[8] - Untitled
[9] - https://github.com/jbx-protocol/juice-interface/issues/344
[10] - For example, https://github.com/jbx-protocol/juice-interface/issues/343
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.