Proposals
IN/Clojure  project

IN/Clojure 2020

India's annual Clojure and ClojureScript conference. 14th-15th Feb, 2020. Pune, MH, IN.

IN/Clojure 2020
IN/Clojure is India’s annual Clojure and ClojureScript conference, including talks about features, libraries, tools, usage, and more. IN/Clojure 2020, our 4th edition, is happening on 14th and 15th Feb 2020 (Fri/Sat) in Pune, Maharashtra. Tickets are on sale, and our CFP is open (closes 20 Jan 2020)! Follow us on Twitter @in_clojure for updates.

Novotel Pune Nagar Road, Crimson Hall, Pune

Propose a session

Submissions are closed for this project

Call for proposals

We welcome talk submissions for the 4th edition of IN/Clojure!

CFP closes Monday, 20 Jan 2020.

This year’s expert Selection Committee includes:

  • Martin Klepsch, Clojure/Script consultant; creator of cljdoc, Clojure Berlin, and Heart of Clojure.
  • Paula Gearon, Software Engineer at Cisco Systems; in her 10th year of Clojure development.
  • Tejas Dinkar, Head of Technology at Quintype; loves to play with Clojure, Ruby, GoLang, ReasonML, and Node.js.

And selected speakers will enjoy sharing the stage with the perennially effervescent Bozhidar Batsov; prolific Clojurist, Emacs fanatic, maintainer of CIDER, nREPL and a dozen related projects, the editor of the community Clojure style guide, and Lisp hacker extraordinaire.

Submit a proposal now! Note:

  • CFP extended to 20 Jan 2020, from 01 Jan 2020.
  • All talk proposers receive a free conference day pass, irrespective of selection status.

For talk ideas, context, and speaker reimbursement information:

For event updates, follow us on twitter.

Why speak at IN/Clojure?

Over the years, IN/Clojure has served as a platform to kickstart a series of Clojure workshops and meet-ups across the country. And, it has helped attendees make a strong case for Clojure and Clojurescript adoption in their companies.

By sharing your ideas, experiences, and knowledge, you too can help foster the growing Clojure community in India, and also add to the global body of Clojure know-how.

And it’s a mighty fine opportunity to meet other Clojurists from across the world, and to meet companies that are using Clojure to solve business problems at scale.

Who should propose a talk?

You can submit a talk regardless of your experience level with Clojure; all perspectives matter.

IN/Clojure’s primary focus is the free exchange of ideas between new and experienced Clojure programmers alike.

You should especially propose a talk, if you’ve been programming Clojure and/or Clojurescript professionally but believe you have nothing to say. Well, you do, or your team does! Think, ideate, submit a proposal!

What to propose?

We’re looking for submissions on a wide range of topics.

  • You did something cool with Clojure lately? We want to hear from you!
  • Maybe you learnt Clojure on weekends and built a small game in ClojureScript? Write in!
  • Maybe you rewrote your old Java, or Go application in Clojure. Tell us all about it.
  • Maybe you rewrote your Clojure application in another language. Well, we want to hear about that too!
  • Maybe you taught Clojure to your friends, and there were some interesting aha! moments you want to talk about? Write in!
  • If you built a wrapper library, a terminal game, a scraper spider, a crud generator, a tflops number cruncher, a distributed messaging platform, or a deep learning thingamajig, yes, you should submit a talk!

How it works

Process

  • You submit a proposal in our public call for proposals system.
  • You may propose one or more talks fitting these length criteria:
    • Full Talks will be 40 mins long, including 5 mins of Q & A.
    • Crisp Talks will be 20 mins long, including 5 mins of Q & A.
    • Lightning Talks will be 10 mins long, with Q & A in the hallways :-)
  • Our selection committee of experts will review and select talks, to help us curate an inclusive and diverse forum.
  • Talk selections are in these phases:
    • DONE: Select up to two “Full” talks by 01 Jan 2020 (see list of proposals).
    • INPROGRESS: Select more talks incrementally, while slots last.
    • CLOSE CFP: to new submissions on 20 Jan 2020 (extended from 01 Jan 2020).
    • Compelling proposals are likely to be selected prior to CFP close, at the selection committee’s discretion.
    • We aim to schedule up to 4 Full talks, 3 Crisp talks, and 3 Lightning talks, or some permutation thereof.
  • Once selected, our team will coordinate with you for travel and stay arrangements.
  • And we will work with you to help you tune and/or polish your content.

Selection philosophy

The smallness of the Clojure ecosystem in India makes it very likely that a subset of the organising team, panelists, and potential speakers are also professionally affiliated with some conference sponsors.

