Member Proposals SOP

Overview

Do you have an idea that could make FWB better or proliferate its pattern language? FWB Proposals are community-led initiatives that benefit the FWB community. Member-driven proposals serve as a conscious effort and intentional contribution to build a robust, member-driven FWB ecosystem.

This proposal guideline is a framework to make it as easy as possible for members to craft and submit successful proposals. All proposals submitted using these guidelines should not fall within the scope of other existing protocols, like Event Keys or Partnerships SOPs.

Full proposal here, abbreviated due to Snapshot character limits.

Why

FWB DAO Members are encouraged to create proposals to contribute to the construction of the community by fostering inclusivity, innovation, and collaboration.

Proposals play a crucial role in shaping the direction and initiatives of the DAO, allowing members to voice their ideas, workshop, and execute them. By engaging in the proposal process, members can enhance community engagement, drive meaningful projects forward, and ensure that the DAO remains true to its ethos and values.

Through proposals, members can influence decision-making, promote transparency, and actively participate in the governance of FWB, ultimately strengthening the community's cohesion and effectiveness.

Who

All current FWB DAO members can submit proposals. The Community Council and Core team will be the stewards of the Member Proposal process, supporting members through feedback and best practices advice. If a proposal is approved, Council Members will provide help to keep the proposal on track, while Core team members will be in charge of following through with milestone completion and the execution of the proposal’s financial plan.

How

The process for member-led proposals should fulfill the following phases, which are stated in a way that allows each member to propose ideas in a way that adapts to their particular needs and the maturity of their proposals.

Proposals that follow this workflow should be impactful for FWB and should not fall in the scope of other active intake flows like Event Keys or Partnerships.

Ideation

First, consider how your proposal responds to one or more of these questions:

• How does this drive value to the FWB community? Is it generating Benefits for FWB members?

• Does this proposal align with the FWB Values and Manifesto?

• What role does Web3 technology play in the project?

• By engaging in this project, is FWB playing the role of creating vibes, onboarding, community creating, or infrastructure building & defining?

• How is this driving forward one or more of our core values and creating a new opportunity for cultural creators and maintainers?

• For example, are we advancing agency by teaching creatives about ownership?

• Are we advocating for an underrepresented group by creating a platform for diverse voices or works of art?

Then, write your proposal as the following template: FWB Proposal Template

Your proposal should effectively communicate:

• What is the project

• How will it proliferate FWB

• How much funding you'll need

• How the funds break down, in a detailed budget. Be mindful that at most 50% of the budget can be requested before the completion of the proposal. The DAO will hold the remaining 50% until the final report is submitted

• How the funds are expected to be received, considering milestones to ensure completion

• What are the success metrics/KPIs associated with the project

• Detailed timeline and milestones (if applicable), considering a preparation period of at least 4 weeks before the proposed date of start or execution.

• What are the ways in which this project will showcase FWB

• Identify potential conflicts of interest, controversy, or risk that the proposal may entail

Alternatively, members are encouraged to reach out to Community Council members or to post to gen-chat to workshop early-stage ideas that have the potential to become Member Proposals.

Intake: Send your proposal to Airtable / Post your proposal in #Discord-channel - to be defined

Workshopping: Workshop in Discord openly with members and interested parties (ie. are other members working on something similar? Is there a chance to collaborate with other members on this proposal or project?) Here, members are expected to shape their proposals with the collaboration of fellow members. At this stage, a proposal is not necessarily completed, and it is intentionally open to incorporate ideas, feedback, and collaborators.

Time: up to two weeks.

When do we consider a proposal ready for discussion? A proposal will be considered ready to move on to the discussion phase once it effectively communicates all the elements stated in the Proposals section of this document, according to the scope and needs of each proposal. ie. A detailed budget will be required if the proposal is asking for treasury funds, and a timeline and milestones will be required if the proposal is to be executed over a period of time.

Discussion After a proposal has been workshopped, it will be discussed with the community on a thread in #live-discussion on Discord. The purpose of this phase is to receive member feedback and address fellow FWB members' thoughts, concerns, and critiques to shape the proposal in a way that is engaging and meaningful for the broader FWB community.

During this time, proposal submitters are expected to engage actively in the discussion with fellow community members, and they are expected to take the time to incorporate their feedback in the proposal document. Failure to do so will result in the proposal not being put up for vote, at the discretion of the Community Council.

Time: 7 days since the proposal is posted in #live-discussion on Discord.

When do we consider a proposal is ready for vote?

A proposal will be considered ready for vote when all major concerns have been addressed or incorporated into the existing proposal. Some proposals will have minimal feedback while others will need to be completely rewritten. The Council will follow along in the debate, unless the proposal is submitted by Core, to ensure all community members' voices have been heard and acknowledged in a meaningful way. Once the proposal has a general sentiment sign-off check, it can go up for vote.

The criteria for whether the proposal has successfully addressed member feedback and will be submitted for vote relies on the Community Council, and a Core team member, who will post it to Snapshot, at most 3 days after the 7 days of discussion have ended.

The Community Council will have the power to veto a proposal if it is considered that the proposal is not viable, if it doesn't align with FWB’s Values and Manifesto, and/or if the FWB Community feedback of the proposal is not supportive of the proposal.

---

Full proposal here, abbreviated due to Snapshot character limits.