ccfddl/ccf-deadlines

What it does

CCF-Deadlines keeps a structured, community-maintained database of submission deadlines for CCF-ranked and other worldwide conferences. It publishes that data through the main website, a tabular portal, a WeChat applet, and a range of clients. The core data lives in YAML files under conference/<sub>/<conf>.yml, so deadlines, timezones, rank labels and official conference links can be reviewed and corrected in pull requests.

The project targets researchers and students who need to plan submissions around CCF/CORE/TH-CPL ranks, and it is also useful for tool builders who want to consume the deadline data. Beyond the web views, there are iCal subscriptions, a Python CLI, a Chrome extension, a Raycast extension, a TUI app, and an agent-oriented MCP server.

Quick start

To browse deadlines, open ccfddl.com and search or filter by venue and rank. If you prefer a lightweight table view, use the tabular portal with no login required.

To add or fix a conference, fork the repository, edit the YAML file for that venue, and open a pull request:

git clone https://github.com/<your-account>/ccf-deadlines.git
cd ccf-deadlines
# edit conference/DB/sigmod.yml

A typical entry records title, description, sub, rank, dblp, and one or more confs entries with year, id, link, timeline deadlines, timezone, date, and place (field reference). The repository asks contributors to use 23:59:59 when only a calendar date is published, and AoE when no timezone is given; leave a date as TBD if it is genuinely unpublished. Then push the branch and open a pull request. Check the CCF category list or the recommended-conference PDF when deciding how to classify a venue.

Using the data and extensions

The MCP server at https://ccfddl.com/mcp is read-only and supports searching conferences, checking deadlines and opening dates, retrieving historical acceptance rates, filtering by CCF/CORE/TH-CPL, pagination, and timezone conversion. It is meant for AI clients that speak the Model Context Protocol; the MCP README has the connection details. The CLI, calendar, Chrome, and TUI clients live in their own subdirectories or repositories, so their install steps are separate from the YAML contribution workflow.

Constraints

Deadline accuracy depends on community contributions and must be checked against official conference pages when a submission is critical. The schema requires title, description, sub, ccf, dblp, year, id, link, timeline.deadline, timezone, date, and place; optional fields include abstract, rebuttal, and decision deadlines along with comments. Timezone support covers UTC-12 through UTC+12, plus AoE and PT with automatic daylight-saving adjustment. The project is MIT-licensed.

HotRepo's take

There is no recorded daily-ranking, snapshot, or HN discussion data for this project in the supplied HotRepo material, so this note is limited to the repository itself. What stands out is the breadth of delivery channels: the same YAML deadline records feed a website, an iCal subscription, a Chrome extension, a CLI, a TUI, and a read-only MCP endpoint. That makes the repository a combination of a data source and a distribution layer rather than a single application. For readers, the practical distinction is between consuming deadlines through the website or calendar feed and contributing corrections to the underlying YAML files; the two workflows have different requirements. The MIT license and the public issue/PR flow make the data reusable, but the value of any single deadline record still depends on the source cited in the corresponding conference entry.