weiting-chen commented on issue #11438: URL: https://github.com/apache/gluten/issues/11438#issuecomment-5661629938
## Public-reference verification update - 2026-09-14 I have updated all 10 rows with the latest public-content checks, preserved the earlier outreach/response history, and separated verified naming fixes from remaining wording concerns. **Current assessment: 2 clearly resolved references (#4, #5), 1 qualified removal (#8), 4 partially resolved references (#1, #2, #3, #6), and 3 still needing corrections (#7, #9, #10). The issue remains open.** ### Findings - **IBM (#1-3):** All three pages now use **Apache Gluten** in the title/main heading and lead. That naming improvement is verified, including the previously blank Azure row. However, "Apache Gluten accelerated Spark engine" remains an engine/component label. Azure documentation also contains "ApacheGluten" without a space. These need clarification or ASF Trademarks guidance; adding the Apache prefix does not by itself settle the product-labeling concern. - **Microsoft (#4):** The current runtime page describes native execution "via Apache Gluten and Velox", without vendor-possessive Gluten wording. The table now reflects this neutral reference rather than the older "remove 3rd party name" description. - **Alibaba (#5-6):** Help documentation passes the textual naming check and redirects to a new URL, now recorded. The blog's first reference and technical heading use Apache Gluten, but "the Intel Apache Gluten team" remains. Proposed clarification: **"Intel contributors to Apache Gluten"**. This is ambiguous affiliation wording, not proof of an ownership claim. - **Kyligence (#7):** The historical February 2023 article still uses bare Gluten in the heading/lead, with "Kyligence Gluten" in the HTML title. Request a prominent dated note identifying the project as Apache Gluten today, plus a title clarification; preserve accurate historical co-development attribution. - **Baidu (#8):** The original URL returns HTTP 200 with article-specific `pageProps.is404=true` and no article content. This supports application-level removal, **not** an HTTP 404/410 or proven permanent deletion. A normal-browser capture of any JavaScript destination would strengthen the evidence. - **Acceldata (#9-10):** Both resources remain live. The blog title/H1 and opening reference omit Apache. The PDF cover (page 1) says "Acceldata's ODP Spark / with Gluten Velox", and its executive summary (page 2) says **"Intel's Gluten plugin"** (apostrophes normalized). Both need correction; the PDF ownership wording is the highest-priority follow-up. ### Next actions 1. Follow up with Acceldata on **both** the blog and PDF, requesting corrected title/cover/lead wording and an acknowledgement/publication ETA. Contact Kyligence for the historical clarification. 2. Follow up with IBM on descriptive rather than product-style naming, and Alibaba on the remaining team wording. Seek ASF Trademarks guidance where interpretation is disputed. No new outreach or escalation is being claimed by this verification update. 3. Add row-specific response dates, ETAs and dated public evidence as changes go live. The January 17 comment reports company-level outreach, but does not establish an acknowledgement or exact contact date for every URL. 4. Publish a short project-docs brand-reference guide and record community agreement on quarterly monitoring, with a named owner and backup. **Proposed next check: 2026-12-14**; this is a proposal, not an agreed or scheduled commitment. Suggested guidance for the documentation: > Refer to the project as **Apache Gluten** in titles, prominent headings and first mentions. Distinguish your product from the Apache project: prefer "Our product accelerates Apache Spark using Apache Gluten and Velox." Avoid wording implying vendor ownership or ASF endorsement. Link to the Apache Gluten homepage, provide appropriate trademark attribution, and follow the ASF name-usage guide. Historical articles may retain original wording with a prominent current-name clarification. Policy references: [ASF name-usage guide](https://www.apache.org/foundation/marks/guide) and [ASF trademark FAQ](https://www.apache.org/foundation/marks/faq/). Subsequent bare-name mentions are not automatically failures, and historical contribution credit is not inherently an ownership claim. **Evidence limits:** Checks used live HTML and direct PDF text/layout extraction, not search snippets. Embedded graphics were not comprehensively visually audited; the actual IBM console UI and Baidu browser-side navigation were not verified. The definition-of-done checkboxes remain unchecked: each row still needs a verified resolution or documented blocker/next step, and the project guidance plus monitoring agreement must be publicly linked. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
