@SaptakS in that issue, the need is to validate POST and PUT speaker and session API payloads according to custom forms. Like if in custom form, track is required for a Session, then don't accept null for it. I can do that issue if you want.
@shivamMg It would be good, if we have a few events to test. Maybe you could help afterwards to create a full JSON set we can import for FOSSASIA 2016. There is the open event scraper that could help to get you started.
I am still getting this error in my local branch and I just updated it:
alembic.util.CommandError: Multiple head revisions are present for given argument 'head'; please specify a specific target revision, '<branchname>@head' to narrow to a specific head, or 'heads' for all heads ```