Skip to content

Commit 7ca5338

Browse files
ajithsureshtiiajithsureshtii
committed
deploy: 21f9bd1 
1 parent b579c44 commit 7ca5338

40 files changed

Lines changed: 24704 additions & 0 deletions

‎preview/pr-18/LICENSE‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2021 Ajith Suresh
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

‎preview/pr-18/README.md‎

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
# 🚀 MPC Deadlines Hub
2+
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! 📅✨
4+
5+
## 🤔 What is MPC?
6+
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)**! 🔍🔐
8+
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
32+
33+
Example record:
34+
35+
```
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]
49+
```
50+
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
63+
64+
| Field name | Description |
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. |
77+
78+
📌 **Please try to maintain consistency in the order of the fields when updating an entry.**
79+
80+
#### 📌 Special Case of Workshops
81+
82+
Workshops can be a bit special! Here’s what to keep in mind when adding them:
83+
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! 🔍
89+
90+
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). 🏷️
100+
101+
#### 🔥 Special Case: `EXP` Tag
102+
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"`).
107+
108+
#### 🔥 Special Case: `EXPCFP` Tag
109+
110+
Sometimes, an event is already **confirmed** and has public details like **dates, location, and venue**, but the **CFP hasn't been published yet**. In this case, use the `EXPCFP` tag.
111+
112+
- This is a more specific version of the `EXP` tag.
113+
- Use `EXPCFP` when the event is definitely happening, but the CFP is **not yet available**.
114+
- As with `EXP`, base your entry on the most recent available details.
115+
116+
This helps signal to others that the event is expected, even though submission details are still pending. 🔍
117+
118+
🔥 **Let's make MPC deadlines easy to track—together!** 🚀
119+
120+
121+
## 🙏 Acknowledgements
122+
123+
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)