Re: Incubator release announcements should have disclaimer?

Hi Sebb, I am from the OpenDAL project. We will update our email template for announcements to ensure that all future announcements have attached disclaimers. You can track this work at https://github.com/apache/incubator-opendal/issues/3157. Thanks! On Fri, Sep 22, 2023, at 06:03, sebb wrot

Jira issues largely being ignored

There does not seem to be much attention given to Jira issues by Incubator members. There also are quite a few Jira issues that can be closed. Sebb - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additiona

[jira] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution

[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-253: --- Labels: CanBeClosed (was: ) > Issues with MXNet releases and their distribution > ---

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767746#comment-17767746 ] Sebb commented on INCUBATOR-253: MXNet graduated in 2022, so this issue can be closed

[jira] [Commented] (INCUBATOR-265) Maybe incorrect clarification in Graduation Guide

[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767745#comment-17767745 ] Sebb commented on INCUBATOR-265: PR has been applied > Maybe incorrect clarification

[jira] [Updated] (INCUBATOR-265) Maybe incorrect clarification in Graduation Guide

[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-265: --- Labels: CanBeClosed (was: ) > Maybe incorrect clarification in Graduation Guide > ---

[jira] [Updated] (INCUBATOR-278) Outdated link to Apachecon 2022 on website

[ https://issues.apache.org/jira/browse/INCUBATOR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated INCUBATOR-278: --- Labels: CanBeClosed (was: ) > Outdated link to Apachecon 2022 on website > --

[jira] [Commented] (INCUBATOR-278) Outdated link to Apachecon 2022 on website

[ https://issues.apache.org/jira/browse/INCUBATOR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767744#comment-17767744 ] Sebb commented on INCUBATOR-278: Seems to have been fixed; this issue can be closed >

Re: Incubator release announcements should have disclaimer?

For example: https://lists.apache.org/list?general@incubator.apache.org:lte=1M:Announce%20release shows several recent announce emails, including: https://lists.apache.org/thread/mod3g7fw695zbsl5cwgtl5okqj8khbvw https://lists.apache.org/thread/9w6cj7lh217tpt04s8lng55b5n4spg1b https://lists.apach

Re: Incubator release announcements should have disclaimer?

> announcements What announcements do you refer to here? Can you elaborate a bit perhaps with samples? Best, tison. sebb 于2023年9月22日周五 00:55写道： > As the subject implies: surely announcements of Incubator releases > should include a prominent Incubation disclaimer? > > There have been some rec

Incubator release announcements should have disclaimer?

As the subject implies: surely announcements of Incubator releases should include a prominent Incubation disclaimer? There have been some recent ones without: OpenDAL Wayang Devlake Paimon Pekko The releases are tagged with Incubating, but that is unlikely to mean much to 3rd parties. Sebb

Re: [DISCUSS] Incubating Proposal of Answer

Hi, About the project name and trademark, according to the trademarks@ reply, > It is possible to use such a name on the understanding that obtaining a > trademark for it is likely to be a more difficult (and longer) process. So it's viable and I also inform the initial committers to think of th

Re: [DISCUSS] Incubating Proposal of Answer

Hi PJ, Thanks for the reply, I will talk to the team and find out if we can figure out a better name for it. I raised the same question when I first heard about the name, but it's hard for the team to give up the product word they already have without a solid objection. Willem Jiang Twitter: wi

Re: [DISCUSS] Incubating Proposal of Answer

I just read the answer from the trademark team. It would be nice to ask the initial team to discuss the cons and pros, especially regarding trademark registration issues and search hits. Both are important for a project. Sheng Wu 吴晟 Twitter, wusheng1108 Justin Mclean 于2023年9月21日周四 22:39写道： > > H

Re: [DISCUSS] Incubating Proposal of Answer

HI, We’ve already asked trademarks the question if the project can use the name. For the answer, see [1] Kind Regards, Justin 1. https://lists.apache.org/thread/ovx9wfst80f28xolf0vhvzzdtzhh1ovq

Re: [DISCUSS] Incubating Proposal of Answer

I sent an email query for feedback on the trademark when sending this proposal. Let's see the feedback from the trademark VP. By the way, The Apache Arrow project[1] may hit the same situation as a common word. [1]https://arrow.apache.org/ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On

Re: [DISCUSS] Incubating Proposal of Answer

Moreover, the functions of the app seem to be not just 'answer', but also 'ask' and 'discuss', with the real goal of community-building. So any variant of Answer for the product name would be a little misleading. a

Re: [DISCUSS] Incubating Proposal of Answer

Thanks for pointing that out. The right URL of the GitHub group is https://github.com/answerdev/ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Sep 21, 2023 at 8:39 PM Xuanwo wrote: > > Hi, there a small typo: > > https://github.com/answer.dev/ always returns HTTP 406 error code. > >

Re: [DISCUSS] Incubating Proposal of Answer

For me, Answer is a problematic name. We're trying to move away from relying on the Apache brand name so project names ideally should work with or without the Apache name. Answer does not work as a brand on its own, it depends on being Apache Answer to make it seem like a brand. I'm not saying that

Re: [DISCUSS] Incubating Proposal of Answer

Hi I have a question for the mentors, do you check whether this general word, `Answer` is an acceptable project name for the foundation? Sheng Wu 吴晟 Twitter, wusheng1108 Jean-Baptiste Onofré 于2023年9月21日周四 20:39写道： > > Hi, > > It looks interesting at first glance. I will do a new pass on the > p

Re: [DISCUSS] Incubating Proposal of Answer

Hi, It looks interesting at first glance. I will do a new pass on the proposal (in more details). Regards JB On Thu, Sep 21, 2023 at 2:00 PM Willem Jiang wrote: > > We want to propose Answer as a new Apache Incubator project. > > Answer[1] is a question-and-answer (Q&A) platform software for t

Re: [DISCUSS] Incubating Proposal of Answer

Hi, there a small typo: https://github.com/answer.dev/ always returns HTTP 406 error code. I believe it should be https://github.com/answerdev/ On Thu, Sep 21, 2023, at 20:00, Willem Jiang wrote: > We want to propose Answer as a new Apache Incubator project. > > Answer[1] is a question-and-answ

[DISCUSS] Incubating Proposal of Answer

We want to propose Answer as a new Apache Incubator project. Answer[1] is a question-and-answer (Q&A) platform software for teams at any scale to build a help center, knowledge base, community forum, etc. The key features of Answer: 1. Questions and Answers - Ask questions and get answers from yo