Skip to content

Commit a5fc607

Browse files
authored
Merge pull request #43 from web3kitty/main
Docs update - Q1 2025
2 parents 6ac62dc + b2173ba commit a5fc607

File tree

10 files changed

+143
-232
lines changed

10 files changed

+143
-232
lines changed

src/content/docs/events/congress.md

Lines changed: 0 additions & 23 deletions
This file was deleted.

src/content/docs/events/index.mdx

Lines changed: 16 additions & 153 deletions
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,28 @@ sidebar:
77

88
import { LinkCard } from '@astrojs/starlight/components';
99

10-
| Lead | Links | Workgroup |
10+
| Lead | Website | Registration |
1111
| --- | --- | --- |
12-
| anon | • Events list: [web3privacy.info/events](https://web3privacy.info/events)<br/> • lu.ma calendar: [lu.ma/web3privacy](https://lu.ma/web3privacy) | [Matrix](https://matrix.to/#/#w3p-events:gwei.cz) |
12+
| anon | [web3privacy.info/events](https://web3privacy.info/events) | [lu.ma/web3privacy](https://lu.ma/web3privacy) |
1313

1414
## Concept
1515

1616
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".
1717

1818
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.
1919

20-
## List of events
20+
## Related Documentation
21+
22+
<LinkCard title="Events page on website" href="https://web3privacy.info/events" />
23+
<LinkCard title="JSON output of data codebase" href="https://data.web3privacy.info" />
24+
<LinkCard title="Summary of Event Seasons" href="/events/seasons" />
25+
<LinkCard title="Event Types specifications" href="/events/types" />
26+
<LinkCard title="Event Formats specifications" href="/events/formats" />
27+
<LinkCard title="Event Call for Proposals (cfp) specifications" href="/events/types" />
28+
<LinkCard title="Event Recording guidelines" href="/events/recording" />
29+
<LinkCard title="Event Production guidelines" href="/events/types" />
30+
2131

22-
<LinkCard title="List of all events on our website" href="https://web3privacy.info/events" />
2332

2433
![screenshot of Events webpage](../assets/events-list.png)
2534

@@ -29,17 +38,10 @@ A machine-readable list of all our events and their details is available:
2938

3039
* Dataset (JSON format): [data.web3privacy.info](https://data.web3privacy.info/)
3140
* Source: [github.com/web3privacy/data/tree/main/src/events](https://github.com/web3privacy/data/tree/main/src/events)
32-
33-
The source files with basic data about our events can be found in our `data` [Git repository](/contributors/git):
34-
35-
* [`@web3privacy/data`](https://github.com/web3privacy/data) (`src/events` directory)
36-
* Feel free to add an event by making a PR to the web3privacy/data/src/events
41+
* The source files with basic data about our events can be found in our `data`: [`@web3privacy/data`](https://github.com/web3privacy/data)
42+
* Feel free to add an event by making a PR to the web3privacy/data repository
3743
* Please do read this docs page in full and respect the naming convention noted here
38-
* For more please read the [how to add an event to website guide](/contributors/add-event-to-website)
39-
40-
| Guide | Link |
41-
| --- | ---- |
42-
| Adding a new event to website | [Link to this Guide in Docs](/contributors/add-event-to-website) |
44+
* Guide on [how to add an event to website guide](/contributors/add-event-to-website)
4345

4446
## Naming conventions
4547

@@ -81,13 +83,6 @@ The name of the event is based on its type, geographical location and year:
8183
* `Web3Privacy Now <event-type> <city> <year>`
8284
* `W3PN <event-type> <city> <year>`
8385

84-
For internal referencing its possible to skip `W3PN` or `Web3Privacy Now` part.
85-
86-
Examples:
87-
* `Web3Privacy Now Summit Prague 2024`
88-
* `W3PN Hackathon Rome 2024`
89-
* `Meetup Bucharest 2024` (internal)
90-
9186
## Seasons
9287

9388
In terms of time, everything is divided into individual programme seasons or planning periods. For us, this is the calendar year.
@@ -102,25 +97,6 @@ Within the season, all events are prepared together as one package. This also ap
10297

10398
Each season as a whole has a predetermined budget that we want to raise from sponsors and donors. These funds are then used to cover the costs associated with organising these events.
10499

105-
The Season Budget consists of budget approved by Web3Privacy Now [Treasury](/governance/treasury).
106-
107-
## Regions
108-
109-
The basic division by location is into major regions according to wider regions or continents (e.g. Europe, LATAM, etc.).
110-
111-
### [Regional teams](/events/regional-teams)
112-
113-
[Regional teams](/events/regional-teams) are responsible for organising events in a specific region. We only start doing events within a region if we have enough people forming a [regional organization team](/events/regional-teams).
114-
115-
### Regions we cover (2024)
116-
117-
For the 2024 season, we want to cover the following regions:
118-
119-
* **Europe** - Europe regional team (EthCC, ETHBerlin, ETHDam, ETHPrague and many more)
120-
* **Devcon (Southeast Asia)**
121-
122-
Our goal in each region is to spread the events evenly, both in time and space across the entire region (or important events that take place there).
123-
124100
## Date and location
125101

126102
Most of our events are held in conjunction with another major Ethereum event in the region (e.g. Devcon(nect), EthCC, ETHBerlin, ETHPrague, etc.).
@@ -151,116 +127,3 @@ The standard duration of one slot is 30 minutes.
151127
At each event, the program is made up of [slots](#slots) that are filled with different formats.
152128

153129
Example: *Talk, Workshop, Panel discussion* etc.
154-
155-
## Production
156-
157-
### Budget
158-
159-
Funds to pay for event expenses and services come from the shared [Season Budget](#season-budget) dedicated for the season.
160-
161-
The amount to be provided for a particular event depends on the [type of event](/events/types), its duration and other parameters.
162-
163-
### Visual identity & Merch
164-
165-
At [this link](https://drive.proton.me/urls/VH7K4YNASM#4MiUNarejsUJ) you can find and download all the files to print posters, tshirts, and stickers.
166-
167-
### Catering
168-
169-
The food and drink provided at a particular event is based on other circumstances, such as the amount of admission or duration of the event. Basically, we try to provide our visitors with as much comfort as possible without spending too much.
170-
171-
On the shortest Meetups there is minimal catering water and snacks like fruit, bagels, pizza or similar.
172-
173-
At longer Summits or Hackathons (or paid events) we try to offer a full range of food and drink, including lunch, dinner and various desserts and drinks (incl. beer).
174-
175-
### Content recording
176-
177-
All content at all our events (Meetup, Summit, Hackathon, Congress) is recorded. For this purpose we use local Recording setup provided by third parties or from the videomaker.
178-
179-
During the event we also record interviews with our own low-cost equipment.
180-
181-
Larger events such as the Summits can also be streamed online.
182-
183-
## Visitors
184-
185-
### Admission
186-
187-
Whether a particular event is free or we charge admission will depend on the context. The entrance fee and its amount are mainly taken as a tool for self-regulation of the number and quality of visitors.
188-
189-
We will apply admission fees where we expect a lot of interest and, on the contrary, events in less busy periods should be free of charge, which will serve as an incentive for visitors.
190-
191-
All our [members](/get-involved/personal-benefits) have a **free admission** to event, even if an entry fee is applied.
192-
193-
### Pre-registration
194-
195-
With the start of each [season](#seasons) we will start pre-registration for **all events** within that season. Potential visitors will be able to express their preferences for when and where they want to attend our events.
196-
197-
The only private information we collect for pre-registration will be name and email. Visitors are advised to use a [privacy email provider](https://www.privacytools.io/privacy-email) like [Skiff Mail](https://skiff.com/mail) or [Proton Mail](https://proton.me/mail).
198-
199-
Pre-registration will be done through temporary event profiles on the [lu.ma platform](https://lu.ma/web3privacy).
200-
201-
Approximately 2-3 months prior to the event, the final registration will open and all people will be notified via the email they entered during pre-registration (see [Ticketing](#ticketing)).
202-
203-
#### Donation methods
204-
205-
We usually accept these donation methods:
206-
* fiat
207-
* cash
208-
* cryptocurrencies
209-
* BTC, BTC (Lightning)
210-
* ETH and stablecoins
211-
* XMR
212-
* zcash
213-
214-
You can find donation addresses and instructions [here](https://docs.web3privacy.info/get-involved/donate/)
215-
216-
## Speakers
217-
218-
We are looking for speakers for all events combined using a single [Call for Proposal (CfP)](/events/cfp) form.
219-
220-
Within this form, speakers are able to choose the months and locations that suit them. This will offer speakers great flexibility in when and where they can present their ideas or projects.
221-
222-
## Partners
223-
224-
If you are interested in visibility of your organization at our events, then we have the following options for you:
225-
226-
### Members (highest form of partnership)
227-
228-
Your organisation can become a [Member](/get-involved/org-benefits) of Web3Privacy Now and automatically gain visibility at our events, depending on the Tier choosen.
229-
230-
### Sponsors
231-
232-
Sponsors are our value-aligned partners who help us maintain financial sustainability. They support our mission by contributing to all our activities, whether it’s a research project, an event, a merchandise release.
233-
234-
Please [contact us](/about-us//contact-us) for more details.
235-
236-
### Media partners
237-
238-
It is possible to become a general partner for all events, or just a partner for a specific event. Please [contact us](/about-us//contact-us) for more details.
239-
240-
### Community partners
241-
242-
We offer local non-profit organizations and communities the opportunity to become a community partner for a specific event. Please [contact us](/about-us/contact-us) for more details.
243-
244-
## Volunteers
245-
246-
TODO
247-
248-
## Privacy
249-
250-
We respect the privacy of our visitors and are therefore guided by the following principles.
251-
252-
**Please respect the privacy of others!**
253-
254-
### No-photo policy
255-
256-
It is forbidden to take any photographs or video recordings of visitors at our events (except on stage) unless they give their express permission.
257-
258-
As organizers, we don't share any such photos, and if we do - it's only with anonymized faces of visitors.
259-
260-
### No personal data sharing
261-
262-
We do not provide the personal information about visitors or other involved people to any other party.
263-
264-
## Code of Conduct
265-
266-
Our events are guided by our community [Code of Conduct](/get-involved/code-of-conduct).
Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
---
2+
title: Event Production
3+
---
4+
5+
# W3PN Event Production Documentation
6+
7+
## Budget
8+
9+
Funds to pay for event expenses and services come from the shared [Season Budget](#season-budget) dedicated for the season.
10+
11+
The amount to be provided for a particular event depends on the [type of event](/events/types), its duration and other parameters.
12+
13+
## Visual identity & Merch
14+
15+
At [this link](https://drive.proton.me/urls/VH7K4YNASM#4MiUNarejsUJ) you can find and download all the files to print posters, tshirts, and stickers.
16+
17+
## Catering
18+
19+
The food and drink provided at a particular event is based on other circumstances, such as the amount of admission or duration of the event. Basically, we try to provide our visitors with as much comfort as possible without spending too much.
20+
21+
On the shortest Meetups there is minimal catering water and snacks like fruit, bagels, pizza or similar.
22+
23+
At longer Summits or Hackathons (or paid events) we try to offer a full range of food and drink, including lunch, dinner and various desserts and drinks (incl. beer).
24+
25+
## Content recording
26+
27+
All content at all our events (Meetup, Summit, Hackathon, Congress) is recorded. For this purpose we use local Recording setup provided by third parties or from the videomaker.
28+
29+
During the event we also record interviews with our own low-cost equipment.
30+
31+
Larger events such as the Summits can also be streamed online.
32+
33+
## Visitors
34+
35+
### Admission
36+
37+
Whether a particular event is free or we charge admission will depend on the context. The entrance fee and its amount are mainly taken as a tool for self-regulation of the number and quality of visitors.
38+
39+
We will apply admission fees where we expect a lot of interest and, on the contrary, events in less busy periods should be free of charge, which will serve as an incentive for visitors.
40+
41+
All our [members](/get-involved/personal-benefits) have a **free admission** to event, even if an entry fee is applied.
42+
43+
### Pre-registration
44+
45+
With the start of each [season](#seasons) we will start pre-registration for **all events** within that season. Potential visitors will be able to express their preferences for when and where they want to attend our events.
46+
47+
The only private information we collect for pre-registration will be name and email. Visitors are advised to use a [privacy email provider](https://www.privacytools.io/privacy-email) like [Skiff Mail](https://skiff.com/mail) or [Proton Mail](https://proton.me/mail).
48+
49+
Pre-registration will be done through temporary event profiles on the [lu.ma platform](https://lu.ma/web3privacy).
50+
51+
Approximately 2-3 months prior to the event, the final registration will open and all people will be notified via the email they entered during pre-registration (see [Ticketing](#ticketing)).
52+
53+
## Speakers
54+
55+
We are looking for speakers for all events combined using a single [Call for Proposal (CfP)](/events/cfp) form.
56+
57+
Within this form, speakers are able to choose the months and locations that suit them. This will offer speakers great flexibility in when and where they can present their ideas or projects.
58+
59+
## Partners
60+
61+
If you are interested in visibility of your organization at our events, then we have the following options for you:
62+
63+
## Members (highest form of partnership)
64+
65+
Your organisation can become a [Member](/get-involved/org-benefits) of Web3Privacy Now and automatically gain visibility at our events, depending on the Tier choosen.
66+
67+
## Sponsors
68+
69+
Sponsors are our value-aligned partners who help us maintain financial sustainability. They support our mission by contributing to all our activities, whether it’s a research project, an event, a merchandise release.
70+
71+
Please [contact us](/about-us//contact-us) for more details.
72+
73+
## Media partners
74+
75+
It is possible to become a general partner for all events, or just a partner for a specific event. Please [contact us](/about-us//contact-us) for more details.
76+
77+
## Community partners
78+
79+
We offer local non-profit organizations and communities the opportunity to become a community partner for a specific event. Please [contact us](/about-us/contact-us) for more details.
80+
81+
## Privacy
82+
83+
We respect the privacy of our visitors and are therefore guided by the following principles.
84+
85+
**Please respect the privacy of others!**
86+
87+
## Volunteer management
88+
89+
## No-photo policy
90+
91+
It is forbidden to take any photographs or video recordings of visitors at our events (except on stage) unless they give their express permission.
92+
93+
As organizers, we don't share any such photos, and if we do - it's only with anonymized faces of visitors.
94+
95+
## No personal data sharing
96+
97+
We do not provide the personal information about visitors or other involved people to any other party.
98+
99+
## Code of Conduct
100+
101+
Our events are guided by our community [Code of Conduct](/get-involved/code-of-conduct).

src/content/docs/events/regional-teams.md

Lines changed: 0 additions & 11 deletions
This file was deleted.

src/content/docs/events/seasons.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,9 @@ sidebar:
66

77
| Season | Regions | Events | Countries | Talks | People | Budget |
88
| --- | --- | --- | --- | --- | --- | --- |
9-
| *2024* | Europe, Devcon | >15 | >10 | >70 | >1000 | $100-150k |
10-
| **2023** | Europe | 3 | 2 | 29 | 334 | ~$16k |
9+
| *2026* | TBD | >15 | >10 | >70 | >1000 | $100-150k |
10+
| *2025* | Europe, LATAM | >15 | >10 | >70 | >1000 | $100-150k |
11+
| *2024* | Europe, Asia | >15 | >10 | >70 | >1000 | $100-150k |
12+
| *2023* | Europe | 3 | 2 | 29 | 334 | ~$16k |
1113

12-
Last updated: 16.03.2024
14+
Last updated: 7.03.2025

0 commit comments

Comments
 (0)