Proposals
Rootconf Delhi edition

Rootconf Delhi edition

On network engineering, infrastructure automation and DevOps

Rootconf

Rootconf is a platform for SRE, DevOps, security and InfoSec developers and cloud operators. We bring the community together through talks, workshops and events.

Propose a session

India International Centre (Kamaladevi Complex), Seminar Hall 1, 2 & 3, New Delhi

Call for proposals

We are accepting talks on the following topics:

  1. Monitoring, logging and alerting – running small-scale and large-scale systems
  2. Automating infrastructure management: tooling and architecture
  3. Infrastructure as code
  4. Network management, network security and network engineering
  5. Architecting for the cloud

Types and duration of talks:

  1. Full talks: 40 mins duration including Q&A
  2. Crisp talks: 20 mins duration including Q&A
  3. Birds of Feather (BOF) sessions of 1 hour duration
  4. Hands-on workshops, of 3-6 hour duration.

You can also suggest a topic for someone else to speak/teach a workshop. If we find a speaker/trainer for the topic you proposed, we will send you a Rootconf t-shirt.

Participant profile for Rootconf Hyderabad will include:

  1. SRE
  2. Distributed systems practitioners
  3. Network engineers
  4. DevOps programmers
  5. Security and DevSecOps professionals

This profile will help you to understand who will be the audience for your talk, and therefore, how you should structure you talk and takeaways.

We don’t accept:

  1. How-to and introductory-level talks.
  2. Tooling talks without a clear problem statement. Instead, tell us what problems the tool solves for you, and why you advocate community members to use the tool.
  3. Proposals where source code is closed or where you cannot reveal code and implementation details.

Guidelines for submitting proposals for Rootconf Delhi:

  1. Write the proposal in gender neutral language. Use the words ‘they/them’ instead of ‘he/she’.
  2. Explain the problem you are solving when submitting a proposal. We give weightage to novelty of problems and problem-solving approaches.
  3. Focus on narrowing down what the audience will learn from your talk. The best way to do this is by putting yourself in the audience’s shoes: what do you want to learn (that will make you a better practitioner) if you were in the audience listening to your own talk?
  4. Provide implementation details. But the implementation details – code samples, architecture approach, etc – in the context of the larger problem you are solving.
  5. Never lose sight of the problem!

Note that reviews will carried out on the proposal pages only, as comments. Proposers must check their proposals for new comments, and to respond to earlier comments.

Passes and honorarium for speakers:

We pay an honorarium of Rs. 3,000 to speakers. Confirmed speakers also get a pass to the conference and a discount code which they can share with their colleagues, communities they are part of, and on social media channels. We do not provide free passes for speakers’ colleagues and spouses. Please don’t ask us for this.

Travel grants for outstation speakers:

Travel grants are available for international and domestic speakers based on the event’s budget. If you require a grant, mention it in the field where you add your location.

Last date for submission is 30 November, 11:59 PM

If you have queries, write to rootconf.editorial@hasgeek.com

Propose a session

All proposals

Confirmed sessions

Not everything can fit in rows and columns

Ashok Vishwakarma (@ashokvishwakarma)

  • 2 comments
  • Thu, 17 Oct

Load balancing: in-depth study to scale @80K TPS

Shrey Agarwal (@shreyagarwal) via Zainab Bawa (@zainabbawa)

  • 0 comments
  • Wed, 21 Aug

Meeseeks(Service-Graph)

Gaurav Sharma (@gaurav75)

  • 10 comments
  • Mon, 6 May

Unconfirmed proposals

Around the cluster in 80ms : The journey of a packet

Monica Gangwar (@monicagangwar)

  • 0 comments
  • Sun, 10 Nov

The era of Smart Contracts

Shrutirupa Banerjiee (@shrutirupa)

  • 2 comments
  • Tue, 29 Oct

Strongly consistent centralized Document Service with eventual consistent Search Store

Aman Bansal (@aman-bansal)

  • 1 comments
  • Sat, 26 Oct

The good, the bad and the ugly of Kubernetes - A Practitioners View!

Vijay Dharap (@dharapvj)

  • 0 comments
  • Sat, 19 Oct

Securing your Kubernetes cluster

saurabh gupta (@gupta-saurabh)

  • 1 comments
  • Tue, 15 Oct

Architecting Scalable and resilent services in Azure

Ameer Jhan (@ameerthehacker)

  • 3 comments
  • Sun, 13 Oct

Solving Real World Problems of Running CMS on Kubernetes using Operators

Adheip Singh (@adheipsingh)

  • 1 comments
  • Wed, 18 Sep

Immutable infrastructure on AWS using HashiCorp

Kashif Razzaqui (@kashif) via Zainab Bawa (@zainabbawa)

  • 0 comments
  • Wed, 21 Aug

Merging two live data-centers into one

Ritikesh (@ritikesh)

  • 4 comments
  • Wed, 14 Aug

Istio and Auth0 securing our applications on Kubernetes cluster

Mamta Jha (@mjha)

  • 6 comments
  • Sat, 10 Aug

Monitoring and Securing your Kubernetes Apps with Istio

Mamta Jha (@mjha)

  • 0 comments
  • Thu, 8 Aug

Zawinski's Law for Webservices

Madhavprasad Pai (@saintpai)

  • 0 comments
  • Wed, 31 Jul

Please don't do this - a conversation on bad programming practices

Shreyansh Pandey (@weirdpanda)

  • 0 comments
  • Thu, 11 Jul