Skip to content

Commit 240bebd

Browse files
ajithsureshtiiajithsureshtii
committed
Updated Readme v1.0
1 parent bddcbe3 commit 240bebd

1 file changed

Lines changed: 89 additions & 52 deletions

File tree

‎README.md‎

Lines changed: 89 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -1,76 +1,113 @@
1-
# Secure Multi-party Computation deadlines countdown
1+
# 🚀 MPC Deadlines Hub
22

3-
Based on [sec-deadlines](https://sec-deadlines.github.io)
3+
Welcome to the **MPC Deadlines Hub**, your one-stop destination for keeping track of the latest deadlines for top Multi-Party Computation (MPC) conferences, journals, and workshops! 📅✨
44

5-
## Adding/updating a conference
5+
## 🤔 What is MPC?
66

7-
* Read the data format description below. **Note that the timezone format sign is inverted** (e.g., UTC+7 is written as `Etc/GMT-7`). It's [not a bug][0]. I hate this format too. I'd be happy to move to a different timezone JavaScript library that uses a friendlier format, but I don't have time for that.
8-
* Update `_data/conferences.yml`. You can do that on Github or locally after forking the repo.
9-
* Send a pull request
7+
Secure Multi-party Computation (MPC) allows a set of mutually distrusting parties to perform a joint computation over their private inputs while preserving the privacy of their individual inputs. Curious to learn more? Check out this **[MPC overview](https://eprint.iacr.org/2020/300)**! 🔍🔐
108

11-
### Conference entry record
9+
## 🚀 Adding/updating a conference
10+
11+
Want to contribute? Awesome! Here’s how:
12+
13+
* Read the data format description below. **Note that the timezone format sign is inverted** (e.g., UTC+7 is written as `Etc/GMT-7`). It's [not a bug][0]. Yeah, we know—it’s weird. If you have a better JavaScript timezone library in mind, hit us up! 😅
14+
* Update `_data/conferences.yml`. You can do this directly on GitHub or locally after forking the repo.
15+
* Send a pull request. 🎉
16+
17+
💡 **Too lazy to create a pull request?** No worries! Drop a message on our **[Telegram Group](https://t.me/+sm414tMmhGhhNTA0)** 📢, and we’ll update the entries for you! 😎🚀
18+
19+
### ✅ Is my entry in scope?
20+
21+
This page is meant to host academic conferences, journals, workshops, and related event deadlines.
22+
23+
Ask yourself these questions before adding an entry:
24+
25+
- 📝 Is there a "Call For Papers"? A submission link? Formatting guidelines (page limits, style guides, etc.)?
26+
- 🔐 Does it mention 'secure multi-party computation', 'MPC', or 'privacy-preserving computing' in its topics?
27+
- 🧐 Is there a peer-review process? Are there named general/program chairs or a program committee?
28+
29+
If you answered **YES** to all of the above, congratulations! Your conference/workshop is a great fit! 🎯
30+
31+
### 🏆 Conference entry record
1232

1333
Example record:
1434

1535
```
16-
- name: Euro S&P
17-
description: IEEE European Symposium on Security and Privacy
18-
year: 2018
19-
link: http://www.ieee-security.org/TC/EuroSP2018/
20-
deadline: "2017-08-15 23:59"
21-
date: April 24-26
22-
place: London, UK
23-
tags: [PRACT, APPLIED]
36+
- name: ACM CCS
37+
description: ACM Conference on Computer and Communications Security
38+
year: 2025
39+
link: https://www.sigsac.org/ccs/CCS2025/
40+
abdeadline: Jan 02, Apr 07
41+
deadline:
42+
- "2025-01-09 23:59"
43+
- "2025-04-14 23:59"
44+
rebut: March 06-19, June 09-22
45+
date: October 13-17
46+
place: Taipei, Taiwan
47+
comment: 2 deadlines. Notifications - March 27, June 30.
48+
tags: [PRACT, APPLIED, CNF, COREAS]
2449
```
2550

26-
Descriptions of the fields:
51+
📌 **Notes:**
52+
53+
- For an event with a **single deadline**, make sure to put the deadline in square brackets, like this:
54+
```
55+
deadline: ["2025-04-01 23:59"]
56+
```
57+
- Not all fields are mandatory! Just add the relevant ones. 😊
58+
59+
- The events are listed in alphabetical order grouped by the categories. Please make sure to have consistency while updating the entries.
60+
61+
62+
### 🔍 Field descriptions
2763

2864
| Field name | Description |
29-
|---------------|-------------------------------------------------------------|
30-
| `name`\* | Short conference name, without year |
31-
| `year`\* | Year the conference is happening |
32-
| `description` | Description, or long name |
33-
| `link`\* | URL to the conference home page |
34-
| `deadline`\* | Deadline, or list of deadlines. (Gory details below) |
35-
| `timezone` | Timezone in [tz][1] format. By default is UTC-12 ([AoE][2]) |
36-
| `date` | When the conference is happening |
37-
| `place` | Where the conference is happening |
38-
| `tags` | One or multiple tags: `THEORY`, `PRACT`, or `WK` |
65+
|--------------|-------------------------------------------------------------|
66+
| `name`* | Short conference name (no year) |
67+
| `description` | Long name or a brief description |
68+
| `year`* | Year the conference is happening |
69+
| `link`* | URL to the conference homepage |
70+
| `abdeadline` | Registration and/or abstract deadline. |
71+
| `deadline`* | Submission deadline(s) |
72+
| `rebut` | Rebuttal window |
73+
| `timezone` | Timezone in [tz][1] format (Default: UTC-12, [AoE][2]) |
74+
| `date` | When the conference is happening |
75+
| `place` | Conference location |
76+
| `tags` | One or more tags as detailed below. |
3977

40-
Fields marked with asterisk (\*) are required.
78+
📌 **Please try to maintain consistency in the order of the fields when updating an entry.**
4179

80+
### 📌 Special Case of Workshops
4281

43-
### Deadline format
82+
Workshops can be a bit special! Here’s what to keep in mind when adding them:
4483

45-
The *deadline* field can contain:
84+
- If the workshop is **affiliated with a conference**, make sure to add the `conference` tag, specifying the name of the main conference. For example:
85+
```
86+
conference: CCS.
87+
```
88+
This helps keep things clear and organized! 🔍
4689

47-
1. The simplest option: a date and time in ISO format. Example: `"2017-08-19 23:59"`.
48-
2. If a deadline is rolling, you can use a template date, just substitute the year with `%y`, or month with `%m`. Example: `"%y-%m-15 23:59"` means there is a deadline on the 15th day of every month, every year. `"2017-%m-15"` means a deadline on 15th day of every month, but only in 2017, i.e. `"2018-01-15"` is not a part of this template.
49-
2. A list of (1) or (2). Example of two rolling deadlines, with one in the end of May every year, and the second in the end of February:
50-
```
51-
- "%y-05-31 23:59"
52-
- "%y-02-28 23:59"
53-
```
5490

55-
On the page, all deadlines are displayed in viewer's local time (that's a feature).
91+
### 🏷️ Tags - Shortlisting Made Easy! 🚀
92+
93+
We use three sets of tags that act as filters to help you quickly find relevant entries.
94+
95+
- **First filter**: Research Domain (e.g., THEORY, PRACT, APPLIED, etc.)
96+
- **Second filter**: Publication Type (e.g., CNF, JRN, WK, PS, etc.)
97+
- **Third filter**: [CORE](https://portal.core.edu.au/conf-ranks/) Ranking (e.g., COREAS, COREA, COREB, etc.)
98+
99+
For the full list of tags, check out [`/_data/filters.yml`](https://github.com/mpc-deadlines/mpc-deadlines.github.io/blob/main/_data/filters.yml). 🏷️
56100

57-
*Note:* If the deadline hour is `{h}:00`, it will be automatically translated into `{h-1}:59:59` to avoid pain and confusion when it happens to be midnight in local time.
101+
### 🔥 Special Case: `EXP` Tag
58102

59-
### Timezones
103+
For an event that has been **announced** but the Call for Papers is **not yet available**, you can still add an entry! Just make sure to:
104+
- Include the `EXP` tag.
105+
- Fill in details based on the **previous year’s** event.
106+
- This will internally set some of the fields to default placeholder values (e.g., `comment: "CFP yet to be announced"`).
60107

61-
The timezone is specified in [tz format][1]. Unlike abbreviations (e.g. EST), these are un-ambiguous. Here are tz codes for some common timezones:
108+
🔥 **Let's make MPC deadlines easy to track—together!** 🚀
62109

63-
| Common name | tz |
64-
|-------------------------------|--------------------------------------------------------------------|
65-
| UTC | `Etc/UTC` |
66-
| America Pacific Time | `America/Los_Angeles` |
67-
| Pacific Standard Time (UTC-8) | `Etc/GMT+8` (Yes, the sign is inverted for some weird reason) |
68-
| America Eastern Time | `America/New_York` |
69-
| Eastern Standard Time (UTC-5) | `Etc/GMT+5` |
70-
| American Samoa Time (UTC-11) | `Pacific/Samoa` or `Etc/GMT+11`. This timezone does not use DST. |
71-
| Aleutian Islands | `America/Adak` |
72110

73-
[0]: https://momentjs.com/timezone/docs/#/zone-object/offset/
74-
[1]: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
75-
[2]: https://www.timeanddate.com/time/zones/aoe
111+
## 🙏 Acknowledgements
76112

113+
Thanks to the amazing **[sec-deadlines](https://sec-deadlines.github.io)** page, which inspired the initial version of this hub. 🙌

0 commit comments

Comments
 (0)