Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Michael Sperber <sperber@deinprogramm.de>
To: caml-list@inria.fr
Subject: [Caml-list] Call for Contributions: BOB 2017 - Berlin, Feb 24, 2017 (Deadline Oct 30)
Date: Mon, 17 Oct 2016 14:23:32 +0200	[thread overview]
Message-ID: <y9l4m4bgo57.fsf@jellaby.local> (raw)


BOB has a strong focus on functional programming, so OCaml proposals are
very welcome!

			 BOB Conference 2017
	 "What happens when we use what's best for a change?"
		  http://bobkonf.de/2017/en/cfp.html
			 Berlin, February 24
			Call for Contributions
		      Deadline: October 30, 2016

You are actively engaged in advanced software engineering methods,
implement ambitious architectures and are open to cutting-edge
innovation? Attend this conference, meet people that share your goals,
and get to know the best software tools and technologies available
today. We strive to offer a day full of new experiences and
impressions that you can use to immediately improve your daily life as
a software developer.

If you share our vision and want to contribute, submit a proposal for
a talk or tutorial!

Topics
------

We are looking for talks about best-of-breed software technology, e.g.:

- functional programming
- persistent data structures and databases
- types
- formal methods for correctness and robustness
- abstractions for concurrency and parallelism
- metaprogramming
- probabilistic programming
- ... everything really that isn’t mainstream, but you think should be.

Presenters should provide the audience with information that is
practically useful for software developers.

This time, we’re especially interested in experience reports. But this
could also take other forms, e.g.:

- introductory talks on technical background
- overviews of a given field
- demos and how-tos

Requirements
------------

We accept proposals for presentations of 45 minutes (40 minutes talk +
5 minutes questions), as well as 90 minute tutorials for
beginners. The language of presentation should be either English or
German.

Your proposal should include (in your presentation language of choice):

- an abstract of max. 1500 characters.
- a short bio/cv
- contact information (including at least email address)
- a list of 3-5 concrete ideas of how your work can be applied in a developer’s daily life
-additional material (websites, blogs, slides, videos of past presentations, …)

Submit here:

https://docs.google.com/forms/d/e/1FAIpQLSfFuyBhBTCOTS0zTXBzY1KVuKpumyIBTucLcJ1ArC1XpWsG-Q/viewform

Organisation

- direct questions to bobkonf at active minus group dot de
- proposal deadline: October 30, 2016
- notification: November 15, 2016
- program: December 1, 2016

NOTE: The conference fee will be waived for presenters, but travel
expenses will not be covered.

Speaker Grants
--------------

BOB has Speaker Grants available to support speakers from groups
under-represented in technology. We specifically seek women speakers
and speakers who are not be able to attend the conference for
financial reasons. Details are here:

http://bobkonf.de/2017/en/speaker-grants.html

Shepherding
-----------

The program committee offers shepherding to all speakers. Shepherding
provides speakers assistance with preparing their sessions, as well as
a review of the talk slides.

Program Committee
-----------------

(more information here: http://bobkonf.de/2017/programmkomitee.html)

- Matthias Fischmann, zerobuzz UG
- Matthias Neubauer, SICK AG
- Nicole Rauch, Softwareentwicklung und Entwicklungscoaching
- Michael Sperber, Active Group
- Stefan Wehr, factis research

Scientific Advisory Board

- Annette Bieniusa, TU Kaiserslautern
- Torsten Grust, Uni Tübingen
- Peter Thiemann, Uni Freiburg



                 reply	other threads:[~2016-10-17 12:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=y9l4m4bgo57.fsf@jellaby.local \
    --to=sperber@deinprogramm.de \
    --cc=caml-list@inria.fr \
    /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