Closed way0utwest closed 3 years ago
I would at least start with integrating sessionize - while it may not check all the boxes, it does most of them
As a speaker, I love Sessionize for the simple reason that it allows me to submit abstracts without having to copy/paste the same information over and over. The last years, SQLSaturdays had this option too, but from their own history of events. And, frankly, with a slightly sub-par interface.
The benefit of using Sessionize is that this would enable me to reuse session abstracts across almost all events I submit to.
Adding my two cents: we could create a unified email list (or similar mechanism) for speakers to subscribe to CFP announcements. Speakers could add tags for which technologies/platforms they know, as well as locations they are willing to speak at. Marcin Gminsky, @marcingminski, already has a data community calendar at https://datacommunity.events/events/.
Since I have been mentioned, I will ad my thoughts as I faced the same questions when building my aggregator.
After talking to speakers, it became apparent that they like sessionize because it's platform agnostic, i.e. they can easily re-use the same event for different conferences and they would not want to re-type, copy-paste the same data into different websites hence I settled on automatically integrating what's already there with my calendar.
What I was also looking into is to integrate the speaker profiles so events and conferences can be filtered by a particular speaker but never had enough time to do much with it.
From: Marcin Gminski notifications@github.com Sent: Friday, December 18, 2020 6:13 AM To: sqlcollaborative/DataSaturdays DataSaturdays@noreply.github.com Cc: Steve Jones steve.jones@red-gate.com; Author author@noreply.github.com Subject: Re: [sqlcollaborative/DataSaturdays] Speaker Sessions CFP Platform (#18)
Since I have been mentioned, I will ad my thoughts as I faced the same questions when building my aggregator.
After talking to speakers, it became apparent that they like sessionize because it's platform agnostic, i.e. they can easily re-use the same event for different conferences and they would not want to re-type, copy-paste the same data into different websites hence I settled on automatically integrating what's already there with my calendar.
What I was also looking into is to integrate the speaker profiles so events and conferences can be filtered by a particular speaker but never had enough time to do much with it.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/sqlcollaborative/DataSaturdays/issues/18#issuecomment-748076898, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6AGDDX3INGQ2OCVFYEL2DSVNIM7ANCNFSM4U42UKKQ.
Redgate respects your privacy. To find out how we handle your personal data, see our privacy policy at https://www.red-gate.com/privacy. Use of our software is subject to our license agreement, https://www.red-gate.com/eula. Our head office is Newnham House, Cambridge Business Park, CB4 0WZ, United Kingdom, and we are registered in the UK as company #3857576.
Sessionize is free for free events. If an event charges a lunch fee - is it free anymore from a Sessionize point of view? I know pre-cons are a no-no, so you can't do pre-con CFP's without paying. We might have to consider looking into the paid version of Sessionize?
But yeah, I do love the ease of use and platform agnostic approach of Sessionize.
I absolutely will say that we should use Sessionize, it makes it simple to use, it can feed a website simply and easily and it will be easy for us to code
In the early days of SQL Saturday when their interface didn't support pre-cons yet, calls for pre-cons were often handled in different ways. Eg. by just asking speakers to mail the organization. Could that be used to enable free Sessionize usage? Or is that skimming the rules too much?
Are the sessionize rates high enough that we should worry?
My contribution: use sessionize.com. Don't reinvent the wheel.
I looked up the new features on sessionize. An important note if we go for integrating with sessionize is to include in t&c that the privacy option for the event in sessionize is open so speakers that don’t get notified can find the event. We can make sure using the sessionize api.
Accessibility Links: Audio Link:https://gofile.io/d/YsEAjk Image Link:https://gofile.io/d/yUjkvx
My two cents. Keep it simple and use just sessionize:
Please don't reinvent the wheel. We will get all the stuff we need in a platform.
Accessibility Links: Audio Link:https://gofile.io/d/imAKO5 Image Link:https://gofile.io/d/UsHRlB
sessionize added via #149
Should we