Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create DIP-47.md #152

Closed
wants to merge 1 commit into from
Closed

Create DIP-47.md #152

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
192 changes: 57 additions & 135 deletions DIPs/DIP-0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,157 +1,79 @@
---
DIP: 0
Title: DIP Purpose and Guidelines
Status: Active
Themes: Meta
Tags: Other
Authors: Bettina Boon Falleur (@BettinaBF), Ligi (@ligi), Heather Davidson (@p0unce), Skylar (@skylarweaver), Joseph Schweitzer (@ethjoe)
Discussion: https://forum.devcon.org
Created: 2020-07-06
DIP: 47
Title: Adoption Hub at Devcon SEA
Status: Draft
Themes: Adoption, Design, Experience, Marketing
Tags: Community Hub, Event Operations, Event Production
Authors: Ira Nezhysnka, Andrej Berlin, Diego Mazo & Co. (community)
Discussion: https://forum.devcon.org](https://forum.devcon.org/t/sea-community-hub-proposal-adoption-hub/3757
Created: 2020-09-17
---


## What’s a DIP?

DIP stands for Devcon(nect) Improvement Proposal. A DIP is a proposal put forth by members of the community describing a desired new feature or process to improve Devcon(nect). A DIP should be concise and provide as much information as possible as well as a rationale for the proposal.

The DIP author is responsible for making the case for a proposed DIP, and community members will be able to comment on it. It is up to the Devcon(nect) Team to choose which proposals are considered, reviewed, and accepted.

## Rationale

