September 16th to 20th, Hamburg, Germany (Adobe Office)
(See the Hackathon Archive for past Operations Workshops and Hackathons)
After the first spontaneous rumathon, we decided that we'll need a bit more of a heads up for the second iteration, so that a larger part of the team can participate
I hear this is an rumathon workshop, are you going to sample RUM all day?
Trying to get as much of the virtual team together, the goal is to have high-bandwidth exchanges on the current state and next steps of RUM. 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 (Alster) | Tuesday (Weser) | Wednesday (Spree) | Thursday (Spree) | Friday (Spree) |
---|---|---|---|---|---|
Morning | Noon: Kickoff, Introductions, Architecture | Hacking | Hacking | Hacking | Demos |
Afternoon | Hacking | Hacking | Hacking | Hacking | - |
Evening | Social | Social | Social | Social | - |
Where is this going to happen? Do you have a windowless conference room blocked out?
In the Hamburg office. We don't have a room yet, but it will likely have windows.
Fly into Germany, then take a train to Hamburg or fly directly to HAM.
Navan has the wrong pin for the Hamburg office, so distances may be off
- the closest Hotel (with availabilty in Navan) is IntercityHotel Hamburg-Altona – it's a 25 minute walk. If you like Deutsche Bahn, you'll feel right home at IntercityHotel
- a nice hotel that I've been staying at (and will stay) is 25hours Altes Hafenamt (also on Navan). It's a 50 minute walk, or 25 minute walk plus ferry ride
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 ....
- user engagement related
scroll
checkpoint to measure the scroll depth for the sites/pages where CTR/CVR is not relevant (ie blog/news pages)- engagement-aware active
time-on-page
calculation where only the time during which the user is actively viewing or interacting with the page is counted
- traffic acquisition related
- analysis of existing query params to refine the categorization we have today and improve if necessary
- bounce rate and time-on-page by source
- cost per acquisition (CPA) investigation
- RUM data consumers
- serving Adobe's massive appetite for data research, and how that intersects with the principles
- we should have some input from GTM team about RUM by the time of the workshop, let's discuss what it means
- Domain to Customer / IMS Org ID mapping As of today we are unable to map customer-managed CDN domains to Edge delivery services licenses. As a result, we can’t identify customers using EDS with their own CDN, which prevents us from linking them to business contracts, or collecting billing information, eg tracking content requests. Let's discuss how we could address this mapping short-term and also let's think about a long-term solution, ideally building an automated process in future
- How to handle customers with Content Security Policy (CSP) and how can we enable Sub-resource integrity (SRI) - mostly for Cloud Service
- Rollout extension
- Lars: Domains/Standalone
- Time on page tracking (active time on page)
- Scroll checkpoint
- Lars: domain list
- Lars: Success Studio Library
- Do some docs and screenshots
- New Sourceselector implementation
- Smart Redirects
- RUM Assistant?
- On-Call for RUM?
- Proxy for enrichment
- Domain/Customer/SKU mapping
- DNS Challenge?
- David: map domain to RUM org, then map rum org to customer/sku – mix auto + manual
- Cloud Service Integration
- David: can we do magenta cloud?
- RUM for Commerce
- How to deal with Web Components and shadow DOM? Paco, Alex?
- End to end test
- Integrity Checksums
- Subresource Integrity
- CSP Weirdness
- Cruncher Performance
- Lars: Negation Syntax for filters
- Alex: back port cruncher pref
- Change delivery entirely
- AEMCS Integration: how to break a site
- Generate list of programs that don’t send data
- Daterange
- Change cloud flare bundling
- Lars: ramp up cloudflare share
- Domainkey provider
- Lower admin scopes
- Catch up with implementation
Who is going to be there? Can I come?
If you had your hands on RUM code in the past year, you are welcome to join us. Put your name on the list, so that planning is a bit easier
- @trieloff
- @langswei
- @cziegeler (Mon - Thu)
- @chicharr
- @ekremney
- @maxakuru
- @phornig
- @kptdobe (Mon - Thu)
- @bosschaert
- @karlpauls
- @puric
What can I do to prepare for the Hackathon?
- Join
#rum-explorers
on Slack