acampora
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Prop189 - Collective Feedback ## Summary The document is a collection of feedback from the GnarsDAO community regarding Prop189, which has recently been "Defeated". The goal of the document: provide a safe space for everyone to give feedback on what should be changed or improved in the following proposal. > Important Links : https://nouns.wtf/vote/189 > Aggregated on-chain comments : https://docs.google.com/spreadsheets/d/1CrfeltulvEydIZ6wx5ncDlRMsNSNdp_v88x6riOYBBo/edit ``` SUMMARY OF AGGREGATED FEEDBACK * Describe how we benefit Nouns overall (proliferation, views, culture, etc) * More detailed breakdown of how the ETH will be spent (what our plans are, how much ETH is allocated for which projects, etc) * Request ETH in tranches / lower ask * Increased details regarding impacts since previous proposal 51 * Elaborate on Gnars governance processes and structure (describe how Gami is not deciding on his own, how proposals are passed, what our governance structure is, etc) * Expand on the core contributors (include brief profiles, links to contact, past work, compensation, etc) * Add more detail about views and engagement on social media * Implement benchmarks for success (monthly, quarterly reports, growth, conversions, attribution data, etc) * More careful about choice of words and interactions with others during the debate/voting periods ``` ## How to use the document Follow the format below to include your feedback Create a section in the document with the following data : ``` * Name: * Discord Handle : * Twitter Handle (Optional) : * Date : * Overall Feedback / Thoughts : * What to avoid (include up to 3 things in a bullet point) * What to improve (include up to 3 things in a bullet point) * The future ask - please specify if the next ask should be 1. Below or equal to 200 ETH 2. Between 200 & 400 ETH 3. Above 400 ETH ```` ## Start here --- **Name** : @knowhow92 **Discord Handle** : knowhow92 #4050 **Twitter Handle (Optional)** : @theocharis.ch **Date** : 23/12/2022 **Overall Feedback / Thoughts** I think it was a great 1st attempt to go big and community showed great support during voting period. The main reason I think this prop was "defeated" is the big ask with no specific details on how money will be spent as well as lack of transparency by the DAO. Lots of people thought Gnars don't have contributors and it's just Gami running the show. We need to organize ourselfs better in PODS as Flowable is trying to do, have specific roles inside the DAO and allow the community to somehow participate in the creation of the next proposal. Lots of great minds in our community with lots of different talents that could help. Don't get me wrong, Gami is a marketing genious but DAO operate different, they have structure and many contributors and these info should be public to anyone as well as their roles inside the DAO. **What to avoid (include up to 3 things in a bullet point)** - Huge ask - Promising too much while we don't even have a structure - Over-shilling **What to improve (include up to 3 things in a bullet point)** - Communication between people involved in making the new prop - Details on how money will be spent - Structure so voters can know their investment will be safe in case something happens to Gami **The future ask - please specify if the next ask should be** - Between 200 & 400 ETH for a 6 months period --- **Name:** Vlad **Discord Handle :** vladhzc#0420 **Twitter Handle:** vladhzc **Date:** 23/12/2022 **Overall Feedback / Thoughts:** I think we had a great start. It was very hard for the community to say no to Gnars after all our work. But I believe the gnars community and its core structures has to be strenghen and creating this new proposal together is a good opportunity to do so. The only danger to me is to us focus **only** on the proposal and stop the development of the team structures we were creating. I also think that we were doing fine until gamis thread about the stunt and that prooved that we have our voice centralised on Gami on twitter we need to improve our external voice as a community. Apart from that I think the new proposal should present the names involved in the board , have a budget break out, may be a simulation of montly spends. **What to avoid (include up to 3 things in a bullet point)** - losing focus on community structuring - going directly onchain - centralization **What to improve (include up to 3 things in a bullet point)** - use gnars.eth wallet to make the proposal - explain better how thatsgnarly works - more community voices on gnars, more general alignment , more defined roles for core members, not just on the proposal, but now ! **The future ask - please specify if the next ask should be** - 420.69 ETH --- **Name:** Case **Discord Handle :** Case#8072 **Twitter Handle:** betcase **Date:** 28/12/2022 **Overall Feedback / Thoughts:** The support that Gnars received from a whole cross-section of the Nouns community was encouraging as well as the energy generated here in the Gnars discord. With all the diviseness across the wider NFT community it feels like Gnars holds a rare position of being a project/DAO that people really want to see succeed even if not directly involved in it. In my mind this forms part of our unique value proposition to Nouns and the world, we're doing things that don't just benefit a minority in a way that avoids the greed we face in crypto and our daily lives. I have to echo what Vlad said though regarding Gnars' core structures, these need improving and at this point I don't feel like the DAO is quite ready to take on the responsibility that a large amount of funding entails. **What to avoid (include up to 3 things in a bullet point)** - Rushing in to writing our next prop before getting our own house in order. **What to improve (include up to 3 things in a bullet point)** - Develop the Gnars endgame, what does the DAO look like, how does it become self-sustainable, how does that benefit Nouns. - Provide clear details in our next prop as to how any funding helps us reach the above mentioned end state. - Have all DAO structures in place before we formalise our next prop, encourage community members to take on more responsibility and allow a pathway for them to possibly become board members/recognise their contributions. **The future ask - please specify if the next ask should be** - No idea --- **Name:** Satori **Discord Handle :** Satori#1337 **Twitter Handle:** @0xSatori **Date:** 12/29/2022 **Overall Feedback / Thoughts:** The whole prop 189 ordeal was bittersweet in my opinion. It revealed the substantial support that we have from the broader nouniverse and definitely provoked much needed discussions about the DAO, subDAOs, governance, and funding models, but also left a bad taste in many Nouner's mouths due to our "publicity stunt". I think part of the issue was the framing of our approach after the fact, when we had been campaigning in a way that was much more serious than it came across in Gami's thread which made people think we were trying to pull one over on them. Moving forward, we need to have much better processes for communication and coordination. Tracking what each other have contributed, working together asynchronously but effectively, and making sure we are all on the same page on how to handle criticisms and discussions around our proposal. The lack of internal communication made communicating effectively with Nouners more difficult, as we were sometimes saying contradictory things and then relying on Gami to clarify. We should all be on the same page at all times so we can avoid this. Agreed with the general sentiment around having improved internal systems in place prior to going back on-chain. Not necessarily perfect systems, but more streamlined, clear, and documented so that we only need to make incremental improvements as needed once we do obtain more funding. This should include pod structure, governance processes, proposal guidelines, onboarding, etc as we've previously discussed. Also, thinking about target resubmit date and potentially think we can aim to have our voting end on the 1 year anniversary of Gnars launch on 2/15/23, which would mean posting on chain around 2/05/23 I believe. That gives us about a month to complete the work we've been discussing. **What to avoid** - Assuming that voters know of us and what we have done - Centralization - Lack of coordination and communication around our approach and proposal campaigning **What to improve** - Describe our governance processes and operational structure - Describe what we've done since proposal 51 and how we will continue to be an important subculture in the nouniverse - Outline how we will track and report our success (regular reports back to Nouns which outline key metrics) **The future ask** - I feel that breaking it up into smaller tranches will be best, but not necessarily reducing overall ask. Based on feedback received I'm leaning towards 4 tranches of 169 ETH, distributed quarterly upon succesful performance and hitting key deliverables that we'll outline in our proposal. - 169 ETH per 3 months x 4 = 676 ETH --- * Name: Jay * Discord Handle : 0xMummy#6289 * Twitter Handle (Optional) : @0xmummy * Date : 12/28/22 * Overall Feedback / Thoughts : I don't think the original prop was a good use of people's time and also risked some of the Gnars reputation. The "just a joke" approach rubbed some people the wrong way, would have rather just let the prop fail and issue a new one after taking feedback. The prop did ignite the spending/accountability discussion, which will end up being healthy for NounsDAO long term * What to avoid (include up to 3 things in a bullet point) `Lump Sum Payment` `Lack of Detail` `Lack of performace metrics` * What to improve (include up to 3 things in a bullet point) `ETH triggered on specific deliverables` `3rd party review of prop performance after milestones/time` `Gnars issued report of success/fail points after milestones/time` * The future ask - please specify if the next ask should be 1. Below or equal to 200 ETH **2. Between 200 & 400 ETH** *The ask should encompass what is needed, then execute the prop in phases with a payment split at start and completetion of each phase* ie. Phase 1 (Gnars Event New York) budget 25eth *list of estimated expenditures 15eth up front, 10eth after event and post mortem report is provided 3. Above 400 ETH --- **Name:** Mari **Discord Handle :** marinioac#6942 **Twitter Handle:** marinioac **Date:** 30/12/2022 **Overall Feedback / Thoughts:** First of all, thanks for giving me space to comment, the entire process was very interesting and I learned a lot! I agree with most feedbacks above, so I’m not going to be repetitive, here it’s my feedback: The whole process showed NounsDAO the good reputation Gami has, but it lacked showing what GnarsDAO is and what it can be, not only in data but also on marketing. Since the prop was presented at the board meeting two days before it was published, the Gnars community didn’t have time to create a media strategy for the voting process. Most of the media and info was published by Gami, and wasn't even through the Gnars accounts. Where were all the Gnars athletes during the vote? Why wasn't there a strategy to flood the media with a bunch of Gnarly content? Coletivo XV has amazing content, but Gnars is a lot more than Coletivo XV and skate. Where were the skiers, the surfers, the kids at TPM and much more? Gnars is about being gnarly, we lacked being gnarly as a community of creative media creators. Gnars instagram and twitter needs help from the community. Most of what has been produced hasn't been published or shared by Gnars accounts. Like some board members have mentioned, we still need to organize some structure before getting so much eth. Imo, everything that grows fast, falls fast. I would like to see Gnars last for a while and for that, it needs structure. Onboard better, deliver more, ask for less. **What to avoid (include up to 3 things in a bullet point)** * Centralization * Not showing all the content GnarsDAO produces, Gnars is not only Gami nor Coletivo XV, it’s a lot more. * No space for doubt **What to improve (include up to 3 things in a bullet point)** * Build a clear onboarding process to encourage the community to participate on and work for the DAO * Better publicize on social media (web2 and 3) the content produced by Gnars’s athletes and projects. And create a gnarly marketing strategy involving the whole community during the vote. For example, making chain effects. * New assets for Gnars NFTs, gnarlier and more unique heads. **The future ask - please specify if the next ask should be** - Between 200 & 400 ETH for 6 months --- **Name:** Davin **Discord Handle :** davinoyesigye#8954 **Twitter Handle:** @davinoyesigye **Date:** 01/06/2023 **Overall Feedback / Thoughts:** After some deliberation i think we should half our ask to 420ETH for 6 months runway, we have been pioneering some cool stuff with gnars and i believe it can be very valuable to nouns. If we can show everything that gnarsDAO has done so far. it can go a long way. But i have to say that the idea of breaking down every penny we're asking for is a little uncalled for because to be honest, we don't even know how we are going to spend the money ourselves. All i know is that gnars has to now spend on 4-6 pillars and pods to help grow the brand i.e. (athletes, artists, admin, dev team, media team) **What to avoid (include up to 3 things in a bullet point)** * Asking for a small amount of ETH that will cripple out growth trajectory * Structuring the proposal to please specific voters, when we have indeed brought alot of value to nouns * setting a roadmap that we may fail to achieve **What to improve (include up to 3 things in a bullet point)** * Performance Metrics and how they will be measured * Reporting tools and who does Gnars report to in the DAO **The future ask - please specify if the next ask should be** 420 ETH for 6 months

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully