We should make use of the Sessionize API

[SQLDBAWithABeard]

Sessionize have built an excellent platform for Speakers, managing call for papers and embedding Agendas

They state

We think pricing should be fair and simple. All features included in each package. Free for community events with no participation fee

https://sessionize.com/pricing

I know that it has been used for events such as DataGrillen, Data Scotland and when organising PowerShell Conference Europe we used it also (we had to pay)

Advantages

• One place for speaker abstracts which they control and also works with other events

• Fantastic Call for Speakers experience for organisers

  • Deals with Acceptance AND declined Emails
  • Easy ranking system, can be used by multiple people at same or different times

• Super Easy to embed the agenda in and it auto updates and is easily accessed by API for other use cases (Apps etc)

[Stuart-Moore]

We use it for relay as well. It needs each event to be checked as ‘not for profit’ rather than the organisation. Which will cause issues if you’re thinking of automating it, though the approval is just an email to support so could still be done.

And if people want to do paid Precons to raise funds that will probably get in the way unless they do that through another platform.

[spaghettidba]

Great point about precons. Honestly, I don't know how much effort it would be to build the session submission / selection / agenda. If we are planning to use their plaform we should probably reach out to them, explain in detail what is the current model and ask what they have to offer.

[SQLDBAWithABeard]

Super point about pre-cons - I think that deserves a separate issue and yes reaching out to Sessionize is a brilliant idea.

[way0utwest]

I like the idea of using a service here overall. I haven't used sessionize from the organizer perspective, but I do think allowing speakers to re-use submissions is good.

I would prefer that we ensure we keep all sessions chosen on a schedule on the DataSaturday side, to provide historical records.

The counterpoint to sessionize might be expanding to pre-cons or other paid items, including Bits-type events or for-profit items, but perhaps that exists outside the charter of this project.

[way0utwest]

Added a more general item on this in #18

[SQLDBAWithABeard]

completed #149