Re: [RESULT] [VOTE] Release Apache Pekko(incubating) gRPC 1.0.2-RC1
FYI - I prepared a patch "Mention that there is no implicit +1 in votes" [1] to include this information. Feel free to give it a review and improve the expression. Best, tison. [1] https://github.com/apache/www-site/pull/338 Ayush Saxena 于2024年1月9日周二 20:56写道： > > > I may prepare a patch on > https://www.apache.org/foundation/voting.html to mention this > explicitly. > > Still doing this would be helpful & maybe an explicit line in the > package release section as well [1], that a RM "can" vote as well, I > have seen couple of folks with this confusion that since you can't > approve your own code, so as a RM you can not vote for the release, > since you prepared the artifacts. > > -Ayush > > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes > > On Mon, 8 Jan 2024 at 15:55, tison wrote: > > > > Aha. I saw "Here is my +1 (binding)." at the bottom of the first mail now > > >_< > > > > Best, > > tison. > > > > PJ Fanning 于2024年1月8日周一 18:15写道： > > > > > > Thanks Tison for checking. I did vote on the initial email. > > > > > > https://lists.apache.org/thread/og2mtjv4nsgrh1mc96cfxbqzz8poysp8 > > > > > > On Mon, 8 Jan 2024 at 11:10, tison wrote: > > > > > > > > Hi PJ, > > > > > > > > Congrats. > > > > > > > > I was told that the RM who drives the release doesn't implicitly vote > > > > a +1. So you'd better cast your own +1 the next time when running a > > > > release. > > > > > > > > But I don't find a policy sentence to mention it. While I think the > > > > argument is valid, I may prepare a patch on > > > > https://www.apache.org/foundation/voting.html to mention this > > > > explicitly. > > > > > > > > Best, > > > > tison. > > > > > > > > PJ Fanning 于2024年1月8日周一 17:48写道： > > > > > > > > > > The vote passes with 3 +1s and no negative votes. All votes were > > > > > binding. > > > > > > > > > > Vote Thread > > > > > https://lists.apache.org/thread/og2mtjv4nsgrh1mc96cfxbqzz8poysp8 > > > > > > > > > > Votes > > > > > Zili Chen (tison) > > > > > Matthew de Detrich > > > > > PJ Fanning > > > > > > > > > > I will proceed with the release and make the announcements. > > > > > > > > > > Thanks to everyone who participated in the development and review of > > > > > this release. > > > > > > > > > > - > > > > > 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 > > > > > > > > > > - > > > 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 > > > > - > 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
Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP
Here is the thread on dev@opendal.a.o [1]. > only Xuanwo and I fix We're in the final PMC anyway and I'm on vacation to spend my time and energy handling issues I spotted. So this topic is discussed and spread within dev@opendal.a.o. It's no longer about whether it's "pointed out" or "proactively managed", but I try to deliver the understanding among the PMC and the community, as well as demonstrate how we can improve it and what the common misunderstanding is. I believe this is how to equip the PMC to handle branding issues. Best, tison. [1] https://lists.apache.org/thread/3qq763vr0k7pg3qmvp2dbvg2pomfnh2j tison 于2024年1月15日周一 21:19写道： > > > the PMC is clear that they're responsible to fix them > > ... and they do fix them. All the fixes above are produced by PMC members. > > > this can be an evidence that the PMC understands their responsibility > > Somewhat I send the email so it's not totally active. But I believe > that the PMC members are willing to manage the project and I just put > the button. > > Best, > tison. > > tison 于2024年1月15日周一 21:12写道： > > > > > Datastax has had recent issues regarding trademarks; please follow the > > > policy, not what other 3rd party companies do. > > > > Of course we should follow the policy primarily. The reference is > > demonstrate what "adding trademark attributions" mean. > > > > > However, they don’t seem to understand that they are responsible for > > > managing their brand and protecting the ASF trademarks > > > > I get your points now. > > > > The PMC prioritizes the issues you spotted and fixed them firstly. > > They may ask questions and seek helps for trademarks to get a best > > practices to comply with the policy. While you may regard it as > > "outsource", the PMC is clear that they're responsible to fix them but > > cross check the understanding. > > > > I can understand now that it can give an imagine only Xuanwo and I fix > > the issues and beyond what you point out, most of the branding > > improvement is started by my comments [1][2][3][4][5]. I may be too > > proactive here to hide others understanding. > > > > The trademark guide [6] clearly declares where we should use the full > > form of the project name. And for other content the PMC generates, > > there can be other potential issues to fix. > > > > I'll send an email in dev@opendal.a.o for conveying this information > > and let other members to review the content they produced or saw. Hope > > this can be an evidence that the PMC understands their responsibility. > > Of course, this is not a one-time action but should be continued as > > the PMC exists :D > > > > Best, > > tison. > > > > [1] https://lists.apache.org/thread/vg5mor8m4twy3578rzdqop0y9t961x6y > > [2] https://issues.apache.org/jira/browse/INFRA-25325 > > [3] https://github.com/apache/incubator-opendal/pull/3984 > > [4] https://github.com/apache/incubator-opendal/pull/3983 > > [5] https://github.com/apache/incubator-opendal/pull/3978 > > [6] https://www.apache.org/foundation/marks/guide > > > > Justin Mclean 于2024年1月15日周一 20:45写道： > > > > > > > > Hi, > > > > > > > Also, for trademark attribution, I understand the databend.rs, if it > > > > refers to OpenDAL, it should contain a Footer like Datastax does[2]. > > > > > > Datastax has had recent issues regarding trademarks; please follow the > > > policy, not what other 3rd party companies do. > > > > > > I can see the project, from what you have provided, has fixed a number of > > > issues pointed out to them. However, they don’t seem to understand that > > > they are responsible for managing their brand and protecting the ASF > > > trademarks. > > > > > > 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
Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP
> the PMC is clear that they're responsible to fix them ... and they do fix them. All the fixes above are produced by PMC members. > this can be an evidence that the PMC understands their responsibility Somewhat I send the email so it's not totally active. But I believe that the PMC members are willing to manage the project and I just put the button. Best, tison. tison 于2024年1月15日周一 21:12写道： > > > Datastax has had recent issues regarding trademarks; please follow the > > policy, not what other 3rd party companies do. > > Of course we should follow the policy primarily. The reference is > demonstrate what "adding trademark attributions" mean. > > > However, they don’t seem to understand that they are responsible for > > managing their brand and protecting the ASF trademarks > > I get your points now. > > The PMC prioritizes the issues you spotted and fixed them firstly. > They may ask questions and seek helps for trademarks to get a best > practices to comply with the policy. While you may regard it as > "outsource", the PMC is clear that they're responsible to fix them but > cross check the understanding. > > I can understand now that it can give an imagine only Xuanwo and I fix > the issues and beyond what you point out, most of the branding > improvement is started by my comments [1][2][3][4][5]. I may be too > proactive here to hide others understanding. > > The trademark guide [6] clearly declares where we should use the full > form of the project name. And for other content the PMC generates, > there can be other potential issues to fix. > > I'll send an email in dev@opendal.a.o for conveying this information > and let other members to review the content they produced or saw. Hope > this can be an evidence that the PMC understands their responsibility. > Of course, this is not a one-time action but should be continued as > the PMC exists :D > > Best, > tison. > > [1] https://lists.apache.org/thread/vg5mor8m4twy3578rzdqop0y9t961x6y > [2] https://issues.apache.org/jira/browse/INFRA-25325 > [3] https://github.com/apache/incubator-opendal/pull/3984 > [4] https://github.com/apache/incubator-opendal/pull/3983 > [5] https://github.com/apache/incubator-opendal/pull/3978 > [6] https://www.apache.org/foundation/marks/guide > > Justin Mclean 于2024年1月15日周一 20:45写道： > > > > > Hi, > > > > > Also, for trademark attribution, I understand the databend.rs, if it > > > refers to OpenDAL, it should contain a Footer like Datastax does[2]. > > > > Datastax has had recent issues regarding trademarks; please follow the > > policy, not what other 3rd party companies do. > > > > I can see the project, from what you have provided, has fixed a number of > > issues pointed out to them. However, they don’t seem to understand that > > they are responsible for managing their brand and protecting the ASF > > trademarks. > > > > 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
Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP
> Datastax has had recent issues regarding trademarks; please follow the > policy, not what other 3rd party companies do. Of course we should follow the policy primarily. The reference is demonstrate what "adding trademark attributions" mean. > However, they don’t seem to understand that they are responsible for managing > their brand and protecting the ASF trademarks I get your points now. The PMC prioritizes the issues you spotted and fixed them firstly. They may ask questions and seek helps for trademarks to get a best practices to comply with the policy. While you may regard it as "outsource", the PMC is clear that they're responsible to fix them but cross check the understanding. I can understand now that it can give an imagine only Xuanwo and I fix the issues and beyond what you point out, most of the branding improvement is started by my comments [1][2][3][4][5]. I may be too proactive here to hide others understanding. The trademark guide [6] clearly declares where we should use the full form of the project name. And for other content the PMC generates, there can be other potential issues to fix. I'll send an email in dev@opendal.a.o for conveying this information and let other members to review the content they produced or saw. Hope this can be an evidence that the PMC understands their responsibility. Of course, this is not a one-time action but should be continued as the PMC exists :D Best, tison. [1] https://lists.apache.org/thread/vg5mor8m4twy3578rzdqop0y9t961x6y [2] https://issues.apache.org/jira/browse/INFRA-25325 [3] https://github.com/apache/incubator-opendal/pull/3984 [4] https://github.com/apache/incubator-opendal/pull/3983 [5] https://github.com/apache/incubator-opendal/pull/3978 [6] https://www.apache.org/foundation/marks/guide Justin Mclean 于2024年1月15日周一 20:45写道： > > Hi, > > > Also, for trademark attribution, I understand the databend.rs, if it > > refers to OpenDAL, it should contain a Footer like Datastax does[2]. > > Datastax has had recent issues regarding trademarks; please follow the > policy, not what other 3rd party companies do. > > I can see the project, from what you have provided, has fixed a number of > issues pointed out to them. However, they don’t seem to understand that they > are responsible for managing their brand and protecting the ASF trademarks. > > 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
Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP
Hi, > Also, for trademark attribution, I understand the databend.rs, if it > refers to OpenDAL, it should contain a Footer like Datastax does[2]. Datastax has had recent issues regarding trademarks; please follow the policy, not what other 3rd party companies do. I can see the project, from what you have provided, has fixed a number of issues pointed out to them. However, they don’t seem to understand that they are responsible for managing their brand and protecting the ASF trademarks. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Graduate Apache OpenDAL (incubating) as a TLP
> 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 于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
