> "all the cookies/privacy information they can get." That was just a copy & paste mistake :)
On Tue, Jan 27, 2026 at 11:40 AM Jarek Potiuk <[email protected]> wrote: > 1. Even though this would be an embedded page and not linked out to > anything, it still has to be owned by the PMC to be embedded on the Airflow > Website. Correct? > > Also - it has to have the correct privacy properties. When any page of > the "airflow.apache.org" is opened - we cannot load an embedded page > from a 3rd-party site (outside of *.apache.org) unless we know it does > not do any tracking. Doing that actually **requires** an INFRA-approved > exception for our website configuration. Normally our website is > served with CSP policies, that causes any attempts to load such embedded > pages will fail. This is for example why we had to copy all web fonts we > use to our website content, because we cannot pull the fonts from Google > web font registry (then it can be used by google to track visitors of . > apache.org sites). Similarly if we directly embed any `*.meetup.com` page > in our "meetups" page, meetup.com can track the users of the "*.apache.org". > This is very strictly controlled on a technical (CSP) and legal (privacy > policy) level. > > 2. If we changed the name of the linked page (even though it would not > appear on the embed) to "airflow" instead of "Astronomer" and gave PMC > members access, we could embed that page on the Airflow website. Correct? > If loading "https://airflow.apache.org/meetups/"; will automatically cause > loading content from "meetup.com/whatever" - then NO. Users of " > airflow.apache.org" have to deliberately make an action on our page - > (like clicking on "load meetup.com content" image) in order to make a > request to "meetup.com/whatever". User needs to make a deliberate > decision to load something from "meetup.com" page when they are visiting " > airflow.apache.org" page. > > So I think the most we can do is to keep our static page and have a link > at the top of the page: "Visit https://www.meetup.com/pro/astronomer-inc/"; > to see more dynamic data and overview. But in this case we have two choices: > > * either we have to explicitly state that we are not maintaining the > content of that page as PMC and it has to be obvious (this happens at the > "ecosystem" page and might happen soon on the Survey page when we thank the > Astronomer for preparing and leading the survey and processing it - which > is super cool. > * or it has to be a PMC-managed account, with PMC ownership (not only > access to edit it).all the cookies/privacy information they can get. > > We can also think about replicating some of the "dynamicness" of the " > meetup.com/pro/" page on our website. I can easily imagine, generation of > similar content via a bit nicer meetup.com by pulling the data from > meetup.com via their APIs and even daily or every 4 hours regeneration of > the page - we can I think relatively easily replicate most of what the page > provides (especially with AI Agents now, we can likely practically 100% > vibe-code it) - it just needs someone to instruct their agent properly. And > to be perfectly honest - if there is a volunteer here who would like to do > it, I think it's absolutely the best way of doing it. We already have quite > a few people who contribute nice fixes to our site - after we made it easy > to contribute to - most recently a PR that improved alignment of the grid > in our "community page" https://github.com/apache/airflow-site/pull/1400 > - results visible at https://airflow.apache.org/community/. > > So maybe rather than embedding or linking to the "pro" page of meetup - we > should use it as an inspiration to improve our page? > > J. > >
