OrangeDAO

Full proposal here: https://docs.google.com/document/d/1Q9MKAWKwwpXxf9BlVg3sQG3RysBeZBkaWyejR39wIYc/edit#heading=h.ddfcrao9n93f

Goal: Provide a framework for the hiring and management of dedicated DAO engineers. Allocate a seasonal budget to fund paying them in USDC.

Single Point of Contact: (Only 1 individual for GovC to reach out with questions, and to represent at TownHall.) mrmemes.eth

Sponsors: Include folks planning to work on this proposal. Do not include folks who are just supportive of this proposal. mrmemes.eth, sayangel.eth

Description:

Purpose:

The DAO currently has a number of projects that it would like to execute on, but are currently short-staffed for engineering help, in particular. Making full time engineering staff available to execute on any project approved by the DAO will open the path to executing on projects much more quickly than any other currently available avenue. Making clear how to apply and receive approval for access to engineers as well as what expectations are placed on those requesting engineering time will promote fair access and efficient use once granted.

Applying:

Any member can apply to receive engineering time to be used for projects intended to benefit the DAO at any time and for any reason. Projects receiving the sponsorship of a permanent committee will automatically be accepted. Projects that pass a proposal that involves a development component will be automatically accepted. Smaller projects or other projects falling outside of these cases can make their case directly to the Dev Committee for access to development resources. This should be initiated via Discord, in the Development Committee channel and by mentioning @DevC. Generally speaking, the Dev Committee will do its best to accommodate all valid requests and allow them to participate in the prioritization process.

Sponsorship:

Sponsorship of a project should be announced by a permanent committee member on behalf of their permanent committee via a discord message that mentions @DevC in the Development Committee channel. Sponsorship indicates agreement of that committee to make itself (or a representative from the committee) available to participate in prioritization sessions (see details below). Failure to attend prioritization forfeits their spot in prioritization for that session.

Prioritization:

Prioritization sessions will be held every two weeks and will last no more than 1 hour. These sessions will determine what’s worked on for the next two week period and should be completed at least 3 days in advance of the next period’s commencement. Participants in prioritization will make their case for the order of their project in the queue of upcoming projects and are expected to agree on the order amongst themselves. Participants should consider:

Duration of time a project has spent in the queue Overall impact of the project for the DAO Work already in progress

Dev Committee members (or a representative member) will act as moderator and tie breaker in the event that participants are not able to come to an agreement.

Expectations:

For projects and project stakeholders: Projects will designate a single PoC for planning purposes. Projects will prepare a detailed scope of work for prioritization, in advance of prioritization and will work with the development committee to ensure that their work is detailed and granular enough to be worked on -The scope of this work must always be less than two weeks and it is the responsibility of the project’s point person to reduce the scope of their tasks into something achievable in two weeks. Dev committee will give feedback on what is actually achievable in that period. Projects with a total scope that is larger than two weeks must still plan for breaking their project down into two week sessions at the end of which a deliverable is provided. Dev committee is here to facilitate scoping, not to execute it or manage it.

For Engineers Available for 40 hours per week of work, with flexibility to pull some overtime during periods of crunch time (should be rare and always discussed in advance)

Management and Oversight:

Broadly speaking, the Dev Committee will attempt to act in a facilitative manner with regard to projects and will encourage direct communication between engineers and project stakeholders. Dev Committee reserves the right to intervene in a project at any point in order to address concerns brought to it by the engineers or project stakeholders. Intervention should most often be in the form of a conversation that helps get things back on track, but in extreme cases could be used to deprioritize a project until some issue has been addressed. The onus is firmly on the project stakeholders to ensure that work is clearly detailed and that engineers are not blocked from moving forward while waiting on responses or interaction with stakeholders.

The Dev Committee will schedule regular 1:1s with engineers and use this feedback to refine the processes outlined here for the betterment of the DAO and for improvement of the experience of the engineers. Reviews will happen quarterly or as needed and should give substantive feedback on performance for the engineers.

The Dev Committee has sole discretion as to how it goes about the hiring process and who it chooses to hire. It should, however, feel encouraged to take into account any opinions and recommendations offered by other DAO members and generally avail itself of the DAOs network of experts wherever it makes sense. The Dev Committee also reserves the right to initiate termination proceedings at any point if it is determined that the engineers in the employ of the DAO are acting in poor faith or otherwise cannot or will not fulfill their duty. Any DAO member may also petition for the termination of any engineer and all such petitions will be taken with extreme gravity.

Candidate Qualifications:

A full Job Description will be issued during the hiring phase, but the spirit of the document should be:

To hire excellent engineers Who are experienced with Web3 technologies Who want more autonomy Are interested in learning more about entrepreneurship Have excellent communication skills Are very organized Are excellent at self-directed work Have experience working remotely

Benefits: This formalizes and makes clear how the development committee will go about hiring for and managing access to dedicated engineering staff. It also makes clear some of the workaday details of managing engineering staff, like reviews, 1-on-1s, allocation/prioritization and in the event of its necessity, termination. The biggest single benefit though, will be having a way to drive forward development efforts for the DAO.

(Link to Proposal Details if applicable)

Success Metrics: Engineering staff is hired and made available to the DAO for work on projects Project stakeholders have fair access to the application and prioritization process Engineering staff always has work teed up in advance Prioritized projects are executed on consistently

Duration: Start: Season 1, as soon as hiring is possible End: No end date, this is an ongoing function

Tokens Requested: (Treasury control) (Treasury Guidance) $USDC Total: 200,000/season (paid biweekly or bimonthly, like a regular paycheck) 100,000 per engineer x 2 engineers

Token Distribution: (Sponsors’ control) $ORANGE Total: 12,000/season directly to the Development Committee, to be distributed amongst themselves as they see fit (preferring even split, but allowing for parties that don’t have inclination or time to participate to bow out). $ETH total: 1/season to fund smart contract deployments and other development-related ETH costs

RISKS: (Open to All Members) By mrmemes.eth:

COUNTERPOINTS: (Open to All Members) By mrmemes.eth:

ADMIN: FOR TREASURY: Transactions Upon Passing: Send 10 $ORANGE From: 0xXXXXXXXXXXXXXXXX (Treasury Gnosis Multisig) To: 0xXXXXXXXXXXXXXXXX ([Name1]’s wallet) Send 0.05 $ETH From: 0xXXXXXXXXXXXXXXXX (Treasury Gnosis Multisig) To: 0xXXXXXXXXXXXXXXXX ([Name1]’s wallet)