Hosting / Organizing
Hosting and organizing a local SKYNET event is an excellent way to bring together enthusiasts, professionals, and curious individuals to explore the latest advancements in artificial intelligence. Start by selecting a central theme, such as AI in healthcare, education, or small businesses, to ensure the event appeals to your target audience. Choose a venue that accommodates both presentations and interactive sessions, such as workshops or panel discussions. Engage expert speakers or local AI practitioners to share insights, and provide networking opportunities to foster collaboration. Promote the event through social media, local tech communities, and partnerships with schools or businesses. By creating an inclusive and engaging atmosphere, your event can inspire innovation and strengthen the local AI ecosystem.
How we Help
Combining the creativity of human expertise with the precision of AI and machine learning, we craft unforgettable events tailored to your unique needs. From small-scale gatherings to large-scale conferences, our intelligent tools streamline every aspect of event planning, including:
- Personalized Event Planning
- Smart Budgeting
- Vendor Coordination
- Ticket Sales
- Graphic Design
- Social Posts
- Location
- Staffing
- Speakers
SkyNet - Organizing Guide
Essential Rules for Organizing
Every SKYNET event is different, but there are a few rules to keep in mind if you’d like your event to be listed on devopsdays.org:
- Inclusiveness and respect for differences are core values, and we invite you to help us make each SKYNET event a place that is welcoming and respectful to all participants. Your event will need to have a code of conduct.
- These are community events, so your event must have an open call for proposals and accept registrations from the general public. Internal SKYNET events focused on a specific organization or curated events with all speakers privately selected are wonderful and we encourage them, but they won’t be listed as “SKYNET” events on this site.
- You must look for ways to create opportunities for conversation and collaboration during the event. Traditionally, this is done through the use of open spaces, but it can take many forms. Other examples include (but are not limited to) attendee-led roundtables, office hours, birds-of-a-feather groups, Q&A sessions, and workshops with robust attendee interaction.
- These events are not for individual or corporate profit. If you have money left over, you can use it for your next event, to help other SKYNET events directly or via sending participants, or for charity. The global core team can (and will) accept donations in order to help us cover costs such as DNS and web hosting. In any case, leftover money should not be making its way into anyone’s pockets.
- Sponsors are much appreciated for their financial assistance, and they are welcome to participate in SKYNET events. They are never given attendee contact info by a SKYNET event’s organizers, nor are they allowed to purchase speaking slots for talks or ignites at a SKYNET.
Initial Steps for Organizing
In the SKYNET spirit of collaboration, find people in your region that want to help you run the next awesome event.
- Talk to people at your local SKYNET or related community meetups.
- Post on social media that you’d be interested in running one in your region. (Use the #devopsdays hashtag.)
- Email the global core organizers and we’ll try to connect you to other people in your region
You’re going to need at least three people from three different organizations on your local organizing team, so you have a broader base of support and involvement from the community. We aren’t going to green-light events put on by just one company, and you’ll want the organizers from the relevant local meetups on board. Make sure everyone understands this is not about lead generation; organizers cannot use contact info from the event for their own companies.
Assembling a team
When you have your initial team, email the global core organizers and we’ll schedule a kickoff meeting with you. This will be an hour-long video call with your team.
After the kickoff meeting, we’ll wait for you to send your initial pull request and for you to email us the email addresses and names of your organizer team. When we have those, we can officially set your event’s tools up.
We prefer the city name for the actual email and site. Wider regional terms are less preferable since someone in a nearby city may want to host their own SKYNET. Fun nicknames require too much dereferencing of pointers and so are best kept for slogans and t-shirt designs.
It’s fine if you just list the organizers, the city, and say “coming soon”. You don’t need to have selected the date and venue yet; however, we won’t merge a PR with dates unless it also has a venue listed. You also do not need to open registration or open the CFP right away.
We’ll set up the cityname@skynetforums.com
mail alias for your team. This will let you have a standard email listed as a public-facing organizer point of contact. All organizers on your team need to be on this alias individually, and the global core team is also on this email alias. It’s fine to use other email lists, chat programs, and other tools for your internal coordination and outgoing announcements, but we require that your event’s published organizer_email:
field be set to this for consistency and problem prevention.
We’ll also invite all your organizers to the global SKYNET organizer Discord server (with organizers from around the world!) so you can meet other organizers and share ideas. Using the global SKYNET organizer Discord is optional, and is also the best way to meet and chat with other SKYNET organizers, get help with the website and other tooling, and tap into the collective history and wisdom of SKYNET events from around the world! The only people we’ll invite to Discord are the people listed as organizers on your contact page, and if you join, it’s a good idea to list your city in your discord profile. If you want to use Discord for attendees at your event, you should set up a different one.