Okay this is helpful Jarek, thank you! So in short, just so I understand: 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? 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?
Let me know if I am missing something, appreciate your guidance. On Mon, Jan 26, 2026 at 1:02 PM Jarek Potiuk <[email protected]> wrote: > This is important for several reasons important for ASF websites - which > are explained in those policies: > > * Apache Project Branding Policy [1] > * Apache Project Corporate Recognition Best Practices [2] > * ASF Data Privacy policies [3] and technical CSSP policy [4] > > Pretty much **everything** for our website **must** follow those policies. > There might be several potential issues with 3rd-party content referred to > or linked from our website: > > * due to branding/vendor neutrality policy [1] linking to a 3rd-party > website is possible, must follow the Corporate Recognition Best practices. > There are quite a few ways PMC can recognize Corporates supporting the > project. "Thank you pages" for sponsoring some things that PMC needs is a > good idea (this is why I alluded to in terms of sponsorship). "Product > Support Pages" - is another (and this is something that our "Ecosystem" [6] > page does - where we have non-endorsed, anyone can get listed, no ad, > factual listings - not implying control of PMC or endorsement of the PMC. > This is even protected by > > * embedding a page (with iframe or other dynamic javascript loading code) > might trigger privacy policy issues [3] and CSSP policy [4]. It boils down > to this: when a user looks at Airflow PMC website, they cannot cause any > cookies or other 3rd-party tracking to happen without explicit user > consent. This is for example why we cannot directly embed youtube video > dynamic javascript/iframe loading. For example in our "use case" pages [5] > we specifically embed images that are part of our website - with the > explicit "click to load YouTube video" overlay that also moves you out to > a 3rd-party (YouTube) site. The User has to explicitly click the image with > "YouTube link here" to go to that page (and invoke user tracking for the > 3rd-party) - this is for example why we **cannot** embed the meetup.com > directly in our website (because of privacy issues). At most we can have a > link to it that is explicitly described as "meetup.com external link". > > In short: > > * we likely won't be able to embed the meetup.com page "automatically" in > the meetup.com website at all (due to privacy) > * we can link to the organization page instead (but it has to be explicit > for the users that they are clicking-out to the 3rd-party). > * and if we link to it, it should not be a link to a vendor-controlled > website (if PMC has no control over it) - we can only link to 3rd-party > sites following the "Product support page" links in such cases. This means > that we have to explicitly state we have no control over that page and > everyone should have the same opportunity to participate. Unless it is > a PMC controlled"account (for example we can link to DockerHub - where > images of Airflow are hosted, because the PMC has control over this account > we link to. > * also when we refer to such a 3rd-party site we can (according to [2]) > add the name of the company and link to it and even a small vendor logo - > as long as this is a "thank you" for the support PMC gets from the vendor - > so basically a "thanks" page. > > J. > > > [1] https://www.apache.org/foundation/marks/pmcs > [2] https://www.apache.org/foundation/marks/linking > [3] https://privacy.apache.org/policies/ > [4] https://infra.apache.org/csp.html > [5] https://airflow.apache.org/use-cases/business_operations/ > [6] https://airflow.apache.org/ecosystem/ > > > On Mon, Jan 26, 2026 at 9:13 PM Briana Steel <[email protected]> > wrote: > >> Hey Jarek, >> >> I hear you on that. And we can definitely explore that. >> >> However, if the page is embedded on the airflow site, the link would not >> show regardless. So, I'm unclear where the actual issue lies? >> >> On Mon, Jan 26, 2026 at 12:04 PM Jarek Potiuk <[email protected]> wrote: >> >>> I think when it's aggregated this way under astronomer-inc It's not >>> **really** in line with how ASF probably would like to see it and with the >>> PMC hat on I'd prefer it to be an "airflow" link. >>> >>> I am not sure what the fee would be for it, but maybe we can get - for >>> example an astronomer sponsorship to cover it (or whoever else would like >>> to sponsor it) - and get it under the "airflow-meetup" groups - managed and >>> controlled by the PMC ? >>> That would make much more sense and it would likely be a better approach >>> - we could then make an Astronomer displayed as the sponsor of the meetup >>> account - like we do with CI for Astronomer and Amazon. That would seem >>> even better from the point of view of marketing, sharing the link and so on. >>> >>> J. >>> >>> >>> On Mon, Jan 26, 2026 at 6:47 PM Briana Steel via dev < >>> [email protected]> wrote: >>> >>>> Hi all, >>>> >>>> I hope you’re doing well! >>>> >>>> I’d like to propose an update to the current Airflow “Meetups” page at >>>> https://airflow.apache.org/meetups/ >>>> >>>> The page currently links to a static list of various meetup groups, but >>>> it >>>> doesn’t provide a centralized view of active and upcoming community >>>> events. >>>> >>>> To make it easier for users to discover and join local and global >>>> Airflow >>>> meetups, I propose replacing or augmenting that section with a link to >>>> our >>>> curated Meetup Pro listing hosted at: >>>> >>>> https://www.meetup.com/pro/astronomer-inc/ >>>> >>>> This page automatically aggregates all of the active Airflow-related >>>> meetup >>>> groups and events across regions, and keeps them up to date without >>>> manual >>>> maintenance. It provides a more dynamic and user-friendly experience for >>>> anyone looking to engage in local Airflow community events. >>>> >>>> I understand the link says Astronomer, but that is because in order to >>>> add >>>> a Meetup group to a "network" you must pay a fee per group. And >>>> therefore, >>>> the Meetup Pro account is under Astronomer's name. However, anyone can >>>> still host a meetup and be the organizer of a meetup group, giving them >>>> full access to build events, etc. If we embed, the link that says >>>> "Astronomer, Inc." would not even be visible. >>>> >>>> Benefits of this update: >>>> >>>> Centralized list of meetups across regions >>>> >>>> Automatically updated event listings >>>> >>>> Reduces maintenance overhead on the Airflow website >>>> >>>> Improves discoverability for community members >>>> >>>> If there’s interest, I’d love to engage someone's assistance in >>>> submitting >>>> the PR and taking a look at the Meetup API. >>>> >>>> Thanks for considering this — looking forward to the community’s >>>> thoughts! >>>> >>>> Best, >>>> Briana Steel >>>> >>>
