acl-org / acl-org/acl-anthology

Ingestion Request: ROCLING 2026

未关闭
#8,880 9 条评论 0 个 reaction 已指派 1 人 已被 @mjpost 认领 在 GitHub 查看
ingestion
主要语言
Python
星标
797
派生
408
平均合并
3 天 19 小时
30 天内合并 PR
36

描述

### General information about this request

- [x] I confirm that I have read the [Information for Submitters](https://aclanthology.org/info/contrib/).
- [ ] I am submitting a request for a **new venue** that does not exist in the ACL Anthology yet.

### Venue Identifier

rocling

### ACL SIG(s) sponsoring or endorsing the whole venue

_No response_

### Volume Title

Proceedings of the 38th Conference on Computational Linguistics and Speech Processing (ROCLING 2026)

### Venue Name (only if you are submitting a new venue)

_No response_

### Venue Website (only if you are submitting a new venue)

_No response_

### Date of Publication

2026-11-02

### Location

Hsinchu, Taiwan

### Supporting Information

Dear Anthology Director,

I am Fernando H. Calderon, one of the publication chairs of [ROCLING 2026](https://rocling2026.github.io/NTHU_rocling_2026/)

We would like to register the proceedings of ROCLING 2026 with the ACL Anthology. Please find the required information below:

(a) The complete list of volumes:

Proceedings of the 38th Conference on Computational Linguistics and Speech Processing (ROCLING 2026)

(b) The desired publication date: 02 November 2026 (four days before the conference date)

Sincerely,
Fernando H. Calderon
Publication Chair, ROCLING 2026
[fhcalderon87@gmail.com](mailto:fhcalderon87@gmail.com)

贡献指南

这个仓库没有索引到贡献指南

调研方向

The issue provides only ingestion metadata (volume title, date, location, identifier) and names no files or tests. Start by finding prior venue/volume ingestion examples and the project’s documented ingestion workflow, then add a ROCLING 2026 record in the same structure. If the repo has a metadata validation or import check, run it after the change. The work is done when the new proceedings entry is present and properly formatted like existing entries.

由索引模型根据 Issue 内容生成。

评估

领域
content
Issue 类型
功能
难度
2/5
预计耗时
1-3 小时
活跃度
冷清
描述清晰度
基本清楚
新手友好度
42/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。