Track & remediate third‑party branding references

### Backend

VL (Velox)

### Bug description

## Background / Why this matters
In the graduation readiness [discussion](https://lists.apache.org/thread/5drn3xwdc8rp55x7blcnfrcf62vrcbqj) concerns were raised about third‑party references using "Gluten" in ways that may:
- omit the full ASF project name on first/prominent mention ("Apache Gluten"), and/or
- imply ownership/vendor affiliation (e.g., "X's Gluten"), and/or
- treat Gluten like a vendor product/component name (e.g., "Gluten accelerated Spark engine").

We should demonstrate a repeatable process to monitor and correct these references, and track remediation status publicly.

## Goal
1) Get the most prominent / first reference updated to "Apache Gluten" (and remove implied ownership/productization language where applicable).
2) Track outreach and public verification.
3) Establish an ongoing monitoring plan so this does not regress.

---

## Proposed approach
### Phase 1 — Outreach (in progress)
- Contact each vendor/site owner requesting:
- First & most prominent reference uses **"Apache Gluten"**
- Remove implied ownership phrasing (e.g., “Intel’s Apache Gluten”)
- Avoid product-style naming like "Gluten accelerated Spark engine"

### Phase 2 — Verification
- Close each row only when the change is publicly visible.
- Capture evidence:
- updated URL + date verified
- optional screenshot / archive link (helpful for audit trail)

### Phase 3 — Monitoring (ongoing)
- Maintain a “watch list” of known pages.
- Run a quarterly scan (manual or scripted) for:
- “Gluten” used without “Apache Gluten” in the title/lead section
- vendor possessive wording (“X’s Apache Gluten”)
- productized terms (“Gluten accelerated Spark”)
- Escalate to ASF Trademarks where guidance is needed or vendors are unresponsive.

---

## Tracking table (Justin’s highlighted list)

> Last public-content check: **2026-09-14**. Status values: Not contacted | Contacted | Acknowledged | Fix in progress | Partially resolved | Needs correction | Fixed (verified) | Blocked / needs Trademarks.
>
> **Partially resolved** means the full-name correction is visible but another concern needs follow-up or guidance; **Needs correction** means the checked page still needs changes. These are content assessments, not claims of a new vendor response or confirmed work in progress. "Verified on" records the inspection date, including unresolved findings. Earlier outreach/response dates are preserved below in ISO format.

