I've reached out to a design contributor to update our current logo in 
accordance with the branding policy requirements:

> ASF's trademarks are either words (e.g., "Apache" and "Apache ProjectName" 
> and "ProjectName") or graphic logos that are intended to serve as trademarks
>  for that ASF software. The ASF feather is also an ASF trademark for Apache 
> software which has special meaning for ASF and special rules regarding its 
> use.

By adding "Apache" and trademark "TM" in the logo, we make sure it's more clear 
that OpenDAL is an Apache Project.

OpenDAL PR: https://github.com/apache/incubator-opendal/pull/3990
OpenDAL Logo: https://www.apache.org/logos/#opendal

On Tue, Jan 16, 2024, at 11:06, tison wrote:
> I saw Xuanwo participate in the trademark attribution thread on
> databend.rs to convey the ASF trademark attribution [1].
>
> This can be reused for any website you admin containing references to
> Apache trademarks. This is not special to Apache trademarks but in
> Apache Kvrocks I ever received a report to convey Redis trademarks
> properly [2].
>
> Best,
> tison.
>
> [1] https://github.com/datafuselabs/databend-docs/pull/355
> [2] https://github.com/apache/kvrocks/issues/1742
>
> tison <[email protected]> 于2024年1月16日周二 11:02写道:
>>
>> I send a PR [1] to improve the trademark symbol usage for Javadocs.
>> This is something I spotted and confirmed by the trademarks@ that can
>> be improved.
>>
>> I guess that with some configuration to the javadoc-plugin, we should
>> be able to improve the footer to convey something like [2] mentioned
>> above.
>>
>> Best,
>> tison.
>>
>> [1] https://github.com/apache/incubator-opendal/pull/3989
>> [2] https://github.com/apache/incubator-opendal/pull/3986
>>
>> tison <[email protected]> 于2024年1月16日周二 10:57写道:
>> >
>> > I send a PR [2] to review our PMC member's blog so that according to the 
>> > policy:
>> >
>> > > Titles or subtitles, including web page title or description metadata.
>> >
>> > The titles use the full form.
>> >
>> > This is also an example that we can review the usage after the
>> > donation. Before the donation, the project should be still called
>> > OpenDAL in my opinion.
>> >
>> > Best,
>> > tison.
>> >
>> > [2] https://github.com/Xuanwo/blog/pull/418
>> >
>> > tison <[email protected]> 于2024年1月16日周二 09:41写道:
>> > >
>> > > Hi,
>> > >
>> > > I send a PR [1] to improve the occurrences on our docs page and blog 
>> > > pages.
>> > >
>> > > One common misunderstanding is that we can use the name "OpenDAL" for
>> > > convenience everywhere and just understand that "Apache OpenDAL™" is
>> > > the full form.
>> > >
>> > > From our branding policy, we should use "Apache OpenDAL™" at least for
>> > > all "the first and most prominent mentions".
>> > >
>> > > You may take a look at [2] and [3] where "Apache Spark™" and "Apache
>> > > Kafka®" are used.
>> > >
>> > > Of course, there is no so-called "commercial company behind" our
>> > > community, so individuals checking the content can take time. But at
>> > > least we can check our own usage for the content we produce. Not only
>> > > our website and distributions, but also our personal content. At least
>> > > to call our project "Apache OpenDAL" - this is not a secondary usage,
>> > > but the primary :D
>> > >
>> > > Best,
>> > > tison.
>> > >
>> > > [1] https://github.com/apache/incubator-opendal/pull/3988
>> > > [2] https://www.databricks.com/blog/introducing-apache-sparktm-35
>> > > [3] https://www.confluent.io/lp/confluent-kafka
>> > >
>> > > Suyan <[email protected]> 于2024年1月16日周二 00:03写道:
>> > >
>> > > >
>> > > > Hi,
>> > > >
>> > > > I’ve added the copyright/trademark statement to our nodejs binding’s 
>> > > > docs footer.[1]
>> > > >
>> > > > Sincerely,
>> > > > Suyan
>> > > >
>> > > > —
>> > > >
>> > > > [1]: https://github.com/apache/incubator-opendal/pull/3986
>> > > >
>> > > >
>> > > > > 2024年1月15日 21:35,tison <[email protected]> 写道:
>> > > > >
>> > > > > Hi,
>> > > > >
>> > > > > As an ASF project, it's the (P)PMC's responsibility to manage our
>> > > > > brand and protect the ASF trademarks. Also, any issue reporting or
>> > > > > patches improving branding from any community member are valid
>> > > > > contributions.
>> > > > >
>> > > > > You can find a concrete guideline about trademarks at [1] and other
>> > > > > references from the links on that page, as well as [2].
>> > > > >
>> > > > > Previously, we fixed [3][4][5] which can be used as examples.
>> > > > >
>> > > > > This email is intended to call for contributions from all the
>> > > > > community members and a notice to all the PMC members that the PMC
>> > > > > should manage our brand and protect the ASF trademarks.
>> > > > >
>> > > > > You may review the content you generated or saw and report/discuss 
>> > > > > any
>> > > > > potential violations here. Or, when you're sure it's a violation, 
>> > > > > send
>> > > > > a fix.
>> > > > >
>> > > > > For sharing the knowledge, you can cross-post the contribution you
>> > > > > made to this thread.
>> > > > >
>> > > > > IIRC, there are still several occurrences in the community pages[6]
>> > > > > that don't comply with the policy. Instead of barely "to comply with
>> > > > > the policy", you may think of improving the description wholly.
>> > > > >
>> > > > > You can do a comparison with other TLPs to get the potential issues,
>> > > > > but remember that TLPs are not always correct, so we should use the
>> > > > > policy as the source and what TLPs do as references.
>> > > > >
>> > > > > If you have any questions, feel free to ask here.
>> > > > >
>> > > > > Best,
>> > > > > tison.
>> > > > >
>> > > > > [1] https://www.apache.org/foundation/marks/guide
>> > > > > [2] https://www.apache.org/foundation/marks/pmcs
>> > > > > [3] https://github.com/apache/incubator-opendal/pull/3850
>> > > > > [4] https://github.com/apache/incubator-opendal/pull/3978
>> > > > > [5] https://github.com/apache/incubator-opendal/pull/3831
>> > > > > [6] https://opendal.apache.org/community/
>> > > >

-- 
Xuanwo

Reply via email to