CCF-Deadlines

English | 简体中文

Help researchers track deadlines of conferences recommended by China Computer Federation (CCF).

Website Preview (Main Site)	Tabular Preview [No Ladder Required]	PyCli Preview [Work In Progress]

Wechat Applet [Work In Progress]

No More Finding and Time Conversion on Your Own!

Add/Update a conference

Contributions are welcomed and greatly appreciated! For further contribution and waterblowing, email chenzh@stu.ecnu.edu.cn through your edu email address with wechatid to join the CCFDDL organization.

To add or update information:

• Fork the repo
• Add/Update the yml file of conference/conf_type/conf_name.yml
• Send a pull request

Tips: check conferences recommended or review pdf

Conference Entry File

Example file: conference/DB/sigmod.yml

- title: SIGMOD
  description: ACM Conference on Management of Data
  sub: DB
  rank: A
  dblp: sigmod
  confs:
    - year: 2022
      id: sigmod22
      link: http://2022.sigmod.org/
      timeline:
        - deadline: '2021-07-02 17:00:00'
          comment: 'first round'
        - deadline: '2021-09-15 17:00:00'
          comment: 'second round'
      timezone: UTC-8
      date: June 12-17, 2022
      place: Philadelphia, PA, USA

Description of the fields:

Field name			Description
title*			Short conference name, without year, uppercase
description*			Description, or long name, with no session
sub*			The category that the conference is labeled by CCF. See the matching table below
rank*			The level that the conference is ranked by CCF, e.g., A, B, C
dblp*			The suffix in dblp url, e.g., iccv in https://dblp.uni-trier.de/db/conf/iccv
confs	year*		Year the conference is happening
	id*		conference name & year, lowercase
	link*		URL to the conference home page
	timeline*	abstract_deadline	Abstract deadline if applicable, optional
		deadline*	Deadline, in the format of yyyy-mm-dd hh:mm:ss or TBD
		comment	Some comments on the conference, optional
	timezone*		Timezone of deadline, currently support UTC-12 ~ UTC+12 & AoE
	date*		When the main conference is happening, e.g., Mar 12-16, 2021
	place*		Where the main conference is happening, e.g., city, country

Fields marked with asterisk (*) are required.

The matching table:

sub	Category name
DS	Computer Architecture/Parallel Programming/Storage Technology
NW	Network System
SC	Network and System Security
SE	Software Engineering/Operating System/Programming Language Design
DB	Database/Data Mining/Information Retrieval
CT	Computing Theory
CG	Graphics
AI	Artificial Intelligence
HI	Computer-Human Interaction
MX	Interdiscipline/Mixture/Emerging

Community activity

Contribution

Maintained by @jacklightChen, @0x4f5da2, @kzoacn, @cubercsl, @spingARbor, @liborui, @PAN-Ziyue, @xuhangc, @RyunMi, @Lukangkang123, @oliverck, @fffmath, @Allenpandas, @yuang-chen, @hepengfei5709, @ViGeng, @QianpengLi577.

Inspired by ai-deadlines.

Best Practice

We recommend branch-based workflow, which is a common practice in open source projects. As shown in the figure below, The basic idea is to create a new branch for each feature or bug fix. Then this new branch can be pushed to forked repository. All changes will be merged into upstream main branch through pull requests.

License