Page History

...

Incubating projects carries both the Apache name and their own project identity. Protecting these names and logos from misuse by third parties is critical. Misuse can confuse users, imply false endorsements, or undermine the vendor-neutral reputation of the Apache Software Foundation (ASF).

Important: Do not wait Please don't wait until graduation to address branding issues. Several podlings have had their graduation delayed because they did not tackle branding and third-party misuse early enough.

...

• Third parties may promote software or services as “official” when they are not.
• Without correction, users may believe the ASF endorses a product, distribution, or company.
• Early intervention avoids helps avoid confusion and builds fosters trust.

3. Preserving Vendor Neutrality

...

• Conference agendas, vendor webinars, and blog posts frequently misuse podling names.
• Podlings should proactively review how their project is listed in external events and press mentions.
• Correct issues early quickly to avoid confusion and to demonstrate show maturity to the IPMC.

Consequences of Not Acting

Several podlings have had their graduation delayed because

...

companies ignored the ASF branding guidelines. and the project failed to correct the misuse until the end of incubation.

...

Early and active management avoids these blockers and shows readiness for TLP status.

...

Common Risks

• A vendor markets a product as “Apache

  Foobar™

  Foo Enterprise Edition,

  ” implying ASF endorsement

  ” implying endorsement by the ASF.

• A company uses the ASF logo on its own website to promote commercial services.

• Blogs

  or

  , conference talks, or press describe

  or infer

  the podling as “Company X’s project”

  rather than an Apache community

  instead of part of the Apache community.

• The project is labelled as “owned by Company X,” “developed at Company X,” or “the creators of Apache Foo”, creating false impressions of origin or control.

• Only one vendor is visibly associated with commercial use,

  creating

  giving the

  perception

  appearance of private ownership.

• The podling itself fails to use the correct name

  (

  — “Apache Foobar (incubating)”

  )

  — in its

  site

  website,

  docs

  documentation, or releases.

• A single company’s employees dominate governance or communication channels, leading outsiders to assume that the company controls the project.

• Third-party materials (e.g., whitepapers, case studies, commercial training) present the podling as a proprietary product rather than an ASF community project.

• Conference booths, banners, or swag display the podling name or logo without “(incubating)”, or present the project as part of a single vendor’s offerings.

...

Good Practices for Podlings

...