caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Roberto Di Cosmo <roberto@dicosmo.org>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Peter Achten <P.Achten@cs.ru.nl>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [TFP'20] draft paper deadline open (January 10 2020) Trends in Functional Programming 2020, 13-14 February, Krakow, Poland
Date: Tue, 26 Nov 2019 11:59:18 +0100	[thread overview]
Message-ID: <20191126105918.GA28686@traveler> (raw)
In-Reply-To: <CAPFanBFJt-v7oa3rGYn63jLpprapb+UEHwbChWMAH2MbEXWPbw@mail.gmail.com>

Thanks Gabriel for raising this important issue. Getting proper Open Access
venues that do not charge APC (or only charge reasonable APC) is of paramount
importance.

You may probably know the LIPIcs series, as an interesting alternative venue:
I do not know whether TFP would qualify, but you could give it some thought

Cheers

--
Roberto


On Tue, Nov 26, 2019 at 11:57:47AM +0100, Gabriel Scherer wrote:
>    Dear Peter (and list),
>    If I understand the CFP correctly, the proceedings of TFP will be
>    published in Springer's LNCS series, which nominally allows authors to
>    retain their copyright for the work, but require an "Open Choice" price
>    of $38 per page to do so; for 20-page submissions, this comes at the
>    rather discouraging price of $760 -- more expensive for me than
>    actually attending TFP.
>    Are there any plans to make TFP a proper Open Access conference, where
>    authors can retain the rights to their work without paying for more
>    than reasonable publication costs?
>    Best
> 
>    On Tue, Nov 26, 2019 at 10:27 AM Peter Achten <[1]P.Achten@cs.ru.nl>
>    wrote:
> 
>      --------------------------------------------------------------------
>      -----
>                            Third call for papers
>               21st Symposium on Trends in Functional Programming
>                                 [2]tfp2020.org
>      --------------------------------------------------------------------
>      -----
>      Did you miss the deadline to submit a paper to Trends in Functional
>      Programming
>      [3]http://cse.chalmers.se/~rjmh/tfp/? No worries -- it's not too
>      late!
>      Submission is open until January 10th 2020, for a presentation slot
>      at
>      the event
>      and post-symposium reviewing.
>      The symposium on Trends in Functional Programming (TFP) is an
>      international
>      forum for researchers with interests in all aspects of functional
>      programming,
>      taking a broad view of current and future trends in the area. It
>      aspires
>      to be
>      a lively environment for presenting the latest research results, and
>      other
>      contributions.
>      * TFP is moving to new winter dates, to provide an FP forum in
>      between the
>         annual ICFP events.
>      * TFP offers a supportive reviewing process designed to help less
>      experienced
>         authors succeed, with two rounds of review, both before and after
>      the
>         symposium itself. Authors have an opportunity to address
>      reviewers'
>      concerns
>         before final decisions on publication in the proceedings.
>      * TFP offers two "best paper" awards, the John McCarthy award for
>      best
>      paper,
>         and the David Turner award for best student paper.
>      * This year we are particularly excited to co-locate with Lambda
>      Days in
>         beautiful Krakow. Lambda Days is a vibrant developer conference
>      with
>      hundreds
>         of attendees and a lively programme of talks on functional
>      programming in
>         practice. TFP will be held in the same venue, and participants
>      will
>      be able
>         to session-hop between the two events.
>      Important Dates
>      ---------------
>      Submission deadline for pre-symposium review:   15th November, 2019
>      --
>      passed --
>      Submission deadline for draft papers:           10th January, 2020
>      Symposium dates:                                13-14th February,
>      2020
>      Visit [4]tfp2020.org for more information.
> 
> References
> 
>    1. mailto:P.Achten@cs.ru.nl
>    2. http://tfp2020.org/
>    3. http://cse.chalmers.se/~rjmh/tfp/
>    4. http://tfp2020.org/

-- 
Roberto Di Cosmo
 
------------------------------------------------------------------
Computer Science Professor
            (on leave at INRIA from IRIF/University Paris Diderot)

Director
Software Heritage                https://www.softwareheritage.org
INRIA			   
Bureau C328		     E-mail : roberto@dicosmo.org         
2, Rue Simone Iff          Web page : http://www.dicosmo.org      
CS 42112		    Twitter : http://twitter.com/rdicosmo 
75589 Paris Cedex 12	        Tel : +33 1 80 49 44 42           
------------------------------------------------------------------                                                 
GPG fingerprint 2931 20CE 3A5A 5390 98EC 8BFC FCCA C3BE 39CB 12D3                        

  reply	other threads:[~2019-11-26 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26  9:27 Peter Achten
2019-11-26 10:57 ` Gabriel Scherer
2019-11-26 10:59   ` Roberto Di Cosmo [this message]
2020-01-07  8:26 Peter Achten

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191126105918.GA28686@traveler \
    --to=roberto@dicosmo.org \
    --cc=P.Achten@cs.ru.nl \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).