mirror of
https://github.com/web3privacy/docs
synced 2024-10-15 18:46:26 +02:00
naming & id convetions for events
This commit is contained in:
parent
583350e16c
commit
c3e96f7fd9
3 changed files with 71 additions and 24 deletions
|
@ -5,27 +5,25 @@ sidebar_label: Events Introduction
|
|||
|
||||
# Events
|
||||
|
||||
| Lead | Links | Workgroup |
|
||||
| --- | --- | --- |
|
||||
| @Tree | • Events list: [web3privacy.info/events](https://web3privacy.info/events)<br/> • lu.ma calendar: [lu.ma/web3privacy](https://lu.ma/web3privacy) | [PM](https://github.com/orgs/web3privacy/projects/7), [GitHub](https://github.com/web3privacy/events), [Matrix](https://matrix.to/#/#w3p-events:gwei.cz) |
|
||||
|
||||
## Concept
|
||||
|
||||
Our event concept is based on creating a unified schedule of events for the entire season and spreading events over whole year and different locations. Instead of just doing one huge event in one location that only happens for a day or two, we are trying to create something like a "distributed conference".
|
||||
|
||||
We aim to produce high quality events that bring a very similar atmosphere and content to many venues around the world, providing a unique experience for visitors, speakers and other participants.
|
||||
|
||||
## List of events
|
||||
|
||||
All our events and RSVPs can be found on our website:
|
||||
|
||||
* [web3privacy.info/events](https://web3privacy.info/events)
|
||||
|
||||
import EventListScreen from '../assets/events-list.png';
|
||||
|
||||
<a href="https://web3privacy.info/events"><img src={EventListScreen} width="75%" /></a>
|
||||
|
||||
### Lu.ma calendar
|
||||
|
||||
Alternatively, announced events are available in our lu.ma calendar:
|
||||
|
||||
* [lu.ma/web3privacy](https://lu.ma/web3privacy)
|
||||
|
||||
## Source data
|
||||
## Structured data source
|
||||
|
||||
The source files with basic data about our events can be found in our `data` [Git repository](/git):
|
||||
|
||||
|
@ -33,6 +31,41 @@ The source files with basic data about our events can be found in our `data` [Gi
|
|||
|
||||
Feel free to edit or modify!
|
||||
|
||||
## Naming conventions
|
||||
|
||||
### Unique event identifier (ID)
|
||||
|
||||
Each event has an assigned unique identifier for referencing.
|
||||
|
||||
The event identifier consists of:
|
||||
|
||||
| Length | Description | Example |
|
||||
| --- | --- | --- |
|
||||
| 1 letter | code of [event type](/events/types) | `s` |
|
||||
| 2 letter | calendar year | `24` |
|
||||
| 2-3 letters | pseudo city/event code | `prg` |
|
||||
| 1 letter | sequence number (optional) | - |
|
||||
|
||||
Example identifiers:
|
||||
* `s24prg` - summit in Prague 2024
|
||||
* `m24dc` - meetup near Devcon 2024
|
||||
* `c25be` - Privacy Corner on MoneroKon 2025
|
||||
* `m25prg2` - second meetup in Prague 2025
|
||||
|
||||
### Name of the event
|
||||
|
||||
The name of the event is based on its type, geographical location and year:
|
||||
|
||||
* `Web3Privacy Now <event-type> <city> <year>`
|
||||
* `W3PN <event-type> <city> <year>`
|
||||
|
||||
For internal referencing its possible to skip `W3PN` or `Web3Privacy Now` part.
|
||||
|
||||
Examples:
|
||||
* `Web3Privacy Now Summit Prague 2024`
|
||||
* `W3PN Hackathon Bled 2024`
|
||||
* `Meetup Bucharest 2024` (internal)
|
||||
|
||||
## Seasons
|
||||
|
||||
In terms of time, everything is divided into individual programme seasons or planning periods. For us, this is the calendar year.
|
||||
|
@ -79,11 +112,9 @@ We are also preparing a couple of separate events within the season, which are i
|
|||
|
||||
## Event types
|
||||
|
||||
We divide events into the following types according to their length and goal:
|
||||
We divide events into different types according to their length and purpose.
|
||||
|
||||
* [Hackathon](./types#hackathon) - a multi-day event including hacking
|
||||
* [Summit](./types#summit) - a day-long gathering
|
||||
* [Meetup](./types#meetup) - shorter gatherings for a few hours
|
||||
Example: *Summit, Meetup, Hackathon* etc.
|
||||
|
||||
[List of event types →](./types)
|
||||
|
||||
|
@ -99,6 +130,8 @@ The standard duration of one slot is 30 minutes.
|
|||
|
||||
At each event, the program is made up of [slots](#slots) that are filled with different formats.
|
||||
|
||||
Example: *Talk, Workshop, Panel discussion* etc.
|
||||
|
||||
[List of program formats →](./formats)
|
||||
|
||||
## Production
|
||||
|
|
|
@ -8,20 +8,28 @@ We divide events into the following types according to their length and goal:
|
|||
|
||||
## Overview
|
||||
|
||||
| Type | [Slots](/events#slots) | Budget | Description |
|
||||
### Main types
|
||||
|
||||
| Type (code) | [Slots](/events#slots) | Budget | Description |
|
||||
| --- | --- | --- | --- |
|
||||
| [Hackathon](#hackathon) | *variable* | $25-50k | a multi-day event including hacking |
|
||||
| [Summit](#summit) | 10 - 16 | $15-30k | a day-long gathering |
|
||||
| [Meetup](#meetup) | 3 - 5 | $1-2k | shorter gatherings for a few hours |
|
||||
| [Meetup](#meetup) (`m`) | 3 - 5 | $1-2k | shorter gatherings for a few hours |
|
||||
| [Summit](#summit) (`s`) | 10 - 16 | $15-30k | a day-long gathering |
|
||||
| [Hackathon](#hackathon) (`h`) | *variable* | $25-50k | a multi-day event including hacking |
|
||||
|
||||
### Associated types
|
||||
|
||||
| Type (code) | [Slots](/events#slots) | Budget | Description |
|
||||
| --- | --- | --- | --- |
|
||||
| [Privacy Corner](https://github.com/web3privacy/privacy-corner) (`c`) | - | $3-10k | pop-up space inside of major hackathons |
|
||||
| Congress (`x`) | - | ? | W3PN governance gathering |
|
||||
|
||||
## Details of types
|
||||
### Hackathon
|
||||
|
||||
A hackathon is usually a multi-day event focused on creation. What makes it different from other types is that it should end with some work being done, whether it's some privacy-focused projects or pushing our own projects forward.
|
||||
### Meetup
|
||||
|
||||
A Hackathon is usually accompanied by one or more Meetups, or possibly a Summit.
|
||||
A meetup is a shorter type of event for 2-6 hours (usually afternoon/evening).
|
||||
|
||||
The number of slots at the hackathon is very flexible.
|
||||
The number of slots at a meetup is usually 3-5.
|
||||
|
||||
### Summit
|
||||
|
||||
|
@ -29,8 +37,10 @@ The Summit is an all-day event, usually followed by an afterparty.
|
|||
|
||||
Summit is usually made up of 10-16 slots.
|
||||
|
||||
### Meetup
|
||||
### Hackathon
|
||||
|
||||
A meetup is a shorter type of event for 2-6 hours (usually afternoon/evening).
|
||||
A hackathon is usually a multi-day event focused on creation. What makes it different from other types is that it should end with some work being done, whether it's some privacy-focused projects or pushing our own projects forward.
|
||||
|
||||
The number of slots at a meetup is usually 3-5.
|
||||
A Hackathon is usually accompanied by one or more Meetups, or possibly a Summit.
|
||||
|
||||
The number of slots at the hackathon is very flexible.
|
|
@ -4,6 +4,10 @@ sidebar_label: Week in the Privacy
|
|||
|
||||
# Week in the Privacy News
|
||||
|
||||
| Lead | Links | Workgroup |
|
||||
| --- | --- | --- |
|
||||
| @Tree | • Web: [news.web3privacy.info](https://news.web3privacy.info/)<br/> • newsletter: [paragraph.xyz/@privacynews](https://paragraph.xyz/@privacynews) | [GitHub](https://github.com/web3privacy/news), [Matrix](https://matrix.to/#/#w3p-news:gwei.cz) |
|
||||
|
||||
Weekly newsletter with round-up of the most important news happening around privacy in Web3.
|
||||
|
||||
* [Subscribe now!](https://paragraph.xyz/@privacynews/subscribe)
|
||||
|
|
Loading…
Reference in a new issue