Home

Welcome to the Confluence wiki!

Here is the discussion on how to automate various conferences all around the world. Our primary focus is right now on automating PyCon India & PyDelhi Conference. We'll be trying to make this as generic as possible so that all other conference would be able to use this.

Raw notes

• Automate as much as possible:

  • As soon as the talks get selected:

  • Speakers get an automated mail that their talk has been selected.

  • Volunteers assigned get an automated mail introducing them to speakers and their team members. - Schedule announcement: json schedule

    • Website & App use this json

  • Automated mail sending before conference to attendees & Speakers along with their timing and hall no.

  • Speaker's get an automated mail regarding submission of the resources for their talk i.e. slides, softwares used(in case of hand's on).

  • Automated mail to the corresponding volunteers of the speakers & attendees regarding the requirements to be fulfilled before the talk/workshop, as the response received by the speaker's side regarding the same.

  • Feedback

  • MoM,

• Work Assignment -- Trello

• Standup --partially done -- https://github.com/CuriousLearner/standup

• TDD

• Junction -- improve

• Volunteers management

• Lightening Talks registration, selection -- Akkshay

  • Register through conference app / website through REST API
  • FCFS talk selection; Select talk with buffer and send mails.
  • Volunteer can override that setting.
  • Submit your slides -- provide it later on a single laptop.

• Registration via mobiles, distribution of swags -- QR Mobile app -- Akkshay

• Social Media -- Twitter & Fb API one click share

• Section for social media things so that people are updated with tweets and blogs.

Tech Stack: Django + MySQL + Celery

RESTful API + Logging

Registration + auth - Volunteers + Users + Speakers - permission

MailSender - templates - volunteers, users, speakers Talks -- Junction SocialMedia -- One Click post - Most volunteers can post to the queue. - One single lead volunteer can approve and then it would be posted. - Section to show the tweets is approved or rejected Lightening Talks

========================================================================

Tables:

• users (id, name, email, gender, tshirt_size, phone, permission_group, ticket_id)
• talks (talk_id, talk_name, duration, talk_group, talk_category)
• permissions (id, permission_name)
• social_media_posts (id, text, attachment, user_id, timestamp, status[POSTED, REJECTED]).

Use case:

• Form T-shirt size mandatory
• Inventory count
• Social media, one click, only bot access.
• Display message on the form that no alterations will be done for the t-shirt size, once form is submitted.
• In case of ticket transfer
• On Spot registration
• All the basic informations must be viewed on the app i.e. What's going on in which audi or lecture hall, What's
  coming up next. Notifications on the start of each thing i.e. Lunch, Talks in various halls.
• There must be separate section of DevSprints on the app to show which projects are currently running there.
• We could add a map box for the route to the venue(via google maps).
• Volunteer confirmation.

Modules:

• Registration
• Mails,
• Talks,
• Devsprint

4. Social Media