caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Tim Molderez <tmoldere@vub.ac.be>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] <Programming> 2017: Call for papers
Date: Mon, 17 Oct 2016 15:38:09 +0200	[thread overview]
Message-ID: <5d27d306-cd22-729c-02e6-afc5eaa536bc@vub.ac.be> (raw)
In-Reply-To: <CAPFanBG5gLBX1Ou9RK0RZ8e7eGoaPJaYtt+cBdraZr+zsFiFeg@mail.gmail.com>

Hi Gabriel,

Thanks for the kind and encouraging words! I'll pass them along to the 
rest of our organizing committee :)

Kind regards,
  Tim


On 17/10/16 15:26, Gabriel Scherer wrote:
> I understand from
>
>    http://2017.programming-conference.org/track/programming-2017-papers#About
>
> and
>
>    http://programming-journal.org/
>
> that the articles submitted to this conference will be published in an
> open-access journal (the sensible kind, were neither authors not
> readers have to pay), that will host all articles on arXiv.
>
> Congratulations for doing things right!
>
> This matters, and to me it makes your conference more attractive than
> others that are stuck in the past, with grotesque copyright assignment
> requirements.
>
> On Mon, Oct 17, 2016 at 5:51 AM, Tim Molderez <tmoldere@vub.ac.be> wrote:
>> <Programming> 2017 : The Art, Science, and Engineering of Programming
>>
>> April 3-6, 2017, Brussels, Belgium
>> http://2017.programming-conference.org
>>
>> We started a new conference and journal focused on everything to do with
>> programming, including the experience of programming. We call the conference
>> <Programming> for short. Paper submissions and publications are handled by
>> the journal. Accepted papers must be presented at the conference.
>>
>> ********************************************************
>>   CALL FOR PAPERS
>> ********************************************************
>>
>> <Programming> 2017 accept scholarly papers including essays that advance the
>> knowledge of programming. Almost anything about programming is in scope, but
>> in each case there should be a clear relevance to the act and experience of
>> programming.
>>
>> PAPER SUBMISSIONS: December 1, 2016
>>
>> We accept submissions covering several areas of expertise. These areas
>> include, but are not limited to:
>>
>> • General-purpose programming
>> • Distributed systems programming
>> • Parallel and multi-core programming
>> • Graphics and GPU programming
>> • Security programming
>> • User interface programming
>> • Database programming
>> • Visual and live programming
>> • Data mining and machine learning programming
>> • Interpreters, virtual machines and compilers
>> • Modularity and separation of concerns
>> • Model-based development
>> • Metaprogramming and reflection
>> • Testing and debugging
>> • Program verification
>> • Programming education
>> • Programming environments
>> • Social coding
>>
>> ********************************************************
>>   CALL FOR WORKSHOP PROPOSALS
>> ********************************************************
>>
>> To build a community and to foster an environment where participants can
>> exchange ideas and experiences related to practical software development,
>> ‹Programming› will host a number of workshops, during the days before the
>> main conference. The workshops will provide a collaborative forum to
>> exchange recent and/or preliminary results, to conduct intensive discussions
>> on a particular topic, or to coordinate efforts between representatives of a
>> technical community. They are intended as a forum for lively discussion of
>> innovative ideas, recent progress, or practical experience on programming
>> and applied software development in general for specific aspects, specific
>> problems, or domain-specific needs. We also encourage practical, hands-on
>> workshops in which participants actually experience one or several aspects
>> of practical software development.
>>
>> WORKSHOP PROPOSAL SUBMISSIONS: November 15, 2016
>>
>> The duration of workshops is in general one day, but we encourage the
>> submission of half-day workshop proposals on focused topics as well. In
>> exceptional situations, e.g., for workshops that involve actual practice of
>> programming-related activities, workshop organizers can request a 2 day
>> workshop slot. If desired, the workshop proceedings can be published in the
>> ACM Digital Library.
>>
>> ********************************************************
>>   IMPORTANT DATES
>> ********************************************************
>>
>> Research paper submissions: December 1, 2016
>> Research paper first notifications: February 1, 2017
>> Research paper final notifications: March 7, 2017
>>
>> Workshop proposals: November 15, 2016
>> PX 2017 workshop submissions: January 15, 2017
>> Poster abstract submissions: January 16, 2017
>>
>> ********************************************************
>>   ORGANIZATION
>> ********************************************************
>>
>> General Chair:
>> Theo D'Hondt, Vrije Universiteit Brussel
>>
>> Local Organizing Chair:
>> Wolfgang De Meuter, Vrije Universiteit Brussel
>>
>> Program Chair:
>> Crista V. Lopes, University of California, Irvine
>>
>> Organizing Committee:
>> Jörg Kienzle (workshops), McGill University
>> Hidehiko Masuhara (demos), Tokyo Institute of Technology
>> Ralf Lämmel (contest), University of Koblenz-Landau
>> Jennifer Sartor (posters), Vrije Universiteit Brussel
>> Tobias Pape (web technology), HPI - University of Potsdam
>> Tim Molderez (publicity), Vrije Universiteit Brussel
>>
>> Program Committee:
>> Andrew Black, Portland State University
>> Shigeru Chiba, University of Tokyo
>> Yvonne Coady, University of Victoria
>> Robby Findler, Northwestern University
>> Lidia Fuentes, Universidad de Málaga
>> Richard Gabriel, IBM Research
>> Elisa Gonzalez Boix, Vrije Universiteit Brussel
>> Jeff Gray, University of Alabama
>> Robert Hirschfeld, HPI - University of Potsdam
>> Roberto Ierusalimschy, Pontifícia Universidade Católica do Rio de Janeiro
>> Jörg Kienzle, McGill University
>> Hidehiko Masuhara, Tokyo Institute of Technology
>> Sasa Misailovic, University of Illinois at Urbana-Champaign
>> Guido Salvaneschi, Technische Universität Darmstadt
>> Mario Südholt, Ecole des mines de Nantes
>> Jurgen Vinju, Centrum Wiskunde & Informatica
>> Tijs van der Storm, Centrum Wiskunde & Informatica
>>
>> ********************************************************
>>
>> <Programming> 2017 is kindly supported by:
>> ACM in-cooperation
>> ACM SIGPLAN in-cooperation
>> ACM SIGSOFT in-cooperation
>> AOSA
>> Vrije Universiteit Brussel
>>
>> ********************************************************
>>
>> For more information, visit http://2017.programming-conference.org
>>
>>
>> --
>> Caml-list mailing list.  Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs


      reply	other threads:[~2016-10-17 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17  9:51 Tim Molderez
2016-10-17 13:26 ` Gabriel Scherer
2016-10-17 13:38   ` Tim Molderez [this message]

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=5d27d306-cd22-729c-02e6-afc5eaa536bc@vub.ac.be \
    --to=tmoldere@vub.ac.be \
    --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).