The Devcon(nect) Team intends DIPs to provide a mechanism for collecting collaborative community input on what should be included at the upcoming Devcon(nect). While we are excited to have a more formal process to hear ideas from the community (roughly inspired by the more decentralized PEP, BIP and [EIP](https://eips.ethereum.org/) processes), this is an experiment, and it should be understood that approval of proposals ultimately lies solely with the Devcon(nect) team. DIPs focus on collaboration in the ecosystem, so please review and collaborate on other proposals rather than submitting possible duplicates.

## Themes
There are two general types of DIPs you can create:
1. A response to one of our [Request for Proposals (RFPs)](https://forum.devcon.org/c/devcon-rfps/5) which are ideas that we would like to see happen at Devcon(nect)!
2. _Any_ idea! We welcome any ideas you have to improve Devcon(nect)!

Here is a list of themes to inspire you:

* **Ticketing** - Anything useful concerning ticketing (e.g. usage of NFTs)
* **Social** - How to make people connect, prior, during and after Devcon(nect)?
* **Environmental Sustainability** - Any idea that helps us make Devcon(nect) more environmentally sustainable
* **Virtual Experience** - Live streaming, and other ways of interacting with people unable to be physically present at Devcon(nect)
* **Purchases & ID** - Let’s do more to use crypto at Devcon(nect)! Onsite and Offsite purchases, bookings,...
* **Community Involvement** - How can we integrate more community input into Devcon(nect)?
* **Art & Beauty** - A cool design for swag items, an art piece, ...
* **Freeform** - Any great ideas you have! From tutu-Tuesday to Bring your own T-rex for closing ceremony
* **Meta** - Any improvement to the DIP process itself. This process is new, and it could benefit from anything that you’ve got in mind. We’d love to hear your thoughts.

## Instances

Which events should this DIP target? Can be `*` for all events or a list of specific events - e.g. `Devcon7`.
## Summary of proposal

## Tags
Devcon(nect) has several aspects to its organisation. To help us better guide you, select the area of focus that concern your DIP:
Inspired by the success of the Design Hub at Devcon 6 and driven by the understanding that design, user research, and marketing are three pillars of decentralized tech adoption, we (see the list of collaborators below) propose to organize an Adoption Hub at Devcon 7.

* **Event Operations** - Anything related to the general organisation of Devcon(nect)
* **Event Production** - Anything to do with the on-site attendee experience
* **Software** - Anything to do with software needs, devcon.org, subdomains, ...
* **Communications** -Anything to do with Devcon(nect)-related communication, media, blog posts, ...
* **Sponsorships** - Anything to do with sponsorships, benefits and more.
* **Other** - Anything else
## Goals of the Adoption Hub

## Resources
Your DIP may require resources from the Devcon(nect) team, so make sure to add them to your draft. This will save us both precious time when evaluating the feasibility of a DIP.
From hands-on co-working sessions and workshops to jams and fun activities, it is where designers researchers and marketers aim to:

* Tech support
* Physical room at venue
* Operational support
* Communication support
* Other: please specify
* Share their knowledge with projects and teams who are looking to give momentum to their user adoption.
* Meet each other to cross-pollinate ideas and collaboratively push our design+research+marketing efforts forward.
* Help the Ethereum ecosystem find new strategies to increase user adoption.
* Facilitate conversations between developers and designers and increase the potential for collaboration after the event.

## Criteria for a Successful DIP
* Aligned with Devcon(nect)’s Code of Conduct and values
* Integration is driven and owned by the stakeholder/project/community
* Willing to collaborate with other projects and people
* Can be integrated with other dApps & projects at Devcon(nect)
* As good as, or better than the non-blockchain alternative (explain why and how)
* FOSS mentality
## Audiences

## Team
The Devcon(nect) team is the final decision maker on the status of a DIP (Accepted - Postponed - Not Implemented). Our team will work together to provide a technical and operational review of all DIP drafts submitted. They are responsible for communicating with the DIP authors and relaying information between teams, and accompany projects through their production-implementation phase to ensure Accepted DIPs are ready for Devcon(nect).
While designers researchers and marketers are the content creators of the Hub programming, we also aim to attract:

## Workflow (From Idea to Implementation)
* Web3 founders and teams looking for advice on driving users to their platforms.
* Designers researchers and marketers NEW to the Web3 space who are looking for mentorship or advice as they get involved with the Web3 community
* Activists artists and makers who want to explore how we can co-create a more user-friendly inclusive and environmentally conscious decentralized web by making ideas heard and put them into action.

#### 1. Eureka!
## Programming

You, the DIP author, just came up with a great idea💡 for Devcon(nect). Either (a) your DIP answers one (or several) of Devcon(nect)'s [RFPs](https://forum.devcon.org/c/devcon-rfps/5) or (b) you came up with another improvement you'd like to suggest!
Over the course of four days, we will guide participants through the journey of user adoption by following best practices from web3-native design, research, and marketing. As a team progresses along its roadmap, we aim to provide the most effective and actionable steps to increase the trust and usage of a project or protocol.

#### 2. Community Feedback
All sessions and activities will be scheduled in order of relevance to a team’s growth stage. As a result, visitors should identify their current stage by looking at the schedule, and recognize the bottlenecks (and needs) that slow down their progress. The sessions will be designed to effectively address those bottlenecks and gain momentum to successfully reach the project’s upcoming goals.

Before writing a formal DIP Draft in Github, take the time to vet your idea. Open a discussion thread in the [Devcon Forum](https://forum.devcon.org/) and make sure to clearly state your idea to allow the community to provide feedback. Share your idea with the community to gather more feedback. This is done to ensure you don't waste your time writing a DIP that either won't get enough traction, is not feasible, or is a duplicate. Take five minutes to read through the [RFPs](https://forum.devcon.org/c/devcon-rfps/5) to make sure your idea doesn’t fit in one — it may save you some time!
While the detailed programming is in the making as we involve more collaborators, below is a list of activity types we are planning to run in the Hub:

#### 3. Process
1. Hands-on workshops:
* Building a success-driven team to create high-value infrastructure
* Brand Lab or reverse-engineering reputation through visual design
* Web 3 marketing acquisition strategies
* Crafting a values-based brand narrative to build a regenerative community
* Conversion Rate Optimization in crypto - how to articulate return on investment
* What magic can teach us about designing delightful experiences
* Finding adoption signals with low-cost no-code experiments.
* more topics to come
2. UX audits
3. Open design sprints
4. Design clinics (product + communication)
5. Ask Us Anything
6. Maker jams
7. Mentoring hours
8. Design/research/marketing memes wall
9. “Confessions from behind the scenes” (maybe)
10. Best practices (UX and GTM strategies).

1. **Draft DIP** - Choose your prettiest digital pen and write your DIP! Follow the yellow brick road: [DIP format](https://github.com/efdevcon/DIPs/blob/master/DIPs/DIP-0.md#dip-format)
2. **Submit DIP** - Click on the scary button and submit your DIP. Ensure you include all information required in the template under DIP Format below.
3. **Editor Review** - Your DIP is now in the hands of the DIP editors team for review.
Editors might request more information and ask to resubmit the DIP.
4. **Devcon(nect) team Review**
* **Draft** - Your DIP that is undergoing rapid iteration and changes
* **Accepted** - Your DIP idea is approved! Now it's time to work on the implementation!
* **Postponed** - Your DIP won’t be possible the upcoming Devcon(nect) - but we love the idea.
* **Not Implemented** - Oh no, the mean Devcon(nect) team, reach out to them and ask for more context to understand their reasoning
* **Changes Requested** - The DIP needs modifications conditional to its validation.
## Equipment & Production Needs
We will finalize this section after receiving a manual with the default setup for the hub space.

#### 4. Implementation
## Contributors

* Definition of project timeline
* Bi-monthly sync with DIP editors & other DIP-authors
* Collaboration with other DIP projects
* Testing
List of dedicated people who will co-create the Adoption Hub experience:

#### 5. Production
* [Andrey Berlin](https://x.com/kischiman)
* [Ira Nezhynska](https://nezhynska.com/)
* [Diego Mazo](https://www.diegomazo.com/)
* [Amy Jung](https://twitter.com/itsamyjung)
* [Stacey Fronek](https://www.linkedin.com/in/stacey-fronek-14ba53111)
* [Georgia Rakusen](https://twitter.com/G_Rak)
* [Hester Bruikman](https://twitter.com/hesterbruikman)
* [Sasha Tănase](https://x.com/sasha_tanase)
* [Tanya Efremova](https://x.com/tanyaef_)
* and more co-creators joining

* Ready for take-off!

## DIP Format

Your first PR should be a first draft of the final DIP. It must meet the formatting criteria (largely, correct metadata in the header). An editor will manually assign it a number before merging it. Make sure you include a discussions-to header with the URL to the [Devcon discussion forum](https://forum.devcon.org)

If your DIP requires images, the image files should be included in a subdirectory of the assets folder for that DIP as follows: assets/dip-N (where N is to be replaced with the DIP number). When linking to an image in the DIP, use relative links such as ../assets/dip-1/image.png.

After submitting editors will go through [this checklist](../checklist.md) - it is encouraged that you already went trough these points yourself.

All DIPs should be written in markdown format. Please use the template below:

```
---
DIP: (Number of DIP)
Title: (Think of a catchy, descriptive, short title)
Status: Draft
Themes: (See themes above)
Tags: (Please select all that apply: Programming, ...)
Instances: (See instances above)
Authors: (Emails of primary contacts)
Resources Required: (Physical space at venue, Operations Support, etc.)
Discussion: (URL of where this DIP gets discussed, preferably on https://forum.devcon.org)
---

-----Summary of Proposal-----
__Simple Summary__
__50 word summary__

-----Abstract-----
__200 word description of the proposal.__

-----Motivation & Rationale-----
__Below are some useful prompts__
- How would this enhance attendee experience?
- How is this solution better than a non-blockchain experience?
- How does this proposal introduce attendees to a novel blockchain/ethereum use case?

-----Implementation-----
__Below are some useful prompts__
- Has any part of this proposal been implemented at other events? If so, please describe how it went.
- Do you require feedback or data from attendees post-event?

-----Operational Requirements & Ownership-----
__Please answer questions below:__
1. What actions are required to implement the proposal at Devcon(nect)?
2. Who will be responsible for the proposal to be implemented effectively? (i.e. working on Day 0)
3. What other projects could this proposal be integrated with? (Bonus points for collaboration across teams :))

-----Links & Additional Information-----
__Any additional information__
```
Loading