Add structure for speakers

Author: cmaureir

README.md

@@ -19,13 +19,13 @@ most in Python conferences, similarly to the most active speakers.
 
 # How to contribute?
 
-For each missing conference in the JSON file, find the information by visiting official 
-websites, archives, and past event pages. For each year, document the sponsorship tiers 
-and costs in a `levels` object (e.g., `"Gold": 10000`), then create an array under that 
-year listing all sponsors with their name, website, and sponsorship level. Find this 
-information from conference websites, sponsor pages, event programs (often PDFs), social 
-media posts, and press releases. Ensure accuracy of sponsor names and URLs, verify 
-sponsorship levels match the documented tiers for that specific year, and maintain 
+For each missing conference in the JSON file, find the information by visiting official
+websites, archives, and past event pages. For each year, document the sponsorship tiers
+and costs in a `levels` object (e.g., `"Gold": 10000`), then create an array under that
+year listing all sponsors with their name, website, and sponsorship level. Find this
+information from conference websites, sponsor pages, event programs (often PDFs), social
+media posts, and press releases. Ensure accuracy of sponsor names and URLs, verify
+sponsorship levels match the documented tiers for that specific year, and maintain
 consistent formatting as shown in the existing `sponsors.json` structure.
 
 Remember to submit a Pull Request with the information and adding the
@@ -35,3 +35,17 @@ conference and year to this README.
 You can open new issues by providing a URL for the conference,
 sponsorship packages details and list of sponsors, so others can extract
 the information. This would be helpful as well!
+
+## Speaker information
+
+The fields for speakers are the following:
+* Full name: extracted from the proposals
+* URL: only if the speaker provided such information for that specific event,
+    this cannot be enriched with other information without their permission.
+    The first field to fetch is Personal website, or the first social media URL
+    that was provided. Please **do not** add more than one URL per speaker.
+* Type: This fields is to point if the proposal was a Poster, Tutorial, Talk,
+    etc.
+* Title: Title of the proposal
+* Level: If provided by the schedule. If two levels are displayed, pick the
+    most general one

speakers.json

@@ -0,0 +1,15 @@
+{
+    "EuroPython": {
+        "2025": {
+            "speakers": [
+                {
+                    "fullname": "",
+                    "url": "",
+                    "type": "",
+                    "title": "",
+                    "level": ""
+                }
+            ]
+        }
+    }
+}