Git Product home page Git Product logo

se-deadlines.github.io's Introduction

Software engineering deadlines countdown

Based on ai-deadlines by @abshkdz and sec-deadlines

Adding/updating a conference

  • Update _data/conferences.yml. You can do that on Github or locally after forking the repo.
  • Send a pull request

Conference entry record

Example record:

- name: ICSE
  description: International Conference on Software Engineering - Research Track
  year: 2025
  link: https://conf.researchr.org/track/icse-2025/icse-2025-research-track
  deadline: 
  - "2024-03-15 23:59"
  - "2024-06-26 23:59"
  date: April 26 - May 4, 2025
  place: Ottawa, Ontario, Canada
  tags: [CO]

Descriptions of the fields:

Field name Description
name* Short conference name, without year
description Description, or long name
year* Year the conference is happening
link* URL to the conference home page
deadline* A list of deadlines. (Gory details below)
date When the conference is happening
place Where the conference is happening
tags One or multiple tags: CO, JO, or WO

Fields marked with asterisk (*) are required.

Deadline format

The deadline field can contain:

  1. The simplest option: a date and time in ISO format. Example: ["2017-08-19 23:59"] (Note that you need to wrap even a single deadline in a list).
  2. If a deadline is rolling, you can use a template date, just substitute the year with %y and the year before the conference with %Y. Example: ["%y-01-15 23:59"] means there is a deadline on the 15th January in the same year as the conference.
  3. A list of (1) or (2). Example of two rolling deadlines, with one in the end of October in the year prior to the conference year, and the second in the end of February in the same year as the conference:
- "%Y-10-31 23:59"
- "%y-02-28 23:59"

On the page, all deadlines are displayed in viewer's local time (that's a feature).

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.

Timezones

Please remember that the timezone should be AoE (Anywhere on Earth) when you submit a pull request.

se-deadlines.github.io's People

Contributors

sivanahamer avatar imranur-rahman avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar

Forkers

sudokara

se-deadlines.github.io's Issues

Multiple tracks same conference

Many software engineering venues have multiple tracks. For example:

  • Research track/full paper track
  • Short paper
  • Industry tack
  • Journal first track
  • Tools tracks
  • Dataset tracks
  • New and emerging ideas track

We could probably, to make it easier to add and find tracks, add a tag to be added when adding an entry. An example how it would look would be the following:

- name: ICSE-JF
  description: International Conference on Software Engineering - Journal-first Papers
  year: 2025
  link: https://conf.researchr.org/track/icse-2025/icse-2025-journal-first-papers
  deadline: 
  - "2024-10-21 23:59"
  date: April 26 - May 4, 2025
  place: Ottawa, Ontario, Canada
  tags: [CO]
  tracks: [JF]

Separate abstract and full paper submission deadline

Many SE conferences follow separate deadlines for abstract and full paper submission within the same track deadline. For example, this years ICSE research track has abstract submission deadline on Mar 15 AoE and full paper submission deadline on Mar 22.

In the current setting, we only show the abstract submission deadline in our website but not the full paper submission deadline. We should think of some way to handle this.

Adding a conference with TBA or invalid deadline breaks the ordering

In main.js, if the deadline for a conference is "TBA", the deadlineByConf for the conference is assigned to null. However, when sorting, the difference in time to today is used, which is not supported for null, leading to wrong sorting of conferences. TBA, future and past deadlines get mixed in the list. The ordering also breaks if an invalid deadline is supplied, even though the site shows the deadline as an Invalid Date.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.