Repository navigation
Demo Application & Tutorial #55
Description
This is all very tentative, should collab with @EzraWeller and Eric
Views:
- DAOs
- DAO
- Members
- Proposals
- Votes
- Add Member
- Reward Member
- Vote
This is all very tentative, should collab with @EzraWeller and Eric
Views:
Activity
orishim commentedon Apr 10, 2020
(from ezra's notes)
A sample DAO UI that:
importsDAOcomponents, etc.)[-]Demo Application[/-][+]Demo Application & Tutorial[/+]arsena21 commentedon Apr 20, 2020
One thing that was mentioned today is that maybe we can just use the Absolute Voting Machine for the UI... so that we don't need to deal with staking / boosting / etc
Would this make things easier?
EzraWeller commentedon Apr 20, 2020
I don't think that's in scope for this project either, since there's currently not an easy way to deploy a DAO that uses absolute voting.
dOrgJelli commentedon Apr 20, 2020
@arsena21 while I agree, currently the Genesis Protocol is the only voting machine that's supported in the stack (migration scripts, subgraph, and client). This means that while those contracts are written and work at the protocol level, they aren't functional in all other layers of the stack.
dOrgJelli commentedon Apr 20, 2020
A way to get around this is to forward users to Alchemy for "advanced" functionality, although I think it should be in scope to support staking and voting.
arsena21 commentedon Apr 20, 2020
Makes sense, thanks for clarifying.
In terms of staking an voting, would we just copy (roughly) the Alchemy UI? Or is there an opportunity to update things a bit? For example, here are some mockups I put together to demonstrate how we could make voting / staking a bit more intuitive:
https://www.figma.com/file/PwNcGfD6Fo29glEtC3Ylv4/New-Proposal-Windows
My main fear is that, if we just copy the Alchemy UI for proposals, it is still just as confusing. Additionally, re-creating the Alchemy UI isn't exactly a piece of cake either, so might be better off re-thinking things a bit.
dOrgJelli commentedon Apr 20, 2020
The idea is to make the UI as simple as possible @arsena21, so no we're not going to recreate Alchemy's UI. Please feel free to send any thoughts here on what you think this should look like! Totally open to suggestions as the views aren't spec'd out yet.
dOrgJelli commentedon Apr 20, 2020
Here's my own shot at describing "hyper simple alchemy" views:
Single DAO Front-Page
Proposals List (Overview)
Proposal Details
Members list view
Treasury view
NOTE
The DAO described is assumed to only have a ContributionReward plugin. If the DAO has other plugins added to it, Alchemy's UI (the "admin" panel) will need to be used. This DAO UI is only concerned with adding members and giving rewards.
@arsena21 @EzraWeller @cbrzn @orishim @orenyodfat please comment on above!
arsena21 commentedon Apr 20, 2020
wouldn't it at a bare minimum need to include everything in the image below (including the proposal box, with voting buttons, boosting sections, etc)
dOrgJelli commentedon Apr 20, 2020
@arsena21 only difference in my above description is that the overview doesn't concern itself with voting and staking, only the title, proposer, and pass/fail details.
arsena21 commentedon Apr 20, 2020
I like the direction you are going with the views.
I would love to (if possible) find a candidate to build this for so that we can refine this, and build something that will be used (and maybe even make a splash!).
How much time do we have before these views need to be locked in (approx)? I am talking to various groups this week / next week but would be good to have a cutoff in mind.
dOrgJelli commentedon Apr 20, 2020
Based on this roadmap doc, the views would begin to be made 2.5 weeks after the engagment begins:
The start date is still TBD though, as we don't have unanimous sign-off. We can discuss this further in slack.
arsena21 commentedon Apr 21, 2020
arsena21 commentedon Apr 29, 2020
So the three projects I'm in talks to for DAO Components are: 1) SuperRare, 2) OpenSea, 3) Unstoppable Domains. The goal is to get one of them committed in the next week or so. I'll work on some quick mockups.
EzraWeller commentedon Apr 30, 2020
@dOrgJelli Feedback for the simple DAO views (the DAOcomponents demo):
General
In general, I think we should view this demo as a developer tool more than something used to impress non-developer clients. The demo should show a developer in a clear way how they can grab and display the right kinds of data and expose certain functions in a UI, but I don't think it needs to show them anything about UX.
Specific
In that light, I think we probably don't need any filtering for lists or buttons that bring up details: just a bunch of data and some buttons/forms hooked up to functions. I don't have time right now, but I can go through the proposal above and try to point out what I think might be removable if that's helpful!
I think we will definitely want to explore the directions you're talking about in that proposal, but I think that should be in a project that comes right after this one (hopefully connected to an existing client or DAO!). Does this make sense?
I think I am speaking for the team here, but let me know if this sounds wrong @arsena21. Sorry if there was some confusion around this!
dOrgJelli commentedon May 1, 2020
Okay sounds great @EzraWeller, would love to schedule a call around this soon w/ @cbrzn, yourself, and @arsena21
arsena21 commentedon May 3, 2020
arsena21 commentedon May 7, 2020
Proposing the following changes so that we can provide something for Unstoppable Domains:
(based on #55 (comment))
-Adding regular / pre-boosted / boosted proposals
-Adding ability to stake
-Adding ability to select which DAO this information is for
That last point is so that: when you deploy a website on Unstoppable Domains, you can enter in the address of your DAO, and then the information is pulled from this DAO.
It would also be cool if when you create your website on UD, you can deploy your DAO at the same time... but I think they might be able to just use DAO Creator for that right?
@EzraWeller what are your thoughts on this? It would not include any design work, just making sure the functionality is there so they can apply designs
EzraWeller commentedon May 8, 2020
Hmm, let's chat about this in Slack instead, I think!
dOrgJelli commentedon May 12, 2020
This is currently underway here: https://github.com/dorgtech/arc.react-demo