-
Notifications
You must be signed in to change notification settings - Fork 700
[TOKYO-2026] Files Created for Event #15557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| +++ | ||
| Title = "Conduct" | ||
| Type = "event" | ||
| Description = "Code of conduct for devopsdays Tokyo 2026" | ||
| +++ | ||
|
|
||
|
|
||
| All attendees, speakers, sponsors, and volunteers at devopsdays Tokyo 2026 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody. | ||
|
|
||
| ### The Quick Version | ||
|
|
||
| Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers. | ||
|
|
||
| ### The Less Quick Version | ||
|
|
||
| Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately. | ||
|
|
||
| Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. | ||
|
|
||
| If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund. | ||
|
|
||
| If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately. | ||
|
|
||
| Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. | ||
|
|
||
| We expect participants to follow these rules at conference and workshop venues and conference-related social events. | ||
|
|
||
| _The devopsdays Tokyo 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| +++ | ||
| Title = "Contact" | ||
| Type = "event" | ||
| Description = "Contact information for devopsdays Tokyo 2026" | ||
| +++ | ||
|
|
||
| If you'd like to contact us by email: {{< email_organizers >}} | ||
|
|
||
| **Our local team** | ||
|
|
||
| {{< list_organizers >}} | ||
|
|
||
|
|
||
| {{< list_core >}} |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| +++ | ||
| Title = "Location" | ||
| Type = "event" | ||
| Description = "Location for devopsdays Tokyo 2026" | ||
| +++ | ||
|
|
||
| [大崎ブライトコアホール (Osaki Bright Core Hall)](http://osaki-hall.jp/) | ||
| 東京都品川区北品川5丁目5-15 | ||
|
|
||
| <iframe src="https://www.google.com/maps/embed?pb=!1m14!1m8!1m3!1d3243.2193467560746!2d139.7294709!3d35.6223187!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x0%3A0x7c3ee69c2c2142e6!2z5aSn5bSO44OW44Op44Kk44OI44Kz44Ki!5e0!3m2!1sen!2sjp!4v1486141716893" width="600" height="450" frameborder="0" style="border:0" allowfullscreen></iframe> |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
| +++ | ||
| Title = "devopsdays Tokyo 2026" | ||
| Type = "welcome" | ||
| aliases = ["/events/2026-tokyo/"] | ||
| Description = "devopsdays Tokyo 2026" | ||
| +++ | ||
|
|
||
| <!-- <div style="text-align:center;"> | ||
| {{< event_logo >}} | ||
| </div> --> | ||
|
|
||
| <div class = "row"> | ||
| <div class = "col-md-2"> | ||
| <strong>Dates</strong> | ||
| </div> | ||
| <div class = "col-md-8"> | ||
| {{< event_start >}} - {{< event_end >}} | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class = "row"> | ||
| <div class = "col-md-2"> | ||
| <strong>Location</strong> | ||
| </div> | ||
| <div class = "col-md-8"> | ||
| {{< event_location >}} | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class = "row"> | ||
| <div class = "col-md-2"> | ||
| <strong>Register</strong> | ||
| </div> | ||
| <div class = "col-md-8"> | ||
| <a href="https://pretix.eu/devopsdaystokyo/2026/">Register to attend the conference!</a> | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class = "row"> | ||
| <div class = "col-md-2"> | ||
| <strong>Propose</strong> | ||
| </div> | ||
| <div class = "col-md-8"> | ||
| <a href="https://confengine.com/conferences/devopsdays-tokyo-2026">Propose a talk!</a> | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class = "row"> | ||
| <div class = "col-md-2"> | ||
| <strong>Program</strong> | ||
| </div> | ||
| <div class = "col-md-8"> | ||
| View the {{< event_link page="program" text="program." >}} | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class = "row"> | ||
| <div class = "col-md-2"> | ||
| <strong>Speakers</strong> | ||
| </div> | ||
| <div class = "col-md-8"> | ||
| Check out the {{< event_link page="speakers" text="speakers!" >}} | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class = "row"> | ||
| <div class = "col-md-2"> | ||
| <strong>Sponsors</strong> | ||
| </div> | ||
| <div class = "col-md-8"> | ||
| <a href="https://www.devopsdaystokyo.org/call-for-sponsor">Sponsor the conference!</a> | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class = "row"> | ||
| <div class = "col-md-2"> | ||
| <strong>Contact</strong> | ||
| </div> | ||
| <div class = "col-md-8"> | ||
| {{< event_link page="contact" text="Get in touch with the organizers" >}} | ||
| </div> | ||
| </div> | ||
|
|
||
| <!-- Uncomment if you added your city twitter name --> | ||
|
|
||
| {{< event_twitter >}} | ||
|
|
||
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,85 @@ | ||||||||||||||||||||||
| name: "2026-tokyo" # The name of the event. Four digit year with the city name in lower-case, with no spaces. | ||||||||||||||||||||||
| year: "2026" # The year of the event. Make sure it is in quotes. | ||||||||||||||||||||||
| city: "Tokyo" # The displayed city name of the event. Capitalize it. | ||||||||||||||||||||||
| event_twitter: "devopsdaystokyo" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp | ||||||||||||||||||||||
| description: "Devopsdays is coming to Tokyo!" # Edit this to suit your preferences | ||||||||||||||||||||||
| ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| # All dates are in unquoted 2026-MM-DDTHH:MM:SS+TZ:TZ, like this: | ||||||||||||||||||||||
| # variable: 2019-01-04T00:00:00+02:00 | ||||||||||||||||||||||
| # variable: 2019-01-05T23:59:59+02:00 | ||||||||||||||||||||||
| # Note: we allow 2026-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day) | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| startdate: 2026-04-14T00:00:00+09:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. | ||||||||||||||||||||||
| enddate: 2026-04-16T23:59:59+09:00 | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| # Leave CFP dates blank if you don't know yet, or set all three at once. | ||||||||||||||||||||||
| cfp_date_start: 2024-11-01T00:00:00+09:00 # start accepting talk proposals. | ||||||||||||||||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||||||||
| cfp_date_end: 2026-03-01T13:00:00+09:00 # close your call for proposals. | ||||||||||||||||||||||
| cfp_date_announce: 2026-03-15T00:00:00+09:00 # inform proposers of status | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| cfp_link: "https://www.devopsdaystokyo.org/" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button. | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| registration_date_start: # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. | ||||||||||||||||||||||
| registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| registration_closed: "" #set this to true if you need to manually close registration before your registration end date | ||||||||||||||||||||||
| registration_link: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. | ||||||||||||||||||||||
|
Comment on lines
+23
to
+27
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Since your registration is open, you need to fill in these dates so it populates on the main page.
Suggested change
|
||||||||||||||||||||||
|
|
||||||||||||||||||||||
| # Location | ||||||||||||||||||||||
| # | ||||||||||||||||||||||
| coordinates: "35.6223187, 139.7294709" # The coordinates of your city. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html | ||||||||||||||||||||||
| location: "大崎ブライトコアホール" # Defaults to city, but you can make it the venue name. | ||||||||||||||||||||||
| location_address: "" #Optional - use the street address of your venue. This will show up on the welcome page if set. | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| nav_elements: # List of pages you want to show up in the navigation of your page. | ||||||||||||||||||||||
| - name: devopsdaystokyo.org | ||||||||||||||||||||||
| url: https://www.devopsdaystokyo.org/ | ||||||||||||||||||||||
| - name: contact | ||||||||||||||||||||||
| - name: conduct | ||||||||||||||||||||||
| # - name: example | ||||||||||||||||||||||
| # icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ | ||||||||||||||||||||||
| # url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
|
|
||||||||||||||||||||||
| # These are the same people you have on the mailing list and Slack channel. | ||||||||||||||||||||||
| team_members: # Name is the only required field for team members. | ||||||||||||||||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Before we can merge this PR, We need an email sent to the info@ mailing address with the following information:
Thank you! |
||||||||||||||||||||||
| - name: "Ippei Suzuki" | ||||||||||||||||||||||
| employer: "Creationline" | ||||||||||||||||||||||
| - name: "Alex Papadimoulis" | ||||||||||||||||||||||
| employer: "Inedo" | ||||||||||||||||||||||
| twitter: "apxld" | ||||||||||||||||||||||
| - name: "Sho Sato" | ||||||||||||||||||||||
| employer: "Inedo" | ||||||||||||||||||||||
| - name: "Yasunobu Kawaguchi" | ||||||||||||||||||||||
| employer: "Attractor" | ||||||||||||||||||||||
| - name: "Hiro Arai" | ||||||||||||||||||||||
| employer: "Creationline" | ||||||||||||||||||||||
| - name: "Tadahiro Yasuda" | ||||||||||||||||||||||
| employer: "Creationline" | ||||||||||||||||||||||
| - name: "Kenta Sasa" | ||||||||||||||||||||||
| employer: "Creationline" | ||||||||||||||||||||||
| - name: "Muneyuki Okamoto" | ||||||||||||||||||||||
| employer: "ITPreneurs Japan" | ||||||||||||||||||||||
| - name: "Toshiya Enami" | ||||||||||||||||||||||
| employer: "ITPreneurs Japan" | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| organizer_email: "[email protected]" # Put your organizer email address here | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| # List all of your sponsors here along with what level of sponsorship they have. | ||||||||||||||||||||||
| # Check data/sponsors/ to use sponsors already added by others. | ||||||||||||||||||||||
| sponsors: | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| # In this section, list the level of sponsorships and the label to use. | ||||||||||||||||||||||
| # You may optionally include a "max" attribute to limit the number of sponsors per level. For | ||||||||||||||||||||||
| # unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all | ||||||||||||||||||||||
| # sponsorship for a specific level, it is best to remove the level. | ||||||||||||||||||||||
| sponsor_levels: | ||||||||||||||||||||||
| - id: gold | ||||||||||||||||||||||
| label: Gold | ||||||||||||||||||||||
| max: 8 | ||||||||||||||||||||||
| - id: logo | ||||||||||||||||||||||
| label: Logo | ||||||||||||||||||||||
| max: 10 | ||||||||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't have these pages created yet, so these links are broken. I'd comment them out until you're ready.