dataplat / datasaturdays Goto Github PK
View Code? Open in Web Editor NEWA repository for open sourcing a solution for Data Saturdays
License: MIT License
A repository for open sourcing a solution for Data Saturdays
License: MIT License
Open issue for the first event and any support needs they may have.
Page is already up: Data Saturday #1 - Pordeone
PR for the page: #35
If there are any needs, please list them in comments below.
Data Saturday Johannesburg 2021
Provisional links to speaker submission and event here:
https://sessionize.com/data-saturday-johannesburg/?e=e0483b
https://www.eventbrite.com/e/data-saturday-johannesburg-2011-tickets-134437071901
~Links will change when event goes live
This will be an online only event, both because its the right thing to do right now and Microsoft our usual venue sponsor do not allow in-person events at the moment.
A test for issue writing but also
Which Version of English are we going to use for this repo. I do not mean the web-site, that will hopefully cater for all but in the wiki, read me etc.
I can cope (more or less thanks to Chrissy) with doing it in US or UK or Aus but I cant cope with UK and US in the same place.
Thoughts please
Issue created as organizers are interested in using this platform.
One of the limitations of the SQLSaturday brand was that it contained "SQL" and "Saturday". As we've seen over time, "SQL" no longer fits for the data platform; it's gotten increasingly broad.
Likewise, organizers occasionally tried to stretch the model to cover events on other days (Sundays or Fridays, for example). Are you positioning this to be an event heled almost exclusively on Saturdays, or do yo want more flexibility than that?
DataDay, DataPlatfomDay....
One of the challenges with sqlsaturday is that a lot of the tools that were genuinely helpful early on were eventually overtaken by other services like sessionise.
At the time of writing, the following are listed as important assetts in the readme:
I wonder whether these need to be centralised and maintained in house in 2021+, or whether we are creating work, overhead and tech debt for ourselves for minimal return.
Perhaps point 1 is better served by a repo with guidance to organisers for self hosting their own wordpress site? Or perhaps we can publish a standard notnet core web app on github with instructions to fork the repo and self host? Perhaps we can talk to Microsoft and ask for free hosting in Azure for these sites, since I'm assuming we are still going to be primarily a microsofty/azure heavy crowd?
As for point 2, can we really expect to build something that's more useful and easier to maintain than sessionise?
Rather than getting into the weeds on these specific points, the emphasis of my question is whether we can be as deliberate about what we DON'T do, as we are about what we DO do. I feel this would help us to avoid creating another powerful centralised org/admin team and support us to keep as much autonomy as possible with the event owners themselves.
This is the issue for the Data Saturday in Guaemala
A number and page are needed.
Any support requests, please comment below.
Easy access to virtual event urls and options.
We should provide a repository with the resources for:
I've organized and promoted an event with videos and it's been so good marketing side. Just an idea:
This is the reason why I would suggest a guideline doc.
I'd like to see an option to run a 1/2 day schedule that repeats in the afternoon, letting each speaker deliver two sessions, but ensuring attendees have 2 options to see a talk
To enable simple easy automated event creation without manual input
Right now, we have GitHub actions which will deploy the website on a new commit to master.
There is a lot missing from the rest of the process. But we are in a good place to start the way we want to go on
https://twitter.com/mipsytipsy/status/1340958240184516611?s=20
I'll start a list, please add to it.
With the new COVID world, and potential limitations on attendance when things open up, I would think a way for attendees to be added to a waitlist, by time of registration. I would include the ability for someone to cancel a registration and auto move of people from the waitlist to the attendee list automatically.
Organizers ought to be able to bulk move xx people as well.
As of 20 Dec 2020, there are six events in flight. I am ignoring Albuquerque and Orlando as they are too far out.
These events need support and help to run. As they are virtual, I think the resources are minimal, but we need something. I have sent this to one organizer already, but welcome comments. The main items needed are:
My advice:
Any other advice or things I've missed are appreciated.
We are 5 events live and each time, an administrator has merged the pull request, which has set off the publish action to publish the site. They have then logged into twitter and sent a tweet from the DataSaturdays account
Automation is the goal - this could be automated using
This is related to #11 and #17, but not really a duplicate.
SQL Saturday was conceived with numbering, meaning events were sequentially listed.
Some people did not like the numbering, as it doesn't brand the event well. As a result, hash tags like #SQLSatSlovenia instead of #SQLSat1010 were used. Sometimes both were used, which is confusing.
I like the numbering, and the milestones (100, 200, etc) and the sequential listing is nice. I also like ensuring the cities are represented.
I would propose that titles and hashtags be suggested as:
I'd prefer to allow people to have multiple events a year in a city, so some differentiation is needed, but also some way to group those that occur in an area.
Most likely part of the session design. Not sure if any different needs to happen other than adding a full day category. Might also need the option to chose a different day. Most pre-conference happen on Friday.
Given the preliminary state of DataSaturdays, I think it would be beneficial to enable Github Discussions on this repo so that high level brainstorming / discussions can happen there and subsequently allow Issues to remain focused on specific action items that can be tied to a PR.
What email options would you want? I'd think that we need these choices for sending an email:
Anything else? I wouldn't think an individual needs to be contacted from the system, but perhaps.
How do we communicate the policies around harassment?
How can someone report harassment to organizers?
In the unlikely event that an issue comes up with an organizer how can someone escalate this for mediation?
In what way do we want to allow speaker and session rating?
In addition, what features are needed:
I assume we are looking at this for a better site than (SQL Saturday)[https://www.sqlsaturday.com/]. With that in mind, perhaps we need a list of the items to deal with? This list likely needs to be on the wiki, but a discussion here first would be good.
I like this idea: https://devopsdays.org/organizing/, it sets out pretty clearly what the "rules" are for using their brand. Not advocating re-using their rules, just their transparency in communicating said rules.
As this is a group community project, and I have seen decisions being made, issues closed, etc., I am concerned that we may not be considering how opinions and views may diverge on issues, especially over time. I realize the early days will be different than things may move over time.
I would propose that we have a motion and second to close issues (or advance them) to a vote, with 2-3 positive votes advancing an issue and 3 negative votes delaying it.
We can always change course or reverse actions, but having a process of some sort would be valuable.
I have heard that for DevOpsDays, profitable events use part of their surplus to provide "bridging" loans to new events, so that they can pay early bills - venue etc. - before their sponsors pay them, which as we all know can take a long time. This is organised in a peer-to-peer way rather than being centrally brokered. I've often thought such a model would be helpful, if unlikely, for SQL Saturday.
To discuss methods, solutions for cloning the website for new events
What payment providers do people think need to be supported. The current SS site support Paypal only.
I know Zelle is big in some places, as is Square. Others for use in EU/APAC?
requesting details from organizers.
We will need a registration page for welcoming and asking participants for the relevant informations.
While most people have email, having a general set of boxes for events was useful. I would propose some guidance here for organizers, as well as some generic support in a framework or organization to allow email for events.
Should we
I would love to see a library that brings all the content from events together
Ideally with the option to either upload or just link content (on github, personal blogs, wherever).
When google searching for presentations, there is a lot of clutter - this could be highly focussed.
Thoughts?
One feature I used a lot while planning my event was the reports. I pulled the sessions submitted report to build the rough draft of what I wanted the schedule to look like. Some of the other ones were nice, but just being able to export the sessions submitted would be useful.
Session Submitted Columns:
Last Name
First Name
Email Address
Session Title
Session Description
Track
Category
Level
Approved
Scheduled
Session Time Preference
Additional Notes
Shirt Size
Speaker Bio
Speaker URL
Twitter
LinkedIn URL
Blog URL
MVP
MCM
MS
Phone Number
Country
Region
City
Address1
Address2
Hey folks, I just wanted to start a conversation because I fear this is starting another org that will just get big and need management. I am certainly being critical here but looking for constructive conversations. Not being negative to be negative. :)
Here are my concerns:
Again, I'm not trying to be negative here, I'm just concerned. I want to avoid cliques as much as possible, and think we have a good opportunity to do that with PASS being gone (simply because it gives us a clean slate).
Pordenone have reached out to us to ask if we can assist, so @spaghettidba is going to provide something that they can use for their event as we wish to support the community.
It is understood that this will not be perfect or perhaps even vaguely represent what this will be going forward but it will be a starting point which we can iterate from
When we started the brand of SQL Saturday, the idea was to not intrude on business days and ensure the event was open to all, as most organizations do not require work on Saturdays, There have been events on most days of the week, though some people have found an issue with the name.
This is some slight overlap with #12 , but I think starting from scratch is a huge opportunity to make things as accessible and inclusive as possible (especially digital content).
Some areas to think about:
We are at the beginning; we have accomplished a lot in a brief time. This is amazing.
I think we should ensure that focusing on Inclusivity and Accessibility are at the forefront of our progress.
With this in mind I add this issue -
We should ensure that we support languages other than English and ensure that our assets are accessible for all
To create a new event - Please follow the process in the Wiki - https://github.com/sqlcollaborative/DataSaturdays/wiki
You can also create an issue using the correct template if you are not comfortable with using source control.
We need a Code of Conduct (or Codes of Conduct) to support:
This seems pretty straightforward in using the same Code of Conduct as other sqlcollaborative projects.
In #27 @andrekamman mentions the CodeOfConduct.com code as a base, which helps tackle internationalization/translation.
Events should have a "base" code of conduct (like above), plus a "supplement" which has event-specific details.
We should additionally provide resources for event organizers so that they feel equipped to provide assistance & response.
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
Super Easy to embed the agenda in and it auto updates and is easily accessed by API for other use cases (Apps etc)
I'm sure we can do powerbi on a map like the one Reza did to match the following web site.
https://www.meetup.com/pro/azuretechgroups
One of the things that the DevOps world seems to have settled on is that centralised and standardised tools can be really helpful, but that "product teams"* should have the final say on whether to adopt them. This keeps the centralised tools teams honest. If there are better tools on the market, teams should be free to use them instead.
May I propose that we adopt the philosophy that all centralised assetts are optional, and that while event owners are free to use them, they are not required to do so.
There are two important consequences of this.
'* I'm aware that it's better to focus on value rather than products, but trying to avoid getting bogged down in terminology.
Their leader Jean Joseph has already created a Sessionize link for the rebadged Haiti SQLSaturday and I offered to promote it here as well. https://sessionize.com/HaitianSQLOneDayEvent
Here is the Eventbrite link as well: https://www.eventbrite.com/e/haitian-sql-one-day-event-tickets-133876158193
Will need support for sponsors
Should we new try and continue the numbering from the SQL Saturday site, that way if we are able to get the SQLSaturday.com brand (Like @way0utwest is tying to do) then we can merge the two streams pretty easily?
~The highest published event I saw was 1023.
We will be handling a lot of PII data.
How to make sure we keep the data safe?
How do we make sure that both attendees stay in control of their data?
And give them a way to share as much or little as they want with the sponsors?
What do we do with indirect PII data?
Also we will need a way for participants to make clear that they are willing to volunteer during an event.
Just by a checkbox or an extra page to opt-in for one or more tasks.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.