Skip to content

Latest commit

 

History

History
128 lines (94 loc) · 6.11 KB

13-ber.md

File metadata and controls

128 lines (94 loc) · 6.11 KB
Raw

Helix Operations Workshop XIII

April 15th to 19th 2024, Village Berlin Workshop Space, Berlin, Germany

(See the Hackathon Archive for past Operations Workshops and Hackathons)

Agenda

I hear this is an operations workshop, are you going to operate all day?

In this operations workshop, we will discuss how we are operating our services, what changes can, should and need to be done to improve quality of service for our customers and quality of life of our operators. We will try to keep it hands-on, so instead of presentations, we will rely on code settling arguments, this means we won't be hacking all the time, there will also be plenty of programming and coding.

The main purpose of the hackathon is social: allow the team to reconnect, meet new team members for the first time, and work on stuff that won't fit neatly into a 45-minute Teams meeting.

Time Monday Tuesday Wednesday Thursday Friday
Morning 9:00 Kick-off, Goals
10:00 Architecture walkthrough		 Hacking Hacking Hacking Hacking
Afternoon Hacking Hacking Hacking Hacking Demos
Evening Social Social Social Social -

Location

Where is this going to happen? Do you have a windowless conference room blocked out?

We've booked a workshop Space at Village Berlin, Kurfürstenstraße 31, 10785 Berlin, Germany.

Travel

Berlin (BER) is an international airport, but most flights from the US will require a connection. If you plan to visit the Basel office as part of this trip, booking a separate Easyjet flight between Berlin and Basel is the cheapest option.

Berlin has good public transport, don't rent a car. You can take the S-Bahn from the airport to the city center, and then walk or take a taxi to the hotel.

The 25hours Hotel Bikini Berlin is a 5 minute walk from Berlin Zoo S-Bahn station and 25 minutes on foot or 10 minutes by Subway from the workshop location. It is available on Navan.

Goals

What are you planning to show at the end of the week?

Put down the topic and the people that would like to discuss it:

The theme of this offsite is to make considerable progress on getting customers onboarded to Helix 5. For this, we group the work into two tracks, both with the goal of iproving live sites. For each of the tracks, think of the five sites that you have most control over, these are the sites that you will work on for the track.

Track 1: Migrate your sites to Helix 5

  • Take 5 sites and migrate them to Helix 5.
  • Keep notes in this Slack Canvas.
  • Get help from: @stefan-guggisberg, @tripodsan, @dominique-pfister, @rofe
  • switch over all the projects you are involved in to helix 5
  • repoless projects (pga tour)?
  • change tutorial to aem.page and aem.live
  • change default new projects to helix5
  • sidekick implications
  • get outside-in, ideal project to work
  • other test sites

Track 2: Improve your sites based on RUM

  • Take 5 sites and look at the RUM data. Fix issues around CWV, missing pages, JS errors
  • Keep notes in that other Slack Canvas
  • Get help from: @trieloff, @uncled, @langswei, @maxakuru
  • RUM data collection clean-up
  • RUM based site clean-up CWV and 404, JS errors

Ideas / Suggestions / Topics Collection

  • RUM domain key management
  • RUM historical data processing
  • Annual RUM dashboard
  • RUM Consent checkpoint
  • Consent integration blueprint in boilerplate
  • domain management in Helix 5: Admin API, Cert Onboarding, Domain Keys, Spacecat
  • move helix (code) repositories to adobe's github enterprise (discuss implications, move some repos and test feasibility)
  • Sharepoint hosting
  • Teams onboarding (vs. slack)
  • Teams app for support?
  • code sync stats/reporting (implementation start/end dates, number and size of commits, ...)

Attendees

Who is going to be there? Can I come?

This workshop is for the Helix on-call team as well as invited black belt VIP leads and invited frequent collaborators. If you have been invited and will come, please put your name down in the list.

  1. @trieloff
  2. @tripodsan
  3. Alex Capt
  4. @stefanseifert
  5. @stefan-guggisberg
  6. @rofe
  7. @dominique-pfister
  8. @langswei
  9. @3vil3mpir3 (Brian Warner)
  10. @amol-anand
  11. @dkuntze
  12. @maxakuru
  13. @solaris007 (DJ)
  14. @gilliankrause
  15. @gmhaack
  16. @fkakatie
  17. Stopp
  18. @royfielding
  19. @karlpauls
  20. @ekremney
  21. @davidnuescheler
  22. @sdmcraft (Satya Deep Maheshwari)
  23. @dylandepass
  24. @mokimo (adobe.com)
  25. @overmyheadandbody (adobe.com)
  26. @phornig

Preparation

What can I do to prepare for the Hackathon?

  1. Read the README.md and linked vision documents in this repo
  2. Join Discord
  3. Install the aem Command Line app and create your first project
  4. Comment on the GitHub issues you think would be good candidates for the Hackathon

Demos