Guidelines for Proposal Submission

Following are the guidelines for proposal submission

Please mention type of Proposal as given below in the Title of the Proposal.
The proposal should have an objective with clear expectation for the audience.
The Proposal description should be short and to the point.
The proposal should have proper prerequisites like environment setup, library version.
No proposal will be selected without a link to appropriate session content like presentation, pdf, code snippets etc.
Proposal content should adhere to code of conduct.
Proposal content links can be updated later.
Proposal content shouldn’t have a company name throughout the content. Mention of the employer is allowed only at the beginning of the content (presentation/pdf).
Background image/wallpaper shouldn’t contain company name/logos.
For any questions, please write to contact@hydpy.org.

Proposal Types

We have three kind of Proposals - General Talks, Lightning Talks and Workshops. Please mention the Proposal type in the Title of the Proposal. Give a Title like Proposal Type : Proposal Title

General Talks

These are the traditional talk sessions scheduled during the first day of conference. They will be conducted on Day 2 of Conference, Sunday, 8th Oct. The length of these tracks are 45 minutes.

Lightning Talks

These are short length talks that will be conducted on Day 2 of Conference, Sunday, 8th Oct. The time limit is 5 minutes. But we can extend it depending on number of talks submitted.

Workshops

As with the talks, we are looking for Workshops that can grow this community at any level. We aim for Workshops that will advance Python, advance this community, and shape the future. Each session runs for 6 full hours plus a break for lunch. There will be 2 workshops going parallely on Day 1 of Conference, Saturday, 7th Oct in the same venue that hosts the main conference. Workshop I is aimed for Begineers while Workshop II is a Advaced Session aimed for Professionals.

Themes and Topics

These will be the themes and topics

Core Python and Python 3 features
Concurrent and Asynchronous programming in Python
Data Science and Analysis
Web Development
Python and IOT
Functional Programming
Artificial Intelligence
Continuous integration and Deployment
Testing
Scientific Computing
Cloud computing with Python

Important Dates

31st August, 2017 : Deadline for Proposal Submission
16th September, 2017 : Talk selection and announcement

Hosted by

pyconfhyd

Submit Proposals for PyConf Hyderabad more

All submissions

Previous Next

[General Talks]: Practicing Continuous Integration and Deployment with Jenkins 2 Pipeline and Python

Submitted Aug 25, 2017

Technical level: Beginner

Jenkins 2.x is equipped with the capabilities to create pipeline-as-code. Pipeline suite of plugins has opened up a multitude of possibilities, like, enhancing the collaborative workflow model that DevOps demands, treating CI/CD as code. Talk would introduce the audience to Jenkins Pipeline (scripted) with the aid of simple deployment model in the cloud. It would appeal to those who are key movers and shakers in Software delivery: DevOps Engineers, Build and Release Managers.

Outline

Pipeline introduction
Basic Pipeline steps
Tips to start writing Pipeline code
In a sample Jenkins project, show usage of steps
Construct a simple build flow to showcase power of Pipeline

Speaker bio

Ram has about two and a half decades of work experience in systems management, continuous integration, mainline health monitoring, release management, tools automation in various industry domains, like, mobile, semiconductor, cybersecurity, and networking. Over the years, I have worked on different types of projects thus accumulating whole set of good practices from both technical and processes aspect. And, I talk will try to integrate some of those practices as part of the demo.