Extend stored data to include speaker package, requested topics etc...

[liam-wiltshire]

For manually submitted events, the submitter should be able to include more or less any data that they deem relevant to speakers who may submit -for example:

• Speaker Package
• Requested Topics
• Talk Types (tutorial, workshop, etc.)

Perhaps this additional 'meta' data could be stored as a JSON object to make it flexible to whatever the user wants to add?

[heiglandreas]

Though I'd store it as a 1:n relation with a type (f.e. speaker-package) and a content. Interface like this? (Replace Twitter etc. with "Speaker-package", "Requested Topics", "Talk-Types" etc) and more space in the fields…