Write DEVCon as Devcon

it is wrong IMHO - but what is used on the site currently
efdevcon · Aug 1, 2023 · 639da8a · 639da8a
1 parent 4edf3e2
commit 639da8a
Show file tree

Hide file tree

Showing 31 changed files with 57 additions and 57 deletions.
diff --git a/DIPs/DIP-0.md b/DIPs/DIP-0.md
@@ -12,47 +12,47 @@ Created: 2020-07-06
 
 ## 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.
+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.
+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.
+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)!
+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)?
+ * **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`.
+Which events should this DIP target? Can be `*` for all events or a list of specific events - e.g. `Devcon7`.
 
 ## Tags
-DEVcon(nect) has several aspects to its organisation. To help us better guide you, select the area of focus that concern your DIP:
+Devcon(nect) has several aspects to its organisation. To help us better guide you, select the area of focus that concern your DIP:
 
-* **Event Operations** - Anything related to the general organisation of DEVcon(nect)
+* **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, ...
+* **Communications** -Anything to do with Devcon(nect)-related communication, media, blog posts, ...
 * **Sponsorships** - Anything to do with sponsorships, benefits and more.
 * **Other** - Anything else
 
 ## 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.
+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.
 
 * Tech support
 * Physical room at venue
@@ -61,21 +61,21 @@ Your DIP may require resources from the DEVcon(nect) team, so make sure to add t
 * Other: please specify
 
 ## Criteria for a Successful DIP
-* Aligned with DEVcon(nect)’s Code of Conduct and values
+* 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)
+* 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
 
 ## 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).
+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).
 
 ## Workflow (From Idea to Implementation)
 
 #### 1. Eureka!
 
-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!
+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!
 
 #### 2. Community Feedback
 
@@ -87,11 +87,11 @@ Before writing a formal DIP Draft in Github, take the time to vet your idea. Ope
  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**
+ 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
+     * **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.
 
 #### 4. Implementation
@@ -148,7 +148,7 @@ __Below are some useful prompts__
 
 -----Operational Requirements & Ownership-----
 __Please answer questions below:__
-1. What actions are required to implement the proposal at DEVcon(nect)?
+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 :))
 

diff --git a/DIPs/DIP-1.md b/DIPs/DIP-1.md
@@ -3,7 +3,7 @@ DIP: 1
 Title: Make Devcon carbon neutral
 Status: Accepted
 Themes: Ticketing, Environmental Sustainability
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event production, Software
 Authors: Raphaël Haupt <raphael@curvelabs.eu>
 Resources Required: Tech support, Communication support

diff --git a/DIPs/DIP-10.md b/DIPs/DIP-10.md
@@ -3,7 +3,7 @@ DIP: 10
 Title: Status as Devcon Communication Layer
 Status: DRAFT
 Themes: Social
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Communication, Event Production, Sponsorship
 Authors: Jonathan Zerah <jonathan@status.im>
 Resources Required: from the Devcon team side - support and communication

diff --git a/DIPs/DIP-11.md b/DIPs/DIP-11.md
@@ -3,7 +3,7 @@ DIP: 11
 Title: A Crypto-Onboarding Escape Room
 Status: Accepted
 Themes: Freeform
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event Production, Other
 Authors: Griffin Ichiba Hotchkiss (@gichiba)
 Discussion: https://forum.devcon.org/t/dip-11-a-crypto-onboarding-escape-room/128

diff --git a/DIPs/DIP-12.md b/DIPs/DIP-12.md
@@ -3,7 +3,7 @@ DIP: 12
 Title: Addition to DIP–1 — Make Devcon Carbon Neutral
 Status: Draft
 Themes: Ticketing, Environmental Sustainability
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event production, Software
 Authors: Raphaël Haupt <raphael@curvelabs.eu>
 Resources Required: Tech support, Communication support

diff --git a/DIPs/DIP-13.md b/DIPs/DIP-13.md
@@ -3,7 +3,7 @@ DIP: 13
 Title: On-chain & trouble-free ticketing for Devcon 6 with GET Protocol
 Status: Not Implemented
 Themes: Ticketing
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event operations
 Authors: Olivier Biggs <olivier@get-protocol.io>
 Resources Required: Operations support

diff --git a/DIPs/DIP-14.md b/DIPs/DIP-14.md
@@ -3,7 +3,7 @@ DIP: 14
 Title: Poster Presentations
 Status: Draft
 Themes: Community Involvement
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event Operations
 Authors: Valerie Vaske <valerie.vaske@gmail.com>
 Resources Required: Physical space at venue, Communication support

diff --git a/DIPs/DIP-15.md b/DIPs/DIP-15.md
@@ -3,7 +3,7 @@ DIP: 15
 Title: Travel insurance
 Status: Draft
 Themes: Travel, Safety
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: DeFi, Insurance, Peer2Peer
 Authors: Christoph Mussenbrock <christoph@etherisc.com>
 Resources Required: CustomerSupportBooth at DevConVI

diff --git a/DIPs/DIP-16.md b/DIPs/DIP-16.md
@@ -3,7 +3,7 @@ DIP: 16
 Title: Universally verifiable off-chain polls for Devcon 6
 Status: Draft
 Themes: Community Involvement, Ticketing
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Software, Event production
 Authors: Pau Escrich <pau@vocdoni.io>, Patricio Worthalter <worthalter@poap.xyz>, Ferran Reyes <ferran@vocdoni.io>
 Resources Required: Communication support

diff --git a/DIPs/DIP-17.md b/DIPs/DIP-17.md
@@ -3,7 +3,7 @@ DIP: 17
 Title: Make Devcon6 Carbon Neutral
 Status: Draft
 Themes: Ticketing, Environmental Sustainability
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event production, Software
 Authors: danceratopz <danceratopz@gmail.com>, haurog <haurog@pm.me>
 Resources Required: Operational support, Communication support, (Tech support?)

diff --git a/DIPs/DIP-18.md b/DIPs/DIP-18.md
@@ -3,7 +3,7 @@ DIP: 18
 Title: Hosting DevCon agenda and document sharing on Swarm
 Status: Accepted
 Themes: Freeform, Website, Agenda
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Software, Event Operations, Attendee Experience
 Authors: Costanza Gallo <costanza@ethswarm.org>
 Resources Required: Operation support

diff --git a/DIPs/DIP-19.md b/DIPs/DIP-19.md
@@ -3,7 +3,7 @@ DIP: 19
 Title: Hosting DevCon Archive Videos on Swarm via Etherna
 Status: Accepted
 Themes: Virtual Experience, Website, Community Involvement
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Software, Event Operations, Communications
 Authors: Costanza Gallo costanza@ethswarm.org
 Resources Required: Operation support

diff --git a/DIPs/DIP-2.md b/DIPs/DIP-2.md
@@ -3,7 +3,7 @@ DIP: 2
 Title: Audius music in common areas and between talks at Devcon
 Status: Withdrawn
 Themes: Art & Beauty
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event Operations, Event Production
 Authors: roneil at the website audius.co
 Resources Required: Operational support

diff --git a/DIPs/DIP-20.md b/DIPs/DIP-20.md
@@ -3,7 +3,7 @@ DIP: 20
 Title: OPEN SOURCED ART from the HEART
 Status: Draft
 Themes: Social
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event Production
 Authors: Shaka Lei Kaumaka (@shakaleikaumaka), Matteo Tambussi (@matlemad), Camilo Cruz (@isdotlove)
 Discussion: https://forum.devcon.org/t/music-sessions-open-mic-stage/387

diff --git a/DIPs/DIP-21.md b/DIPs/DIP-21.md
@@ -3,7 +3,7 @@ DIP: 21
 Title: Building Web3 Developer Communities Hub
 Status: Not Implemented
 Themes: Social
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event Production
 Authors: sunny@superfluid.finance, fran@superfluid.finance
 Resources Required: Physical room at venue, Tech support, Basic Equipment (Furniture, Power Outlets, TV, etc.)

diff --git a/DIPs/DIP-22.md b/DIPs/DIP-22.md
@@ -3,7 +3,7 @@ DIP: 22
 Title: Design Community Hub at Devcon Bogota
 Status: Accepted
 Themes: Design, Experience
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Community Hub, Event Operations, Event Production
 Authors: amy@raw-haus.co
 Resources Required: Physical space at venue, Basic Equipment, On-site Operations/Technical Point Person to ask questions about setup 

diff --git a/DIPs/DIP-23.md b/DIPs/DIP-23.md
@@ -3,7 +3,7 @@ DIP: 23
 Title: CRYPTOMURALS - Street art hunting
 Status: Draft
 Themes: Social, Art & Beauty, Community Involvement, Public Goods.
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Software, Communications, Others.
 Authors: 0xnats@proton.me j.caraballose@gmail.com cryptomurals@gmail.com manu@doingud.com sanchit@doingud.com
 Resources Required: Development of the street art hunt platform by DoinGud, Production of 3 murals in Bogotá by ELAR,GAVILÁN & TONRA, Graffiti tour guides for 4 days, operations support.

diff --git a/DIPs/DIP-24.md b/DIPs/DIP-24.md
@@ -3,7 +3,7 @@ DIP: 24
 Title: Women Leaders in Web3 Community Hub at Devcon
 Status: Accepted
 Themes: Social, Community Involvement, Art & Beauty
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Community Hub, Event Production
 Authors: daphneacharles@gmail.com
 Resources Required: Physical space at venue, Signage, Comfortable chairs for AMA, panel, and DEI training sessions, Floor pillows for circle discussions, speed friending, and wellness activities, Screen, Desks for hands on workshops, Whiteboard

diff --git a/DIPs/DIP-25.md b/DIPs/DIP-25.md
@@ -3,7 +3,7 @@ DIP: 25
 Title: Live UX Research
 Status: Draft
 Themes: Design, Experience, Research
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event production, programming
 Authors: hester@uxenzo.com
 Resources Required: Physical space, Registration

diff --git a/DIPs/DIP-26.md b/DIPs/DIP-26.md
@@ -3,7 +3,7 @@ DIP: 26
 Title: Cryptoeconomics & Governance Community Hub 
 Status: Accepted
 Themes: Social
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Community Hub, Event Production
 Authors: Angela Kreitenweis (angela@tokenengineering.net), Eugene Leventhal (eugene@scrf.io). Patricia Brolezzi (patricia@tokenengineering.net)
 Resources Required: Physical space at venue, additional screens for the laptop connection if possible

diff --git a/DIPs/DIP-27.md b/DIPs/DIP-27.md
@@ -3,7 +3,7 @@ DIP: 27
 Title: Community Hub - Temporary Anonymous Zone
 Status: Accepted
 Themes: Community Involvement
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Community Hub, Event Production
 Authors: Althea <althea@ethereum.org>
 Resources Required: Physical space, signage, seating, screen

diff --git a/DIPs/DIP-28.md b/DIPs/DIP-28.md
@@ -3,7 +3,7 @@ DIP: 28
 Title: ZK Community Hub
 Status: Accepted
 Themes: Social, Community Involvement
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Community Hub, Event Production
 Authors: michael@0xparc.org, remy@0xparc.org
 Resources Required: Seating for discussion groups, TV-sized screen, Power Outlet, Signage, Desks and tables, Whiteboard

diff --git a/DIPs/DIP-29.md b/DIPs/DIP-29.md
@@ -3,7 +3,7 @@ DIP: 29
 Title: Regen Corner -- Devcon Bogota Community Hub
 Status: Accepted
 Themes: Social, Community Involvement, Environmental Sustainability, Art & Beauty
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Community Hub, Event Production, Regen
 Authors: sinouhe.monteironunes@gmail.com, bruno.regens.unite@outlook.com
 Resources Required: Seating/pillows for discussion groups, Access to the venue for session holders, Screen for showing schedule, Screen/tablet for POAP dispenser, Power outlet, Whiteboard or flipchart, Plants

diff --git a/DIPs/DIP-3.md b/DIPs/DIP-3.md
@@ -3,7 +3,7 @@ DIP: 3
 Title: Book your accommodation on-chain, 0% commissions paid to intermediaries.
 Status: Accepted
 Themes: Ticketing, Purchases & ID
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Attendee Experience
 Authors: Maksim Izmaylov <max@windingtree.com> & Luca Cosivi <luca@windingtree.com>
 Resources Required: Local contacts and Promotion on all channels including website

diff --git a/DIPs/DIP-30.md b/DIPs/DIP-30.md
@@ -3,7 +3,7 @@ DIP: 30
 Title: "'Climate Friendly Devcon VI' POAP Holders get lunch priority"
 Status: Accepted
 Themes: Environmental Sustainability
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event production
 Authors: danceratopz <danceratopz@gmail.com>, haurog <haurog@pm.me>
 Resources Required: Operational support

diff --git a/DIPs/DIP-4.md b/DIPs/DIP-4.md
@@ -3,7 +3,7 @@ DIP: 4
 Title: Treasure Hunt Game
 Status: Accepted
 Themes: Social
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event Production
 Authors: Alberto Granzotto <agranzot@mailbox.org>
 Resources Required: Communication support, Access to the venue before the event starts

diff --git a/DIPs/DIP-5.md b/DIPs/DIP-5.md
@@ -3,7 +3,7 @@ DIP: 5
 Title: Keycard at Devcon
 Status: Postponed
 Themes: Ticketing, Purchase & ID
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Attendee Experience
 Authors: Guy-Louis Grau <guylouis@status.im>
 Resources Required: Operational support, Communication support

diff --git a/DIPs/DIP-6.md b/DIPs/DIP-6.md
@@ -3,7 +3,7 @@ DIP: 6
 Title: Attestation based ticketing solution for Devcon
 Status: Accepted
 Themes: RFP-1 On-chain Ticketing
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event Operations, Event Production, Software
 Authors: Weiwu Zhang <weiwu.zhang@alphawallet.com>, Sunil Tom <sunil.tom.jose@alphawallet.com>, Victor Zhang <victor.zhang@alphawallet.com>
 Resources Required: software development, operations Support and tech support

diff --git a/DIPs/DIP-8.md b/DIPs/DIP-8.md
@@ -3,7 +3,7 @@ DIP: 8
 Title: Proof of Attendance Protocol - basics
 Status: Accepted
 Themes: Social
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Event Production
 Authors: Patricio Worthalter <worthalter@poap.xyz>
 Resources Required: Strong operations supports

diff --git a/DIPs/DIP-9.md b/DIPs/DIP-9.md
@@ -3,7 +3,7 @@ DIP: 9
 Title: Devcon 5.1
 Status: Not Implemented
 Themes: Virtual Experience
-Instances: [DEVcon6]
+Instances: [Devcon6]
 Tags: Other
 Authors: Cristian Espinoza (@crisgarner)
 Discussion: https://forum.devcon.org/t/devcon-5-1-or-devcon-6-alpha/71