EuroPython 2016 Sprints

• Features

  • Be able to manage cancelled talks.
  • REST API for some tools (mobile app, access from ep-tools....).
  • Management of volunteers and tasks.
  • Connect the ticket search app to the database or REST API.
  • Add more "types" of participants: "keynote", "sponsor".
  • Tinder-like interface for talk votings, or something more dynamic. (Right now, the position of the talk influences the voting).
  • Management for financial aid.
  • Scheduler/Queue (Celery) for mailings.
  • https://en.wikipedia.org/wiki/Single_transferable_vote for the talk voting (this would have to be discussed with the program WG first)
  • User documentation for the admins, e.g., "how to add a sponsor", "how to manage the talks", etc.

• Bugs to fix

  • Critical

    • Improve the setup, be able to startup without an initial DB.
    • Improve the CONTRIBUTION/GET_STARTED documentation.
    • Give details on the models/domain parts in the documentation, e.g., how to modify the talks, users.
    • Cleanup users with duplicate accounts.
    • Fix the issue with duplicate accounts.
      • the current codebase is using some features of django_social_auth that are not supported by the current version of django_social_auth. An up-to-date Django could probably fix the whole issue (specific version TBC).
      • django_social_auth is deprecated and the recommended module to do this is python_social_auth.
      • the system assumes that user emails are unique in various places, causing problems when a user has multiple accounts with the same email address
    • Update to Django 1.8, check dependencies with Django CMS.
    • Store Stripe transaction IDs in the database. This will make management/support of orders easier and also is a prerequisite for processing refunds directly through the website at some point.

  • Not critical

    • Remove the SIM card sale part.
    • Remove the left-side menu in the schedule page for mobiles.
    • Manage refunds through the website.
    • Should we use PostgreSQL instead SQLite.
    • Python 3?

• Ideas on the refactoring

  • We need tests.
  • Merge of p3 and conference.
  • Simplify the codebase.