Proposal [Non-Constitutional]: Establish the ArbitrumDAO Procurement Committee
Vote: Establish Procurement Committee
We are voting in favor of this proposal but have our reservations with the continuity of this program.
The ARDP and ARDC are both examples of how a DAO can become more sophisticated in terms of professionalizing its operations. Creating subcommittees is a good practice for effective decision making and proposal creation. But the introduction of numerous subcommittees can also create unnecessary overlap in jobs. In our eyes, the functions of the ARDP and ARDC have enough overlap to justify combining them to an extent in the long run. Either way, they’ll need to be in close communication. A natural point for something like the ARDP would be to create frameworks based on the interactions they have during their tenure, this way the frameworks are empirically designed. But that’s likely too much to ask for. To establish strong frameworks there should be a dedicated task force like the ARDP, but the current six month timeline, along with the corresponding compensation package, should be limited to 6 months and not subject to an automatic reelection period. Unlike the ARDC, which is more-so a continual program, the ARDP can likely accomplish its tasks within the 6 month period. The hard part about creating these frameworks is the initial stage. Afterwards, it’s about monitoring and revamping current frameworks. Therefore, this committee should be ascribed a passive role long-term. In its passive state, the ARDP should also begin resorting to the ARDC and the DAO for continual feedback. We believe it’s fine for the working group to be limited to 3 competent people, but during the passive lifetime of the ARDP after the initial 6 months, it may be a good idea to add more members to the team. Again, this later stage ARDP is mostly a monitoring committee.