tag:blogger.com,1999:blog-27705661.post5822547534499976525..comments2023-10-28T10:58:57.140+00:00Comments on Process Algebra Diary: Report on the EATCS General Assembly at ICALP 2016Luca Acetohttp://www.blogger.com/profile/01092671728833265127noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-27705661.post-62785941632009296502016-08-23T17:39:34.020+00:002016-08-23T17:39:34.020+00:00The proceedings of ICALP'16 are now officially...The proceedings of ICALP'16 are now officially published and available here:<br /><br />http://www.dagstuhl.de/dagpub/978-3-95977-013-2Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-27705661.post-86839698216066718682016-07-21T14:31:54.516+00:002016-07-21T14:31:54.516+00:00Sylvain,
Thank you very much for your comments/q...Sylvain, <br /><br />Thank you very much for your comments/questions. I will forward them to the proceedings chair for ICALP and to the new president of the EATCS right away. <br /><br />Luca Acetohttps://www.blogger.com/profile/01092671728833265127noreply@blogger.comtag:blogger.com,1999:blog-27705661.post-32909789987261752492016-07-21T13:54:28.345+00:002016-07-21T13:54:28.345+00:00Thanks for the report! I attended the meeting, an...Thanks for the report! I attended the meeting, and it was quite interesting. I have two questions related to publication issues:<br /><br />1. About authors not complying with the typesetting instructions, I would like to point out that lipics is much more demanding than others with respect to final versions, resulting in substantial efforts to prepare them. I am for instance guilty of ignoring some recommendations (no cleverref, and although not explicitly stated, no natbib), that would involve a major rehaul of my LaTeX sources, but comply with the other time-consuming requisites (single LaTeX file, with only the needed macros and BibTeX entries).<br /><br />Given the number of conferences now publishing with lipics, it might make sense to ask the community for help with improving the process; I'd for instance rather help solving whatever issues there might be with cleverref and natbib once and for all for everyone rather than rewrite my files by hand for every conference paper.<br /><br />I would also second Mikkel Thorup's suggestion to set up a web-based interface so that authors could validate their final submissions directly.<br /><br />2. About posting final versions of accepted papers online, I would go further as in FOCS' call for paper, which indicates that "Authors are encouraged to post full versions of their submissions in a freely accessible on-line repository such as the arxiv, the ECCC, or the Cryptology ePrint archive. (Papers that are not written well enough for public dissemination are probably also not ready for submission to FOCS.) We expect that authors of accepted papers will make full versions of their papers, with proofs, available by the camera-ready deadline."Sylvainhttps://www.blogger.com/profile/05888158547954503588noreply@blogger.comtag:blogger.com,1999:blog-27705661.post-18523862939632360702016-07-20T09:53:59.737+00:002016-07-20T09:53:59.737+00:00Marc, I have added a brief account of the discussi...Marc, I have added a brief account of the discussion related to the proceedings to the post. I also included some of your comment.) A version of this post will appear in the October issue of the Bulletin of the EATCS. Let me know if you have any other comment. Luca Acetohttps://www.blogger.com/profile/01092671728833265127noreply@blogger.comtag:blogger.com,1999:blog-27705661.post-80850960046497398332016-07-20T09:26:46.937+00:002016-07-20T09:26:46.937+00:00Thanks, Luca, for the clarifications. We are also ...Thanks, Luca, for the clarifications. We are also looking forward to future ICALP volumes in LIPIcs. Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-27705661.post-78926317023380073342016-07-20T09:01:19.091+00:002016-07-20T09:01:19.091+00:00Marc,
I do not think that I blamed LIPIcs for th...Marc, <br /><br />I do not think that I blamed LIPIcs for the delay at any point. I simply referred to teething problems and I squarely took the blame for the delay, both at the General Assembly and in the blog post devoted to it. I will add your comment to the main body of the post, if you want. <br /><br />Regarding the typesetting issues that you raise, those were also discussed at the General Assembly. Thore Husfeldt mentioned them, as editor of a recent LIPIcs proceedings. I thanked Thore and asked the audience to help the proceedings chair and the LIPIcs staff by sticking to the typesetting instructions they are given. There was an interesting follow-up discussion and you will receive some of the suggestions from the EATCS Secretary Office. <br /><br />The ICALP deadline for delivering the proceedings versions of the papers is April 30. Since the conference takes in the first or the second week of July, it is impossible for ICALP to deliver the papers to LIPIcs ten weeks before the conference <br /><br />We are looking forward to working together with LIPIcs for future editions of ICALP. <br /><br />Luca Acetohttps://www.blogger.com/profile/01092671728833265127noreply@blogger.comtag:blogger.com,1999:blog-27705661.post-18273944041173060052016-07-20T08:39:37.293+00:002016-07-20T08:39:37.293+00:00The LIPIcs issue is a pity, indeed. One should men...The LIPIcs issue is a pity, indeed. One should mention that LIPIcs asked for a 10-week pre-conference submission of all the material, but ICALP said 6 weeks is the minimum. We tried to cope with that, but failed. But it's not only LIPIcs to blame. <br /><br />Interestingly, some papers contains flaws that LIPIcs is still trying to resolve as part of publishing a high-quality proceedings volume. <br /><br />Most of the authors did not comply to our typesetting instructions which results in a huge amount of additional work for LIPIcs. How come?Anonymousnoreply@blogger.com