?????? [DISCUSS] EventMesh Proposal
Hi, Many previous developments took place internally, but from the perspective of contributors, there have been more and more users, at least now oppo, alibaba, etc. users are participating in the contribution. I believe that with the help of the instructor, we have a better understanding of building the community. I think we are ready to enter apache instead of a temporary interest. Thanks, Eason ---- ??: "general" https://github.com/WeBankFinTech/EventMesh Willem Jiang Twitter: willemjiang Weibo: willem On Sat, Aug 15, 2020 at 9:09 AM Eason Chen https://github.com/WeBankFinTech/EventMesh/issues [2]https://github.com/WeBankFinTech/EventMesh/issues/5 Willem Jiang Twitter: willemjiang Weibo: willem - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Hi, All code of the project will be donated to ASF. There were some inconsistencies when the project was just open source, but now it is developed based on the github version. Thanks, Eason -- Original -- From: "general"
?????? [CANCEL-VOTE] Accept EventMesh into Apache Incubator
Hi, Because there are some issues that have not been clarified, I cancel the voting first, and I will restart the process after all the issues are clarified. Thanks, Eason ---- ??: "general" https://lists.apache.org/thread.html/r12b7357f2a9458e6d6719558f36c0bbf7f786771d1f727848d5170b4%40%3Cgeneral.incubator.apache.org%3E [2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
Re: [VOTE] Accept EventMesh into Apache Incubator
-1 non-binding. yousa Eason Chen 于2020年8月14日周五 下午7:57写道： > Hi, > > > After the discussion of EventMesh proposal (discussion thread is here[1]), > I would like to call a VOTE to accept it into the Apache Incubator. > > > Please cast your vote: > > > [ ] +1, bring EventMesh into Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring EventMesh into Incubator, because... > > > The vote will open at least for 72 hours and only votes from the Incubator > PMC are binding. > > > > The project's proposal is available at [2]. > > > [1] > https://lists.apache.org/thread.html/r12b7357f2a9458e6d6719558f36c0bbf7f786771d1f727848d5170b4%40%3Cgeneral.incubator.apache.org%3E > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
Re: [VOTE] Accept EventMesh into Apache Incubator
-1 non-binding. As mentioned in the discussion thread, the proposal should reflect the real situation of the project, and the contributors of the project should make active efforts to develop the community on public channels, such as github. Sheng Wu 于 2020年8月15日周六 上午11:49写道： > -1 binding > > My concerns are clear in the discussion thread. > The community is not caring for the community/user feedback from what I > have seen, such as GitHub issue discussions. > ASF and ASF incubator should never a pre-condition of the OSS community is > active or not. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Eason Chen 于2020年8月14日周五 下午7:57写道： > > > Hi, > > > > > > After the discussion of EventMesh proposal (discussion thread is > here[1]), > > I would like to call a VOTE to accept it into the Apache Incubator. > > > > > > Please cast your vote: > > > > > > [ ] +1, bring EventMesh into Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring EventMesh into Incubator, because... > > > > > > The vote will open at least for 72 hours and only votes from the > Incubator > > PMC are binding. > > > > > > > > The project's proposal is available at [2]. > > > > > > [1] > > > https://lists.apache.org/thread.html/r12b7357f2a9458e6d6719558f36c0bbf7f786771d1f727848d5170b4%40%3Cgeneral.incubator.apache.org%3E > > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal >
Re: [VOTE] Accept EventMesh into Apache Incubator
-1 binding My concerns are clear in the discussion thread. The community is not caring for the community/user feedback from what I have seen, such as GitHub issue discussions. ASF and ASF incubator should never a pre-condition of the OSS community is active or not. Sheng Wu 吴晟 Twitter, wusheng1108 Eason Chen 于2020年8月14日周五 下午7:57写道： > Hi, > > > After the discussion of EventMesh proposal (discussion thread is here[1]), > I would like to call a VOTE to accept it into the Apache Incubator. > > > Please cast your vote: > > > [ ] +1, bring EventMesh into Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring EventMesh into Incubator, because... > > > The vote will open at least for 72 hours and only votes from the Incubator > PMC are binding. > > > > The project's proposal is available at [2]. > > > [1] > https://lists.apache.org/thread.html/r12b7357f2a9458e6d6719558f36c0bbf7f786771d1f727848d5170b4%40%3Cgeneral.incubator.apache.org%3E > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
Re: [DISCUSS] EventMesh Proposal
We need to build the community around the project once we open source the code. It's quite important for the health of the project. Even the project is accepted as a podling of incubator, you still need to keep building the community. >From the information we got through the Github project, I cannot get the conclusion that you are building the community here[1]. I don't know you plan of the internal version and the open source version, if there are two different version projects why are you so urge to contribute the project which is not in active development to Apache? I think Sheng Wu already expressed the same concern as I did. Please think about it carefully, and make process to address our concerns. [1]https://github.com/WeBankFinTech/EventMesh Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Aug 15, 2020 at 9:09 AM Eason Chen wrote: > > Hi, > > > After the project was open sourced, we did not conduct evangelism, and the > internal version iterations were not synchronized in time. Many of these > issues and prs were raised by many of our partners, and many of them were not > reflected on github. Some document changes were also requested by them, It is > not very irregular at present, but we will run the standardized mechanism > later. > > > Thanks, > Eason > > > > > --原始邮件-- > 发件人: > "general" > > 发送时间:2020年8月14日(星期五) 晚上9:37 > 收件人:"Incubator General" > 主题:Re: [DISCUSS] EventMesh Proposal > > > > Hi, > > I just spent some time on the issues of EventMesh[1], it looks like > there are a bunch of people interested about this project, but > unfortunately the recent replied issue is about three weeks ago. > It's quite strange for me that the project maintainers are not keen to > answer the issues if they want to build the community from the > scratch. > > I also checked the commit logs, I can only find some small > documentation fixes which were done through the Github web interface. > I cannot find any new feature development commits after went through > the commits. > I'm not sure if WeBankFinTech guys do regular development on this repo. > > BTW, There is still an open issue asking if all the features are open > sourced[2]. > > [1]https://github.com/WeBankFinTech/EventMesh/issues > [2]https://github.com/WeBankFinTech/EventMesh/issues/5 > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
HI, > After the project was open sourced, we did not conduct evangelism, and the > internal version iterations were not synchronized in time. Does that mean a different version to what in that GitHub will be donated to ASF? That may complicate things a little as we would need to know who the contributors were. Thanks, Justin
?????? [DISCUSS] EventMesh Proposal
Hi, After the project was open sourced, we did not conduct evangelism, and the internal version iterations were not synchronized in time. Many of these issues and prs were raised by many of our partners, and many of them were not reflected on github. Some document changes were also requested by them, It is not very irregular at present, but we will run the standardized mechanism later. Thanks, Eason ---- ??: "general" https://github.com/WeBankFinTech/EventMesh/issues [2]https://github.com/WeBankFinTech/EventMesh/issues/5 Willem Jiang Twitter: willemjiang Weibo: willem On Fri, Aug 14, 2020 at 7:42 PM Eason Chen
Fwd: [IMPORTANT] - Migration to ci-builds.a.o
Hi - This migration has been completed for the Incubator clutch analysis and site build. It’s crunch time now. Some podlings have managed to move their builds, but others have not. (1) Request a Folder for your project from Infra. We are no longer putting podling builds in the Incubator folder. (2) There is a script to move build ”projects”. https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees (3) Request missing plugins from Infra on builds@a.o mailing list. (4) Fix any GitHub credential issues. Ask for help. Start yesterday! Regards, Dave > Begin forwarded message: > > From: Gavin McDonald > Subject: [IMPORTANT] - Migration to ci-builds.a.o > Date: July 16, 2020 at 9:33:08 AM PDT > To: builds > Reply-To: bui...@apache.org > Reply-To: gmcdon...@apache.org > > Hi All, > > This NOTICE is for everyone on builds.apache.org. We are migrating to a new > Cloudbees based Client Master called https://ci-builds.apache.org. The > migrations of all jobs needs to be done before the switch off date of 15th > August 2020, so you have a maximum of 4 weeks. > > There is no tool or automated way of migrating your jobs, the > differences in the platforms, the plugins and the setup makes it impossible > to do in a safe way. So, you all need to start creating new jobs on > ci-infra.a.o and then , when you are happy, turn off your old builds on > builds.a.o. > > There are currently 4 agents over there ready to take jobs, plus a floating > agent which is shared amongst many masters (more to come). I will migrate > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > will keep an eye of load across both and adjust accordingly. > > If needed, create a ticket on INFRA jira for any issues that crop up, or > email here on builds@a.o. there may be one or two plugins we need to > install/tweak etc. > > We will be not using 'Views' at the top level, but rather we will take > advantage of 'Folders Plus' - each project will get its own Folder and have > authorisation access to create/edit jobs etc within that folder. I will > create these folders as you ask for them to start with. This setup allows > for credentials isolation amongst other benefits, including but not limited > to exclusive agents (Controlled Agents) for your own use , should you have > any project targeted donations of agents. > > As with other aspects of the ASF, projects can choose to just enable all > committers access to their folder, just ask. > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not > be setting up any forwarding rules or anything like that. > > So, please, get started *now *on this so you can be sure we are all > completed before the final cutoff date of 15th August 2020. > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > tickets. > > Hadoop and related projects have their own migration path to follow, same > cut off date, Cassandra, Beam, CouchDB have already migrated and are doing > very well in their new homes. > > Lets get going ... > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team
Re: svn commit: r1880840 - /incubator/public/trunk/content/projects/superset.xml
Hi - The change made here broke the Incubator clutch analysis and site build. These files are XML and sections are important. I’ve fixed this. > On Aug 13, 2020, at 3:44 PM, maximebeauche...@apache.org wrote: > > Author: maximebeauchemin > Date: Thu Aug 13 22:44:06 2020 > New Revision: 1880840 > > URL: http://svn.apache.org/viewvc?rev=1880840=rev > Log: > adding link to our wiki > > Modified: >incubator/public/trunk/content/projects/superset.xml > > Modified: incubator/public/trunk/content/projects/superset.xml > URL: > http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/superset.xml?rev=1880840=1880839=1880840=diff > == > --- incubator/public/trunk/content/projects/superset.xml [utf-8] (original) > +++ incubator/public/trunk/content/projects/superset.xml [utf-8] Thu Aug 13 > 22:44:06 2020 > @@ -6,397 +6,8 @@ > http://purl.org/DC/elements/1.0/; rel="schema.DC"/> > > > - > - > - Superset Project Incubation Status > - This page tracks the project status, incubator-wise. For more > general > - project status, look on the project website. > - > - > - Description > - Superset is an enterprise-ready web application for data > exploration, data visualization and dashboarding. > - > - > - News > - > -2017-05-02 Project enters incubation. > - > - > - > - Project info > - > -link to the main website > - > - > -link to the page(s) that tell how to participate (Website,Mailing > -lists,Bug tracking,Source code) > - > - > -link to the project status file (Committers,non-incubation action > -items,project resources, etc) > - > - If the project website and code repository are not yet setup, use > the > - following table: > - > - > - item > - type > - reference > - > - > - Website > - www > - > - href="http://superset.incubator.apache.org/;>http://superset.incubator.apache.org/ > - > - > - > - . > - wiki > - . > - > - > - Mailing list > - dev > - id="mail-dev">dev@superset.incubator.apache.org > - > - > - . > - commits > - id="mail-commits">commits@superset.incubator.apache.org > - > - > - Bug tracking > - . > - > -https://issues.apache.org/jira/browse/Superset;>Jira: > Superset > - > - > - > - Source code > - GIT > - > - href="https://github.com/apache/incubator-superset.git;>https://github.com/apache/incubator-superset.git > - > - > - > - Champion > - daijy > - Daniel Dai > - > - > - Mentors > - hashutosh > - Ashutosh Chauhan > - > - > - . > - lukehan > - Luke Han > - > - > - . > - jim > - Jim Jagielski > - > - > - . > - sameerp > - Sameer Paranjpye > - > - > - Committers > - Maxime Beauchemin > - maximebeauchemin > - > - > - . > - > - Alanna Scott > - > - > - . > - > - Bogdan Kyryliuk > - > - > - . > - > - Vera Liu > - > - > - . > - jfeng > - Jeff Feng > - > - > - . > - hashutosh > - Ashutosh Chauhan > - > - > - . > - nishant > - Nishant Bangarwa > - > - > - . > - bslim > - Slim Bouguerra > - > - > - . > - > - Priyank Shah > - > - > - . > - > - Harsha Chintalapani > - > - > - . > - daijy > - Daniel Dai > - > - > - > - > - Incubation status reports > - > - href='https://whimsy.apache.org/board/minutes/superset.html'>Apache Superset > Status Reports > - > - > - > - Incubation work items > - > -Project Setup > -This is the first phase on incubation, needed to start the > project at Apache. > - > - Item assignment is shown by the Apache id. > - Completed tasks are shown by the completion date > (-MM-dd). > - > - > - Identify the project to be incubated > - > - > - date > - item > - > -
Re: [DISCUSS] EventMesh Proposal
Willem Jiang 于2020年8月14日周五 下午9:38写道： > Hi, > > I just spent some time on the issues of EventMesh[1], it looks like > there are a bunch of people interested about this project, but > unfortunately the recent replied issue is about three weeks ago. > It's quite strange for me that the project maintainers are not keen to > answer the issues if they want to build the community from the > scratch. > Hi Willem Thanks for taking a look at this too. That is why I am concerned from day one I saw this proposal. Joining the ASF incubator is about learning how to build the community and make it better, rather than all things that should happen after the movement like this is a condition for the project to begin to run? Even issues opened for months, the proposal has been sent out for 10 days, and I had pointed out the concerns for 7 days. Still, no one cares about GitHub issues. Is that normal for a community? Why don't the initial PPMC members care about the project in these so many days? I love the ASF's Community Over Codes, so my all interests are focusing on the people who maintain the projects. My concerns are still there. Sheng Wu 吴晟 Twitter, wusheng1108 > > I also checked the commit logs, I can only find some small > documentation fixes which were done through the Github web interface. > I cannot find any new feature development commits after went through > the commits. > I'm not sure if WeBankFinTech guys do regular development on this repo. > > BTW, There is still an open issue asking if all the features are open > sourced[2]. > > [1]https://github.com/WeBankFinTech/EventMesh/issues > [2]https://github.com/WeBankFinTech/EventMesh/issues/5 > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Aug 14, 2020 at 7:42 PM Eason Chen wrote: > > > > Thanks Justin, and can not agree more. > > > > > > Thanks everyone for your attention to this project and your valuable > comments. > > > > > > If everyone has no problems, i will initiate the voting processs later. > > > > > > Thanks, > > Eason > > > > > > -- 原始邮件 -- > > 发件人: > "general" > < > jus...@classsoftware.com; > > 发送时间:2020年8月14日(星期五) 下午4:57 > > 收件人:"general" > > > 主题:Re: [DISCUSS] EventMesh Proposal > > > > > > > > Hi, > > > > The incubator prefers that a project comes with a community around it > but it’s not essential. Not having one may possibly make graduation harder, > as long as the project is aware of that I don’t see any issues. > > > > Thanks, > > 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: [VOTE] Release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0 (ROUND3)
Hello IPMC , We still need 2 binding votes on this release. Can anyone help vote? Thank you very much! GAO JUN 于2020年8月13日 周四12:07写道： > Hello IPMC and DolphinScheduler Community, > > > > This is a call for a vote to release Apache DolphinScheduler Maven Plugin > (Incubating) version 1.0.0. > > > > The Apache DolphinScheduler community has voted on and approved a proposal > to release Apache DolphinScheduler Maven Plugin (Incubating) 1.0.0 > > > > We now kindly request the Incubator IPMC members review and vote on this > incubator release. > > > > Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow > scheduling system, dedicated to solving the complex dependencies in data > processing, making the scheduling system out of the box for data processing. > > > > DolphinScheduler community vote and result threads: > > > https://lists.apache.org/thread.html/re4d26427e71440ab4dd2cb97d10c4f500e15ea5534836ff0fa54bd78%40%3Cdev.dolphinscheduler.apache.org%3E > > > > > https://lists.apache.org/thread.html/r82b2fe70fdf64842a9167e5798a79d00eef70ddcb99e4db0f0d66a09%40%3Cdev.dolphinscheduler.apache.org%3E > > > > The release candidates: > > > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/ > > > > Maven 2 staging repository: > > > https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1039/org/apache/dolphinscheduler/dolphinscheduler-maven-plugin/1.0.0/ > > > > Git tag for the release: > > > https://github.com/apache/incubator-dolphinscheduler-maven-plugin/releases/tag/1.0.0 > > > > Release Commit ID: > > > https://github.com/apache/incubator-dolphinscheduler-maven-plugin/commit/10280f9d52ad5cfaf1256fcf5a7955be23d464c5 > > > > Keys to verify the Release Candidate: > > https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS > > > > Look at here for how to verify this release candidate: > > > https://github.com/apache/incubator-dolphinscheduler-maven-plugin/blob/1.0.0/README.md > > > > The vote will be open for at least 72 hours or until a necessary number of > > votes are reached. > > Please vote accordingly: > > > > [ ] +1 approveg > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > Checklist for reference: > > > > [ ] Download links are valid. > > > > [ ] Checksums and PGP signatures are valid. > > > > [ ] Source code artifacts have correct names matching the current release. > > > > [ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo. > > > > [ ] All files have license headers if necessary. > > > > [ ] No compiled archives bundled in source archive. > > > > More detail checklist please refer: > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > The following votes are carried over from DolphinScheduler dev mailing > list: > > +1 Furkan KAMACI > > > > > > DolphinScheduler(Incubator) PPMC > > Jun Gao 高俊 > > > > gaojun2...@gmail.com > > -- > > > -- DolphinScheduler(Incubator) PPMC Jun Gao 高俊 gaojun2...@gmail.com
Re: [DISCUSS] EventMesh Proposal
Hi, I just spent some time on the issues of EventMesh[1], it looks like there are a bunch of people interested about this project, but unfortunately the recent replied issue is about three weeks ago. It's quite strange for me that the project maintainers are not keen to answer the issues if they want to build the community from the scratch. I also checked the commit logs, I can only find some small documentation fixes which were done through the Github web interface. I cannot find any new feature development commits after went through the commits. I'm not sure if WeBankFinTech guys do regular development on this repo. BTW, There is still an open issue asking if all the features are open sourced[2]. [1]https://github.com/WeBankFinTech/EventMesh/issues [2]https://github.com/WeBankFinTech/EventMesh/issues/5 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Aug 14, 2020 at 7:42 PM Eason Chen wrote: > > Thanks Justin, and can not agree more. > > > Thanks everyone for your attention to this project and your valuable comments. > > > If everyone has no problems, i will initiate the voting processs later. > > > Thanks, > Eason > > > -- 原始邮件 -- > 发件人: > "general" > > 发送时间:2020年8月14日(星期五) 下午4:57 > 收件人:"general" > 主题:Re: [DISCUSS] EventMesh Proposal > > > > Hi, > > The incubator prefers that a project comes with a community around it but > it’s not essential. Not having one may possibly make graduation harder, as > long as the project is aware of that I don’t see any issues. > > Thanks, > 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: [DISCUSS] EventMesh Proposal
I will leave that up to your mentors. I think my feeling is already very clear for you. Sheng Wu 吴晟 Twitter, wusheng1108 Eason Chen 于2020年8月14日周五 下午7:55写道： > Thanks for your continued attention. > As i mentened before in my first discuss "And I'd like to emphasize that > the community however small it might look so far",if there are > seemingly inaccurate descriptions in the proposal, I can modify it as > needed. > > > > > --原始邮件-- > 发件人: > "general" > < > wu.sheng.841...@gmail.com; > 发送时间:2020年8月14日(星期五) 下午4:46 > 收件人:"Incubator" > 主题:Re: [DISCUSS] EventMesh Proposal > > > > Eason Chen > Hi, > Maybe a bit misunderstood, what I am trying to explain is that even > if the > project is really in its infancy, it does not prevent the building > under > apache way. In fact, many apache projects are built from 0. And > mentors > also don't think this is a big problem. > > > I don't think this is a problem either. > That is why I keep saying, the only thing I want, is to adjust the proposal > to state the fact. Currently, the proposal looks like, you have an active > community already. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > > > Thanks, > Eason > > > --nbsp;原始邮件nbsp;-- > 发件人: > > "general" > > < > wu.sheng.841...@gmail.comgt;; > 发送时间:nbsp;2020年8月14日(星期五) 下午4:02 > 收件人:nbsp;"Incubator" > 主题:nbsp;Re: [DISCUSS] EventMesh Proposal > > > > Why are you arguing this with me? > > I am not saying anything about the future, or nothing about whether > this > project is good or not. > > The risk and challenges are only things that could happen based on the > current status, community-level only. > And it is higher than some projects had a larger or more active > community. > That is a factor, isn't it? > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Eason Chen > gt; amp;gt;1. Just open-sourced > gt; amp;gt;3. Community development would be a challenge > gt; > gt; > gt; As mentioned earlier, the project is still in its infancy. I > also > asked > gt; the mentors how to build the community. I believe that with > the help > of > gt; apache way and the mentors, we have reasons and confidence > to make > products > gt; more diversified and build a healthy internationalization > community. > gt; > gt; > gt; amp;gt;2. Have a risk of being an orphaned project > gt; > gt; > gt; > gt; Event is a huge ecosystem, and especially eventmesh will be > a very > gt; promising direction，currently such products are scarce, but > the > demand will > gt; be greater > gt; > gt; > gt; > gt; > gt; -- 原始邮件 -- > gt; 发件人: > > gt;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; > "general" > > gt;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; > < > gt; wu.sheng.841...@gmail.comamp;gt;; > gt; 发送时间:amp;nbsp;2020年8月14日(星期五) 下午3:01 > gt; 收件人:amp;nbsp;"Incubator" amp;gt;; > gt; > gt; 主题:amp;nbsp;Re: [DISCUSS] EventMesh Proposal > gt; > gt; > gt; > gt; Eason Chen 下午2:43写道： > gt; > gt; amp;gt; Our product has actually received a lot of > attention from > people. We > gt; have > gt; amp;gt; conducted communication with many people and > collected their > gt; opinions. We > gt; amp;gt; plan to abstract eventmesh more independently, > make product > gt; positioning > gt; amp;gt; clearer, and make it easier for everyone to > participate. We > will > gt; invest > gt; amp;gt; more time and energy to build the community. > gt; amp;gt; > gt; > gt; I think you misunderstand Ming's and my points, > gt; We are not saying you have to have a large community, for > now, we are > gt; asking you to make sure, your statement/proposal is matching > your > current > gt; status. > gt; > gt; Do you mean, the project community is more active than I > found? > gt; If so, I would like to ask for more materials(including open > discussion, > gt; news, blogs, issue, pull requests) to prove your points, EN > and CN > are both > gt; fine for me. > gt; > gt; I hope the status could be clear before any formal vote. > gt; > gt; Sheng Wu 吴晟 > gt; Twitter, wusheng1108 > gt; > gt; > gt; amp;gt; > gt; amp;gt; > gt; amp;gt; > gt; amp;gt; > gt; amp;gt; > > --amp;amp;nbsp;原始邮件amp;amp;nbsp;-- > gt; amp;gt; 发件人: > gt; > >
Re: Giving our PMs and contributors triage rights on GitHub
Few comments, needs of the Apache Airflow project. In short: big +1 on enabling the "triage role". On 2020/08/13 18:43:06, Julian Hyde wrote: > By PM, I presume that you mean either Product Manager or Program Manager. > I’ve worked at a few companies that practiced “commercial open source”, and > there is inherent tension in the relationship with the “business” people. I read that as Project Manager as well. I think when there are many issues in a project, it is often useful that the teams working on a project also have a Project Manager that helps the team to remove obstacles (this is, I think the main role of great Project Manager). This is the case, where several companies have whole teams dedicated to improve the OSS project. The developers still act as sole contributors on the OSS project, but they are paid by another organisation to do so and the Project Manager is there to make sure the teams work well together as well as individuals. We have some great example of that in our company where we have teams of contributors (also committers and PMCs) working on Apache Airflow and Apache Beam projects (among others) and there are PMs for those projects. What's more - those PMs are not there to provide "Business direction" but to make people working "well" together and there are some good example of people like that who learned how to do it in the open-source cases. Quite recently at the Airflow Summit, our PM Karolina - gave (together with our CTO) great talk about it and explained the challenges and benefits of having a PM in such team: https://www.youtube.com/watch?v=KIEMEYM2PEs=PLGudixcDaxY3RGLSlWoN_cEEXhIT1OPmj=37 . I can heartily recommend the talk to everyone who is interested in the subject! What's more - if you have great PMs who are really part of the team, they are super happy to contribute to the whole OSS project - and being able to help with the teamwork (for example by organixing issues and helping with tracking the progress) might be a huge help for both - the teams and the project. I think we are really blessed by having such people in our company, but I think there are more people like that. > The key questions are whether a PM can participate in the community (which > means being active on the dev list), make contributions of value to the > project (‘earn merit’), and can put aside their professional affiliation and > act solely in the interests of the project. This is precisely what we require > committers to do. Yes. It's possible and I think it's the same for different people. Actually this statement makes me quite a bit uncomfortable. It somehow implies developer's "superiority" in terms of being able to comply with the rules of Apache regarding professional affiliation. It hurts my way of thinking about people being individuals and I personally think that there is a "discriminating" thought hidden in this statement. Being developer myself I could also feel that way, but I think personal integrity is not really related to the role you have in any company or your job description or affiliation with the company. I know both "business" people and "developers" with both excellent integrity and very poor one. So I totally don't see why "business people" would be inferior in this role. Both business people and developers have different kinds of commercial relation, sometimes ownership sometimes pay structure that might make it easier or more difficult to separate the affiliation from the organisation they are in - but I think it's eventually all the matter of personal integrity, peer pressure and a number of other factors that determine the actions of that individual - regardless of the job role they have. I - for one - have a significant ownership in the company i work in (being co-founder) but my role is purely engineering one - but my ownership could also influence decisions I make. > So, by this logic, a PM would earn committership in a few short months. But I > guess you’re running into a chicken-and-egg problem: if the only > contributions a PM can make are triaging bugs, then how can they earn enough > merit to be made a contributor? One solution is for them to contribute in > other ways, for example writing documentation and testing. That's the very thing - chicken and egg - I think it is very hot and important topic discussed recently that we should have more "non-code" committers in Apache projects and how valuable they are. I think we should make it easy for them to contribute. In our case - more often than not - PMs input to the documentation can be very, very limited. Most of the documentation we have should really be written down by the developers. For testing - we do everything possible to automate it in our project, and again - there is a limited help PMs can provide here. But this is entirely different story for organizing work (in whatever way). It's entirely different for Open Source projects than
[VOTE] Accept EventMesh into Apache Incubator
Hi, After the discussion of EventMesh proposal (discussion thread is here[1]), I would like to call a VOTE to accept it into the Apache Incubator. Please cast your vote: [ ] +1, bring EventMesh into Incubator [ ] +0, I don't care either way [ ] -1, do not bring EventMesh into Incubator, because... The vote will open at least for 72 hours and only votes from the Incubator PMC are binding. The project's proposal is available at [2]. [1]https://lists.apache.org/thread.html/r12b7357f2a9458e6d6719558f36c0bbf7f786771d1f727848d5170b4%40%3Cgeneral.incubator.apache.org%3E [2]https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
?????? [DISCUSS] EventMesh Proposal
Thanks for your continued attention. As i mentened before in my first discuss "And I'd like to emphasize that the community however small it might look so far",if there are seemingly inaccurate descriptions in the proposal, I can modify it as needed. ---- ??: "general" https://incubator.apache.org/guides/names.html gt; amp;gt; amp;amp;gt; amp;amp;amp;gt; [2] https://www.uspto.gov/trademark gt
?????? [DISCUSS] EventMesh Proposal
Thanks Justin, and can not agree more. Thanks everyone for your attention to this project and your valuable comments. If everyone has no problems, i will initiate the voting processs later. Thanks, Eason -- -- ??: "general"
Re: [DISCUSS] EventMesh Proposal
Hi, The incubator prefers that a project comes with a community around it but it’s not essential. Not having one may possibly make graduation harder, as long as the project is aware of that I don’t see any issues. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] EventMesh Proposal
Eason Chen 于2020年8月14日周五 下午4:25写道： > Hi, > Maybe a bit misunderstood, what I am trying to explain is that even if the > project is really in its infancy, it does not prevent the building under > apache way. In fact, many apache projects are built from 0. And mentors > also don't think this is a big problem. > I don't think this is a problem either. That is why I keep saying, the only thing I want, is to adjust the proposal to state the fact. Currently, the proposal looks like, you have an active community already. Sheng Wu 吴晟 Twitter, wusheng1108 > > > Thanks, > Eason > > > --原始邮件-- > 发件人: > "general" > < > wu.sheng.841...@gmail.com; > 发送时间:2020年8月14日(星期五) 下午4:02 > 收件人:"Incubator" > 主题:Re: [DISCUSS] EventMesh Proposal > > > > Why are you arguing this with me? > > I am not saying anything about the future, or nothing about whether this > project is good or not. > > The risk and challenges are only things that could happen based on the > current status, community-level only. > And it is higher than some projects had a larger or more active community. > That is a factor, isn't it? > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Eason Chen > gt;1. Just open-sourced > gt;3. Community development would be a challenge > > > As mentioned earlier, the project is still in its infancy. I also > asked > the mentors how to build the community. I believe that with the help > of > apache way and the mentors, we have reasons and confidence to make > products > more diversified and build a healthy internationalization community. > > > gt;2. Have a risk of being an orphaned project > > > > Event is a huge ecosystem, and especially eventmesh will be a very > promising direction，currently such products are scarce, but the > demand will > be greater > > > > > -- 原始邮件 -- > 发件人: > > "general" > > < > wu.sheng.841...@gmail.comgt;; > 发送时间:nbsp;2020年8月14日(星期五) 下午3:01 > 收件人:nbsp;"Incubator" > 主题:nbsp;Re: [DISCUSS] EventMesh Proposal > > > > Eason Chen > gt; Our product has actually received a lot of attention from > people. We > have > gt; conducted communication with many people and collected their > opinions. We > gt; plan to abstract eventmesh more independently, make product > positioning > gt; clearer, and make it easier for everyone to participate. We > will > invest > gt; more time and energy to build the community. > gt; > > I think you misunderstand Ming's and my points, > We are not saying you have to have a large community, for now, we are > asking you to make sure, your statement/proposal is matching your > current > status. > > Do you mean, the project community is more active than I found? > If so, I would like to ask for more materials(including open > discussion, > news, blogs, issue, pull requests) to prove your points, EN and CN > are both > fine for me. > > I hope the status could be clear before any formal vote. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > gt; > gt; > gt; > gt; > gt; > --amp;nbsp;原始邮件amp;nbsp;-- > gt; 发件人: > > gt;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; > nbsp; "general" > > gt;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; > nbsp; < > gt; wenm...@apache.orgamp;gt;; > gt; 发送时间:amp;nbsp;2020年8月14日(星期五) 中午11:35 > gt; 收件人:amp;nbsp;"general" amp;gt;; > gt; 抄送:amp;nbsp;"legal-discuss" amp;gt;; > gt; 主题:amp;nbsp;Re: [DISCUSS] EventMesh Proposal > gt; > gt; > gt; > gt; amp;gt; Thanks for the honesty, I prefer you should > adjust the > proposal to > gt; match > gt; amp;gt; the reality. Such as > gt; amp;gt; 1. Just open-sourced > gt; amp;gt; 2. Have a risk of being an orphaned project > gt; amp;gt; 3. Community development would be a challenge > gt; > gt; As mentioned in wusheng’s previous email, the challenge > should be > stated in > gt; the proposal. > gt; > gt; Thanks, > gt; Ming Wen, Apache APISIX amp;amp; Apache SkyWalking > gt; Twitter: _WenMing > gt; > gt; > gt; Eason Chen 上午10:52写道： > gt; > gt; amp;gt; Thanks for your help and answers @Duane, i will > initiate the > voting > gt; amp;gt; processs later if you have no other questions. > gt; amp;gt; > gt; amp;gt; > gt; amp;gt; > gt; amp;gt; > gt; amp;gt; > > --amp;amp;nbsp;原始邮件amp;amp;nbsp;-- > gt; amp;gt; 发件人: > gt;
?????? [DISCUSS] EventMesh Proposal
Hi, Maybe a bit misunderstood, what I am trying to explain is that even if the project is really in its infancy, it does not prevent the building under apache way. In fact, many apache projects are built from 0. And mentors also don't think this is a big problem. Thanks, Eason ---- ??: "general" https://incubator.apache.org/guides/names.html gt; amp;gt; amp;amp;gt; [2] https://www.uspto.gov/trademark gt; amp;gt; amp;amp;gt; gt; amp;gt; amp;amp;gt; Thanks gt; amp;gt; amp;amp;gt; Henry gt; amp;gt; amp;amp;gt; gt; amp;gt; amp;amp;gt; Michael Andr?? Pearce < michael.andre.pea...@me.com gt; .invalidamp;amp;gt; gt; amp;gt; ??2020??8??6?? gt; amp;gt; amp;amp;gt; 3:33?? gt; amp;gt; amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; Hi gt; amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; Im PMC member from ActiveMQ project. gt; amp;gt; amp;amp;gt;amp;amp;gt; I like the idea, nice. +1 on it as a project idea. gt; amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; I am though a little -1 on the name of the project, gt; I would gt; amp;gt; recommend gt; amp;gt; amp;amp;gt;amp;amp;gt; that an alternative name for the project is found as gt; there maybe gt; amp;gt; a conflict gt; amp;gt; amp;amp;gt;amp;amp;gt; in rights ability to copyright and trademark to it. gt; amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; I??m aware there is a commercial vendor messaging gt; company called gt; amp;gt; Solace, gt; amp;gt; amp;amp;gt;amp;amp;gt; where they use and market their product with heavy gt; use of the gt; amp;gt; name Event gt; amp;gt; amp;amp;gt;amp;amp;gt; Mesh, you can see this just googling event mesh, gt; brings back many gt; amp;gt; hits to gt; amp;gt; amp;amp;gt;amp;amp;gt; their products, marketing material and other gt; records, so they may gt; amp;gt; hold a gt; amp;gt; amp;amp;gt;amp;amp;gt; heavy claim to this name. gt; amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; Best gt; amp;gt; amp;amp;gt;amp;amp;gt; Michael gt; amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; On 4 Aug 2020, at 18:33, Kevin Ratnasekera < gt; amp;gt; djkevincr1...@gmail.comamp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; wrote: gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; Hi Easen, gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; +1, Having worked in a similar domain so gt; far, I have to say gt; amp;gt; this is an gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; interesting project. If you are seeking new gt; mentors, please gt; amp;gt; consider gt; amp;gt; amp;amp;gt;amp;amp;gt; adding gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; me as a mentor to the project. gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; Regards gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; Kevin gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; On Tue, Aug 4, 2020 at 3:34 PM Eason Chen < gt; amp;gt; daerduoc...@qq.comamp;amp;gt; wrote: gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; Good time of the time to all! gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; I'd like to bring this new gt; interesting project for the gt; amp;gt; discussion, gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; comments and feedback with the aim gt; of starting a formal gt; amp;gt; [VOTE] of its gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; acceptance into Incubator. gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; People behind this project aren't gt; new to Apache: some of gt; amp;gt; them were gt; amp;gt; amp;amp;gt;amp;amp;gt; behind gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; the Apache RocketMQ, which I gt; consider a huge gt; amp;gt; success(especially in gt; amp;gt; amp;amp;gt;amp;amp;gt; China)as gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; the community is literally thriving gt; almost 3 years after gt; amp;gt; the gt; amp;gt; amp;amp;gt;amp;amp;gt; graduation. gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; gt; amp;gt; amp;amp;gt;amp;amp;gt; amp;amp;gt;amp;amp;gt; I have been involved a
Re: [DISCUSS] EventMesh Proposal
Why are you arguing this with me? I am not saying anything about the future, or nothing about whether this project is good or not. The risk and challenges are only things that could happen based on the current status, community-level only. And it is higher than some projects had a larger or more active community. That is a factor, isn't it? Sheng Wu 吴晟 Twitter, wusheng1108 Eason Chen 于2020年8月14日周五 下午3:51写道： > 1. Just open-sourced > 3. Community development would be a challenge > > > As mentioned earlier, the project is still in its infancy. I also asked > the mentors how to build the community. I believe that with the help of > apache way and the mentors, we have reasons and confidence to make products > more diversified and build a healthy internationalization community. > > > 2. Have a risk of being an orphaned project > > > > Event is a huge ecosystem, and especially eventmesh will be a very > promising direction，currently such products are scarce, but the demand will > be greater > > > > > -- 原始邮件 -- > 发件人: > "general" > < > wu.sheng.841...@gmail.com; > 发送时间:2020年8月14日(星期五) 下午3:01 > 收件人:"Incubator" > 主题:Re: [DISCUSS] EventMesh Proposal > > > > Eason Chen > Our product has actually received a lot of attention from people. We > have > conducted communication with many people and collected their > opinions. We > plan to abstract eventmesh more independently, make product > positioning > clearer, and make it easier for everyone to participate. We will > invest > more time and energy to build the community. > > > I think you misunderstand Ming's and my points, > We are not saying you have to have a large community, for now, we are > asking you to make sure, your statement/proposal is matching your current > status. > > Do you mean, the project community is more active than I found? > If so, I would like to ask for more materials(including open discussion, > news, blogs, issue, pull requests) to prove your points, EN and CN are both > fine for me. > > I hope the status could be clear before any formal vote. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > > > > > --nbsp;原始邮件nbsp;-- > 发件人: > > "general" > > < > wenm...@apache.orggt;; > 发送时间:nbsp;2020年8月14日(星期五) 中午11:35 > 收件人:nbsp;"general" 抄送:nbsp;"legal-discuss" 主题:nbsp;Re: [DISCUSS] EventMesh Proposal > > > > gt; Thanks for the honesty, I prefer you should adjust the > proposal to > match > gt; the reality. Such as > gt; 1. Just open-sourced > gt; 2. Have a risk of being an orphaned project > gt; 3. Community development would be a challenge > > As mentioned in wusheng’s previous email, the challenge should be > stated in > the proposal. > > Thanks, > Ming Wen, Apache APISIX amp; Apache SkyWalking > Twitter: _WenMing > > > Eason Chen > gt; Thanks for your help and answers @Duane, i will initiate the > voting > gt; processs later if you have no other questions. > gt; > gt; > gt; > gt; > gt; > --amp;nbsp;原始邮件amp;nbsp;-- > gt; 发件人: > > gt;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; > "general" > > gt;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; > < > gt; duane.pa...@gmail.comamp;gt;; > gt; 发送时间:amp;nbsp;2020年8月11日(星期二) 凌晨0:16 > gt; 收件人:amp;nbsp;"legal-discuss" amp;gt;; > gt; 抄送:amp;nbsp;"general" amp;gt;; > gt; 主题:amp;nbsp;Re: [DISCUSS] EventMesh Proposal > gt; > gt; > gt; > gt; I work for Solace and have consulted internally to confirm > that we do > not > gt; have any copyright or trademark on the term “Event Mesh”. > It’s true > it is > gt; something our products are closely aligned with, but it is an > industry term > gt; that has been adopted by Gartner and is gaining traction in > the > industry. > gt; Solace does not oppose the term being used in other > applicable > products or > gt; projects. > gt; > gt; +1 (non-binding) on the idea. > gt; > gt; Cheers, > gt; Duane > gt; > gt; On Thu, Aug 6, 2020 at 11:51 AM heng du < > duhengfore...@apache.org > amp;gt; > gt; wrote: > gt; > gt; amp;gt; Hi @Michael > gt; amp;gt; > gt; amp;gt; Thanks for your advice. As far as I know, > Solace doesn't > have a > gt; product > gt; amp;gt; called Eventmesh, They're just using that name > to promote > their PubSub > gt; amp;gt; platform. > gt; amp;gt; > gt; amp;gt; But in
?????? [DISCUSS] EventMesh Proposal
1. Just open-sourced 3. Community development would be a challenge As mentioned earlier, the project is still in its infancy. I also asked the mentors how to build the community. I believe that with the help of apache way and the mentors, we have reasons and confidence to make products more diversified and build a healthy internationalization community. 2. Have a risk of being an orphaned project Event is a huge ecosystem, and especially eventmesh will be a very promising direction??currently such products are scarce, but the demand will be greater -- -- ??: "general" https://incubator.apache.org/guides/names.html gt; amp;gt; [2] https://www.uspto.gov/trademark gt; amp;gt; gt; amp;gt; Thanks gt; amp;gt; Henry gt; amp;gt; gt; amp;gt; Michael Andr?? Pearce https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal gt
Re: [DISCUSS] EventMesh Proposal
Thanks for @Duane's reply. Duane Pauls 于2020年8月11日周二 上午12:25写道： > I work for Solace and have consulted internally to confirm that we do not > have any copyright or trademark on the term “Event Mesh”. It’s true it is > something our products are closely aligned with, but it is an industry term > that has been adopted by Gartner and is gaining traction in the industry. > Solace does not oppose the term being used in other applicable products or > projects. > > +1 (non-binding) on the idea. > > Cheers, > Duane > > On Thu, Aug 6, 2020 at 11:51 AM heng du wrote: > > > Hi @Michael > > > > Thanks for your advice. As far as I know, Solace doesn't have a product > > called Eventmesh, They're just using that name to promote their PubSub > > platform. > > > > But in order not to cause trouble in the future, I also ask guys of > Apache > > Brand to help check whether this name is appropriate. For us, we've been > > using the name EventMesh for a long time, and we want to keep it so that > > users can get better product positioning from the name. > > > > And base on this document[1], we searched in the U.S. Patent Office[2] > and > > found nothing inappropriate. > > > > [1] https://incubator.apache.org/guides/names.html > > [2] https://www.uspto.gov/trademark > > > > Thanks > > Henry > > > > Michael André Pearce 于2020年8月6日周四 > > 下午3:33写道： > > > >> Hi > >> > >> Im PMC member from ActiveMQ project. > >> I like the idea, nice. +1 on it as a project idea. > >> > >> I am though a little -1 on the name of the project, I would recommend > >> that an alternative name for the project is found as there maybe a > conflict > >> in rights ability to copyright and trademark to it. > >> > >> I’m aware there is a commercial vendor messaging company called Solace, > >> where they use and market their product with heavy use of the name Event > >> Mesh, you can see this just googling event mesh, brings back many hits > to > >> their products, marketing material and other records, so they may hold a > >> heavy claim to this name. > >> > >> Best > >> Michael > >> > >> > On 4 Aug 2020, at 18:33, Kevin Ratnasekera > >> wrote: > >> > > >> > Hi Easen, > >> > > >> > +1, Having worked in a similar domain so far, I have to say this is an > >> > interesting project. If you are seeking new mentors, please consider > >> adding > >> > me as a mentor to the project. > >> > > >> > Regards > >> > Kevin > >> > > >> > On Tue, Aug 4, 2020 at 3:34 PM Eason Chen wrote: > >> > > >> >> Good time of the time to all! > >> >> > >> >> > >> >> I'd like to bring this new interesting project for the discussion, > >> >> comments and feedback with the aim of starting a formal [VOTE] of its > >> >> acceptance into Incubator. > >> >> > >> >> > >> >> People behind this project aren't new to Apache: some of them were > >> behind > >> >> the Apache RocketMQ, which I consider a huge success(especially in > >> China)as > >> >> the community is literally thriving almost 3 years after the > >> graduation. > >> >> > >> >> > >> >> I have been involved a little bit with this project when it just > >> started > >> >> in WeBank a few years ago. And I'd like to emphasize that the > community > >> >> however small it might look so far, has been aligned with Apache ways > >> of > >> >> doing things. Heng Du (from RocketMQ PMC) is very instrumental in > >> >> tirelessly helping this group to learn what it means to be a truly > open > >> >> source project. > >> >> > >> >> > >> >> The code is already under ALv2 and is publicly available. As you will > >> see > >> >> it has a lot of dependency connections with the rest of Apache > >> ecosystem > >> >> and IMO will fit very well here and continue to grow the community. > >> >> > >> >> > >> >> The project's proposal is available at [1]. > >> >> > >> >> > >> >> Thank you very much for the feedback you're willing to provide! > >> >> > >> >> > >> >> With best regards, > >> >> > >> >> Eason Chen > >> >> > >> >> > >> >> > >> >> [1] > >> >> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal > >> > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> >
Re: [DISCUSS] EventMesh Proposal
Eason Chen 于2020年8月14日周五 下午2:43写道： > Our product has actually received a lot of attention from people. We have > conducted communication with many people and collected their opinions. We > plan to abstract eventmesh more independently, make product positioning > clearer, and make it easier for everyone to participate. We will invest > more time and energy to build the community. > I think you misunderstand Ming's and my points, We are not saying you have to have a large community, for now, we are asking you to make sure, your statement/proposal is matching your current status. Do you mean, the project community is more active than I found? If so, I would like to ask for more materials(including open discussion, news, blogs, issue, pull requests) to prove your points, EN and CN are both fine for me. I hope the status could be clear before any formal vote. Sheng Wu 吴晟 Twitter, wusheng1108 > > > > > --原始邮件-- > 发件人: > "general" > < > wenm...@apache.org; > 发送时间:2020年8月14日(星期五) 中午11:35 > 收件人:"general" 抄送:"legal-discuss" 主题:Re: [DISCUSS] EventMesh Proposal > > > > Thanks for the honesty, I prefer you should adjust the proposal to > match > the reality. Such as > 1. Just open-sourced > 2. Have a risk of being an orphaned project > 3. Community development would be a challenge > > As mentioned in wusheng’s previous email, the challenge should be stated in > the proposal. > > Thanks, > Ming Wen, Apache APISIX Apache SkyWalking > Twitter: _WenMing > > > Eason Chen > Thanks for your help and answers @Duane, i will initiate the voting > processs later if you have no other questions. > > > > > --nbsp;原始邮件nbsp;-- > 发件人: > > "general" > > < > duane.pa...@gmail.comgt;; > 发送时间:nbsp;2020年8月11日(星期二) 凌晨0:16 > 收件人:nbsp;"legal-discuss" 抄送:nbsp;"general" 主题:nbsp;Re: [DISCUSS] EventMesh Proposal > > > > I work for Solace and have consulted internally to confirm that we do > not > have any copyright or trademark on the term “Event Mesh”. It’s true > it is > something our products are closely aligned with, but it is an > industry term > that has been adopted by Gartner and is gaining traction in the > industry. > Solace does not oppose the term being used in other applicable > products or > projects. > > +1 (non-binding) on the idea. > > Cheers, > Duane > > On Thu, Aug 6, 2020 at 11:51 AM heng du gt; > wrote: > > gt; Hi @Michael > gt; > gt; Thanks for your advice. As far as I know, Solace doesn't > have a > product > gt; called Eventmesh, They're just using that name to promote > their PubSub > gt; platform. > gt; > gt; But in order not to cause trouble in the future, I also ask > guys of > Apache > gt; Brand to help check whether this name is appropriate. For > us, we've > been > gt; using the name EventMesh for a long time, and we want to > keep it so > that > gt; users can get better product positioning from the name. > gt; > gt; And base on this document[1], we searched in the U.S. Patent > Office[2] and > gt; found nothing inappropriate. > gt; > gt; [1] https://incubator.apache.org/guides/names.html > gt; [2] https://www.uspto.gov/trademark > gt; > gt; Thanks > gt; Henry > gt; > gt; Michael André Pearce .invalidgt; > 于2020年8月6日周四 > gt; 下午3:33写道： > gt; > gt;gt; Hi > gt;gt; > gt;gt; Im PMC member from ActiveMQ project. > gt;gt; I like the idea, nice. +1 on it as a project idea. > gt;gt; > gt;gt; I am though a little -1 on the name of the project, > I would > recommend > gt;gt; that an alternative name for the project is found as > there maybe > a conflict > gt;gt; in rights ability to copyright and trademark to it. > gt;gt; > gt;gt; I’m aware there is a commercial vendor messaging > company called > Solace, > gt;gt; where they use and market their product with heavy > use of the > name Event > gt;gt; Mesh, you can see this just googling event mesh, > brings back many > hits to > gt;gt; their products, marketing material and other > records, so they may > hold a > gt;gt; heavy claim to this name. > gt;gt; > gt;gt; Best > gt;gt; Michael > gt;gt; > gt;gt; gt; On 4 Aug 2020, at 18:33, Kevin Ratnasekera < > djkevincr1...@gmail.comgt; > gt;gt; wrote: > gt;gt; gt; > gt;gt; gt; Hi Easen, > gt;gt; gt; > gt;gt; gt; +1, Having worked in a similar domain so > far, I have to say > this is an > gt;gt; gt; interesting project. If you are seeking new > mentors, please > consider > gt;gt; adding > gt;gt; gt; me as a mentor to the project. > gt;gt; gt; > gt;gt; gt; Regards > gt;gt; gt; Kevin > gt;gt; gt; > gt;gt; gt; On Tue, Aug 4, 2020 at 3:34 PM Eason Chen < > daerduoc...@qq.comgt; wrote: > gt;gt; gt; > gt;gt; gt;gt; Good time of the time to all! > gt;gt; gt;gt; > gt;gt; gt;gt; > gt;gt; gt;gt; I'd like to bring this new > interesting project
?????? [DISCUSS] EventMesh Proposal
Our product has actually received a lot of attention from people. We have conducted communication with many people and collected their opinions. We plan to abstract eventmesh more independently, make product positioning clearer, and make it easier for everyone to participate. We will invest more time and energy to build the community. ---- ??: "general" https://incubator.apache.org/guides/names.html gt; [2] https://www.uspto.gov/trademark gt; gt; Thanks gt; Henry gt; gt; Michael Andr?? Pearce https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal gt;gt
