https://github.com/ccfddl/ccf-deadlines
⏰ Collaboratively track deadlines of conferences recommended by CCF (Website, Python Cli, Wechat Applet) / If you find it useful, please star this project, thanks~
https://github.com/ccfddl/ccf-deadlines
artificial-intelligence ccf-rankings computer-systems conf-deadline data-management deadline networked-systems security-systems social-computing software-engineering
Last synced: 15 days ago
JSON representation
⏰ Collaboratively track deadlines of conferences recommended by CCF (Website, Python Cli, Wechat Applet) / If you find it useful, please star this project, thanks~
- Host: GitHub
- URL: https://github.com/ccfddl/ccf-deadlines
- Owner: ccfddl
- License: mit
- Created: 2021-02-01T06:08:25.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2024-04-13T05:27:00.000Z (about 1 year ago)
- Last Synced: 2024-04-13T20:06:30.979Z (about 1 year ago)
- Topics: artificial-intelligence, ccf-rankings, computer-systems, conf-deadline, data-management, deadline, networked-systems, security-systems, social-computing, software-engineering
- Language: Vue
- Homepage: https://ccfddl.github.io
- Size: 8.53 MB
- Stars: 4,828
- Watchers: 22
- Forks: 346
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
- stars - ccfddl/ccf-deadlines
README
# CCF-Deadlines
[](https://github.com/ccfddl/ccf-deadlines/blob/main/LICENSE)
[](https://github.com/ccfddl/ccf-deadlines/commits/main)
[](https://github.com/ccfddl/ccf-deadlines/pulls)
English | [简体中文](./README.zh-CN.md)
Help researchers track deadlines of conferences recommended by [China Computer Federation (CCF)](https://www.ccf.org.cn/).
Website Preview
(Main Site)
Tabular Preview
No Ladder Required
PyCli Preview
Work In Progress
Wechat Applet
Work In Progress
Raycast Extension
Available Now
**No More Finding and Time Conversion on Your Own!**
## iCal Subscription:
- English: `https://ccfddl.com/conference/deadlines_en.ics`
- 简体中文: `https://ccfddl.com/conference/deadlines_zh.ics`
The filter is mapped to the name of iCal file in the following rules:
- one filter: `deadlines_en.ics` and `deadlines_zh.ics`
- two filters: `deadlines_{lang}_{rank}.ics` and `deadlines_{lang}_{sub}.ics`
- common filters: `deadlines_{lang}_{rank}_{sub}.ics`
For example, given filter: lang=zh, sub=AI,CG, ccf=A,thcpl=A, then it will refer to `deadlines_zh_ccf_A_AI.ics`, `deadlines_zh_ccf_A_CG.ics`, `deadlines_zh_thcpl_A_AI.ics` and `deadlines_zh_thcpl_A_CG.ics`.
## Add/Update a conference
Contributions are welcomed and greatly appreciated!
To add or update information:
- Fork the repo
- Add/Update the yml file of conference/conf_type/conf_name.yml
- Send a [pull request](https://github.com/ccfddl/ccf-deadlines/pulls)
Tips: check [conferences recommended](https://www.ccf.org.cn/Academic_Evaluation/By_category/) or review [pdf](.readme_assets/ccf_recommended_2022.pdf)
## Conference Entry File
Example file: conference/DB/sigmod.yml
```yaml
- title: SIGMOD
description: ACM Conference on Management of Data
sub: DB
rank:
ccf: A
core: A*
thcpl: 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*
ccf*
The level that the conference is ranked by CCF, e.g., A, B, C, N
core
The level that the conference is ranked by CORE, e.g., A*, A, B, C, N
thcpl
The level that the conference is ranked by TH-CPL, e.g., A, B, N
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 [](https://repography.com)
[](https://github.com/ccfddl/ccf-deadlines/commits)
[](https://github.com/ccfddl/ccf-deadlines/issues)
[](https://github.com/ccfddl/ccf-deadlines/pulls)
[](https://github.com/ccfddl/ccf-deadlines/graphs/contributors)
## Contribution
Maintained by [@jacklightChen](https://github.com/jacklightChen), [@0x4f5da2](https://github.com/0x4f5da2), [@kzoacn](https://github.com/kzoacn), [@cubercsl](https://github.com/cubercsl), [@spingARbor](https://github.com/spingARbor), [@liborui](https://github.com/liborui), [@PAN-Ziyue](https://github.com/PAN-Ziyue), [@xuhangc](https://github.com/xuhangc), [@RyunMi](https://github.com/RyunMi), [@Lukangkang123](https://github.com/Lukangkang123), [@oliverck](https://github.com/oliverck), [@fffmath](https://github.com/fffmath), [@Allenpandas](https://github.com/Allenpandas), [@yuang-chen](https://github.com/yuang-chen), [@hepengfei5709](https://github.com/hepengfei5709), [@ViGeng](https://github.com/ViGeng), [@QianpengLi577](https://github.com/QianpengLi577).
Inspired by [ai-deadlines](https://aideadlin.es/).
### 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
[](https://app.fossa.com/projects/git%2Bgithub.com%2Fccfddl%2Fccf-deadlines?ref=badge_large)
