├── layouts ├── shortcodes │ └── toc.html ├── _default │ ├── list.html │ ├── single.html │ └── baseof.html ├── robots.txt └── partials │ ├── banner.html │ ├── breadcrumbs.html │ └── footer.html ├── static ├── images │ ├── rave_bg.jpg │ └── rave_codehilite_bg.gif ├── .htaccess ├── js │ ├── events-calendar.js │ ├── calendar-DO-NOT-EDIT.json │ └── jquery.min.js └── style │ └── screen.css ├── archetypes └── default.md ├── .gitignore ├── NOTICE ├── source ├── event │ ├── past-events.md │ ├── __index.md │ └── calendar.md ├── about │ ├── endorsed.md │ ├── __index.md │ ├── roadshow.md │ └── commcode │ │ ├── __index.md │ │ ├── volunteer.md │ │ └── playbook.md ├── organize │ ├── __index.md │ └── roadshow.md ├── involved │ ├── mailing-lists.md │ └── __index.md └── _index.md ├── getcalendar.sh ├── .asf.yaml ├── config.toml ├── .github └── workflows │ └── getcalendar.yml ├── README.md ├── Jenkinsfile └── LICENSE /layouts/shortcodes/toc.html: -------------------------------------------------------------------------------- 1 | {{ .Page.TableOfContents }} -------------------------------------------------------------------------------- /layouts/_default/list.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 | {{ .Content }} 3 | {{ end }} 4 | -------------------------------------------------------------------------------- /layouts/_default/single.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 | {{ .Content }} 3 | {{ end }} 4 | -------------------------------------------------------------------------------- /static/images/rave_bg.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/apache/comdev-events-site/HEAD/static/images/rave_bg.jpg -------------------------------------------------------------------------------- /archetypes/default.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "{{ replace .Name "-" " " | title }}" 3 | date: {{ .Date }} 4 | draft: true 5 | --- 6 | 7 | -------------------------------------------------------------------------------- /static/images/rave_codehilite_bg.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/apache/comdev-events-site/HEAD/static/images/rave_codehilite_bg.gif -------------------------------------------------------------------------------- /layouts/robots.txt: -------------------------------------------------------------------------------- 1 | User-agent: * 2 | 3 | Disallow: /404/ 4 | Disallow: 404.html 5 | 6 | SITEMAP: {{ "sitemap.xml" | absLangURL }} 7 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Hugo generated 2 | resources 3 | target 4 | .hugo_build.lock 5 | 6 | # IntelliJ generated 7 | *.iml 8 | .idea 9 | .java-version 10 | -------------------------------------------------------------------------------- /NOTICE: -------------------------------------------------------------------------------- 1 | Apache Comdev 2 | Copyright 2020 The Apache Software Foundation 3 | 4 | This product includes software developed at 5 | The Apache Software Foundation (https://www.apache.org/). 6 | -------------------------------------------------------------------------------- /source/event/past-events.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Apache Past Events 3 | --- 4 | 5 | # Past ApacheCons 6 | 7 | For details on past ApacheCons, and archived sites of previous 8 | events (where available), please see 9 | [https://archive.apachecon.com/](https://archive.apachecon.com/) 10 | 11 | Information on past ApacheCons is also available on the 12 | [ApacheCon Wiki](https://cwiki.apache.org/confluence/display/apachecon/) 13 | -------------------------------------------------------------------------------- /layouts/partials/banner.html: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /layouts/partials/breadcrumbs.html: -------------------------------------------------------------------------------- 1 | {{ $url := replace .Permalink ( printf "%s" .Site.BaseURL) "" }} 2 | {{ $.Scratch.Add "path" "/" }} 3 | 4 | Home 5 | {{ range $index, $element := split $url "/" }} 6 | {{ $.Scratch.Add "path" $element }} 7 | {{ if ne $element "" }} 8 |   {{ replace (humanize .) ".html" "" }} 9 | {{ $.Scratch.Add "path" "/" }} 10 | {{ end }} 11 | {{ end }} 12 | 13 | -------------------------------------------------------------------------------- /layouts/partials/footer.html: -------------------------------------------------------------------------------- 1 | 15 | -------------------------------------------------------------------------------- /getcalendar.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | 3 | # Fetch calendar data; will be stored as calendar-DO-NOT-EDIT.json 4 | 5 | CALENDAR_ID="nerseigospses068jd57bk5ar8@group.calendar.google.com" 6 | API_KEY="AIzaSyDJkXq1faq2G5NkFkFTh9Sikdpc2YXTVXs" 7 | NOW=$(date '+%Y-%m-%dT%H:%M:%SZ') 8 | OPTS="?key=${API_KEY}&timeMin=${NOW}&singleEvents=true&orderBy=startTime&timezone=UTC&maxResults=20" 9 | 10 | echo "Fetching calendar data" 11 | 12 | curl -sS -o calendar-DO-NOT-EDIT.json "https://www.googleapis.com/calendar/v3/calendars/${CALENDAR_ID}/events${OPTS}" \ 13 | -H 'accept: application/json, text/javascript, */*; q=0.01' \ 14 | -H 'origin: https://events.apache.org' 15 | 16 | echo "Fetched data" 17 | -------------------------------------------------------------------------------- /source/about/endorsed.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Apache Endorsed Events 3 | --- 4 | 5 | # Apache endorsed/approved events 6 | 7 | There are many third-party events produced every year that focus on 8 | Apache Software Foundation projects. The ASF encourages these events, as 9 | they expand the reach of our projects and our message. 10 | 11 | If you are producing an Apache-related event, and using our brands and 12 | marks, we ask that contact us for our official approval. Along with 13 | this, we will also help promote these events, where possible and 14 | appropriate. Whether or not you want to collaborate with us on your 15 | event, you MUST adhere to our [branding policy](https://www.apache.org/foundation/marks/events.html). 16 | -------------------------------------------------------------------------------- /source/event/__index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Apache Conferences Calendar 3 | slug: index 4 | --- 5 | 6 | ## Upcoming Apache events 7 | 8 | This is the list of upcoming official Apache events, and 9 | those events which have been approved to use Apache Marks under the 10 | [Third Party Event Branding Policy][1]. 11 | 12 | 15 | 16 | 18 | 19 | For a complete list of events see our [calendar](calendar.html). 20 | 21 | In addition to Official Apache Events, there are a wide range of other 22 | events which feature Apache projects and technologies. 23 | 24 | 25 | 26 | 27 | [1]: https://www.apache.org/foundation/marks/events.html 28 | -------------------------------------------------------------------------------- /source/organize/__index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Organize an Apache Event 3 | slug: index 4 | --- 5 | 6 | If you want to host your own Apache project event, or propose a 7 | [roadshow](/about/roadshow.html) about the ASF, get in touch with us on the [Event Planning 8 | mailing list](mailto:planners@apachecon.com). 9 | 10 | **Important!** While we appreciate other parties producing events to tell the world about 11 | our many great Apache projects and communities, [Apache trademarks and brands](https://whimsy.apache.org/brand/list) 12 | are also important to us. To use any Apache trademarks in conjunctions with events, 13 | you **must** request permission by following the 14 | [Third Party Event Branding Policy](https://www.apache.org/foundation/marks/events.html). 15 | 16 | * [Organizing a Roadshow event](roadshow) 17 | 18 | 19 | -------------------------------------------------------------------------------- /source/event/calendar.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Apache Conferences Calendar 3 | --- 4 | 5 | This Calendar is maintained by the [Apache Conferences Committee][1] (ConCom). It's used to list official Apache events, and 6 | those events which have been approved to use Apache Marks under the [Third Party Event Branding Policy][2]. 7 | 8 | The calendar can be viewed at [https://www.google.com/calendar/...][4] 9 | 10 | This Calendar is also available as an [iCal feed][3] 11 | 12 | 13 | [1]: https://www.apache.org/foundation/conferences.html 14 | [2]: https://www.apache.org/foundation/marks/events.html 15 | [3]: https://www.google.com/calendar/ical/nerseigospses068jd57bk5ar8%40group.calendar.google.com/public/basic.ics 16 | [4]: https://www.google.com/calendar/embed?src=nerseigospses068jd57bk5ar8%40group.calendar.google.com&ctz=UTC 17 | -------------------------------------------------------------------------------- /.asf.yaml: -------------------------------------------------------------------------------- 1 | # See: https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features 2 | 3 | github: 4 | description: "Website sources for the Apache Events website" 5 | homepage: https://events.apache.org 6 | labels: 7 | - apache 8 | - community 9 | - comdev 10 | - events 11 | - hugo 12 | 13 | notifications: 14 | commits: commits@community.apache.org 15 | issues: dev@community.apache.org 16 | pullrequests: dev@community.apache.org 17 | 18 | # Looks like this may be needed to override the default host name 19 | publish: 20 | whoami: asf-site 21 | hostname: events.apache.org 22 | 23 | # Test site in preview/sample; output to preview/sample-staging 24 | # autostage will publish the site at community-sample.staged.apache.org 25 | staging: 26 | profile: ~ 27 | whoami: asf-staging 28 | autostage: preview/* 29 | -------------------------------------------------------------------------------- /config.toml: -------------------------------------------------------------------------------- 1 | baseURL = "https://events.apache.org" 2 | title = "Apache Software Foundation Events" 3 | languageCode = "en" 4 | 5 | contentDir = "source" 6 | publishDir = "target/content" 7 | 8 | disablePathToLower = true 9 | uglyURLs = true 10 | enableRobotsTXT = true 11 | disableBrowserError = true 12 | timeout = 3000 13 | 14 | disableKinds = ["taxonomy", "taxonomyTerm"] 15 | ignoreFiles = [ ] # No files to ignore 16 | 17 | # Highlighting config. See https://help.farbox.com/pygments.html 18 | pygmentsCodeFences = true 19 | pygmentsUseClasses = false 20 | pygmentsStyle = "emacs" 21 | 22 | # Enable Git variables like commit, lastmod 23 | enableGitInfo = true 24 | 25 | [markup.goldmark.renderer] 26 | unsafe = true 27 | 28 | [blackfriday] 29 | # hrefTargetBlank = true # We don't want everything opened in a new window 30 | fractions = false 31 | 32 | [frontmatter] 33 | date = ["date", ":filename", "publishDate", "lastmod"] 34 | 35 | [params] 36 | repositoryUrl = "https://github.com/apache/comdev-events-site" 37 | repositorySourceBranch = "main" 38 | -------------------------------------------------------------------------------- /source/organize/roadshow.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Roadshow Bid Process 3 | --- 4 | 5 | ## DRAFT 6 | 7 | This is intended to document the bid process for running/hosting a 8 | Roadshow. In particular, if you want ASF budget for it. 9 | 10 | You need, at a minimum 11 | 12 | * Event chair 13 | * Must be an ASF member 14 | * Must be resident in the city where the event is proposed 15 | * Volunteers to support (how many?) 16 | * City/Venue selected 17 | * University cities are preferred 18 | * Local tech firms that can sponsor? 19 | * Local keynote suggestion 20 | * Proposed timeline, starting with CFP, going through schedule, speaker notification, the event, and the post-event 21 | * Budget 22 | * Leads on sponsorship helpful 23 | * Contribute to event "runbook" as output from the event 24 | 25 | 26 | To run a roadshow or other small event without ASF budget, you only need to: 27 | 28 | * Follow our branding guidelines - https://www.apache.org/foundation/marks/events 29 | * [Tell us about it](mailto:planners@apachecon.com) 30 | * Have an Apache member involved in the planning 31 | 32 | -------------------------------------------------------------------------------- /.github/workflows/getcalendar.yml: -------------------------------------------------------------------------------- 1 | name: Fetch the Google Calendar 2 | 3 | on: 4 | workflow_dispatch: # only works in default branch 5 | push: 6 | schedule: # only works in default branch 7 | - cron: '50 9 * * *' 8 | 9 | permissions: 10 | contents: write 11 | 12 | jobs: 13 | fetch-calendar: 14 | runs-on: ubuntu-latest 15 | 16 | steps: 17 | - uses: actions/checkout@v4 18 | - name: Curl calendar 19 | run: | 20 | git config user.email "dev@community.apache.org" 21 | git config user.name "Comdev automated workflow" 22 | cd static/js 23 | echo "download calendar" 24 | bash ../../getcalendar.sh 25 | git status 26 | echo "preparing to push change(s)" 27 | git add . 28 | if git commit -m "Update calendar data (getcalendar.yml workflow)" 29 | then 30 | git push 31 | echo "Changed!" 32 | exit 0 33 | else 34 | echo "No change" 35 | true # ensure success 36 | fi 37 | env: # for gh 38 | GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} 39 | -------------------------------------------------------------------------------- /source/about/__index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: About ASF Events 3 | slug: index 4 | --- 5 | 6 | The Apache Software Foundation (ASF) runs, or participates in some fashion in, 7 | a number of different types of events, which different target audiences and goals, to educate about our 8 | projects and about the Foundation, and to build the communities. 9 | 10 | The main types of event we work with around ASF projects are: 11 | 12 | - [Community Over Code](/about/commcode/index.html) - the ASF's official conference 13 | - [Roadshows](/about/roadshow.html) - bringing ASF content around the world 14 | - [Endorsed events](/about/endorsed.html) - run by third parties using Apache brands 15 | 16 | If you want to organize your own event that uses ASF brands or trademarks in any way, we strongly encourage you to 17 | [coordinate with us](/organize/index.html). 18 | 19 | 20 | ## About This Website 21 | 22 | - This website is maintained by volunteers, various conference Planners, and the [VP, Conferences for the ASF](//whimsy.apache.org/foundation/orgchart/vp-concom). 23 | - Got questions or ideas? Come discuss events on our [mailing 24 | lists](https://events.apache.org/involved/mailing-lists.html)! 25 | -------------------------------------------------------------------------------- /static/.htaccess: -------------------------------------------------------------------------------- 1 | # 2 | # Licensed to the Apache Software Foundation (ASF) under one or more 3 | # contributor license agreements. See the NOTICE file distributed with 4 | # this work for additional information regarding copyright ownership. 5 | # The ASF licenses this file to You under the Apache License, Version 2.0 6 | # (the "License"); you may not use this file except in compliance with 7 | # the License. You may obtain a copy of the License at 8 | # 9 | # http://www.apache.org/licenses/LICENSE- 2.0 10 | # 11 | # Unless required by applicable law or agreed to in writing, software 12 | # distributed under the License is distributed on an "AS IS" BASIS, 13 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 14 | # See the License for the specific language governing permissions and 15 | # limitations under the License. 16 | RewriteEngine On 17 | 18 | # Redirect to https is done elsewhere 19 | 20 | # ApacheCon lives on its own domain 21 | Redirect temp /apachecon https://www.apachecon.com 22 | 23 | # Redirect to current CoC event website 24 | # This should agree with 25 | # https://raw.githubusercontent.com/apache/www-site/main/content/events/.htaccess 26 | # and the default event in 27 | # https://www.apachecon.com/event-images/snippet.js 28 | Redirect /x/current-event.html https://events.apache.org/ 29 | -------------------------------------------------------------------------------- /source/about/roadshow.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: About Apache Roadshows 3 | --- 4 | 5 | Apache Roadshows are small regional one- or two-day events, intended to 6 | build local community and educate about what the Apache Software 7 | Foundation does. 8 | 9 | While not a traditional roadshow (ie, a traveling event with multiple 10 | stops), we use the name to indicate that there may be multiple small 11 | events on a particular continent. Thus, the Europe Roadshow may have small 12 | events in Berlin and Barcelona during the course of a year, while the 13 | North America Roadshow might have events in DC and Chicago. 14 | 15 | Road shows are typically one or two days, having one or two tracks of 16 | content. They are often focused on a particular technology (e.g., 17 | Tomcat or Spark) or industry segment (e.g., IoT or Big Data). 18 | 19 | They can be organized by any Apache member, and may receive 20 | funding and promotion from the ASF, based on availability. It may be 21 | colocated with another event, or it may be standalone. 22 | 23 | Road shows are a great way for companies to support the ASF via donated 24 | space and sponsorship. If you'd like to host a roadshow, please contact 25 | the [community development mailing 26 | list](https://lists.apache.org/list.html?dev@community.apache.org) with 27 | your ideas. 28 | 29 | ### Other event types include: 30 | 31 | - [Community Over Code](/about/commcode/index.html) 32 | - [Endorsed events](/about/endorsed.html) 33 | -------------------------------------------------------------------------------- /source/involved/mailing-lists.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Apache Conferences and Events Mailing Lists 3 | --- 4 | 5 | There are several main mailing lists on which discussion and planning of Apache 6 | Software Foundation events occurs: 7 | 8 | | ApacheCon Announce | announce@apachecon.com | 9 | |-------------------|------------------------------| 10 | | Subscription address: | [announce-subscribe@apachecon.com](mailto:announce-subscribe@apachecon.com) | 11 | | Archives: | [Web archives](https://lists.apache.org/list.html?announce@apachecon.com) | 12 | | Use: | Read-only: Announcements of, and details about, Apache events | 13 | 14 | | ApacheCon Discuss | apachecon-discuss@apache.org | 15 | |-------------------|------------------------------| 16 | | Subscription address: | [apachecon-discuss-subscribe@apache.org](mailto:apachecon-discuss-subscribe@apache.org) | 17 | | Archives: | [Web archives](https://lists.apache.org/list.html?apachecon-discuss@apache.org) | 18 | | Use: | Public discussion of Apache events | 19 | 20 | | Community Development | dev@community.apache.org | 21 | |--------------------------|---------------------------------| 22 | | Subscription address: | [dev-subscribe@community.apache.org](mailto:dev-subscribe@community.apache.org) | 23 | | Archives: | [Web archives](https://lists.apache.org/list.html?dev@community.apache.org) | 24 | | Use: | Since events are produced and organized by the Apache [community development](https://community.apache.org) PMC, most event discussion starts on the ComDev mailing list | 25 | 26 | | Planners (Planning committee members only) | planners@apachecon.com | 27 | |--------------------------|---------------------------------| 28 | | Subscription address: | [planners-subscribe@apachecon.com](mailto:planners-subscribe@apachecon.com) | 29 | | Subscription note: | All subscriptions are moderated. Since budget and other confidential matters are discussed here, this list is not available to the public. Contact V.P. Conferences if you have questions. | 30 | | Archives: | [(Private) Web archives](https://lists.apache.org/list.html?planners@apachecon.com) | 31 | | Use: | Policy, budgets, discussions with external parties which cannot be done in public. Used for detailed planning of events. | 32 | -------------------------------------------------------------------------------- /source/involved/__index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Getting Involved in Apache Events 3 | slug: index 4 | --- 5 | 6 | There are a number of different ways to get involved with Events at Apache. 7 | Many of these come under the umbrella of the Conferences Committee, but 8 | some fall under different groups, such as the 9 | [Apache Community Development Project](https://community.apache.org/). 10 | 11 | If you are an Apache Committer, and you're interested in putting on an 12 | Apache Event, please see the [Organising Events](/organize/index.html) 13 | section for more help. If you are interested in helping others out with 14 | putting on an Apache Event, you are advised to join the appropriate 15 | [mailing list](mailing-lists.html), and volunteer for events there. 16 | This could be for a project specific event, such as a Hackathon or 17 | Meetup, for a foundation wide event, such as a BarCamp or Retreat, 18 | or a larger event such as a Roadshow or a Project / Project Cluster 19 | related small conference. 20 | 21 | If you are interested in putting on an external event making use of 22 | Apache Brands and Marks, please see the 23 | [Third Party Event Branding Policy](https://www.apache.org/foundation/marks/events.html) 24 | for information on the approval process and requirements. 25 | 26 | If you are interested in speaking about Apache at external events, then please see 27 | [Apache Speakers Resources](https://community.apache.org/speakers/index.html) that are 28 | maintained by the [Apache Community Development Project](https://community.apache.org/). 29 | 30 | If you are putting on an external event, and would like a small number of 31 | speakers for it to talk about Apache Projects and Technologies, please see the 32 | [Apache Speakers Resources](https://community.apache.org/speakers/index.html) for 33 | information on finding speakers. 34 | 35 | If you are putting on an external event, and you are interested in 36 | having an Apache track, or an Apache barcamp / hackathon style event, 37 | please contact 38 | [ConCom, the Conference Committee](https://www.apache.org/foundation/conferences.html) 39 | to discuss the possibility. 40 | 41 | If you are interested in attending an Apache Event, or an Apache 42 | related event, please see the [Calendar](/event/calendar.html) to discover 43 | what is coming up. 44 | -------------------------------------------------------------------------------- /source/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Apache Software Foundation Events 3 | --- 4 | 5 | 6 | 7 | 8 | 13 | 14 | The ASF runs and participates in a number 15 | of events related to our Apache projects throughout the year. These events have three main purposes: 16 | 17 | * Educate the world about the work and mission of the ASF 18 | * Provide technical information about our many Apache projects 19 | * Build developer and user communities 20 | 21 | Running a third party or project event? You must comply with the [events 22 | branding policy](https://www.apache.org/foundation/marks/events). 23 | 24 | The [ASF Travel Assistance Committee](https://tac.apache.org/) provides financial 25 | assistance for selected ASF events, to those who would otherwise be unable to attend them. 26 | 27 | ## Upcoming Events 28 | 29 | 32 | 33 | 35 | 36 | Follow us on Twitter at [@ApacheCon](https://twitter.com/apachecon) for 37 | the latest news and announcements. 38 | 39 | Disclaimer: Events called 'ApacheCon', 'Apache Roadshow' or 'Community over Code' (events in 40 | bold) are official Apache Software Foundation events. Other listed events are put on by projects, 41 | or third-party producers, and are listed here to support our community, but are not official 42 | Foundation events. 43 | 44 | ## Past Events & Get Involved 45 | 46 | - See the [past ASF events](https://apachecon.com/history.html), stretching back to 1998! 47 | - Want to get involved? [Volunteers are welcome](https://events.apache.org/involved/) on a variety of tasks. 48 | - Running your own Apache-branded event? Be sure to [get trademark permission](//www.apache.org/foundation/marks/events.html). 49 | - [Promote upcoming ASF events](https://www.apachecon.com/event-images/) on your personal or project website. 50 | 51 | Community Over Code and all ASF-run events operate under the terms of the [ASF's Code of Conduct](//www.apache.org/foundation/policies/conduct.html). 52 | 53 | 54 | 55 | 56 | 57 | -------------------------------------------------------------------------------- /source/about/commcode/__index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: About Community Over Code 3 | slug: index 4 | --- 5 | 6 | Community Over Code (formerly ApacheCon) is the official conference of the Apache Software Foundation. 7 | Its primary goals are education and community building. We try to 8 | produce one each calendar year somewhere in North America and Europe, 9 | and are working on expanding this to the rest of the world. 10 | 11 | If you want to volunteer to help with Community Over Code, please 12 | [join our mailing lists](/involved/mailing-lists.html), 13 | and see what [volunteer opportunities](/about/commcode/volunteer.html) we have, 14 | bearing in mind that it sometimes gets out of date. 15 | 16 | ## What Is Community Over Code? 17 | 18 | While Community Over Code events vary from year to year and location to location, there 19 | are some components that you can count on happening at every Community Over Code. 20 | 21 | - Community Over Code has at least 4 tracks of technical content, and often more. 22 | - Projects, or groups of related projects, may request a dedicated 23 | track where they will provide a track chair, and have freedom to 24 | create their own content for a project/topic sub-conference. In this 25 | way, Community Over Code resembles a convention of ASF project conferences. 26 | - There can be a hackathon space where projects can gather to work on 27 | code, or work out community issues. 28 | - There will be a **State of the Foundation** Keynote by the President or 29 | other officer, providing an overview of the ASF's accomplishments. 30 | - There will be a PGP key signing. 31 | - The event is usually 3 days or more. 32 | 33 | Community Over Code is the one annual event for the particular continent in 34 | question. As such, it draws an international audience, both in 35 | speakers and attendees. 36 | 37 | The documentation around how to plan an ApacheCon may be found in the 38 | [ApacheCon Playbook](/about/commcode/playbook.html). Most planning tasks 39 | are done by volunteers who commit to help - at least a little - throughout 40 | the planning process for one specific conference. 41 | 42 | You can find out more about what ApacheCon events are in the works on 43 | the [Community Over Code NA](https://communityovercode.org} and [Community Over Code EU](https://eucommunityovercode.org) websites, and see what events 44 | we've done in the past on 45 | [archive.apachecon.com](https://archive.apachecon.com/). 46 | 47 | Other event types include: 48 | 49 | - [Roadshows](/about/roadshow.html) 50 | - [Endorsed events](/about/endorsed.html) 51 | -------------------------------------------------------------------------------- /static/js/events-calendar.js: -------------------------------------------------------------------------------- 1 | // Update the calendar page from the json file 2 | 3 | // Where to put things 4 | var events = $('#events'); 5 | if (!events) { 6 | events = $('body').append("