This does not negatively influence talk selection. Quite the opposite, it makes us especially mindful of selection bias, and we keep each other in check. In other words, IN/Clojure is not “pay to play”. Sponsors do not get special preference, and friends do not get to cut in line.

Additionally, our conference code of conduct naturally applies to the conduct of the talk selection process as well.

To exist, IN/Clojure fundamentally relies on the good sense and kindness of involved people, and the community at large. Please do write to team@inclojure.org for questions and clarifications.

Speaker reimbursement

All talk proposers receive a free conference day pass, irrespective of selection status.

For speakers whose submissions are accepted, IN/Clojure will reimburse economy-class travel costs:

  • For international travel – up to INR 80K (approx. USD 1200)
  • For domestic travel – up to INR 15K

And we will provide up to 2 nights / 3 days of stay to cover your time at the conference.

See other talks listed on this page, and submit yours today!

All proposals

Confirmed sessions

Clojure Macros - the good, the bad and the messy

Aravind Baskaran (@aravindbaskaran)

  • 0 comments
  • Wed, 15 Jan

Light Table: The strange and wonderful saga of a pure Clojure editor.

Pratik Karki (@theawesomekarki)

  • 2 comments
  • Tue, 31 Dec

The Future of Clojure Tooling

Bozhidar Batsov (@bbatsov) via Aditya Athalye (@otheradi)

  • 0 comments
  • Mon, 23 Dec

Building data platforms from business stores using Clojure

Mayur Jadhav (@mj13)

  • 1 comments
  • Thu, 14 Nov

Clojure of Things

Adam Helinski (@dvlopt)

  • 0 comments
  • Thu, 31 Oct

Unconfirmed proposals

Team Dynamics & Communication Skills (Team Project Productivity, Start Ups & Management)

CRUX CONCEPTION

  • 1 comments
  • Mon, 20 Jan

Clojure for Java (OOPS) programmers

Rashmi Mittal (@rashmimittal)

  • 0 comments
  • Mon, 20 Jan

Wasm on Clojure

Emmanuel Antony (@emmanuelantony2000)

  • 0 comments
  • Sun, 19 Jan

Clojure is difficult, but worth it

sezal jain (@sezal)

  • 0 comments
  • Fri, 17 Jan

Pushing immutability down to persistance layer

Shivek Khurana

  • 0 comments
  • Thu, 16 Jan

Once Upon a Kotlin in Clojure

Siddharth (@sidkulk)

  • 1 comments
  • Mon, 13 Jan

Lazy Seq's - Why are they so lazy?

Ramsharan Gorur Jayaraman (@sharangj)

  • 0 comments
  • Sun, 12 Jan

Growing a Clojure Company from small to mid-sized (and hopefully beyond): tips, tricks, habits, practices

Vedang Manerikar (@vedang)

  • 1 comments
  • Tue, 31 Dec

Postgres-backed Job Scheduler for Clojure

Murtaza Akbari (@murtaza0xff)

  • 0 comments
  • Fri, 27 Dec

The power of meta

Amarjeet Yadav (@amarjeet000)

  • 0 comments
  • Wed, 25 Dec

Building Clojure apps :through a college student's perspective

varun krishna (@vhawk19)

  • 1 comments
  • Wed, 11 Dec

Polylith + Component = The Grand Design

Gautam Roy (@gautamr)

  • 0 comments
  • Sat, 23 Nov

From Lazy Lisper to Confident Clojurist

Alexander Oloo (@alekcz)

  • 0 comments
  • Tue, 19 Nov

Clojure through the eyes of a Java developer

Kannan Ramamoorthy (@kannangce)

  • 0 comments
  • Mon, 18 Nov

Composable Data Pipelines for not-so-Big Data

Akaash Patnaik (@worldpiece)

  • 1 comments
  • Sun, 10 Nov

Debuggers in Lisps

Suvrat Apte (@suvratapte)

  • 0 comments
  • Thu, 7 Nov

Fight Complexity with Functional Programming

Gopal S Akshintala (@gopalakshintala)

  • 1 comments
  • Wed, 6 Nov

GANGES: Clojure retro game music engine

Bobby Towers (@porkostomus)

  • 1 comments
  • Tue, 29 Oct

Functional Programming Patterns

abhinav sarkar (@abhinavsarkar)

  • 2 comments
  • Mon, 28 Oct

GraphQL subscriptions with Lacinia, and how it compares to Java and Node.js

Gerard Klijs (@gklijs)

  • 0 comments
  • Mon, 28 Oct