-
Notifications
You must be signed in to change notification settings - Fork 709
[ISLAMABAD-2026] Add initial event page #15941
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
Open
ABDULLAH408
wants to merge
4
commits into
devopsdays:main
Choose a base branch
from
ABDULLAH408:add-islamabad-2026
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| +++ | ||
| Title = "Conduct" | ||
| Type = "event" | ||
| Description = "Code of conduct for devopsdays Islamabad 2026" | ||
| +++ | ||
|
|
||
| All attendees, speakers, sponsors, and volunteers at devopsdays Islamabad 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 and positive event experience for everyone. | ||
|
|
||
| ### 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 with no 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 Islamabad 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| +++ | ||
| Title = "Contact" | ||
| Type = "event" | ||
| Description = "Contact information for devopsdays Islamabad 2026" | ||
| +++ | ||
|
|
||
| If you'd like to contact us by email: {{< email_organizers >}} | ||
|
|
||
| **Our local team** | ||
|
|
||
| {{< list_organizers >}} | ||
|
|
||
| {{< list_core >}} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| +++ | ||
| Title = "Sponsor" | ||
| Type = "event" | ||
| Description = "Sponsor devopsdays Islamabad 2026" | ||
| +++ | ||
|
|
||
| If you are interested in sponsoring devopsdays Islamabad 2026, please contact the organizers by email at {{< email_organizers >}}. | ||
|
|
||
| More details about sponsorship levels and opportunities will be announced soon. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| +++ | ||
| Title = "devopsdays Islamabad 2026" | ||
| Type = "welcome" | ||
| aliases = ["/events/2026-islamabad/"] | ||
| Description = "devopsdays Islamabad 2026" | ||
| +++ | ||
|
|
||
| devopsdays Islamabad 2026 is coming soon. More details about the date, venue, speakers, sponsors, registration, and program will be announced soon. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,67 @@ | ||
| name: "2026-islamabad" # 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: "Islamabad" # The displayed city name of the event. Capitalize it. | ||
| event_twitter: "devopsdays" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp | ||
| description: "Devopsdays Islamabad 2026 is coming soon!" | ||
| ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. | ||
|
|
||
| startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet. | ||
| enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet. | ||
|
|
||
| cfp_date_start: # start accepting talk proposals. | ||
| cfp_date_end: # close your call for proposals. | ||
| cfp_date_announce: # inform proposers of status | ||
|
|
||
| cfp_link: "" #if you have a custom link for submitting proposals, add it here. | ||
|
|
||
| registration_date_start: # start accepting registration. Leave blank if registration is not open yet. | ||
| registration_date_end: # close registration. Leave blank if registration is not open yet. | ||
|
|
||
| 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. | ||
|
|
||
| location: "Islamabad" # Defaults to city, but you can make it the venue name. | ||
| location_address: "" #Optional - use the street address of your venue. | ||
|
|
||
| event_social_linkedin: "" | ||
| event_social_slack: "" | ||
| event_social_listserv: "" | ||
| event_social_twitter: "" | ||
| event_social_mastodon: "" | ||
| event_social_bsky: "" | ||
| event_social_youtube: "" | ||
|
|
||
| social_shares: | ||
|
|
||
| nav_elements: | ||
| - name: sponsor | ||
| - name: contact | ||
| - name: conduct | ||
|
|
||
| team_members: | ||
|
phrawzty marked this conversation as resolved.
|
||
| - name: "Abdullah Haroon" | ||
| employer: "Labourites" | ||
| role: "Organizer" | ||
| - name: "Farhan Ashraf" | ||
| employer: "Systems Ltd" | ||
| role: "Organizer" | ||
| - name: "Junaid Hanif" | ||
| employer: "Tech Harbour" | ||
| role: "Organizer" | ||
|
|
||
| organizer_email: "islamabad@devopsdays.org" | ||
|
|
||
| sponsors: | ||
|
|
||
| sponsors_accepted: "no" | ||
|
|
||
| sponsor_levels: | ||
| - id: gold | ||
| label: Gold | ||
| - id: silver | ||
| label: Silver | ||
| max: 0 | ||
| - id: bronze | ||
| label: Bronze | ||
| - id: community | ||
| label: Community | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.