> independently Hello Justin,
After reading the trademark guide[1], I agree that the (P)PMC can review the occurrence again since it clearly wrote: > The first and most prominent mentions must use the full form: "Apache > Hadoop®" of the name for any individual usage and it gives a certain list about what occurrences are counted. So we should use "Apache OpenDAL™" in every such occurrence: > * Titles or subtitles, including web page title or description metadata. > * The first and most prominent header elements within any major document > section. > * The first and most prominent callout, sidebar, or other types of > highlighted blocks of content displayed to the user. > * The first and most prominent uses in running or body text within the > document. > * For graphics headers or diagrams, the full form of the name must be clear > in the graphic itself where practical; if not, the full form of the name must > be used in a prominent caption header, or accompanying explanation of the > graphic. > * For video content, in the title and first uses, as well as the last use or > any use in credits, must be the full form of the name. All of the distribution pages and API docs should already follow this policy, but several website pages can be still improved. Also, for trademark attribution, I understand the databend.rs, if it refers to OpenDAL, it should contain a Footer like Datastax does[2]. However, the (P)PMC is continuously proactively resolving this issue already, instead of negatively responding. Before the graduation discussion, when I noticed GreptimeDB doesn't use OpenDAL is the Apache form, I submitted a PR[3]. Of course, it's still not follow strictly Apache Foo™ so I'll submit a new PR to improve it. Moreover, when you firstly spot the issues about using "Apache Foo" in the name in some certain pages, beyond the pages you referref to, the OpenDAL PPMC checks all the bindings pages and updates them accordingly to this policy. Moreover, when we notice that using a logo containing Apache and the trademark symbol can help convey the Apache brand, we start a discussion to improve it [4]. Moreover, when we are aware that trademarks@ holds an NPM account that can help convey the Apache brand, we file a ticket to integrate the release process with it [5]. Moreover, we don't negatively barely "fixing" the issue, but think of the policy and what is the best way we follow it effectively. So instead of dropping the Python API docs to cancel the branding wart, we developed a common solution that can be used in all the ASF Python projects [6]. Moreover, we're actively checking other pages you didn't refer to [7][8], while I noticed that it should use the TM symbol to follow the policy strictly now. Your feedback is as common as a general issue report so we want to ask for the details page and paragraph referred, just like when trademarks@ asks PMCs to fix issues it will identify the pages and concrete issues. Besides, I noticed that @TheASF which should be controlled by marketing or press or trademarks doesn't use trademark symbol [9] when announcing. Of course, this is not a reason that the policy can be workaround but something that the account manager should fix. However, we should understand the challenges we're facing when fixing these issues. The OpenDAL PMC is proactively understanding the policy and fixing issues as much as they can. Remember that we're volunteers, so spotting issues and collaborating to resolve the issue are welcome. Best, tison. [1] https://www.apache.org/foundation/marks/guide [2] https://www.datastax.com/ [3] https://github.com/GreptimeTeam/greptimedb/pull/2653 [4] https://lists.apache.org/thread/vg5mor8m4twy3578rzdqop0y9t961x6y [5] https://issues.apache.org/jira/browse/INFRA-25325 [6] https://github.com/apache/incubator-opendal/pull/3850 [7] https://github.com/apache/incubator-opendal/pull/3978 [8] https://github.com/apache/incubator-opendal/pull/3831 [9] https://twitter.com/TheASF Justin Mclean <jus...@classsoftware.com> 于2024年1月15日周一 13:40写道： > > Hi, > > The (P)PMC must be able to do this independently. Just look at each of the > resources you listed and ask yourself: > - Is Apache Foo being used in the most prominent place? > - Are we using the trademark symbol? > - Does the page include trademark attribution for any Apache trademarks used? > > Our full trademark policy covers a lot more than this, but that’s a good > start. > > Kind Regards, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
