Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Daniel S. Katz
@danielskatz@fediscience.org  路  activity timestamp 3 weeks ago

arXiv says it will no longer accept computer science (CS) category review articles and position papers unless they have been accepted at a journal or a conference and complete successful peer review.

See https://blog.arxiv.org/2025/10/31/attention-authors-updated-practice-for-review-articles-and-position-papers-in-arxiv-cs-category/

But then in the details, it turns out that the work doesn't just have to be accepted, it also has to be published with a DOI, and it can't be published by a workshop at a conference, as "the review conducted at conference workshops generally does not meet the same standard of rigor of traditional peer review".

Unless my published position paper is not open access, what value would there be in putting it on arXiV after it has already been published?

And as a workshop organizer who takes peer review seriously, I feel a bit insulted. This workshop/conference distinction seems particularly harsh when many CS conferences have more workshop papers than conference papers, and the workshops, as highly focused venues, can have higher quality peer-review than the parent conference.

And finally, conferences publish non-peer reviewed work (such as invited papers), which seems to mean that this new policy isn't really going to work like the moderators think it will.

As an AEiC of @joss, I understand that dealing with AI-generated papers is a challenge, but I feel like this change is going to harm the community more than it will help it.

  • Copy link
  • Flag this post
  • Block
J. Nathan Matias 馃Γ
@natematias@social.coop replied  路  activity timestamp 3 weeks ago

@danielskatz I can definitely see how this will create issues for the community.

I'm not affiliated with the arxiv team, but I do study content moderation. Moderating arxiv is a *lot* of work that isn't funded nearly at the level it needs, so maybe this could be an opportunity for more of the AI companies that rely on arxiv to help keep it going?

https://info.arxiv.org/about/supporters.html

  • Copy link
  • Flag this comment
  • Block
herbert
@hvdsomp@w3c.social replied  路  activity timestamp 3 weeks ago

@natematias @danielskatz Just sipping my beer and smoking my pipe, wondering whether the problem @arxiv_cs is trying to address with this new policy might be related to an unmanageable influx of AI slop submissions.

  • Copy link
  • Flag this comment
  • Block
Christian Meesters
@rupdecat@fediscience.org replied  路  activity timestamp 3 weeks ago

@danielskatz @joss

When I started to work in #HPC, the people I had the misfortune to work with published only with and for conferences. All of this work was studentware, resp. abandonware. Classical proof-of-concept stuff.

I cannot remark on the quality of review in this field. But from the group I am thinking of, every output was lousy - and they claimed to go to prestigious conferences. Still today I hardly ever draw relevant information from such CS conference papers. My point of view might be a bit special, I have to admit.

So, I don't know if those arXiv arguments are valid. Yet, I feel my - certainly biased - view confirmed.

Edit: PS it is rather unfortunate that the blog link does not offer numbers.

  • Copy link
  • Flag this comment
  • Block
Alan Sill
@AlanSill@mast.hpc.social replied  路  activity timestamp 3 weeks ago

@rupdecat @danielskatz @joss Personally, I prefer the JOSS model. Computer Science papers that fail to include accessible, complete archives of source code and relevant details used to prepare the results in the paper are in my opinion not reproducible, and should not be published or accepted by any journal or outlet. JOSS is a shining example of the right way to do things, in my opinion.

  • Copy link
  • Flag this comment
  • Block
Daniel S. Katz
@danielskatz@fediscience.org replied  路  activity timestamp 3 weeks ago

@AlanSill @rupdecat @joss

But the point here is for position papers and similar, which don't have computational elements...

  • Copy link
  • Flag this comment
  • Block
Christian Meesters
@rupdecat@fediscience.org replied  路  activity timestamp 3 weeks ago

@AlanSill

I could not agree more!

@danielskatz @joss

  • Copy link
  • Flag this comment
  • Block
hpc.social admins
@admin@mast.hpc.social replied  路  activity timestamp 3 weeks ago

@rupdecat @danielskatz @joss Personally, I prefer the JOSS model. Computer Science papers that fail to include accessible, complete archives of source code and relevant details used to prepare the results in the paper are in my opinion not reproducible, and should not be published or accepted by any journal or outlet. JOSS is a shining example of the right way to do things, in my opinion.

  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About 路 Code of conduct 路 Privacy 路 Users 路 Instances
Bonfire social 路 1.0.0 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login