├── .eslintrc.json
├── .gitignore
├── .jsbeautifyrc
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE.md
├── README.md
├── coc.html
├── convince-my-boss.docx
├── convince-my-boss.html
├── convince-my-boss.txt
├── custom
└── css
│ ├── accordion.css
│ ├── animate.css
│ ├── bootstrap.css
│ ├── bootstrap.min.css
│ ├── buttons.css
│ ├── scroll.css
│ └── style.css
├── data
├── schedule.json
├── speakers.json
└── sponsors.json
├── faq.html
├── font-awesome
├── css
│ ├── font-awesome.css
│ └── font-awesome.min.css
├── fonts
│ ├── FontAwesome.otf
│ ├── fontawesome-webfont.eot
│ ├── fontawesome-webfont.svg
│ ├── fontawesome-webfont.ttf
│ └── fontawesome-webfont.woff
├── less
│ ├── bordered-pulled.less
│ ├── core.less
│ ├── fixed-width.less
│ ├── font-awesome.less
│ ├── icons.less
│ ├── larger.less
│ ├── list.less
│ ├── mixins.less
│ ├── path.less
│ ├── rotated-flipped.less
│ ├── spinning.less
│ ├── stacked.less
│ └── variables.less
└── scss
│ ├── _bordered-pulled.scss
│ ├── _core.scss
│ ├── _fixed-width.scss
│ ├── _icons.scss
│ ├── _larger.scss
│ ├── _list.scss
│ ├── _mixins.scss
│ ├── _path.scss
│ ├── _rotated-flipped.scss
│ ├── _spinning.scss
│ ├── _stacked.scss
│ ├── _variables.scss
│ └── font-awesome.scss
├── fonts
├── glyphicons-halflings-regular.eot
├── glyphicons-halflings-regular.svg
├── glyphicons-halflings-regular.ttf
└── glyphicons-halflings-regular.woff
├── hotels.html
├── icons
├── android-icon-144x144.png
├── android-icon-192x192.png
├── android-icon-36x36.png
├── android-icon-48x48.png
├── android-icon-72x72.png
├── android-icon-96x96.png
├── apple-icon-114x114.png
├── apple-icon-120x120.png
├── apple-icon-144x144.png
├── apple-icon-152x152.png
├── apple-icon-180x180.png
├── apple-icon-57x57.png
├── apple-icon-60x60.png
├── apple-icon-72x72.png
├── apple-icon-76x76.png
├── apple-icon-precomposed.png
├── apple-icon.png
├── browserconfig.xml
├── favicon-16x16.png
├── favicon-32x32.png
├── favicon-96x96.png
├── favicon.ico
├── manifest.json
├── ms-icon-144x144.png
├── ms-icon-150x150.png
├── ms-icon-310x310.png
├── ms-icon-70x70.png
└── window-close-solid.svg
├── img
├── 10.png
├── armin-ronacher.png
├── arrow-right .png
├── arrow-right.png
├── banner-logo.png
├── bg.png
├── bg1.jpg
├── border1.png
├── border2.png
├── card-bg1.jpg
├── card-image.jpg
├── carol-willing.png
├── circle1.png
├── circle2.png
├── dots.png
├── favicon.png
├── fb.png
├── footer-logo.png
├── left-arrow.png
├── mail.png
├── main-banner.jpg
├── micro.png
├── oyo_rooms_contact_banner.png
├── pdfdownload.png
├── ran1.jpg
├── sidu-ponnappa.png
├── speaker.jpg
├── speaker.png
├── sponser1.png
├── sponser2.png
├── sponser3.png
├── sponsors
│ ├── DBS_Logo.png
│ ├── DESCO_Logo_2c.jpg
│ ├── Elucidata.svg
│ ├── LiveHealth_logo.png
│ ├── Manninglogo_outline.png
│ ├── Pramati.png
│ ├── VMware_logo.jpg
│ ├── aqr.jpg
│ ├── atonarp.png
│ ├── corteva.png
│ ├── fossee.png
│ ├── go-jek.png
│ ├── google_developers.png
│ ├── hackerrank.png
│ ├── ibm.png
│ ├── indeed.png
│ ├── jetbrains.svg
│ ├── logo-innovaccer-full.png
│ ├── pipal.png
│ ├── reckonsys.png
│ ├── soroco.png
│ ├── talent-sprint.png
│ ├── zaubacloud.png
│ └── zeomega.png
├── ticket-image.jpeg
├── timeline
│ ├── PyCon2009.jpg
│ ├── PyCon2010.jpg
│ ├── PyCon2011.jpg
│ ├── PyCon2012.jpg
│ ├── PyCon2013.jpg
│ ├── PyCon2014.jpg
│ ├── PyCon2015.jpg
│ ├── PyCon2016.jpg
│ └── PyCon2017.jpg
├── travis-oliphant.png
├── twitt.png
├── venuebg.jpg
├── venuebg3.jpg
└── wc.png
├── index.html
├── js
├── bootstrap.js
├── bootstrap.min.js
├── canvas.js
├── content.js
├── custom.js
├── index.js
├── index_canvas.js
├── jquery-1.10.2.js
├── jquery.easing.min.js
├── jquery.min.js
├── jquery.scrollTo.js
├── jtline.js
├── schedule.js
├── speaker.js
├── sponsor.js
├── timeline.js
├── twitterfetch.js
└── wow.min.js
├── main-agenda.pdf
├── open-spaces.html
├── speakers.html
├── sponsorship.html
├── sponsorship_prospectus.pdf
├── ticket-transfer.txt
├── travel.html
├── volunteer.html
└── workshop-prerequisites.html
/.eslintrc.json:
--------------------------------------------------------------------------------
1 | {
2 | "env": {
3 | "browser": true,
4 | "es6": true,
5 | "jquery": true
6 | },
7 | "extends": "standard",
8 | "globals": {
9 | "angular": false,
10 | "WebSocket": false,
11 | "THREE": false
12 | },
13 | "rules": {
14 | "brace-style": [2, "stroustrup"],
15 | "indent": ["error", 4],
16 | "max-len": [2, {
17 | "code": 120,
18 | "ignoreUrls": true
19 | }],
20 | "no-invalid-this": 1,
21 | "no-var": 0,
22 | "no-redeclare": "warn",
23 | "no-unused-vars": "warn",
24 | "one-var": ["off", "always"],
25 | "semi": [1, "always"]
26 | }
27 | }
28 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | /.vs
2 | /.vscode
3 | /node_modules
4 | package-lock.json
5 | package.json
6 | *.ini
7 | PyCon 2018 India Logo.ico
--------------------------------------------------------------------------------
/.jsbeautifyrc:
--------------------------------------------------------------------------------
1 | {
2 | "end_with_newline": true,
3 | "indent_char": " ",
4 | "indent_size": 4,
5 | "indent_with_tabs": false,
6 | "max_preserve_newlines": 3,
7 | "js": {
8 | "brace_style": "end-expand",
9 | "break_chained_methods": false,
10 | "indent_level": 0,
11 | "jslint_happy": false,
12 | "jslint_happy_align_switch_case": false,
13 | "keep_array_indentation": true,
14 | "space_after_anon_function": true,
15 | "space_before_conditional": true,
16 | "space_in_empty_paren": false,
17 | "space_in_paren": false,
18 | "wrap_attributes": "auto",
19 | "wrap_line_length": 0
20 | },
21 |
22 | "html": {
23 | "brace_style": "collapse",
24 | "extra_liners": ["head", "body", "/html"],
25 | "indent_body_inner_html": true,
26 | "indent_head_inner_html": true,
27 | "indent_inner_html": false,
28 | "unformatted": ["a", "sub", "sup", "b", "i", "u"],
29 | "wrap_attributes": "auto",
30 | "wrap_attributes_indent_size": 4,
31 | "wrap_line_length": 120
32 | },
33 |
34 | "css": {
35 | "convert_quotes": "single",
36 | "selector_separator_newline": true,
37 | "space_around_selector_separator": true
38 | }
39 | }
40 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6 |
7 | ## Our Standards
8 |
9 | Examples of behavior that contributes to creating a positive environment include:
10 |
11 | * Using welcoming and inclusive language
12 | * Being respectful of differing viewpoints and experiences
13 | * Gracefully accepting constructive criticism
14 | * Focusing on what is best for the community
15 | * Showing empathy towards other community members
16 |
17 | Examples of unacceptable behavior by participants include:
18 |
19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances
20 | * Trolling, insulting/derogatory comments, and personal or political attacks
21 | * Public or private harassment
22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission
23 | * Other conduct which could reasonably be considered inappropriate in a professional setting
24 |
25 | ## Our Responsibilities
26 |
27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28 |
29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30 |
31 | ## Scope
32 |
33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34 |
35 | ## Enforcement
36 |
37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact@in.pycon.org. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38 |
39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40 |
41 | ## Attribution
42 |
43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44 |
45 | [homepage]: http://contributor-covenant.org
46 | [version]: http://contributor-covenant.org/version/1/4/
47 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contribution Guidelines
2 |
3 | Thanks for your interest in contributing to PyCon India 2018 website. Your valuable contribution is much appreciated.
4 |
5 | The following is a set of guidelines for contributing to PyCon India 2018.
6 |
7 | ## How Can I Help?
8 |
9 | Start looking through the issues and watch out for any issues with the `bug` or `help wanted` labels. Issues marked with these labels haven't been assigned to anyone yet and we would love for you to work on them.
10 |
11 | ### Request a feature
12 |
13 | If you think there is a cool feature you would like to add please create an issue for that and we will assign that to you if the feature looks good to add.
14 |
15 | ## Reporting bugs
16 |
17 | If you find any bugs, it would be great if you would let us know so we can look into it. You can do so by creating an issue. If you don't know how to create an issue, please follow [these instructions](https://help.github.com/articles/creating-an-issue/). Screenshots and notes for how you encountered the bug are really helpful when reporting bugs!
18 |
19 | ## Creating Pull Requests
20 |
21 | After you've created a patch that fixes an issue, please submit a pull request for it. Mention **@pythonindia/pycon-2018-team** to get the Pull Request reviewed. If you're not sure how to create a pull request, please follow [these instructions](https://help.github.com/articles/creating-a-pull-request/). In general we'd like to ask you to please target the master branch with your pull requests.
22 |
23 | We recommend creating a new branch for each feature task/bug since it makes easier to edit commits in future if needed.
24 |
25 | ## Reviewing Issues and Pull Requests
26 |
27 | You're welcome to review issues and pull requests, provide feedback, and answer questions. Please remember to be friendly and respectful when commenting on issues or pull requests, and always follow our [Code of Conduct](https://in.pycon.org/2018/coc.html). It's okay for people to make mistakes and ask questions!
28 |
29 |
30 | ## How Can I Get Help?
31 |
32 | If you have a question or need help, please leave a comment on the issue you have a question about or are working on. We will try to answer your question and help you as soon as possible.
33 |
34 | If you are stuck on some issue and would like help from someone in the community you can ask help in the mailing list of PyCon India. Be sure to mention the Issue # and mention **Website Contribution** in Subject line so it will be easier for people to help you in this regard.
35 |
36 | ## Workflow & Merging Pull Requests
37 |
38 | - We will be using master branch for development and gh-pages branch for viewing the website directly using github pages
39 |
40 | - Reviews to Pull Request created can be requested by mentioning **@pythonindia/pycon-2018-team** in the Pull Request body or comments
41 |
42 | - Anyone is free to Review any Pull Request but merge access will be limited to the Web Working Group of PyCon India 2018
43 |
44 | - Feature Changes will be reviewed by the Web Working Group or other contributors, while Hotfixes can be merged without a review or even directly pushed by the Web Working group without the need of a PR
45 |
46 |
47 |
48 | The Contribution Guidelines have been based on CONTRIBUTING.md from the [2017 DjangoCon U.S. website repo](https://github.com/djangocon/2017.djangocon.us)
49 |
--------------------------------------------------------------------------------
/LICENSE.md:
--------------------------------------------------------------------------------
1 | The assets in this repository are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
2 |
3 |
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
4 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # PyCon India 2018 Website
2 | This is the official website of PyCon India 2018, the Premier Conference in India on using and developing the Python Programming Language.
3 |
4 | The PyCon India 2018 Website is a website purely made of html, css and javascript/jQuery
5 |
6 | ## Contributing to the Website
7 |
8 | Please read our [Contribution Guidelines](CONTRIBUTING.md) to Contribute to the Website
9 |
10 | ## Code of Conduct
11 |
12 | As a contributor please follow the [Code of Conduct](CODE_OF_CONDUCT.md) to keep the community open and inclusive. Also please read and follow the [PyCon India Code of Coduct](https://in.pycon.org/2018/coc.html) which governs the overall Conduct for the Conference.
13 |
14 | ## License
15 |
16 | [Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License](LICENSE.md)
17 |
--------------------------------------------------------------------------------
/convince-my-boss.docx:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/pythonindia/inpycon2018/f2beb31a9b62c643c46f6c17ec646eb0c3e1ba3c/convince-my-boss.docx
--------------------------------------------------------------------------------
/convince-my-boss.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
115 | Do you want to attend PyCon India, this year? Not sure how to pitch the same to your boss. Well, we are here to help. Leave 116 | the hard work to us, use this letter as template and edit it to help make your case. We hope to see you at PyCon 117 | India 2018, tickets are available here. For downloads, please refer to this section. 118 |
119 |Dear {bossName},
121 | 122 |I’d like to attend the upcoming PyCon India 2018 conference taking place October 5-9, 2018 in Hyderabad, India. PyCon's 123 | are premier conferences about developing and using the Python programming language. It attracts the best programmers, 124 | experts, enthusiasts, community leaders, entrepreneurs, and even college students from all corners of the country 125 | and abroad.
126 |The event focuses on key aspects of sharing knowledge and experience, solving important issues together, learning 127 | and collaborating, meeting and network with the best and brightest in the community in an open-source ecosystem.
128 |About a 1000+ of the industry's most dedicated and experienced individuals from different fields are bound to be 129 | in attendance for the 10th edition of this mega event. An opportunity like this is crucial for our company’s growth 130 | and development.
131 |Here's how my presence at PyCon India 2018 could effectively help us and our brand get exposed to an ocean full of 132 | opportunities that we are yet to explore.
133 |134 |
PyCon India aims at bringing folks who love Python under one roof and create a healthy environment to learn. 137 | Fusing together fields of Data analysis, ML/AI, Automation, Web development, Software development and more.
138 |It's a unique chance to create strategic partnerships and promote our company's brand at the forefront of the 142 | Python Community in India, by gathering valuable insights on current market trends and also recruiting fresh 143 | talent. 144 |
145 |PyCon India is also a learning opportunity, offering a wide array of talks, workshops, keynotes, developer 149 | sprints strung together in a packed schedule each day divided by various tracks that people could follow.
150 |Each presented by industry experts, community leaders and many young minds delving into new technologies and 154 | latest trends in the market. Some including ML/AI, Automation, Embedded Systems, Networking, Security, Web 155 | Development. 156 |
157 |I will also be meeting top technical minds, brainstorm with them on ideas, challenges, and best practices. 161 | Collaborate with them on projects and solve technical issues.
162 |It is THE conference to go to for Python professionals. You can learn more about the conference and last year's 166 | talk and sessions here.
167 |If I register before 30th of June, the fee is only 1200 rupees. Included in the conference ticket is access to all 168 | PyCon India keynotes and talks, sponsor showcase, community spaces (if included this time) and many other networking 169 | events, an official PyCon India T-shirt along with lunch and high-tea in the evening for both days (6th-7th October)
170 |I would be happy to write a post-conference report detailing what I’ve learned and to recommend any changes that 171 | we could implement to improve our practices. Please let me know if you have any questions or concerns. I hope we 172 | can make this opportunity work.
173 |Thank you,
174 |
{yourName}