| ID | Company / Site | URL | Issue pattern (summary) | Outreach owner | Status | Date contacted | Vendor response / ETA | Verified on | Evidence |
|---:|---|---|---|---|---|---|---|---|---|
| 1 | IBM Docs (AWS) | https://www.ibm.com/docs/en/watsonxdata/aws?topic=engine-introduction-gluten-accelerated-spark | Full name corrected; engine-style naming remains for review | weiting-chen | Partially resolved | 2026-01-06 | 2026-01-07 (prior tracker); no new ETA recorded | 2026-09-14 | Title/H1 and lead: "Apache Gluten accelerated Spark engine". January naming fix remains verified; this does not independently resolve product-labeling concerns. Next: request descriptive wording such as "Spark acceleration using Apache Gluten", or ASF Trademarks guidance. |
| 2 | IBM Docs (Standard) | https://www.ibm.com/docs/en/watsonxdata/standard/2.2.x?topic=components-gluten-accelerated-spark-engine | Full name corrected; engine-style naming remains for review | weiting-chen | Partially resolved | 2026-01-06 | 2026-01-30 (prior tracker); no new ETA recorded | 2026-09-14 | Title/H1: "Apache Gluten accelerated Spark engine"; lead correctly describes Apache Gluten as a native engine plugin. Provisioning text retains the engine label. Next: clarify title/component naming or seek ASF Trademarks guidance. |
| 3 | IBM Docs (Azure) | https://www.ibm.com/docs/en/watsonxdata-azure?topic=engine-provisioning-gluten-accelerated-spark | Full name corrected; engine/component labeling remains for review | weiting-chen | Partially resolved | Not recorded per URL; IBM outreach reported 2026-01-17 | No row-specific acknowledgement or ETA recorded | 2026-09-14 | Title/H1: "Provisioning Apache Gluten accelerated Spark engine"; lead uses Apache Gluten. Documented Type label says "ApacheGluten accelerated Spark engine". Next: review title/component labels and missing space; actual console UI was not inspected. |
| 4 | Microsoft Learn | https://learn.microsoft.com/en-us/fabric/data-engineering/runtime | First reference now uses Apache Gluten without vendor possessive wording | weiting-chen | Fixed (verified) | 2026-01-06 | 2026-01-22 (prior tracker) | 2026-09-14 | Current native-execution description says "via Apache Gluten and Velox". No vendor-possessive Gluten wording found in the retrieved article. Earlier evidence said the third-party name was removed; current text instead names Apache Gluten neutrally. |
| 5 | Alibaba Cloud Help | https://www.alibabacloud.com/help/en/analyticdb/analyticdb-for-mysql/security-and-compliance/full-state-adb-mysql-spark-overview | First reference correctly identifies Apache Gluten as integrated technology | weiting-chen | Fixed (verified) | 2026-01-15 | 2026-01-16 (prior tracker) | 2026-09-14 | Original tracked URL redirects (301) to this page. First relevant sentence says the edition "integrates Apache Gluten and Velox". No ownership/product-style Gluten wording found in retrieved text. |
| 6 | Alibaba Cloud Blog | https://www.alibabacloud.com/blog/601761 | Full name corrected; vendor-affiliation wording still needs clarification | weiting-chen | Partially resolved | 2026-01-15 | 2026-01-16 (prior tracker); no new ETA recorded | 2026-09-14 | First reference and heading "4.1 Process of Apache Gluten + Velox" use the full name. Section 4 still says "the Intel Apache Gluten team". Next: request "Intel contributors to Apache Gluten". This is an ambiguity, not an established ownership claim. |
| 7 | Kyligence (CN) | https://cn.kyligence.io/news/kyligence-gluten/ | Historical article lacks prominent current-name clarification | weiting-chen | Needs correction | Not recorded | No row-specific acknowledgement or ETA recorded | 2026-09-14 | HTML title begins "Kyligence Gluten"; article heading and lead use bare "Gluten" for a February 2023 event. Next: contact the owner for a prominent dated Apache Gluten clarification and title update while preserving accurate historical attribution. |
| 8 | Baidu Cloud | https://cloud.baidu.com/article/3322112 | Original article is currently application-level not found | weiting-chen | Fixed (verified) | 2026-01-06 | 2026-01-30 (prior tracker: article removed) | 2026-09-14 | Qualified removal evidence: HTTP 200, no HTTP redirect; article-specific __NEXT_DATA__ has pageProps.is404=true for article 3322112, with no article content. This is not an HTTP 404/410 or proof of permanent deletion. Next: capture a normal-browser check of any JavaScript destination. |
| 9 | Acceldata Blog | https://www.acceldata.io/blog/odp-apache-spark-with-gluten-velox | Full name missing from title/H1 and opening reference | weiting-chen | Needs correction | Not recorded per URL; Acceldata outreach reported 2026-01-17 | No row-specific acknowledgement or ETA recorded | 2026-09-14 | HTTP 200. H1: "Accelerating Apache Spark with Gluten + Velox: Vectorized Execution for Big Data at Scale"; opening reference: "Acceldata's ODP Spark with Gluten + Velox" (apostrophe normalized). Next: correct HTML title, H1 and lead to Apache Gluten and distinguish vendor offering from project. |
| 10 | Acceldata PDF | https://marketing.acceldatasolutions.net/odp-spark-with%20gluten-velox.pdf | Full name missing from cover/lead; explicit vendor-possessive wording remains | weiting-chen | Needs correction | Not recorded per URL; Acceldata outreach reported 2026-01-17 | No row-specific acknowledgement or ETA recorded | 2026-09-14 | HTTP 200, 20-page PDF. Page 1 cover: "Acceldata's ODP Spark / with Gluten Velox"; page 2: "Intel's Gluten plugin" (apostrophes normalized). Next: republish cover/title and lead with Apache Gluten, remove vendor possessive, and review headings/running titles. |

**Verification notes:** Evidence is from live HTML and PDF text/layout extraction, not search snippets. Embedded graphics were not comprehensively visually audited. Historical corporate contributions are not inherently ownership claims; remaining product/affiliation ambiguities need clarification rather than a definitive legal conclusion. Adding "Apache" or changing a URL slug alone is not sufficient to resolve every concern. No new vendor outreach, acknowledgement, or ASF Trademarks decision is claimed by this update.

**Preserved item 5 URL:** https://www.alibabacloud.com/help/en/analyticdb/analyticdb-for-mysql/user-guide/spark-confidential-engine-overview

---

## Definition of done (for this issue)
- [ ] All 10 items have either:
- **Fixed (verified)** with evidence, OR
- **Blocked** with documented reason + next step (e.g., needs ASF Trademarks guidance / vendor unresponsive)
- [ ] A short "Brand reference guidance" snippet exists in project docs (how to reference Apache Gluten correctly)
- [ ] A lightweight monitoring cadence is agreed (quarterly scan + owner)

---

## Notes / suggested phrasing vendors can use
✅ Preferred:
- “Powered by **Apache Gluten** …”
- “Acceleration using **Apache Gluten** and Velox …”

⚠️ Avoid:
- “Gluten accelerated Spark engine” (productized naming)
- “Intel’s Apache Gluten” / “ Gluten” (implied ownership)

---

## Next actions
- Assign an owner per row.
- Update status columns as outreach progresses.
- Add verification evidence when changes go live.

### Gluten version

_No response_

### Spark version

None

### Spark configurations

_No response_

### System information

_No response_

### Relevant logs

```bash

```

Start with the tracking table and verification notes, then review the ten listed URLs and update each status only when public evidence supports it. Check that every item is Fixed (verified) or Blocked with a reason and next step; also confirm that the project guidance snippet and quarterly monitoring plan are documented.

Written by the indexing model from the issue text.