-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FSE vs ESECFSE #39
Comments
This should probably be fixed given that ESEC/FSE was not officially renamed to FSE. We probably need another conference entry in the MY* files therefore too. |
It is renamed as of 2024. So we need two labels for the two different conference names, but I would prefer to always use FSE only in keys. In the future, this conference will only be known as FSE due to the rename anyway. |
But then we would invalidate lots of keys retroactively. (Key aliases would be nice. :D) This would also add a special case to key naming conventions. Yet when many existing keys are inconsistent anyway, then renaming every key to FSE will be better than no renaming. |
Status of this issue:
|
Currently, citations are not consistent about the abbreviation of the conference. For example: OBM+:FSE17 and SSA:ESECFSE17
The text was updated successfully, but these errors were encountered: