Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name
sebb 于2024年5月8日周三 16:12写道： > > Remember that the purpose of the incubator prefix is to clearly signal > that the code is under Incubation. > > It is essential that this change does not result in losing this indication. > > AFAICT, for most podlings, dropping the incubator prefix will require > additional work to ensure that the Incubation status is clear to > users, > and will require additional work by the IPMC to ensure that podlings > adequately display the Incubation status for each repository. Can't agree more on this. In this vote proposal, we implicitly add many more checks for IPMC, and lead more potential arguments about whether the incubating status indicator is clear enough. We are making IPMC pay the price in the future by removing a simple GitHub supported operation. On second thought, I am changing my vote to -1 binding. > > > On Wed, 8 May 2024 at 08:30, alin.jerpe...@sony.com > wrote: > > > > +1 (non binding) > > > > from my experience will make the documentation and releases easy to migrate > > after graduation > > > > Best regards > > Alin > > > > Från: hulk > > Skickat: den 8 maj 2024 09:06 > > Till: general@incubator.apache.org > > Ämne: Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name > > > > -0 (binding) On Wed, 8 May 2024 at 13: 58, Richard Zowalla > zowalla. com> wrote: > -0 (binding) > > (I like the prefix) > > Am 8. Mai > > 2024 07: 41: 16 MESZ schrieb Sheng Wu : > >-0 > > ZjQcmQRYFpfptBannerStart > > Caution : This email originated from outside of Sony. > > Do not click links or open any attachments unless you recognize the sender > > and know the content is safe. Please report phishing if unsure. > > > > ZjQcmQRYFpfptBannerEnd > > > > -0 (binding) > > > > On Wed, 8 May 2024 at 13:58, Richard Zowalla wrote: > > > > > -0 (binding) > > > > > > (I like the prefix) > > > > > > Am 8. Mai 2024 07:41:16 MESZ schrieb Sheng Wu : > > > >-0 binding > > > > > > > >Sheng Wu 吴晟 > > > >Twitter, wusheng1108 > > > > > > > >Dave Fisher 于2024年5月8日周三 12:16写道： > > > >> > > > >> +0 (binding) wave > > > >> > > > >> > On May 7, 2024, at 5:34 PM, Francis Chuang > > > wrote: > > > >> > > > > >> > +1 (binding) > > > >> > > > > >> > I think this is a pragmatic and well-thought out approach. > > > >> > > > > >> > Francis > > > >> > > > > >> > On 8/05/2024 10:31 am, tison wrote: > > > >> >> Hi, > > > >> >> Following the discussion thread [1], I'd start a vote on the > > > following > > > >> >> proposals: > > > >> >> 1. Establish a consensus to allow and finally converge podling's > > > GitHub repo to > > > >> >> have a name without the incubator- prefix. > > > >> >> 2. Allow existing ongoing podlings to ask the INFRA to drop their > > > >> >> incubator- prefix by now, not MUST during the graduation. > > > >> >> 3. Update the docs on incubator.apache.org everywhere if the > > > description > > > >> >> can conflict with this consensus. > > > >> >> 4. Update the docs on incubator.apache.org to guide how to describe > > > >> >> podling's incubating status on the GitHub repo (namely, including > > > >> >> "incubating" in the repo description and README, point to the > > > DISCLAIMER > > > >> >> content). > > > >> >> [1] https://lists.apache.org/thread/kxvdkrf8g8yr6hww1n08r21xdy67y4ok > > > >> >> +1 allow podling's GitHub repo to have a name without the incubator- > > > >> >> prefix, and other items above > > > >> >> +0 do not care strongly > > > >> >> -1 disagree the proposals above, because ... > > > >> >> Please vote with your ASF ID followed by (binding) if you are a > > > member of > > > >> >> the Incubator PMC or (not binding) if not. > > > >> >> Vote will be open for at least 72 hours. > > > >> >> Best, > > > >> >> tison. > > > >> > > > > >> > - > > > >> > 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 > > > > > > > > > > > > > -- > > Best Regards, > > - *Hulk Lin* > > > > - > 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] Drop the incubator- prefix for podling's GitHub repo name
-0 binding Sheng Wu 吴晟 Twitter, wusheng1108 Dave Fisher 于2024年5月8日周三 12:16写道： > > +0 (binding) wave > > > On May 7, 2024, at 5:34 PM, Francis Chuang wrote: > > > > +1 (binding) > > > > I think this is a pragmatic and well-thought out approach. > > > > Francis > > > > On 8/05/2024 10:31 am, tison wrote: > >> Hi, > >> Following the discussion thread [1], I'd start a vote on the following > >> proposals: > >> 1. Establish a consensus to allow and finally converge podling's GitHub > >> repo to > >> have a name without the incubator- prefix. > >> 2. Allow existing ongoing podlings to ask the INFRA to drop their > >> incubator- prefix by now, not MUST during the graduation. > >> 3. Update the docs on incubator.apache.org everywhere if the description > >> can conflict with this consensus. > >> 4. Update the docs on incubator.apache.org to guide how to describe > >> podling's incubating status on the GitHub repo (namely, including > >> "incubating" in the repo description and README, point to the DISCLAIMER > >> content). > >> [1] https://lists.apache.org/thread/kxvdkrf8g8yr6hww1n08r21xdy67y4ok > >> +1 allow podling's GitHub repo to have a name without the incubator- > >> prefix, and other items above > >> +0 do not care strongly > >> -1 disagree the proposals above, because ... > >> Please vote with your ASF ID followed by (binding) if you are a member of > >> the Incubator PMC or (not binding) if not. > >> Vote will be open for at least 72 hours. > >> Best, > >> tison. > > > > - > > 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: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
Repeated my opinion again 1. Incubating should be required for words in README and other places mentioned, such as blogs, videos, website, github repository 2. incubator- prefix is required. 3. DISCLAIMER is required. All of these make sure the incubating status is clear. All these have existed for years and are easy to practice. Basically, nothing needs to be changed about this. Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2024年4月23日周二 09:24写道： > > Hi, > > Recently, the new added podlings, namely Amoro and Hertzbeat, have their > GitHub repo in the names: > > * https://github.com/apache/amoro > * https://github.com/apache/hertzbeat > > ... which is different to the other 20+ podlings and 200+ repos [1] > existing (this number counts retired ones and those for the Incubator PMC > itself, but it's approximate). > > [1] > https://github.com/orgs/apache/repositories?language==incubator-==all > > My opinion is to agree that generally: > > 1. The incubator prefix comes from the SVN days where all podlings were under > the incubator SVN tree. > 2. Dropping the incubator- prefix for podling's GitHub repo can reduce some > graduation tasks (although it's somewhat a milestone and ceremony for the > podling, and INFRA does not find it a large job, as well as it won't break > downstream almost due to redirections). > 3. It's still significant to make it clear that a podling is in the > incubating status and thus a DISCLAIMER to protect the ASF branding. > > With these premises, I started this thread with the following proposals and > questions. > > 1. Establish a consensus to allow podling's GitHub repo to have a name > without incubator- prefix. > 2. Allow other podlings to ask the INFRA to drop their incubator- prefix by > now, not MUST during the graduation. > 3. Update the docs on incubator.apache.org everywhere if the description > can conflict with this consensus. > 4. However, find a way to clarify that a repo belongs to a podling. > > For 4, I'd propose to add the "incubating" words to each repo's README. > This can be regarded as treating those READMEs a homepage for the repo and, > > 1. Name the project as "Apache Foo (Incubating)" in its first and most > prominent uses, hopefully and H1 heading. > 2. Add a footer including the Incubator logo and DISCLAIMER, like the > current footer of Apache Answer (Incubating) [3] > > [3] https://answer.apache.org/ > > This method, however, can be a new chore for podlings that have many > satellite repos that may previously claim their incubating status by naming > the repos incubator-foo-satellite. But it's just another template to > follow, so it won't be a big deal. > > Looking forward to your thoughts on this proposal and any suggestions to > improve the implementation part. > > Best, > tison. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Questions about a new project entering Apache Incubator
With no further update, the consensus is clear from most that. The podlings should have `incubator-` prefix as most other projects followed. Armoro and Hertzbeat PPMC team, please fix this. Sheng Wu 吴晟 Twitter, wusheng1108 Chao Gong 于2024年4月17日周三 20:03写道： > > Hi rat O, > > Sorry for slowly response, We will clean the non-english language in the > codes later. > > Best Wishes. > Tom > > rat O 于2024年4月17日周三 17:48写道： > > > > > > For projects in incubation, is it no longer necessary for the project > > name to have the "incubator-" prefix as it used to be? > > > > Thanks to the Apache members for responding. It make me know that this > > issue is being looked into. > > > > > I wonder if the situation of having a significant amount of non-English > > languages in the codes, like these > > > > > https://github.com/apache/hertzbeat/blob/master/warehouse/src/main/java/org/apache/hertzbeat/warehouse/config/WarehouseProperties.java > > , > > > > > https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/entity/manager/NoticeRule.java > > , > > > > > https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/config/AviatorConfiguration.java > > > ... > > > , will all of them also be addressed in the future? > > > > I would also like to receive a response from Apache regarding this issue > > of a significant amount of non-English language in codes. > > > > > > From: tison > > Sent: Wednesday, April 17, 2024 5:16 PM > > To: general@incubator.apache.org > > Subject: Re: Questions about a new project entering Apache Incubator > > > > And [1] is actually update the community docs without INFRA changes. > > Previously (and now?), foo.incubator.apache.org has the same content with > > foo.apache.org unless you explicitly ask INFRA to change. > > > > Like even > > https://flink.incubator.apache.org/. > > > > I guess the main "pain point" is whimsy Web check checks " > > foo.incubator.apache.org" in config in some file on SVN before, and thus > > cause the Web check having a red mark. > > > > Best, > > tison. > > > > > > tison 于2024年4月17日 周三17:02写道： > > > > > I vote in [1] since it's how we practice for quite a while and it's a > > > clear consensus by the vote. > > > > > > All the repo of podlings have incubator- prefix, I don't see a motivation > > > to change. > > > > > > In [2] it says: > > > > > > > make less work for Infra > > > > > > I wonder if INFRA complained for this process. And what is the associated > > > JIRA ticket in INFRA to do the rename. I'd like to take INFRA's opinion > > > into consideration. > > > > > > In my previous experience, keep the name "foo", let INFRA move the repo, > > > rename it to "incubator-foo", and drop the prefix on graduation. In this > > > way, the link "apache/foo" will always work with GH redirections. > > > > > > To John: > > > > > > > , it can be confusing that they do. > > > > > > What is the certain redirection causing your confusion? > > > > > > Best, > > > tison. > > > > > > [1] > > > https://lists.apache.org/thread/n18gkb23bp005gb176jnwo2nrxty3z84 > > > [2] > > > https://github.com/apache/amoro/issues/2700 > > > > > > > > > Sheng Wu 于2024年4月17日 周三12:09写道： > > > > > >> This is not to get the conclusion, and it is not clear, and many other > > >> project repositories are with this prefix. > > >> > > >> > > >> > > https://incubator.apache.org/guides/transferring.html#first_steps_outside_the_incubator > > >> (tison > > >> found) > > >> > > >> Graduation doc is there indicating incaubtor- prefix is expected. This > > is > > >> just a 10s operation on GitHub admin page, not a heavy work. Graduation > > is > > >> not happening every day, even not every month. Developer don't have to > > >> change remote git, as that redirect forward is supported too. > > >> > > >> More importantly, I don't agree this is clear without prefix. > > >> > > >> This us serious change, if you inist this is clear, start a vote. A lot > > of > > >> ppl in this con
Re: Questions about a new project entering Apache Incubator
This is not to get the conclusion, and it is not clear, and many other project repositories are with this prefix. https://incubator.apache.org/guides/transferring.html#first_steps_outside_the_incubator (tison found) Graduation doc is there indicating incaubtor- prefix is expected. This is just a 10s operation on GitHub admin page, not a heavy work. Graduation is not happening every day, even not every month. Developer don't have to change remote git, as that redirect forward is supported too. More importantly, I don't agree this is clear without prefix. This us serious change, if you inist this is clear, start a vote. A lot of ppl in this context don't agree too. Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 Justin Mclean 于2024年4月17日 周三11:59写道： > Hi, > > Both of these projects are new and just getting set up. I'd give them a > little time to do that. Infra in recent years have asked to minimise work > for them on graduation. We recently dropped the requirement for having > incubating in podling domain names so I don't see it's needed in repo names > as long as it clear the project is an incubating project. > Kind Regards, > Justin > > > On Wed, 17 Apr 2024, 1:47 pm Willem Jiang, wrote: > > > With the "incubator" profix, it's easy for us to tell if the project > > belongs to the incubator and it is still in the incubating process. > > Currently I cannot find any disclaimer document[1] in the repo root > > directory from [2][3] to tell if they are still in the incubator or > > not. > > > > [1]https://incubator.apache.org/policy/incubation.html#disclaimers > > [2]https://github.com/apache/amoro > > [3]https://github.com/apache/hertzbeat > > > > Willem Jiang > > > > On Wed, Apr 17, 2024 at 11:06 AM Calvin Kirs wrote: > > > > > > Podlings are not yet fully accepted as part of the Apache Software > > > Foundation. > > > > > > I haven't specifically witnessed any formal decision or process for > > > removing the "incubator" prefix from repository names. > > > > > > Unless there are compelling reasons to remove the "incubator" prefix, I > > > believe it's important to maintain a clear distinction between Podlings > > and > > > TLPs, especially in situations where confusion is likely to arise. > > > > > > On Wed, Apr 17, 2024 at 10:32 AM Sheng Wu > > wrote: > > > > > > > Same mistake for Armoro as Hertzbeat team was misguided from > > > > https://github.com/apache/amoro/issues/2700 > > > > > > > > This is not discussed AFAIK, and the description is not correct. > > > > GitHub supported renaming and repository path forward automatically > > > > years ago. apache/incubator-foo -> apache/foo is transparent and both > > > > addresses work. > > > > > > > > This should not be changed randomly considering many other projects > > > > are using incubator- prefix. This renaming causes confusion. IPMC are > > > > making sure the website has `incubating` and disclaimer as always, > > > > suddenly some projects even could use repository names without > > > > prefixes. This is wrong. > > > > > > > > Mentors of Armoro and Hertzbeat should follow the existing > > > > requirements, and PPMC members of these two projects should ask INFRA > > > > to rename, adding the incubator- prefix back. > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > Xuanwo 于2024年4月17日周三 10:19写道： > > > > > > > > > > > For projects in incubation, is it no longer necessary for the > > project > > > > > > name to have the "incubator-" prefix as it used to be? > > > > > > > > > > Based on the discussions in this mailing list, the only change made > > is > > > > the removal of `incubator` from the domain. Now, users access ` > > > > polding.apache.org` instead of `polding.incubator.apache.org` by > > default. > > > > > > > > > > The project and releases are still required to include "incubator", > > and > > > > it's important for the PPMC to clearly communicate that this project > > > > remains under incubation. > > > > > > > > > > In this case, I believe Hertzbeat PPMC made a mistake. I will > suggest > > > > they rename it to incubator-hertzbeat. > > > > > > > > > > On Mon, Apr 15, 2024, at 14:23, rat O wrote:
Re: Questions about a new project entering Apache Incubator
Same mistake for Armoro as Hertzbeat team was misguided from https://github.com/apache/amoro/issues/2700 This is not discussed AFAIK, and the description is not correct. GitHub supported renaming and repository path forward automatically years ago. apache/incubator-foo -> apache/foo is transparent and both addresses work. This should not be changed randomly considering many other projects are using incubator- prefix. This renaming causes confusion. IPMC are making sure the website has `incubating` and disclaimer as always, suddenly some projects even could use repository names without prefixes. This is wrong. Mentors of Armoro and Hertzbeat should follow the existing requirements, and PPMC members of these two projects should ask INFRA to rename, adding the incubator- prefix back. Sheng Wu 吴晟 Twitter, wusheng1108 Xuanwo 于2024年4月17日周三 10:19写道： > > > For projects in incubation, is it no longer necessary for the project > > name to have the "incubator-" prefix as it used to be? > > Based on the discussions in this mailing list, the only change made is the > removal of `incubator` from the domain. Now, users access > `polding.apache.org` instead of `polding.incubator.apache.org` by default. > > The project and releases are still required to include "incubator", and it's > important for the PPMC to clearly communicate that this project remains under > incubation. > > In this case, I believe Hertzbeat PPMC made a mistake. I will suggest they > rename it to incubator-hertzbeat. > > On Mon, Apr 15, 2024, at 14:23, rat O wrote: > > First of all, congratulations to HertzBeat for successfully entering > > the Apache Incubator. > > > > I noticed that the project has created an issue for an unknown license > > and is ready to address it. I'm sure the project will also address > > other unknown licenses, if they exist. > > > > I wonder if the situation of having a significant amount of non-English > > languages in the codes, like these > > https://github.com/apache/hertzbeat/blob/master/warehouse/src/main/java/org/apache/hertzbeat/warehouse/config/WarehouseProperties.java, > > https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/entity/manager/NoticeRule.java, > > https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/config/AviatorConfiguration.java > > ... > > , will all of them also be addressed in the future? > > > > For projects in incubation, is it no longer necessary for the project > > name to have the "incubator-" prefix as it used to be? > > -- > Xuanwo > > - > 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] Accept HertzBeat Into the ASF Incubator
+1 binding Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 Duo Zhang 于2024年4月3日 周三11:01写道： > +1 binding > > I think Sheng Wu's suggestions are all good follow-ons after joining > the incubator, agree these are not blockers for incubation. > > Good Luck! > > Thanks. > > Xinyu Zhou 于2024年4月3日周三 10:50写道： > > > > +1 binding. > > > > Good Luck! > > > > Regards, > > Xinyu Zhou > > > > > > > > On Wed, Apr 3, 2024 at 10:19 AM roryqi wrote: > > > > > +1, Thanks. > > > > > > Xin Wang 于2024年4月3日周三 09:43写道： > > > > > > > +1, binding > > > > > > > > Xun Liu 于2024年4月3日周三 08:58写道： > > > > > > > > > +1 (binding) > > > > > > > > > > Best regards, > > > > > Xun Liu > > > > > > > > > > On Wed, Apr 3, 2024 at 7:33 AM zhongyi tan > > > > wrote: > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > Good luck > > > > > > > > > > > > > > > > > > > > > > > > 在 2024/4/2 20:15，“Zhang Yonglun” > > > > > zhangyong...@apache.org>> 写入: > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > Thanks to everyone who has already taken the time to vote. > > > > > > > > > > > > > > > > > > I just wanted to gently remind that our voting process is > nearing its > > > > > > deadline, and we're still hoping to gather more input. Your > thoughts > > > > > > and opinions truly matter to us. > > > > > > > > > > > > > > > > > > Your participation in the vote will not only shape our decisions > but > > > > > > also ensure that we consider a diverse range of perspectives. We > > > value > > > > > > every voice and want to make sure everyone has the opportunity to > > > > > > contribute. > > > > > > > > > > > > > > > > > > If you haven't already, please take a moment to cast your vote. > And > > > if > > > > > > you have any questions or need assistance, feel free to reach > out to > > > > > > me anytime. > > > > > > > > > > > > > > > > > > Thank you for your time and consideration. > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > Zhang Yonglun > > > > > > > > > > > > > > > > > > Zhang Yonglun > > zhangyong...@apache.org > > > > >> > > > > > > 于2024年3月29日周五 14:24写道： > > > > > > > > > > > > > > Hi Incubator, > > > > > > > > > > > > > > Following the discussion [DISCUSS] Incubating Proposal for > > > > > HertzBeat[1], > > > > > > > I am starting this official vote for the HertzBeat project. > > > > > > > > > > > > > > Here is their proposal: > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > > > > < > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > > > > > > > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > > > [ ] +1, bring into the Incubator > > > > > > > [ ] +0, I don't care either way > > > > > > > [ ] -1, do not bring HertzBeat into the Incubator, because... > > > > > > > > > > > > > > The vote will open for one week from today. > > > > > > > > > > > > > > [1] > > > https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > > > > < > > > > > > https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > > > > > > > > > > > > > > > > Best Regards, > > > > > > > Zhang Yonglun > > > > > > > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > > > > > > general-unsubscr...@incubator.apache.org> > > > > > > For additional commands, e-mail: > general-h...@incubator.apache.org > > > > > > <mailto:general-h...@incubator.apache.org> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Thanks, > > > > Xin > > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept HertzBeat Into the ASF Incubator
I am not holding anything. I didn't vote -1. Sheng Wu 吴晟 Twitter, wusheng1108 John D. Ament 于2024年3月29日周五 21:13写道： > > On Fri, Mar 29, 2024 at 8:41 AM Sheng Wu wrote: > > > Hi > > > > Yes, a project doesn't have to separate the repository into two for > > both website and source codes, once the license has been reviewed. > > Calcite is another TLP, which is guaranteed, so it is on their PMC > > oversight. > > > > My suggestion is based on things that may not be suitable in your > > final release, such as logos from other vendors, > > https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons. > > Those may be available to use on your website, but not available for > > source tar. Such as Apple Inc. logo is included currently. > > - https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons > > - > > https://github.com/dromara/hertzbeat/blob/master/home/static/img/icons/ios.svg > > > > > > > I don't understand what you're trying to ask the proposed project to do. > It seems like you're holding them to a bar that is above what podlings are > expected to follow when coming in to even be considered accepted to the > ASF. I don't think any of this needs to be resolved before we accept the > project, we all know that there's a period between when the project leaves > its former home and enters its new home that they are in transition and > need to make a large number of changes. > > None of this blocks acceptance, looks like a great addition > +1 from me. > > John > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Francis Chuang 于2024年3月29日周五 15:47写道： > > > > > > Thanks, Chao Gong, for addressing those issues in > > > > > https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588 > > > > > > Looking at the updated website, the issues raised have been taken care > > of. > > > > > > Regarding keeping the website's source code and project code in the > > > project repository, I don't think it's 100% necessary to separate the > > > website into a separate repository. > > > > > > For Calcite, our site is in the same repository as our code: > > > https://github.com/apache/calcite/tree/main/site > > > > > > We include the correct licenses in the LICENSE file when we build a > > > release, using a template: > > > https://github.com/apache/calcite/blob/main/LICENSE > > > > > > Francis > > > > > > On 29/03/2024 6:05 pm, Sheng Wu wrote: > > > > Some things should be fixed > > > > > > > > 1. At the top of the home page, > > > GitHub⭐️⭐️> exists, this should be removed. > > > > 2. At the top menu, exists, I don't think this project > > > > is Huawei, and please don't use another vendor's brand. > > > > 3. Similar with <2>, but for OSPP. That is also another org brand. > > > > 4. When I first lands on the homepage, there is a pop up box to ask me > > > > star on GitHub. This should be removed too. GitHub repository is just > > > > a bi-way synced mirror repository. ASF has its own code repository, > > > > which is also the main repository to make sure vendor neutral. > > > > > > > > A thing you should fix later, your website source codes and resources > > > > are in the same repository. Those things may not be able to be > > > > included considering the license and binaries(png, videos) may be > > > > included. In the ASF, website is usually a separate repository. > > > > But the in your proposal seems not included. Please > > > > reach your mentors and fix the proposal. > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > Zhang Yonglun 于2024年3月29日周五 14:24写道： > > > >> > > > >> Hi Incubator, > > > >> > > > >> Following the discussion [DISCUSS] Incubating Proposal for > > HertzBeat[1], > > > >> I am starting this official vote for the HertzBeat project. > > > >> > > > >> Here is their proposal: > > > >> > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > >> > > > >> Please cast your vote: > > > >> > > > >> [ ] +1, bring into the Incubator > > > >> [ ] +0, I don't care either way > > > >> [ ] -1, do not bring HertzBeat into the Incubator, because... >
Re: [VOTE] Accept HertzBeat Into the ASF Incubator
Hi Yes, a project doesn't have to separate the repository into two for both website and source codes, once the license has been reviewed. Calcite is another TLP, which is guaranteed, so it is on their PMC oversight. My suggestion is based on things that may not be suitable in your final release, such as logos from other vendors, https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons. Those may be available to use on your website, but not available for source tar. Such as Apple Inc. logo is included currently. - https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons - https://github.com/dromara/hertzbeat/blob/master/home/static/img/icons/ios.svg Sheng Wu 吴晟 Twitter, wusheng1108 Francis Chuang 于2024年3月29日周五 15:47写道： > > Thanks, Chao Gong, for addressing those issues in > https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588 > > Looking at the updated website, the issues raised have been taken care of. > > Regarding keeping the website's source code and project code in the > project repository, I don't think it's 100% necessary to separate the > website into a separate repository. > > For Calcite, our site is in the same repository as our code: > https://github.com/apache/calcite/tree/main/site > > We include the correct licenses in the LICENSE file when we build a > release, using a template: > https://github.com/apache/calcite/blob/main/LICENSE > > Francis > > On 29/03/2024 6:05 pm, Sheng Wu wrote: > > Some things should be fixed > > > > 1. At the top of the home page, > GitHub⭐️⭐️> exists, this should be removed. > > 2. At the top menu, exists, I don't think this project > > is Huawei, and please don't use another vendor's brand. > > 3. Similar with <2>, but for OSPP. That is also another org brand. > > 4. When I first lands on the homepage, there is a pop up box to ask me > > star on GitHub. This should be removed too. GitHub repository is just > > a bi-way synced mirror repository. ASF has its own code repository, > > which is also the main repository to make sure vendor neutral. > > > > A thing you should fix later, your website source codes and resources > > are in the same repository. Those things may not be able to be > > included considering the license and binaries(png, videos) may be > > included. In the ASF, website is usually a separate repository. > > But the in your proposal seems not included. Please > > reach your mentors and fix the proposal. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Zhang Yonglun 于2024年3月29日周五 14:24写道： > >> > >> Hi Incubator, > >> > >> Following the discussion [DISCUSS] Incubating Proposal for HertzBeat[1], > >> I am starting this official vote for the HertzBeat project. > >> > >> Here is their proposal: > >> https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > >> > >> Please cast your vote: > >> > >> [ ] +1, bring into the Incubator > >> [ ] +0, I don't care either way > >> [ ] -1, do not bring HertzBeat into the Incubator, because... > >> > >> The vote will open for one week from today. > >> > >> [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > >> > >> Best Regards, > >> Zhang Yonglun > >> > >> - > >> 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: [VOTE] Accept HertzBeat Into the ASF Incubator
Some things should be fixed 1. At the top of the home page, exists, this should be removed. 2. At the top menu, exists, I don't think this project is Huawei, and please don't use another vendor's brand. 3. Similar with <2>, but for OSPP. That is also another org brand. 4. When I first lands on the homepage, there is a pop up box to ask me star on GitHub. This should be removed too. GitHub repository is just a bi-way synced mirror repository. ASF has its own code repository, which is also the main repository to make sure vendor neutral. A thing you should fix later, your website source codes and resources are in the same repository. Those things may not be able to be included considering the license and binaries(png, videos) may be included. In the ASF, website is usually a separate repository. But the in your proposal seems not included. Please reach your mentors and fix the proposal. Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2024年3月29日周五 14:24写道： > > Hi Incubator, > > Following the discussion [DISCUSS] Incubating Proposal for HertzBeat[1], > I am starting this official vote for the HertzBeat project. > > Here is their proposal: > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > Please cast your vote: > > [ ] +1, bring into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring HertzBeat into the Incubator, because... > > The vote will open for one week from today. > > [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn > > Best Regards, > Zhang Yonglun > > - > 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] Incubating Proposal for HertzBeat
Hi, At the bottom of the website, the link to Dromara 知识星球, seems to be a commercial channel. Please consider to remove that. ASF is a vendor neutral org, you should not charge for end users or vendors. Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 Chao Gong 于2024年3月26日 周二16:21写道： > Hi Twice, we have removed the existing advertising in repo and website. > Please see https://github.com/dromara/hertzbeat > https://hertzbeat.dromara.org/. > > On 2024/03/19 01:59:37 Twice Pragma wrote: > > Sorry but just for curious, I wonder how you will handle the existing > advertising for and only for TanCloud in Hertzbeat repo and website (e.g. > in README.md)? > > > > Best, > > Twice > > > > > > From: Chao Gong > > Sent: Monday, March 18, 2024 1:07:40 AM > > To: general@incubator.apache.org > > Subject: Re: [DISCUSS] Incubating Proposal for HertzBeat > > > > Thanks for your reminder and suggestion. > > > > > > > > Best wishes, > > Tom > > > > On 2024/03/17 15:32:37 Sheng Wu wrote: > > > Thanks for the explanation. It is clear, and I am good as you could > > > make the final call. There will be a lot of issues to deal with during > > > the incubating, just recommend removing vendor links from the website, > > > project readme, and document as much as possible. I know it will take > > > time. > > > > > > Wearing the out-of-ASF hat, only as a friendly reminder, make sure you > > > have talked to enough people knowing best about the challenges you > > > will face after you donate your company core project to a > > > vendor-neutral foundation. > > > Foundation projects are for the public good, not for your company's > > > financial good. The better your project is incubated in the > > > foundation, the less controllability you will have for the project. > > > Think deeply. > > > Note, that this is irrelevant to the incubating proposal, it is just a > > > reminder from a person who founded a project and is working on a > > > startup. > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > Chao Gong 于2024年3月17日周日 23:15写道： > > > > > > > > > > > Hi Sheng, > > > > > > > > The https://github.com/dromara/hertzbeat code repository contains > documentation code in the “home” directory. All our open-source code, > frontend, backend, and official website are housed within this single > repository. > > > > > > > > As you can see, the Tancloud website is nearly the same as > Hertzbeat. We will rebuild Tancloud’s official website later to distinguish > it from Hertzbeat. > > > > > > > > Tancloud is a company registered by the founder of Hertzbeat to > build SAAS. This company has only one employee, which is myself. We will > ensure that the vendor is completely okay with donating the entire project > to the foundation. Additionally, we will distinguish between the brands, > logos, and other elements of Hertzbeat and Tancloud. > > > > > > > > We will sign an SGA and address any related copyright issues. > > > > > > > > Regarding the setup of the incubation time of duration, we referred > to other incubation projects. However, this is an estimated timeframe that > may change depending on the actual progress of the incubation. We will be > patient in participating in incubation. > > > > > > > > Regarding other entities using Hertzbeat to build SAAS, we believe > it’s acceptable, subject to the foundation’s rules. > > > > > > > > Best wishes, > > > > Tom > > > > > > > > On 2024/03/17 12:34:28 Sheng Wu wrote: > > > > > I have more questions around this project. > > > > > > > > > > I saw from the proposal, https://github.com/dromara/hertzbeat is > the > > > > > only code repository included, no other part. Then where the docs > go? > > > > > > > > > > With docs, I can see https://tancloud.cn/ and > > > > > https://hertzbeat.dromara.org/ are using nearly the same content, > page > > > > > style, etc. > > > > > Who will be the owner of those pages? > > > > > From what I understand, the simple SGA for this one repository(code > > > > > base) is not enough. You need to make sure that vendor is totally > fine > > > > > with donating the whole thing to the foundation to avoid conflicts > in > > >
Re: [DISCUSS] Incubating Proposal for HertzBeat
Thanks for the explanation. It is clear, and I am good as you could make the final call. There will be a lot of issues to deal with during the incubating, just recommend removing vendor links from the website, project readme, and document as much as possible. I know it will take time. Wearing the out-of-ASF hat, only as a friendly reminder, make sure you have talked to enough people knowing best about the challenges you will face after you donate your company core project to a vendor-neutral foundation. Foundation projects are for the public good, not for your company's financial good. The better your project is incubated in the foundation, the less controllability you will have for the project. Think deeply. Note, that this is irrelevant to the incubating proposal, it is just a reminder from a person who founded a project and is working on a startup. Sheng Wu 吴晟 Twitter, wusheng1108 Chao Gong 于2024年3月17日周日 23:15写道： > > Hi Sheng, > > The https://github.com/dromara/hertzbeat code repository contains > documentation code in the “home” directory. All our open-source code, > frontend, backend, and official website are housed within this single > repository. > > As you can see, the Tancloud website is nearly the same as Hertzbeat. We will > rebuild Tancloud’s official website later to distinguish it from Hertzbeat. > > Tancloud is a company registered by the founder of Hertzbeat to build SAAS. > This company has only one employee, which is myself. We will ensure that the > vendor is completely okay with donating the entire project to the foundation. > Additionally, we will distinguish between the brands, logos, and other > elements of Hertzbeat and Tancloud. > > We will sign an SGA and address any related copyright issues. > > Regarding the setup of the incubation time of duration, we referred to other > incubation projects. However, this is an estimated timeframe that may change > depending on the actual progress of the incubation. We will be patient in > participating in incubation. > > Regarding other entities using Hertzbeat to build SAAS, we believe it’s > acceptable, subject to the foundation’s rules. > > Best wishes, > Tom > > On 2024/03/17 12:34:28 Sheng Wu wrote: > > I have more questions around this project. > > > > I saw from the proposal, https://github.com/dromara/hertzbeat is the > > only code repository included, no other part. Then where the docs go? > > > > With docs, I can see https://tancloud.cn/ and > > https://hertzbeat.dromara.org/ are using nearly the same content, page > > style, etc. > > Who will be the owner of those pages? > > From what I understand, the simple SGA for this one repository(code > > base) is not enough. You need to make sure that vendor is totally fine > > with donating the whole thing to the foundation to avoid conflicts in > > the future. > > But this is the homepage of the company, are they OK with this? What > > is the plan for these existing pages and the name? Will the company > > rebuild their home page before the donation? > > > > I also read the introduction page(in Chinese), > > https://support.qq.com/products/379369/team#story-1 > > It mentioned, TanCloud is actually the SAAS version of HertzBeat. > > Will the company OK to say we are only a kind of cloud service powered > > by Apache HertzBeat(Incubating)? This also means, other entities could > > use Apache HertzBeat to build the SAAS too once the donation is done, > > and even used the same statement `powered by Apache HertzBeat` like > > TanCloud do. > > > > Project mentors, and initial committers, how many of you are in the > > company, that could you confirm all above are granted by the company' > > legal part? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Sheng Wu 于2024年3月17日周日 18:34写道： > > > > > > > > > > > > > > > Chao Gong 于2024年3月17日 周日16:59写道： > > >> > > >> Hi Sheng, Xuanwo, > > >> > > >> Thank you very much for your attention and feedback on HertzBeat. > > >> > > >> Sorry for any confusion caused, we have updated the proposal to indicate > > >> that TanCloud will sign SGA. Dromara is an open source community > > >> organized by a group of open source enthusiasts, and it does not own the > > >> copyright of projects. > > >> > > >> We will clean up related copyright issues and documents according to the > > >> requirements of the incubator. > > > > > > > > > Please make sure at least vendor trademark, platforms are not included. > > > The foundation is
Re: [DISCUSS] Incubating Proposal for HertzBeat
I have more questions around this project. I saw from the proposal, https://github.com/dromara/hertzbeat is the only code repository included, no other part. Then where the docs go? With docs, I can see https://tancloud.cn/ and https://hertzbeat.dromara.org/ are using nearly the same content, page style, etc. Who will be the owner of those pages? >From what I understand, the simple SGA for this one repository(code base) is not enough. You need to make sure that vendor is totally fine with donating the whole thing to the foundation to avoid conflicts in the future. But this is the homepage of the company, are they OK with this? What is the plan for these existing pages and the name? Will the company rebuild their home page before the donation? I also read the introduction page(in Chinese), https://support.qq.com/products/379369/team#story-1 It mentioned, TanCloud is actually the SAAS version of HertzBeat. Will the company OK to say we are only a kind of cloud service powered by Apache HertzBeat(Incubating)? This also means, other entities could use Apache HertzBeat to build the SAAS too once the donation is done, and even used the same statement `powered by Apache HertzBeat` like TanCloud do. Project mentors, and initial committers, how many of you are in the company, that could you confirm all above are granted by the company' legal part? Sheng Wu 吴晟 Twitter, wusheng1108 Sheng Wu 于2024年3月17日周日 18:34写道： > > > > > Chao Gong 于2024年3月17日 周日16:59写道： >> >> Hi Sheng, Xuanwo, >> >> Thank you very much for your attention and feedback on HertzBeat. >> >> Sorry for any confusion caused, we have updated the proposal to indicate >> that TanCloud will sign SGA. Dromara is an open source community organized >> by a group of open source enthusiasts, and it does not own the copyright of >> projects. >> >> We will clean up related copyright issues and documents according to the >> requirements of the incubator. > > > Please make sure at least vendor trademark, platforms are not included. The > foundation is vendor neutral. > >> >> >> Best wishes, >> Tom >> >> On 2024/03/16 13:22:11 Zhang Yonglun wrote: >> > Hi IPMC members, >> > >> > I would like to propose a new project to the ASF incubator - HertzBeat. >> > >> > HertzBeat[1] is an easy-to-use, open source, real-time monitoring >> > system. It features an agentless architecture, high-performance >> > clustering, Prometheus compatibility, and powerful custom monitoring >> > and status page building capabilities. >> > >> > Here is the proposal - >> > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal >> > >> > I would be the Champion of the project. I will mentor and help the project >> > through the incubator with Yu Xiao [xia...@apache.org], Justin Mclean >> > (jmcl...@apache.org). >> > >> > We are open to hearing the feedback from the incubator. >> > >> > [1] https://hertzbeat.dromara.org/ >> > >> > -- >> > >> > Zhang Yonglun >> > Apache ShenYu & ShardingSphere >> > >> > - >> > 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: [DISCUSS] Incubating Proposal for HertzBeat
Chao Gong 于2024年3月17日 周日16:59写道： > Hi Sheng, Xuanwo, > > Thank you very much for your attention and feedback on HertzBeat. > > Sorry for any confusion caused, we have updated the proposal to indicate > that TanCloud will sign SGA. Dromara is an open source community organized > by a group of open source enthusiasts, and it does not own the copyright of > projects. > > We will clean up related copyright issues and documents according to the > requirements of the incubator. Please make sure at least vendor trademark, platforms are not included. The foundation is vendor neutral. > > Best wishes, > Tom > > On 2024/03/16 13:22:11 Zhang Yonglun wrote: > > Hi IPMC members, > > > > I would like to propose a new project to the ASF incubator - HertzBeat. > > > > HertzBeat[1] is an easy-to-use, open source, real-time monitoring > > system. It features an agentless architecture, high-performance > > clustering, Prometheus compatibility, and powerful custom monitoring > > and status page building capabilities. > > > > Here is the proposal - > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > > I would be the Champion of the project. I will mentor and help the > project > > through the incubator with Yu Xiao [xia...@apache.org], Justin Mclean > > (jmcl...@apache.org). > > > > We are open to hearing the feedback from the incubator. > > > > [1] https://hertzbeat.dromara.org/ > > > > -- > > > > Zhang Yonglun > > Apache ShenYu & ShardingSphere > > > > - > > 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] Incubating Proposal for HertzBeat
We also need a update about salaried developers and current deserve status as this is mostly a vendor project, we hope the project owners could provide honest status. You don't need to worry about we don't have many developers, that is the purpose of the incubating. And I want to ask, why do you set up the period of estimated incubating is 1 year. 1 year is a short time, and most of you are not that experienced about ASF. I would like to ask you to be patient and learn slowly. Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 Chao Gong 于2024年3月17日 周日16:59写道： > Hi Sheng, Xuanwo, > > Thank you very much for your attention and feedback on HertzBeat. > > Sorry for any confusion caused, we have updated the proposal to indicate > that TanCloud will sign SGA. Dromara is an open source community organized > by a group of open source enthusiasts, and it does not own the copyright of > projects. > > We will clean up related copyright issues and documents according to the > requirements of the incubator. > > Best wishes, > Tom > > On 2024/03/16 13:22:11 Zhang Yonglun wrote: > > Hi IPMC members, > > > > I would like to propose a new project to the ASF incubator - HertzBeat. > > > > HertzBeat[1] is an easy-to-use, open source, real-time monitoring > > system. It features an agentless architecture, high-performance > > clustering, Prometheus compatibility, and powerful custom monitoring > > and status page building capabilities. > > > > Here is the proposal - > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > > I would be the Champion of the project. I will mentor and help the > project > > through the incubator with Yu Xiao [xia...@apache.org], Justin Mclean > > (jmcl...@apache.org). > > > > We are open to hearing the feedback from the incubator. > > > > [1] https://hertzbeat.dromara.org/ > > > > -- > > > > Zhang Yonglun > > Apache ShenYu & ShardingSphere > > > > - > > 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] Incubating Proposal for HertzBeat
I did a simple review on the docs page of this project. The documents include a lot of parts leading user for TanCloud Inc. cloud service and their social connection platforms. Such as - Vendor Cloud SAAS, https://console.tancloud.cn/passport/login - https://console.tancloud.cn/ - https://github.com/dromara/hertzbeat?tab=readme-ov-file#-join-discussion - Bilibili page is owned by an individual. Is this company good to remove all these information and transfer the ownership to the foundation and trademark? I can see the company owned this project, as LICENSE/NOTICE says so from https://github.com/dromara/hertzbeat/blob/master/NOTICE > Copyright https://www.hertzbeat.com https://www.tancloud.cn All Rights > Reserved. And in the proposal, it never mentioned there is developers paid by TanCloud, is that correct? I doubt on this. What is the relationship between dromara org, TanCloud, and the project? Sheng Wu 吴晟 Twitter, wusheng1108 Chao Gong 于2024年3月17日周日 10:31写道： > > Hi Fanning, Dave > > I am tom from hertzbeat community. > > Thank you very much for your attention and feedback on hertzbeat. > > We have do a PODLINGNAMESEARCH and there are no other projects discovered > using this name hertzbeat through patent inquiry. > > Regarding the car rental company brand Hertz you mentioned, we think there is > a clear difference between hertz and hertzbeat. We can find hundreds of > trademarks containing hertz. Hertz is not only a car rental company brand, > but also a common noun - the SI unit of frequency > > We check hertzbeat has not been registered as a trademark in class 9. The > hertz trademark has 38 results in class 9, such as hertz, hertzEagle, > hertzstuck, nuhertz, TeraHertz+ and so on. These trademarks related to Hertz > do not conflict with each other, so why not hertzbeat? > > For this, we can pay more attention to using the hertzbeat brand as a whole > in future documents and publicity, distinguish it from hertz, and clearly > distinguish it in materials such as logos. > > We have been using this name for nearly three years, and it is widely known > and loved by the community and users. We hope to keep this name if possible. > Thanks! > > Best wishes, > Tom > > On 2024/03/16 13:22:11 Zhang Yonglun wrote: > > Hi IPMC members, > > > > I would like to propose a new project to the ASF incubator - HertzBeat. > > > > HertzBeat[1] is an easy-to-use, open source, real-time monitoring > > system. It features an agentless architecture, high-performance > > clustering, Prometheus compatibility, and powerful custom monitoring > > and status page building capabilities. > > > > Here is the proposal - > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal > > > > I would be the Champion of the project. I will mentor and help the project > > through the incubator with Yu Xiao [xia...@apache.org], Justin Mclean > > (jmcl...@apache.org). > > > > We are open to hearing the feedback from the incubator. > > > > [1] https://hertzbeat.dromara.org/ > > > > -- > > > > Zhang Yonglun > > Apache ShenYu & ShardingSphere > > > > - > > 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: [VOTE] Graduate Apache Pekko (incubating) as a TLP
+1 binding. Sheng Wu 吴晟 Twitter, wusheng1108 Willem Jiang 于2024年2月28日周三 21:51写道： > > +1 (binding) > Good luck! > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Feb 26, 2024 at 7:25 PM PJ Fanning wrote: > > > > Hi everyone, > > > > We have positive feedback on the Pekko Vote thread [1] (result [2]). > > > > I'd like to start an official Incubator VOTE thread now. > > > > Below are some facts and project highlights from the incubation phase > > as well as the draft resolution: > > > > * All modules have at least a v1.0.0 release > > * 19 releases (across 12 modules) [3] > > * Evidence of good uptake of the Pekko releases and a large number of > > ecosystem libs now support Pekko - over 100 non Apache libraries use > > Pekko libs under the hood > > * well over 1000 PRs merged > > * 25+ code contributors > > * We've had 3 different release managers to date. > > * dozens more users who have been involved in discussions, code > > reviews, raising issues, etc. > > * We have met all maturity criteria as outlined in [4]. > > > > > > Please vote on the resolution pasted below to graduate Apache Pekko > > from the Incubator to the Top Level Project. > > > > [ ] +1 Graduate Apache Pekko from the Incubator. > > [ ] +0 No opinion. > > [ ] -1 Don't graduate Apache Pekko from the Incubator because ... > > > > This vote will open for at least 72 hours. > > > > I would like to thank everyone who have participated in the Apache > > Pekko community. I would also like to thank the Apache Incubator > > community as well as Apache Infrastructure team and general ASF > > community for your support. > > > > > > [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx > > [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o > > [3] https://incubator.apache.org/projects/pekko.html > > [4] > > https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko > > > > > > > > --- > > > > Establish the Apache Pekko Project > > > > > > WHEREAS, the Board of Directors deems it to be in the best interests > > of the Foundation and consistent with the Foundation's purpose to > > establish a Project Management Committee charged with the creation and > > maintenance of open-source software, for distribution at no charge to > > the public, related to Pekko: a toolkit and an ecosystem for building > > highly concurrent, distributed, reactive and resilient applications > > for Java and Scala. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache Pekko Project", be and hereby is > > established pursuant to Bylaws of the Foundation; and be it further > > > > > > RESOLVED, that the Apache Pekko Project be and hereby is responsible > > for the creation and maintenance of software related to Pekko: a > > toolkit and an ecosystem for building highly concurrent, distributed, > > reactive and resilient applications for Java and Scala.; and be it > > further > > > > > > RESOLVED, that the office of "Vice President, Apache Pekko" be and > > hereby is created, the person holding such office to serve at the > > direction of the Board of Directors as the chair of the Apache Pekko > > Project, and to have primary responsibility for management of the > > projects within the scope of responsibility of the Apache Pekko > > Project; and be it further > > > > > > RESOLVED, that the persons listed immediately below be and hereby are > > appointed to serve as the initial members of the Apache Pekko Project: > > > > Claude Warren (claude) > > Jean-Baptiste Onofré (jbonofre) > > Justin Mclean (jmclean) > > PJ Fanning (fanningpj) > > Roman Shaposhnik (rvs) > > Ryan Skraba (rskraba) > > Sheng Wu (wu-sheng) > > Alexandru Nedelcu (alexelcu) > > Arnout Engelen (engelen) > > Dani Schroeter (dsc) > > Greg Methvin (gregm) > > Guobin Li (liguobin) > > He Pin (hepin) > > Johannes Rudolph (jrudolph) > > Jonas Chapuis (jchapuis) > > Matthew de Detrich (mdedetrich) > > Nicolas Vollmar (nvollmar) > > Samuele Resca (samueler) > > Sean Glover (seanglover) > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that PJ Fanning be appointed
Re: [VOTE] Release Apache OpenDAL(incubating) 0.44.1 - Incubator Vote Round 1
+1 binding - Compiling from source codes passed on Mac M3 - ASC checked. - LICENSE and NOTICE are there - DISCLAIMER exists - Download links work - Version correct Good luck Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2024年1月3日周三 15:35写道： > > Carry my +1 from the dev list > > Best, > tison. > > Xuanwo 于2024年1月3日周三 15:33写道： > > > > Hello Incubator PMC, > > > > The Apache OpenDAL community has voted and approved the release of Apache > > OpenDAL(incubating) 0.44.1. We now kindly request the IPMC members > > review and vote for this release. > > > > OpenDAL is a data access layer that allows users to easily and efficiently > > retrieve data from various storage services in a unified way. > > > > OpenDAL community vote thread: > > > > https://lists.apache.org/thread/r76vnpfm2g1rhf1q33x7bmtmw137dlb4 > > > > Vote result thread: > > > > https://lists.apache.org/thread/rbh65l5sbrd1bd45d2nm2h20lqhzy7x1 > > > > The release candidate: > > > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.44.1-rc.1/ > > > > This release has been signed with a PGP available here: > > > > https://downloads.apache.org/incubator/opendal/KEYS > > > > Git tag for the release: > > > > https://github.com/apache/incubator-opendal/releases/tag/v0.44.1-rc.1 > > > > Maven staging repo: > > > > https://repository.apache.org/content/repositories/orgapacheopendal-1023/ > > > > Please download, verify, and test. > > > > The VOTE will be open for at least 72 hours and until the necessary > > number of votes are reached. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > To learn more about apache opendal, please see https://opendal.apache.org/ > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > More detailed checklist please refer to: > > https://github.com/apache/incubator-opendal/tree/main/scripts > > > > To compile from source, please refer to: > > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > > > Here is python script in release to help you verify the release candidate: > > > > ./scripts/verify.py > > > > Thanks > > > > Xuanwo > > > > - > > 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: [VOTE] Release Apache OpenDAL(incubating) 0.44.0-rc.1 - Incubator Vote Round 1
+1 binding 1. Faced the same issue as Tison. MacOS M3 finder extracting doesn't work. 2. `tav -xvf` works with compiling on MacOS. 3. LICENSE and NOTICE are there. 4. gpg signed verified. 5. sha is there. One nit, release managers is using the GPG key for two mail boxes(one for gmail, the other for apache mail box). This should be fine, but when I use GPG Keychain UI, it reports signed by gmail only. This could be confusing. Recommend using a specific GPG key by using apache mail box for ASF release only. Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2023年12月29日周五 22:21写道： > > +1 (binding) > > Thank you Xuanwo. I use macos Finder's extract UI and it fails to > build. Using `tar -xvf` works. > > Best, > tison. > > Xuanwo 于2023年12月29日周五 22:00写道： > > > > Hi, tison > > > > The tarball doesn't have `bindings/c` in the `Cargo.toml` > > > > ```toml > > 18 │ [workspace] > > 19 │ default-members = ["core"] > > 20 │ exclude = [ > > 21 │ "examples", > > 22 │ > > 23 │ ] > > 24 │ members = [ > > 25 │ "core", > > 26 │ "core/fuzz", > > 27 │ "core/edge/*", > > 28 │ "core/benches/vs_*", > > 29 │ > > 30 │ "bindings/nodejs", > > 31 │ "bindings/python", > > 32 │ "bindings/java", > > 33 │ > > 34 │ > > 35 │ ] > > 36 │ resolver = "2" > > ``` > > > > We used to met dirty cache issues on other platforms. Would you like to > > double check it? > > > > Use `tar -xvf` to extract the tarball instead of using a system > > decompression application. > > > > On Fri, Dec 29, 2023, at 16:30, tison wrote: > > > -1 binding > > > > > > + Download links valid > > > + GPG sign correctly > > > > > > $ for i in (*.tgz|*.tar.gz|*.nupkg); do echo $i; gpg --verify $i.asc $i; > > > done > > > apache-opendal-incubating-0.44.0-src.tar.gz > > > gpg: Signature made 二 12/26 20:49:34 2023 CST > > > gpg:using RSA key 25812FA45EC6D2DDCBE4B6604F43CB2BC2E9EFE5 > > > gpg: Good signature from "dqhl76 (Identifier for authoring code on > > > GitHub) " [unknown] > > > gpg: aka "Liuqing Yue (Apache Committer) > > > " [unknown] > > > gpg: WARNING: This key is not certified with a trusted signature! > > > gpg: There is no indication that the signature belongs to the > > > owner. > > > Primary key fingerprint: 2581 2FA4 5EC6 D2DD CBE4 B660 4F43 CB2B C2E9 > > > EFE5 > > > > > > + Checksum matched > > > + LICENSE and NOTICE exists > > > > > > - Cannot build and test Java binding: > > > > > > Caused by: > > > failed to read > > > `/Users/tison/Labs/vropendal/apache-opendal-incubating-0.44.0-src/bindings/c/Cargo.toml` > > > > > > Caused by: > > > No such file or directory (os error 2) > > > > > > Seems we exclude those directories and it cause build failure. > > > > > > Best, > > > tison. > > > > > > Xuanwo 于2023年12月28日周四 13:14写道： > > >> > > >> Carry my non-binding +1 VOTE from the dev@o.a.o > > >> > > >> On Thu, Dec 28, 2023, at 13:12, Liuqing Yue wrote: > > >> > Hello Incubator PMC, > > >> > > > >> > The Apache OpenDAL community has voted and approved the release of > > >> > Apache > > >> > OpenDAL(incubating) 0.44.0-rc.1. We now kindly request the IPMC members > > >> > review and vote for this release. > > >> > > > >> > OpenDAL is a data access layer that allows users to easily and > > >> > efficiently > > >> > retrieve data from various storage services in a unified way. > > >> > > > >> > OpenDAL community vote thread: > > >> > > > >> > https://lists.apache.org/thread/nycyfc1m6819bj8vsb20vmbnlhs0kbdn > > >> > > > >> > Vote result thread: > > >> > > > >> > https://lists.apache.org/thread/pfnlmn9vqn1rqdy54wzm3mkx1wnt9mv6 > > >> > > > >> > The release candidate: > > >> > > > >> > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.44.0-rc.1/ > > >> > > > >> > This release has been signed with a PGP available here: > > >> &
Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator
+1 binding Have a better ASF and open source journey in the future Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 Xuanwo 于2023年12月29日 周五08:22写道： > Hello all, > > We've got positive feedback on the DISCUSS thread[1], I'd like to start an > official VOTE thread now. > > Below are some facts and project highlights from the incubation phase > as well as the draft resolution: > > - Currently, our community consists of 19 committers, including mentors, > with 12 serving as PPMC members. > - At present, we boast 164 contributors. > - Throughout the incubation period, we've made 9 releases—averaging at > least one per month. > - We've had 7 different release managers to date. > - Our software is in production use by 10 known entities and is a > dependency > for 263 GitHub projects and 18 crates.io packages. > - To date, we have opened 1,200+ issues with 1,100+ successfully resolved. > - We have submitted a total of 2,400+ PRs, most of them have been merged > or closed. > - We have met all maturity criteria as outlined in [2]. > > Please vote on the resolution pasted below to graduate Apache OpenDAL from > the incubator to the Top Level Project. > > [ ] +1 Graduate Apache OpenDAL from the Incubator. > [ ] +0 No opinion. > [ ] -1 Don't graduate Apache OpenDAL from the Incubator because ... > > This vote will open for at least 72 hours. > > Many thanks to our mentors and everyone else for their support. > > [1] https://lists.apache.org/thread/3lwt4zkm1ovoskrz77y69pwntvn27xvs > [2] https://opendal.apache.org/community/maturity > > --- > > Establish the Apache OpenDAL Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to Open Data Access Layer: Access data freely, painlessly, and > efficiently. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache OpenDAL Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache OpenDAL Project be and hereby is responsible > for the creation and maintenance of software related to Open Data Access > Layer: Access data freely, painlessly, and efficiently; and be it > further > > RESOLVED, that the office of "Vice President, Apache OpenDAL" be and > hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the Apache OpenDAL > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache OpenDAL > Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache OpenDAL Project: > > * Cai Lue > * Chojan Shang > * Han Xu > * Hao Ding > * Jun Ouyang > * Mingzhuo Yin > * Sheng Wu > * Sundy Li > * Ted Liu > * Willem Ning Jiang > * Xiangdong > * Xiaoqiao He > * Zheao Li > * Zili Chen > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hao Ding be appointed to > the office of Vice President, Apache OpenDAL, to serve in accordance > with and subject to the direction of the Board of Directors and the > Bylaws of the Foundation until death, resignation, retirement, removal > or disqualification, or until a successor is appointed; and be it > further > > RESOLVED, that the Apache OpenDAL Project be and hereby is tasked with > the migration and rationalization of the Apache Incubator OpenDAL > podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > OpenDAL podling encumbered upon the Apache Incubator PMC are hereafter > discharged. > > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Graduate Apache OpenDAL (incubating) as a TLP - Incubator
About the https://opendal.apache.org/docs/python/opendal.html, it is already on the apache.org site. It is obvious that it belongs to the ASF. About other distribution platforms, using short names, rather than apache or asf prefixes is a common practice. Keeping the readme clear and stating it is an Apache project, is a good practice. And AFAIK, pypi, crates, docs should be updated accordingly and have to rely on the next release. For other projects, which are not controlled by the committers, it takes time to add Apache. None of the found ones seem to hurt ASF branding. Sheng Wu 吴晟 Twitter, wusheng1108 Justin Mclean 于2023年12月27日周三 15:15写道： > > HI, > > > >> 2. https://opendal.apache.org/docs/python/opendal.html > > This is not fixed. I suggest the PMC members have a good read of our branding > policy to understand what is needed here. [1] At a minimum, the project needs > to be referred to as “Apache OpenDAL”, and the trademark attribution needs to > be added. Please see [2] as well, in particular [3] and [4], but there are > other issues here as well. > > > NOTE: pypi.org, crates.io, docs.rs will be updated after our next release > > published. > > Can you fix the description and add the trademark attributions without making > a release? > > Kind Regards, > Justin > > 1. https://www.apache.org/foundation/marks/responsibility > 2. https://www.apache.org/foundation/marks/pmcs > 3. https://www.apache.org/foundation/marks/pmcs#naming > 4. https://www.apache.org/foundation/marks/pmcs#attributions - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [LICENSE QUESTION] Use jmh as a benchmark tool
I think once it stays in the test scope, it should be good. The release policy is about compiling sources to get the binary, which means the final version could work without GPLx is the most important part. Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2023年12月27日周三 09:09写道： > > Hi, > > The new podling Fury depends on jmh[1] which is licensed under GPLv2 > with "CLASSPATH" EXCEPTION. > > IIRC Flink ever factored out its benchmark code into a separate repo > [2] to comply with ASF's license policy [3]. > > But since Fury doesn't modify jmh's code, just refers to some > "org.openjdk.jmh." classes, I wonder if it's the same that a Java > source file refers to JDK's classes under GPLv2 with "CLASSPATH" > EXCEPTION. > > Or, we can exclude the benchmark code from the release like [4] but > still hold it in the VCS. > > Best, > tison. > > [1] https://github.com/openjdk/jmh?tab=GPL-2.0-1-ov-file > [2] https://github.com/apache/flink-benchmarks > [3] https://www.apache.org/legal/resolved.html > [4] https://github.com/apache/incubator-opendal/blob/main/.gitattributes > > - > 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] Graduate Apache OpenDAL (incubating) as a TLP - Incubator
My +1 binding Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2023年12月25日周一 14:20写道： > > Carry my +1 from the dev maliing list. > > OpenDAL developed a diverse and vibrant community to release > high-quality OSS software during the past months and I believe its > maturity is at the level of a TLP. > > Good luck. > > Best, > tison. > > Xuanwo 于2023年12月25日周一 10:22写道： > > > > Hi, all > > > > OpenDAL began its incubation journey on February 27, 2023. Since then, > > our community has significantly matured. > > > > After discussion with the community [1] and voted [2], [3] for graduation > > with > > the result at [4], [5]. So, we'd like to start the discussion and would > > appreciate any feedback toward graduation! > > > > Below are some facts and project highlights from the incubation phase > > as well as the draft resolution: > > > > - Currently, our community consists of 20 committers, including mentors, > > with 12 serving as PPMC members. > > - At present, we boast 162 contributors. > > - Throughout the incubation period, we've made 9 releases—averaging at > > least one per month. > > - We've had 7 different release managers to date. > > - Our software is in production use by 10 known entities and is a dependency > > for 261 GitHub projects and 18 crates.io packages. > > - To date, we have opened 1,100+ issues with 1,000+ successfully resolved. > > - We have submitted a total of 2,300+ PRs, most of them have been merged > > or closed. > > - We have met all maturity criteria as outlined in [6]. > > > > We've resolved all branding issues which include Logo, GitHub repo, > > document, website, and others. > > > > I'd also like to take this opportunity to extend a heartfelt thank you to > > our > > mentors. Your timely assistance throughout the incubation period was > > invaluable, > > and we're grateful for your support in answering our numerous questions. > > > > Thanks a lot, Sheng Wu, Ted Liu, Willem Ning Jiang, Xiaoqiao He and Zili > > Chen! > > > > --- > > > > Establish the Apache OpenDAL Project > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > the Foundation and consistent with the Foundation's purpose to establish > > a Project Management Committee charged with the creation and maintenance > > of open-source software, for distribution at no charge to the public, > > related to Open Data Access Layer: Access data freely, painlessly, and > > efficiently. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache OpenDAL Project", be and hereby is > > established pursuant to Bylaws of the Foundation; and be it further > > > > RESOLVED, that the Apache OpenDAL Project be and hereby is responsible > > for the creation and maintenance of software related to Open Data Access > > Layer: Access data freely, painlessly, and efficiently; and be it > > further > > > > RESOLVED, that the office of "Vice President, Apache OpenDAL" be and > > hereby is created, the person holding such office to serve at the > > direction of the Board of Directors as the chair of the Apache OpenDAL > > Project, and to have primary responsibility for management of the > > projects within the scope of responsibility of the Apache OpenDAL > > Project; and be it further > > > > RESOLVED, that the persons listed immediately below be and hereby are > > appointed to serve as the initial members of the Apache OpenDAL Project: > > > > * Cai Lue > > * Chojan Shang > > * Han Xu > > * Hao Ding > > * Jun Ouyang > > * Mingzhuo Yin > > * Sheng Wu > > * Sundy Li > > * Ted Liu > > * Willem Ning Jiang > > * Xiangdong > > * Xiaoqiao He > > * Zheao Li > > * Zili Chen > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hao Ding be appointed to > > the office of Vice President, Apache OpenDAL, to serve in accordance > > with and subject to the direction of the Board of Directors and the > > Bylaws of the Foundation until death, resignation, retirement, removal > > or disqualification, or until a successor is appointed; and be it > > further > > > > RESOLVED, that the Apache OpenDAL Project be and hereby is tasked with > > the migration and rationalizat
Re: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1
Glad to help. Suggest canceling this vote, and enhancing your release process doc, then, start a new one with a correct signature from the release manager. Notice, don't remove anyone's KEY from KEYS, ever, even it is expired. People may need them to verify your legacy releases in the future. Sheng Wu 吴晟 Twitter, wusheng1108 LinkinStar 于2023年12月20日周三 15:53写道： > > Hello Sheng Wu, > > Yes, I misunderstood. I thought KEYS can only contain one public key, no > other public keys are allowed to exist at the same time. That's why I was > forced to do this signature. It helped me solve a real problem. Thanks a > lot. > > Best regards, > LinkinStar > > On Wed, Dec 20, 2023 at 3:45 PM Sheng Wu wrote: > > > KEYS is a very for all existing public keys. Not for a specific > > individual. Are you misunderstanding this? > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > LinkinStar 于2023年12月20日周三 15:31写道： > > > > > > Hi Xuanwo, > > > > > > Thank you very much for your suggestions. I'm very sorry, perhaps my > > > understanding of the release signature is a little misguided. This is > > > because we feel that there can only be one download address for KEYS, > > e.g. > > > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS. If > > there > > > can only be one public key, then there can only be one private key. So we > > > previously felt that all published content can always have only one > > private > > > key to sign. That's why we use this mode. Because we would think that if > > a > > > different person were to sign it, then the public key would change and > > the > > > previous release would not be verified. For example, The A RM signed the > > > released version 1.0.0. The B RM signed the released version 1.1.0. If B > > > replaces the public key > > > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS, then > > > version 1.0.0 will fail to verify it if you use the same public key. > > > > > > Best regards, > > > LinkinStar > > > > > > On Wed, Dec 20, 2023 at 3:06 PM Xuanwo wrote: > > > > > > > > Regarding the signature issue you mentioned, only release manager and > > > > joyqi > > > > > know the secret GPG keys. This is to ensure that no matter what the > > > > problem > > > > > is, there is someone available to help resolve issues that arise in > > the > > > > > release. > > > > > > > > I feel like it's better to use different gpg keys that owned by RM > > > > themselves. > > > > > > > > As the community expands, we'll welcome new PPMC members and Release > > > > Managers (RMs) from outside your company. Regarding security, it's > > risky > > > > for RMs to share GPG keys. In terms of community independence, the > > release > > > > process should not be overly reliant on joyqi. Should joyqi be > > unavailable > > > > or preoccupied, can the release process continue without interruption? > > > > > > > > On Wed, Dec 20, 2023, at 14:57, LinkinStar wrote: > > > > > Hi Xuanwo, > > > > > > > > > > Firstly, these files in the vaunt folder are reward badges for user > > > > > contributions. For now, we are using it. > > > > > Regarding the signature issue you mentioned, only release manager and > > > > joyqi > > > > > know the secret GPG keys. This is to ensure that no matter what the > > > > problem > > > > > is, there is someone available to help resolve issues that arise in > > the > > > > > release. > > > > > > > > > > Best regards, > > > > > LinkinStar > > > > > > > > > > On Wed, Dec 20, 2023 at 2:41 PM Xuanwo wrote: > > > > > > > > > >> Hi, > > > > >> > > > > >> I found those images are included in source tarball: > > > > >> > > > > >> - .vaunt/bug.png > > > > >> - .vaunt/enhancement.png > > > > >> > > > > >> Are they needed by users? Is it possible to remove them from the src > > > > >> release? > > > > >> > > > > >> Regarding PGP signatures, I'm confident that all are valid. But I > > found > > > > >> that those tarball > > > > >> are signed by jo...@apache.org wh
Re: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1
KEYS is a very for all existing public keys. Not for a specific individual. Are you misunderstanding this? Sheng Wu 吴晟 Twitter, wusheng1108 LinkinStar 于2023年12月20日周三 15:31写道： > > Hi Xuanwo, > > Thank you very much for your suggestions. I'm very sorry, perhaps my > understanding of the release signature is a little misguided. This is > because we feel that there can only be one download address for KEYS, e.g. > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS. If there > can only be one public key, then there can only be one private key. So we > previously felt that all published content can always have only one private > key to sign. That's why we use this mode. Because we would think that if a > different person were to sign it, then the public key would change and the > previous release would not be verified. For example, The A RM signed the > released version 1.0.0. The B RM signed the released version 1.1.0. If B > replaces the public key > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS, then > version 1.0.0 will fail to verify it if you use the same public key. > > Best regards, > LinkinStar > > On Wed, Dec 20, 2023 at 3:06 PM Xuanwo wrote: > > > > Regarding the signature issue you mentioned, only release manager and > > joyqi > > > know the secret GPG keys. This is to ensure that no matter what the > > problem > > > is, there is someone available to help resolve issues that arise in the > > > release. > > > > I feel like it's better to use different gpg keys that owned by RM > > themselves. > > > > As the community expands, we'll welcome new PPMC members and Release > > Managers (RMs) from outside your company. Regarding security, it's risky > > for RMs to share GPG keys. In terms of community independence, the release > > process should not be overly reliant on joyqi. Should joyqi be unavailable > > or preoccupied, can the release process continue without interruption? > > > > On Wed, Dec 20, 2023, at 14:57, LinkinStar wrote: > > > Hi Xuanwo, > > > > > > Firstly, these files in the vaunt folder are reward badges for user > > > contributions. For now, we are using it. > > > Regarding the signature issue you mentioned, only release manager and > > joyqi > > > know the secret GPG keys. This is to ensure that no matter what the > > problem > > > is, there is someone available to help resolve issues that arise in the > > > release. > > > > > > Best regards, > > > LinkinStar > > > > > > On Wed, Dec 20, 2023 at 2:41 PM Xuanwo wrote: > > > > > >> Hi, > > >> > > >> I found those images are included in source tarball: > > >> > > >> - .vaunt/bug.png > > >> - .vaunt/enhancement.png > > >> > > >> Are they needed by users? Is it possible to remove them from the src > > >> release? > > >> > > >> Regarding PGP signatures, I'm confident that all are valid. But I found > > >> that those tarball > > >> are signed by jo...@apache.org which is not the release manager. > > >> > > >> Are you internally sharing jo...@apache.org's secret GPG keys? Or have > > >> you signed those > > >> tarballs through CI with the key stored as GitHub secrets? > > >> > > >> On Wed, Dec 20, 2023, at 14:25, LinkinStar wrote: > > >> > Hello, > > >> > > > >> > This is a call for vote to release Apache Answer(Incubating) > > version > > >> > v1.2.1-RC1. > > >> > > > >> > The vote thread: > > >> > > > https://lists.apache.org/thread/w9ybd1rygd4x9o9ryx3k2ho3n49664p6 > > >> > > > >> > Vote Result: > > >> > > > https://lists.apache.org/thread/7h9rmwn7fbrn7dhk1620lzj43063r7vj > > >> > > > >> > The release candidates: > > >> > > > >> > > > >> > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.1-incubating-RC1/ > > >> > > > >> > Release notes: > > >> > > > >> https://github.com/apache/incubator-answer/releases/tag/v1.2.1-RC1 > > >> > > > >> > Git tag for the release: > > >> > > > >> https://github.com/apache/incubator-answer/releases/tag/v1.2.1-RC1 > > >> > > > >> > Git commit id for the release: > > >> > > > >> > > >
Re: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1
LinkinStar 于2023年12月20日周三 14:57写道： > > Hi Xuanwo, > > Firstly, these files in the vaunt folder are reward badges for user > contributions. For now, we are using it. > Regarding the signature issue you mentioned, only release manager and joyqi > know the secret GPG keys. This is to ensure that no matter what the problem > is, there is someone available to help resolve issues that arise in the > release. This doesn't make sense. If the private key is shared, then that key should not be used anymore. If the key isn't shared, why joyqi could sign, but doesn't call out for a vote? If you are a member of PPMC, you could add your own key(signed by your Apache ID), and sign the tar. Generally, unless there are some special cases, you should not start a vote on others' signed tars. > > Best regards, > LinkinStar > > On Wed, Dec 20, 2023 at 2:41 PM Xuanwo wrote: > > > Hi, > > > > I found those images are included in source tarball: > > > > - .vaunt/bug.png > > - .vaunt/enhancement.png > > > > Are they needed by users? Is it possible to remove them from the src > > release? > > > > Regarding PGP signatures, I'm confident that all are valid. But I found > > that those tarball > > are signed by jo...@apache.org which is not the release manager. > > > > Are you internally sharing jo...@apache.org's secret GPG keys? Or have > > you signed those > > tarballs through CI with the key stored as GitHub secrets? > > > > On Wed, Dec 20, 2023, at 14:25, LinkinStar wrote: > > > Hello, > > > > > > This is a call for vote to release Apache Answer(Incubating) version > > > v1.2.1-RC1. > > > > > > The vote thread: > > > https://lists.apache.org/thread/w9ybd1rygd4x9o9ryx3k2ho3n49664p6 > > > > > > Vote Result: > > > https://lists.apache.org/thread/7h9rmwn7fbrn7dhk1620lzj43063r7vj > > > > > > The release candidates: > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.1-incubating-RC1/ > > > > > > Release notes: > > > > > https://github.com/apache/incubator-answer/releases/tag/v1.2.1-RC1 > > > > > > Git tag for the release: > > > > > https://github.com/apache/incubator-answer/releases/tag/v1.2.1-RC1 > > > > > > Git commit id for the release: > > > > > > > > https://github.com/apache/incubator-answer/commit/82fdfc77636d8d1ce28710d929a8c22bb52834ef > > > > > > Keys to verify the Release Candidate: > > > https://dist.apache.org/repos/dist/release/incubator/answer/KEYS > > > > > > The vote will be open for at least 72 hours or until the necessary > > > number of votes are reached. > > > > > > Please vote accordingly: > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > [ ] Checksums and PGP signatures are valid. > > > [ ] Source code distributions have correct names matching the current > > > release. > > > [ ] LICENSE and NOTICE files are correct for each Answer repo. > > > [ ] All files have license headers if necessary. > > > [ ] No unlicensed compiled archives bundled in source archive. > > > > > > To compile from the source, please refer to: > > > > > > https://github.com/apache/incubator-answer#building-from-source > > > > > > Thanks, > > > LinkinStar > > > > -- > > Xuanwo > > > > - > > 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
[RESULT] [VOTE] Accept Seata Into the ASF Incubator
Hi Within 8 days of voting, we have received 13 +1 binding and 6 +1 no-binding, the vote passed. Welcome Seata to the ASF incubator. The vote details are as follows Binding votes(+13): - Sheng Wu - PJ Fanning - Jean-Baptiste Onofré - Huxing Zhang - Heng Du - Furkan KAMACI - Willem Jiang - Xin Wang - Xinyu Zhou - Xiaorui Wang - Kevin Ratnasekera - Xiangdong Huang - Ayush Saxena Non-binding votes(+6): - Xin Wang - Eason Chen - Kent Yao - Bertil Chapuis - Jialin Qiao - ConradJam Sheng Wu 吴晟 Twitter, wusheng1108 Sheng Wu 于2023年10月29日周日 15:10写道： > > Thanks, everyone for the voting. > I am closing this vote and going to send the RESULT mail soon. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > Ayush Saxena 于2023年10月27日周五 11:15写道： > > > > +1(Binding) > > > > -Ayush > > > > > On 26-Oct-2023, at 5:28 PM, ConradJam wrote: > > > > > > +1 (non-binding) > > > > > > > > > Xiangdong Huang 于2023年10月26日周四 10:22写道： > > > > > >> +1 binding. > > >> --- > > >> Xiangdong Huang > > >> Kevin Ratnasekera 于2023年10月25日周三 20:17写道： > > >>> +1 (binding) > > >>> On Wed, Oct 25, 2023 at 1:13 PM Xiaorui Wang > > >>> wrote: > > >>>> +1 binding > > >>>> Best regards, > > >>>> Xiaorui Wang https://github.com/vintagewang > > >>>> On Wed, Oct 25, 2023 at 5:44 PM Xinyu Zhou wrote: > > >>>>> +1 binding > > >>>>> Regards, > > >>>>> Xinyu Zhou > > >>>>> On Wed, Oct 25, 2023 at 5:40 PM Willem Jiang > >>>>> wrote: > > >>>>>> +1 binding. > > >>>>>> Willem Jiang > > >>>>>> Twitter: willemjiang > > >>>>>> Weibo: 姜宁willem > > >>>>>> On Sat, Oct 21, 2023 at 8:51 PM Sheng Wu < > > >> wu.sheng.841...@gmail.com> > > >>>>>> wrote: > > >>>>>>> Hi Incubator > > >>>>>>> Following the discussion from <[DISCUSS] Incubating Proposal of > > >>>>>> Seata>[1], > > >>>>>>> I am starting this official vote for the Seata project. > > >>>>>>> Here is their proposal, > > >>> https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal > > >>>>>>> Please cast your vote: > > >>>>>>> [ ] +1, bring into the Incubator > > >>>>>>> [ ] +0, I don't care either way > > >>>>>>> [ ] -1, do not bring Seata into the Incubator, because... > > >>>>>>> The vote will open for one week from today, Oct. 21st, 2023 > > >>>>>>> [1] > > >>> https://lists.apache.org/thread/jtg7tt725r9mf35gqxph65vz8gdbwq94 > > >>>>>>> Sheng Wu 吴晟 > > >>>>>>> Twitter, wusheng1108 > > >>> - > > >>>>>>> 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 > > > > > > > > > -- > > > Best > > > > > > ConradJam > > > > - > > 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] Accept Seata Into the ASF Incubator
Thanks, everyone for the voting. I am closing this vote and going to send the RESULT mail soon. Sheng Wu 吴晟 Twitter, wusheng1108 Ayush Saxena 于2023年10月27日周五 11:15写道： > > +1(Binding) > > -Ayush > > > On 26-Oct-2023, at 5:28 PM, ConradJam wrote: > > > > +1 (non-binding) > > > > > > Xiangdong Huang 于2023年10月26日周四 10:22写道： > > > >> +1 binding. > >> --- > >> Xiangdong Huang > >> Kevin Ratnasekera 于2023年10月25日周三 20:17写道： > >>> +1 (binding) > >>> On Wed, Oct 25, 2023 at 1:13 PM Xiaorui Wang > >>> wrote: > >>>> +1 binding > >>>> Best regards, > >>>> Xiaorui Wang https://github.com/vintagewang > >>>> On Wed, Oct 25, 2023 at 5:44 PM Xinyu Zhou wrote: > >>>>> +1 binding > >>>>> Regards, > >>>>> Xinyu Zhou > >>>>> On Wed, Oct 25, 2023 at 5:40 PM Willem Jiang >>>>> wrote: > >>>>>> +1 binding. > >>>>>> Willem Jiang > >>>>>> Twitter: willemjiang > >>>>>> Weibo: 姜宁willem > >>>>>> On Sat, Oct 21, 2023 at 8:51 PM Sheng Wu < > >> wu.sheng.841...@gmail.com> > >>>>>> wrote: > >>>>>>> Hi Incubator > >>>>>>> Following the discussion from <[DISCUSS] Incubating Proposal of > >>>>>> Seata>[1], > >>>>>>> I am starting this official vote for the Seata project. > >>>>>>> Here is their proposal, > >>> https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal > >>>>>>> Please cast your vote: > >>>>>>> [ ] +1, bring into the Incubator > >>>>>>> [ ] +0, I don't care either way > >>>>>>> [ ] -1, do not bring Seata into the Incubator, because... > >>>>>>> The vote will open for one week from today, Oct. 21st, 2023 > >>>>>>> [1] > >>> https://lists.apache.org/thread/jtg7tt725r9mf35gqxph65vz8gdbwq94 > >>>>>>> Sheng Wu 吴晟 > >>>>>>> Twitter, wusheng1108 > >>> - > >>>>>>> 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 > > > > > > -- > > Best > > > > ConradJam > > - > 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] Accept Seata Into the ASF Incubator
My own +1 binding Sheng Wu 吴晟 Twitter, wusheng1108 Kent Yao 于2023年10月23日周一 23:49写道： > > +1 (non-binding), good luck. > > Kent > > Eason Chen 于2023年10月23日周一 14:21写道： > > > > +1 (non-binding) > > > > Good luck! > > > > On Mon, Oct 23, 2023 at 11:24 AM Xin Wang wrote: > > > > > > +1 (non-binding) > > > > > > Good luck! > > > > > > Xin Wang > > > > > > Jialin Qiao 于2023年10月23日周一 09:42写道： > > > > > > > +1, Good luck! > > > > — > > > > Jialin Qiao > > > > Apache IoTDB PMC > > > > > > > > Huxing Zhang 于2023年10月23日周一 09:39写道： > > > > > > > > > > +1 (binding) > > > > > > > > > > Good luck! > > > > > > > > > > On Sat, Oct 21, 2023 at 8:51 PM Sheng Wu > > > > wrote: > > > > > > > > > > > > Hi Incubator > > > > > > > > > > > > Following the discussion from <[DISCUSS] Incubating Proposal of > > > > Seata>[1], > > > > > > I am starting this official vote for the Seata project. > > > > > > > > > > > > Here is their proposal, > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > [ ] +1, bring into the Incubator > > > > > > [ ] +0, I don't care either way > > > > > > [ ] -1, do not bring Seata into the Incubator, because... > > > > > > > > > > > > The vote will open for one week from today, Oct. 21st, 2023 > > > > > > > > > > > > [1] https://lists.apache.org/thread/jtg7tt725r9mf35gqxph65vz8gdbwq94 > > > > > > > > > > > > > > > > > > Sheng Wu 吴晟 > > > > > > Twitter, wusheng1108 > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best Regards！ > > > > > Huxing > > > > > > > > > > - > > > > > 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: [VOTE] Accept Seata Into the ASF Incubator
PJ Fanning 于2023年10月21日周六 21:47写道： > > +1 (binding) > > Seata seems to be in good shape. > > One minor nit - the dependency list in > https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal > has a great deal out of outdated dependencies - with a large number of > CVEs associated with them. Thanks for pointing out. Yes, this should be on the TODO list as a high priority. I have created an issue to track this, https://github.com/seata/seata/issues/5945 > > > On Sat, 21 Oct 2023 at 13:52, Sheng Wu wrote: > > > > Hi Incubator > > > > Following the discussion from <[DISCUSS] Incubating Proposal of Seata>[1], > > I am starting this official vote for the Seata project. > > > > Here is their proposal, > > https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal > > > > Please cast your vote: > > > > [ ] +1, bring into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring Seata into the Incubator, because... > > > > The vote will open for one week from today, Oct. 21st, 2023 > > > > [1] https://lists.apache.org/thread/jtg7tt725r9mf35gqxph65vz8gdbwq94 > > > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > - > > 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
[VOTE] Accept Seata Into the ASF Incubator
Hi Incubator Following the discussion from <[DISCUSS] Incubating Proposal of Seata>[1], I am starting this official vote for the Seata project. Here is their proposal, https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal Please cast your vote: [ ] +1, bring into the Incubator [ ] +0, I don't care either way [ ] -1, do not bring Seata into the Incubator, because... The vote will open for one week from today, Oct. 21st, 2023 [1] https://lists.apache.org/thread/jtg7tt725r9mf35gqxph65vz8gdbwq94 Sheng Wu 吴晟 Twitter, wusheng1108 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of Seata
Hi IPMC Is there any concern left before initializing the vote? I hope we have addressed most before the start. I can see the Seata project is open to learning more about the ASF culture in the incubating process. It is not perfect and fully compatible with ASF yet, this is the point of the whole incubating. Sheng Wu 吴晟 Twitter, wusheng1108 Min Ji 于2023年10月17日周二 12:30写道： > > Hi, > > > In the proposal, you mention having added people to the committer team. How > > many people have you added and what were their company affiliations since > > making the project open-source? From the proposal, it seems only people > > affiliated with Alibaba and Ant Group have been made committers? Is this > > correct? > > The affiliations of the Committers' companies are included in the > "Required Resources#Affiliations" section. Apart from Alibaba and Ant > Group, they come from companies such as TongDun, EWorld, 360, TruthAI, > DaShenLin, JD, Helios, and others. It is a community with a diverse > group of Committers. > > > > Regarding risks, you mention that a large number of companies use the > > project, but they seem reliant on Alibaba and Ant Group. What would happen > > if one of these companies changed direction and decided to no longer > > contribute to the project? > > The technical development of the Seata community is driven by the > community itself, and it strives to create a technologically neutral > community whose direction of development relies on the consensus > mechanism of the community. Even if colleagues from Alibaba and Ant > Group are no longer involved, it will not affect the development of > the community. The possibility of such an incident occurring is almost > impossible, as within Alibaba and Ant Group, Seata has already been > used as a critical infrastructure application in order transaction and > payment scenarios. > > > > Many companies have their own forks of the project. Why are they currently > > developing outside the project? > > The Seata community is very willing to accept and often merge the PRs > submitted by other companies. There are many reasons why they choose > to keep their contributions as private forks and not contribute to the > project. Common reasons include: personalized needs, company policies, > or private infrastructure, etc. > > > > What will happen to the website at Seata.io <http://seata.io/> after the > > project joins teh ASF? > > The domain seata.io will be CNAME to the subdomain allocated to Seata > by Apache. The existing content of the official website will be > migrated to the new official website. The new display content will be > modified according to Apache's requirements for project websites. > > > > You say that no CCLAs from other companies are needed, but you have listed > > several people with their affiliations in the initial committer list. The > > Alibaba ICLA doesn't transfer copyright, so the ASF will need ICLA or CCLAs > > from those people and anyone else who has contributed significantly to the > > project. > > All initial committers are ready to sign the CCLA or ICLA with ASF. > > > > Min Ji describes themselves as “The Founder of Seata”. Are they willing to > > no longer refer to themselves in that way once it becomes an Apache > > project? The ASF doesn’t allow dictators (benevolent or otherwise) is this > > understood by the people putting together the proposal? > > I think I understand this. > > - > 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: Re: [DISCUSS] Incubating Proposal of Seata
Hi Zhiyuan Lei I have added you as an initial committer, and listed as Tencent on the Affiliations part. Welcome to the project community. To Min Ji, the proposal updated. https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal Sheng Wu 吴晟 Twitter, wusheng1108 Min Ji 于2023年10月17日周二 12:10写道： > > Zhiyuan Lei, welcome to join as an initial committer! We look > forward to your greater contributions during the incubation period. > > Hi, Sheng Wu. I think we need to make a modification to the initial > committer list section in the proposal, adding "Zhiyuan Lei" to the > list. > > 雷志远 于2023年10月14日周六 23:47写道： > > > > Hi, I am a committer of Seata: > > https://seata.io/en/docs/developers/developers_dev/ name：leizhiyuan > > > > My main contributions are implementing full support for the protobuf > > protocol in Seata, fixing multiple bugs, making some code optimizations, > > and providing support for user usage. > > > > I am very happy to see Seata joining Apache’s incubator and I would like to > > continue contributing as an initial committer to Seata. > > > > On 2023/10/14 09:49:28 Sheng Wu wrote: > > > Jean-Baptiste Onofré 于2023年10月14日周六 14:04写道： > > > > > > > > Hi > > > > > > > > It's a very interesting project and proposal. > > > > > > > > As Seata is already an Open Source project for a while, why going to > > > > an ASF project now ? > > > > The idea is to grow the community and/or to have an open governance ? > > > > > > This proposal was initialized one year ago. It took a lot of time to > > > make the two enterprises (Ant Group and Alibaba) to approve this > > > donation. > > > > > > The initial idea I got from the team is for a better and more healthy > > > community. Also, they hope more users out of China mainland to adopt > > > this solution/project. > > > They believe the ASF is a good place. > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > > > > > > Just curious :) > > > > > > > > Thanks, > > > > Regards > > > > JB > > > > > > > > On Wed, Oct 11, 2023 at 8:36 AM Sheng Wu wrote: > > > > > > > > > > Hi Incubator > > > > > > > > > > I would like to propose a new project to the ASF incubator - Seata. > > > > > > > > > > Seata[1] is an open-source distributed transaction solution that > > > > > delivers high-performance and easy-to-use distributed transaction > > > > > services under a microservices architecture. > > > > > This project is owned by Alibaba and Ant Group. They have agreed to > > > > > sign the SGAs and CCLAs for the donation. > > > > > > > > > > Here is their proposal, > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal > > > > > > > > > > I would be the Champion of the project. I am going to mentor and help > > > > > the project go through the incubator with Justin Mclean(justin at > > > > > classsoftware dot com), Huxing Zhang(huxing at apache dot org), and > > > > > Heng Du(duhengforever at apache dot org). > > > > > > > > > > So far, the project has a large user group and diverse dev team, it is > > > > > healthy and moving forward. > > > > > Within the ASF requirements, the MySQL dependency is the major issue > > > > > we need to resolve after being accepted due to GPL limitations. The > > > > > project community has supported to use other databases such as > > > > > PostgreSQL, they just need to remove the MySQL driver from the binary > > > > > and keep it optional. > > > > > > > > > > We are open to hearing the feedback from the incubator. > > > > > > > > > > [1] https://seata.io/en/ > > > > > > > > > > Sheng Wu 吴晟 > > > > > Twitter, wusheng1108 > > > > > > > > > > - > > > > > 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: [DISCUSS] Incubating Proposal of Seata
Jean-Baptiste Onofré 于2023年10月14日周六 14:04写道： > > Hi > > It's a very interesting project and proposal. > > As Seata is already an Open Source project for a while, why going to > an ASF project now ? > The idea is to grow the community and/or to have an open governance ? This proposal was initialized one year ago. It took a lot of time to make the two enterprises (Ant Group and Alibaba) to approve this donation. The initial idea I got from the team is for a better and more healthy community. Also, they hope more users out of China mainland to adopt this solution/project. They believe the ASF is a good place. Sheng Wu 吴晟 Twitter, wusheng1108 > > Just curious :) > > Thanks, > Regards > JB > > On Wed, Oct 11, 2023 at 8:36 AM Sheng Wu wrote: > > > > Hi Incubator > > > > I would like to propose a new project to the ASF incubator - Seata. > > > > Seata[1] is an open-source distributed transaction solution that > > delivers high-performance and easy-to-use distributed transaction > > services under a microservices architecture. > > This project is owned by Alibaba and Ant Group. They have agreed to > > sign the SGAs and CCLAs for the donation. > > > > Here is their proposal, > > https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal > > > > I would be the Champion of the project. I am going to mentor and help > > the project go through the incubator with Justin Mclean(justin at > > classsoftware dot com), Huxing Zhang(huxing at apache dot org), and > > Heng Du(duhengforever at apache dot org). > > > > So far, the project has a large user group and diverse dev team, it is > > healthy and moving forward. > > Within the ASF requirements, the MySQL dependency is the major issue > > we need to resolve after being accepted due to GPL limitations. The > > project community has supported to use other databases such as > > PostgreSQL, they just need to remove the MySQL driver from the binary > > and keep it optional. > > > > We are open to hearing the feedback from the incubator. > > > > [1] https://seata.io/en/ > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > - > > 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: [VOTE] Release Apache OpenDAL(incubating) 0.41.0-rc.1 - Incubator Vote Round 1
+1 binding. 1. Version checked. 2. Download link correct 3. Compiling passed for core(rust), python, nodejs, Java(jar with aarm) 4. asc checked 5. LICENSE and NOTICE exist Sheng Wu 吴晟 Twitter, wusheng1108 Xuanwo 于2023年10月13日周五 01:27写道： > > Carry my non-binding +1 vote from OpenDAL community. > > On Thu, Oct 12, 2023, at 15:30, Suyan wrote: > > Hello Incubator PMC, > > > > The Apache OpenDAL community has voted and approved the release of Apache > > OpenDAL(incubating) 0.41.0-rc.1. We would like to request the IPMC members > > to review and vote for this release. > > > > OpenDAL is a data access layer that allows users to easily and efficiently > > retrieve data from various storage services in a unified way. > > > > OpenDAL community vote thread: > > > > https://lists.apache.org/thread/zwr6m8qpgj82r7wkxmnovb6yv19hl7ng > > > > Vote result thread: > > > > https://lists.apache.org/thread/lm5t2f6v31lp8bmltoppqsxowxvos89x > > > > The release candidate: > > > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.41.0-rc.1/ > > > > This release has been signed with a PGP available here: > > > > https://downloads.apache.org/incubator/opendal/KEYS > > > > Git tag for the release: > > > > https://github.com/apache/incubator-opendal/releases/tag/v0.41.0-rc.1/ > > > > Maven staging repo: > > > > https://repository.apache.org/content/repositories/orgapacheopendal-1015/ > > > > Please download, verify, and test. > > > > The VOTE will be open for at least 72 hours and until the necessary > > number of votes are reached. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > To learn more about Apache OpenDAL(incubating), please see > > https://opendal.apache.org/ > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > More detailed checklist please refer to: > > https://github.com/apache/incubator-opendal/tree/main/scripts > > > > To compile from the source, please refer to: > > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > > > Here is a Python script in release to help you verify the release candidate: > > > > ./scripts/verify.py > > > > Thanks > > > > Sincerely, > > Suyan > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > -- > Xuanwo > > - > 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
[DISCUSS] Incubating Proposal of Seata
Hi Incubator I would like to propose a new project to the ASF incubator - Seata. Seata[1] is an open-source distributed transaction solution that delivers high-performance and easy-to-use distributed transaction services under a microservices architecture. This project is owned by Alibaba and Ant Group. They have agreed to sign the SGAs and CCLAs for the donation. Here is their proposal, https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal I would be the Champion of the project. I am going to mentor and help the project go through the incubator with Justin Mclean(justin at classsoftware dot com), Huxing Zhang(huxing at apache dot org), and Heng Du(duhengforever at apache dot org). So far, the project has a large user group and diverse dev team, it is healthy and moving forward. Within the ASF requirements, the MySQL dependency is the major issue we need to resolve after being accepted due to GPL limitations. The project community has supported to use other databases such as PostgreSQL, they just need to remove the MySQL driver from the binary and keep it optional. We are open to hearing the feedback from the incubator. [1] https://seata.io/en/ Sheng Wu 吴晟 Twitter, wusheng1108 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Answer into the Apache Incubator
+1 binding Good luck. Sheng Wu 吴晟 Twitter, wusheng1108 Willem Jiang 于2023年10月3日周二 08:17写道： > > Following up the [DISCUSS] thread on Answer [1] I would like to call a > VOTE to accept into the Apache Incubator. > > Answer is a question-and-answer (Q) platform software for teams at > any scale to build a help center, knowledge base, community forum, > etc. > > Please cast your vote: > > [ ] +1, bring into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring Answer into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > Please check out the Answer Proposal from the incubator wiki[2]. > > [1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal > > Best Regards, > > 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of Answer
I think it is good to go. Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 tison 于2023年9月29日 周五15:48写道： > This proposal should be good to go :D > > Best, > tison. > > > Willem Jiang 于2023年9月28日周四 18:34写道： > > > Hi, > > > > After talking with the Answer development team about the brand name > > issue, there is some feedback from the team. > > They still want to use the answer as the project name, and they don't > > plan to provide commercial products or online services based on this > > project so far. > > > > Please let me know if there are any other concerns about this project. > > I will start a vote next week if there are no other objections. > > > > Best regards, > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Sep 21, 2023 at 11:14 PM tison wrote: > > > > > > 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 the > > > pros and cons. > > > > > > Let's say we don't have a blocker here but potential trade-offs. Apache > > > Arrow can be > > > a compare whose name is also a common word, and the community built up > > the > > > brand recognition so the name is associated with the project. > > > > > > Best, > > > tison. > > > > > > > > > Willem Jiang 于2023年9月21日周四 23:00写道： > > > > > > > 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: willemjiang > > > > Weibo: 姜宁willem > > > > On Thu, Sep 21, 2023 at 9:36 PM PJ Fanning > > wrote: > > > > > > > > > > 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 we should stop calling our projects > Apache > > > > > XYZ yet but I just think the XYZ needs to work as a standalone > > project > > > > > name too. Even something like 'Answer Platform' and 'Apache Answer > > > > > Platform' might make the name more specific. Imagine trying to > search > > > > > online for 'Answer'. There are more than 14 billion matches on > > Google. > > > > > > > > > > On Thu, 21 Sept 2023 at 13:51, Sheng Wu > > > > > wrote: > > > > > > > > > > > > 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 > > > > > > > proposal (in more details). > > > > > > > > > > > > > > Regards > > > > > > > JB > > > > > > > > > > > > > > On Thu, Sep 21, 2023 at 2:00 PM Willem Jiang < > > willem.ji...@gmail.com> > > > > wrote: > > > > > > > > > > > > > > > > We want to propose Answer as a new Apache Incubator project. > > > > > > > > > > > > > > > > Answer[1] is a question-and-answer (Q) platform software > for > > > >
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写道： > > 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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 > 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) 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 your > > users and team. > > 2. Content Organization and Management - Organize your content with > > flag, moderation, and permission. > > 3. Content Management - Manage topics and discussions in the community > > with tags. > > 4. Reputation - Reward users for their contribution: answer, verify, > > and upvote correct info. Always keep the information up-to-date. > > > > I'd be happy to be the Champion of this project, and may Thanks to > > Zili Chen ， Justin Mclean > apache.org>, and Christofer Dutz for mentoring > > the answer project and helping us polish the incubating proposal[2]. > > > > The word answer is a generic name, and trademarking it is impossible. > > But if we add the prefix of Apache, it could be more reasonable to > > use. I look forward to your feedback and thank you for your help. > > > > [1]https://github.com/answer.dev/ > > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal > > > > Best regards, > > > > 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 > > > > - > 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] Incubating Proposal for OzHera
Hi Please notice the term, IPMC represents Incubator Project Management Committees, there is only one IPMC, no (s). You could say members of IPMC. This is happening repeatedly. Please correct in the next time. Sheng Wu 吴晟 Apache SkyWalking Twitter, wusheng1108 Yu Xiao 于2023年9月9日 周六21:12写道： > Hi Justin, > > Thank you so much for your reply and advice. > > I will discuss with the current mentors about the suggestion and also > try to find new mentors to increase the diversity. > > The project leaders have already started working on the issues raised > by other IPMCs, such as "Initial committers proposal", "Ozhera > separation from Mone", "IP and License clean" etc. > > Hope I could share a refined proposal in the near future! > > Best wishes! > > 于2023年9月9日周六 11:56写道： > > > > Hi, > > > > For instance, I see your 4th higher committer doesn't seem to be on the > initial committers list? > > > > 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] Incubating Proposal for OzHera
Sheng Wu 于2023年9月6日周三 22:52写道： > > They are already beginning to remove the screenshots and comments that > have proved the UI copy behaviors. > They had known that and did that intentionally. > > Screenshots, https://twitter.com/wusheng1108/status/1699432297429114959. > Now, if you see the issue again, it is > gone.https://github.com/XiaoMi/mone/issues/689 > > They have admitted their UIs are similar(most likely directly > referring) to Aliyun Yunxiao commercial services. (Translation from > their top3 maintainer's feedback) > > Anyway, I think the evidence is clear, there are bigger issues than > `too-early-to-join`. > AFAIK, the project and the maintainers are not suitable for ASF > culture, even hard to say good enough in the OSS culture. > > More and more China local foundation members and PPMC members are > showing up to share their concerns and consensus of saying NO to the > project. > They have all the right to do things on their own, but let's keep the > foundation and incubator safe from this kind of chaos. One update, Xiaomi Inc. and Aliyun Inc. seem to have some confident agreement on this issue. The issue title has been updated as `have settled`(translated from Chinese). And original complaint had been removed too. I want to point out, this doesn't mean it is good for the foundation. >From the current statement, we can only guess there are conflicts, but they have an agreement. But they don't declare that the UI design is IP clearance. This should be hold as a potential IP issue. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > tison 于2023年9月6日周三 22:36写道： > > > > > attaching the screenshot > > > > I don't see an attachment in your email. If you paste the screenshot > > inline, it can be filtered out by mailing list policy. You can attach a > > file or upload it to an external image hosting service. > > > > Best, > > tison. > > > > > > Sheng Wu 于2023年9月6日周三 21:23写道： > > > > > One more update. > > > With this project being noticed by this project, the parent project is > > > facing the challenge of copying from Ali Yunxiao, which is one of the > > > Aliyun commercial services. > > > Ref source in CN, https://github.com/XiaoMi/mone/issues/689, attaching > > > the screenshot in case of the owner deleted this issue. > > > > > > The good thing is, that this is not the ASF and incubator issue, we > > > don't have an obligation to prove this is true or false. > > > But this is a validation of my feelings that this project was not > > > audited carefully, although one of them declared they are. > > > > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > Calvin Kirs 于2023年9月6日周三 20:15写道： > > > > > > > > Is this a (community) with only 38 issues? > > > > There are tons of commits from the community. How does the decision > > > > happen? ok, I saw this, relying on Gitter[1] with only 6 people and 8 > > > > messages? > > > > > > > > pls forgive me, after reviewing your proposal > > > > I really don’t know how to describe it. > > > > > > > > [1]https://app.gitter.im/#/room/#monegrow_community:gitter.im > > > > > > > > On Wed, Sep 6, 2023 at 6:14 PM Zhiyong Zhang > > > wrote: > > > > > > > > > > Without Mone, OzHera can be used independently. Currently, in addition > > > to Xiaomi, there are also some external manufacturers using or researching > > > it. Mone is a larger collection within Xiaomi, and we are considering open > > > sourcing all of it in the future (which includes cicd rpc, registration > > > center, container management, stress testing system, API platform, > > > gateway, > > > tunnel governance, etc.) > > > > > > > > > > On 2023/09/05 17:45:24 Xuanwo wrote: > > > > > > Hi, > > > > > > > > > > > > Thanks for the interesting proposal first! > > > > > > > > > > > > I would like to understand the connection between Xiaomi/mone and > > > OzHera. Will OzHera be transferred from Xiaomi/mono to > > > apache/incubator-ozhera while keeping the rest of the code unchanged? Can > > > OzHera be used independently without Xiaomi/mono? > > > > > > > > > > > > On Tue, Sep 5, 2023, at 11:11, Yu Xiao wrote: > > > > > > > Dear incubator community, > > > > > > > > > > > > > > I would like to propose OzHera[
Re: [DISCUSS] Incubating Proposal for OzHera
They are already beginning to remove the screenshots and comments that have proved the UI copy behaviors. They had known that and did that intentionally. Screenshots, https://twitter.com/wusheng1108/status/1699432297429114959. Now, if you see the issue again, it is gone.https://github.com/XiaoMi/mone/issues/689 They have admitted their UIs are similar(most likely directly referring) to Aliyun Yunxiao commercial services. (Translation from their top3 maintainer's feedback) Anyway, I think the evidence is clear, there are bigger issues than `too-early-to-join`. AFAIK, the project and the maintainers are not suitable for ASF culture, even hard to say good enough in the OSS culture. More and more China local foundation members and PPMC members are showing up to share their concerns and consensus of saying NO to the project. They have all the right to do things on their own, but let's keep the foundation and incubator safe from this kind of chaos. Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2023年9月6日周三 22:36写道： > > > attaching the screenshot > > I don't see an attachment in your email. If you paste the screenshot > inline, it can be filtered out by mailing list policy. You can attach a > file or upload it to an external image hosting service. > > Best, > tison. > > > Sheng Wu 于2023年9月6日周三 21:23写道： > > > One more update. > > With this project being noticed by this project, the parent project is > > facing the challenge of copying from Ali Yunxiao, which is one of the > > Aliyun commercial services. > > Ref source in CN, https://github.com/XiaoMi/mone/issues/689, attaching > > the screenshot in case of the owner deleted this issue. > > > > The good thing is, that this is not the ASF and incubator issue, we > > don't have an obligation to prove this is true or false. > > But this is a validation of my feelings that this project was not > > audited carefully, although one of them declared they are. > > > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Calvin Kirs 于2023年9月6日周三 20:15写道： > > > > > > Is this a (community) with only 38 issues? > > > There are tons of commits from the community. How does the decision > > > happen? ok, I saw this, relying on Gitter[1] with only 6 people and 8 > > > messages? > > > > > > pls forgive me, after reviewing your proposal > > > I really don’t know how to describe it. > > > > > > [1]https://app.gitter.im/#/room/#monegrow_community:gitter.im > > > > > > On Wed, Sep 6, 2023 at 6:14 PM Zhiyong Zhang > > wrote: > > > > > > > > Without Mone, OzHera can be used independently. Currently, in addition > > to Xiaomi, there are also some external manufacturers using or researching > > it. Mone is a larger collection within Xiaomi, and we are considering open > > sourcing all of it in the future (which includes cicd rpc, registration > > center, container management, stress testing system, API platform, gateway, > > tunnel governance, etc.) > > > > > > > > On 2023/09/05 17:45:24 Xuanwo wrote: > > > > > Hi, > > > > > > > > > > Thanks for the interesting proposal first! > > > > > > > > > > I would like to understand the connection between Xiaomi/mone and > > OzHera. Will OzHera be transferred from Xiaomi/mono to > > apache/incubator-ozhera while keeping the rest of the code unchanged? Can > > OzHera be used independently without Xiaomi/mono? > > > > > > > > > > On Tue, Sep 5, 2023, at 11:11, Yu Xiao wrote: > > > > > > Dear incubator community, > > > > > > > > > > > > I would like to propose OzHera[1] as a new apache incubator > > project, you > > > > > > can find the proposal[2] of OzHera for more detail. > > > > > > > > > > > > OzHera is an application performance observation platform that > > centers > > > > > > around applications, > > > > > > integrating metric monitoring, link tracing, logs, alerts, and > > other > > > > > > capabilities. > > > > > > The Hera platform has the following core features: > > > > > > > > > > > > ** Embrace Cloud Native > > > > > > Complies with the Opentracing standard, integrating multiple star > > > > > > open-source products such as OpenTelemetry, > > > > > > Grafana, Prometheus, ES, CAdvisor, etc. At the same time, Hera > > deeply > > > > > > adapts to K8S, > > > > > > p
Re: [DISCUSS] Incubating Proposal for OzHera
One more update. With this project being noticed by this project, the parent project is facing the challenge of copying from Ali Yunxiao, which is one of the Aliyun commercial services. Ref source in CN, https://github.com/XiaoMi/mone/issues/689, attaching the screenshot in case of the owner deleted this issue. The good thing is, that this is not the ASF and incubator issue, we don't have an obligation to prove this is true or false. But this is a validation of my feelings that this project was not audited carefully, although one of them declared they are. Sheng Wu 吴晟 Twitter, wusheng1108 Calvin Kirs 于2023年9月6日周三 20:15写道： > > Is this a (community) with only 38 issues? > There are tons of commits from the community. How does the decision > happen? ok, I saw this, relying on Gitter[1] with only 6 people and 8 > messages? > > pls forgive me, after reviewing your proposal > I really don’t know how to describe it. > > [1]https://app.gitter.im/#/room/#monegrow_community:gitter.im > > On Wed, Sep 6, 2023 at 6:14 PM Zhiyong Zhang wrote: > > > > Without Mone, OzHera can be used independently. Currently, in addition to > > Xiaomi, there are also some external manufacturers using or researching it. > > Mone is a larger collection within Xiaomi, and we are considering open > > sourcing all of it in the future (which includes cicd rpc, registration > > center, container management, stress testing system, API platform, gateway, > > tunnel governance, etc.) > > > > On 2023/09/05 17:45:24 Xuanwo wrote: > > > Hi, > > > > > > Thanks for the interesting proposal first! > > > > > > I would like to understand the connection between Xiaomi/mone and OzHera. > > > Will OzHera be transferred from Xiaomi/mono to apache/incubator-ozhera > > > while keeping the rest of the code unchanged? Can OzHera be used > > > independently without Xiaomi/mono? > > > > > > On Tue, Sep 5, 2023, at 11:11, Yu Xiao wrote: > > > > Dear incubator community, > > > > > > > > I would like to propose OzHera[1] as a new apache incubator project, you > > > > can find the proposal[2] of OzHera for more detail. > > > > > > > > OzHera is an application performance observation platform that centers > > > > around applications, > > > > integrating metric monitoring, link tracing, logs, alerts, and other > > > > capabilities. > > > > The Hera platform has the following core features: > > > > > > > > ** Embrace Cloud Native > > > > Complies with the Opentracing standard, integrating multiple star > > > > open-source products such as OpenTelemetry, > > > > Grafana, Prometheus, ES, CAdvisor, etc. At the same time, Hera deeply > > > > adapts to K8S, > > > > providing one-click deployment on K8S through operator. > > > > > > > > ** Precise: Availability Metrics > > > > We have defined corresponding availability metrics for common RPC > > > > (Dubbo, HTTP, etc.) requests. > > > > These request-scope metrics are automatically extracted from tracing > > > > by Hera, and during extraction, > > > > we enhance the ability to recognize business error codes. > > > > A single metric can accurately express the exceptions encapsulated by > > > > RPC and business processing. > > > > > > > > ** Quick: Metrics-Tracing-Logging Linkage > > > > Based on traceId, it links the alarm -> metrics -> link -> log closed > > > > loop. > > > > From the moment the alarm card touches the user, the user can quickly > > > > view the link and log situation related to this alarm, > > > > greatly improving the efficiency of problem locating. > > > > > > > > ** Economical > > > > Less than 0.1% storage cost, satisfying 99.9% of tracing demands > > > > OzHera achieves the recognition of abnormal calls (error span, > > > > abnormal business error codes, > > > > error logs, single span time exceeding 1 second, etc.) and ensures the > > > > storage of data for the entire call link of abnormal traces. > > > > For normal traces, we adopt a default random sampling strategy of one > > > > in ten thousand. > > > > > > > > ** Enterprise-level Observable Products > > > > Complete account, permission, application management mechanisms, > > > > allowing users to quick
Re: [DISCUSS] Incubating Proposal for OzHera
I want to offinally feedback, if this proposal goes to the vote process, I
will give my -1 binding considering
1. Project is too early, no init community to prove the project will work.
2. Don't have enough knowledge about open source relative legal affairs.
3. Mostly Chinese involved, it seems to aim on local users only.
I will only expect to re-evaluate the community status one and two years
later. They should not hurry on this.
Sheng Wu 吴晟
tison 于2023年9月6日 周三16:01写道：
> FWIW I rejected an incubator proposal before they submitted it formally in
> the past weeks with the suggestion to run an open-source community first as
> Sheng & Ming suggested above.
>
> This is never permanent. And often, a healthy project takes a few months to
> determine whether entering the incubator is a good idea. All the projects I
> mentored (Kvrocks, StreamPark, and OpenDAL) have been running a community
> for one to two years outside the incubator.
>
> Be aware that it's not a hard requirement, but the understanding of
> "entering the incubator" is the concern.
>
> > There is no magic in the Apache incubator. Don't expect the incubator
> will make your project international and successful
>
> I read this sentence as a reply to the following understanding:
>
> >> The user interface currently only has Chinese, and the
> internationalization of the page requires a longer time to iterate, but we
> will complete the transformation of this function in the early stage of
> incubation;
> >> We have checked in advance, and we hope to do the replacement and
> upgrade during the future incubation period.
> >>> Our project is open and is willing to cooperate with the Apache
> Incubator community, mentors, and other relevant parties to resolve
> potential license issues.
>
> The mission of Incubator is[1]:
>
> > It helps those incoming projects (called "podlings") adopt the Apache
> style of governance and operation and guides them to the ASF services
> available to our projects so they can become top-level ASF projects
> ("TLPs").
>
> ... and according to the answer of "Does our project fit the Apache
> Incubator?"[2]:
>
> > To give our "podlings" (incubating projects) the best chances of success,
> we usually ask them to enter the Incubator with at least the start of a
> community built around an existing codebase.
>
> So the Incubator doesn't help in "create" the community, but help in shape
> the community following the Apache style of governance and operation.
>
> Best,
> tison.
>
> [1] https://incubator.apache.org/
> [2]
>
> https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
>
>
> Ming Wen 于2023年9月6日周三 14:55写道：
>
> > After reading these responses, I feel that this project is not ready to
> > enter the Apache Incubator, especially considering that you have received
> > support from 6 mentors and communicated with them.
> > There is no magic in the Apache incubator. Don't expect the incubator
> will
> > make your project international and successful. For example, I noticed
> the
> > issues were all in Chinese, and no one reviewed PRs before merged.
> >
> > Thanks,
> > Ming Wen, Apache APISIX PMC Chair
> > Twitter: _WenMing
> >
> >
> > Zhiyong Zhang 于2023年9月5日周二 22:33写道：
> >
> > >
> > >
> > > On 2023/09/05 05:56:51 Sheng Wu wrote:
> > > > Several important things
> > >
> > > The entire project https://github.com/XiaoMi/mone has passed the
> > internal
> > > audit of Xiaomi, and the owners and leaders of the entire project are
> > > consistent with the initiators of the ozhera project. The main donation
> > to
> > > ASF this time is ozhera-all, and other modules follow the Apache
> > protocol,
> > > which will not cause protocol or ownership ambiguity.
> > > > 1. You are mentioning the donation is about
> > > > `https://github.com/XiaoMi/mone/tree/master/ozhera-all`
> <https://github.com/XiaoMi/mone/tree/master/ozhera-all>
> > <https://github.com/XiaoMi/mone/tree/master/ozhera-all>
> > > <https://github.com/XiaoMi/mone/tree/master/ozhera-all>, It is a part
> > > > of the repository, so will others stay out of the ASF? If so, have
> the
> > > > project been going through Xiaomi's internal audit about the sharing
> > > > codes between this part of the whole project? Who owns that?
> > >
> > > We hope to complete the internationalization transformation with the
> help
> > > of ASF; we are preparing the English document
Re: [DISCUSS] Incubating Proposal for OzHera
tison 于2023年9月5日周二 22:53写道： > > Hi, > > Glad to see a new incubator proposal. Comments inline. > > > There is a relatively clear division of labor among the mentors, and the > mentors will regularly assign us corresponding tasks. > > This sounds interesting. Could you elaborate on the "division of labor" and > previous tasks "assigned" by mentors to initial committers? A good question, and a bigger concern. Who can assign the mentors to work? Are they paid in some ways by Xiaomi? So, they will work for the company and the project? > > > I hope that ozhera can play its value in the observability of > cloud-native applications. > >> How would you process the branding > > The concern here is that ozhera, as a submodule of Mone, can suffer from > its packages and UIs convey the Mone branding still held by Xiaomi. If an > ASF project is tightly coupled with a vendor-specific project, it may be a > concern. > > > The versions we have chosen strictly comply with the GPL and Apache2.0 > agreements. > > The ASF states its project won't contain GPL-licensed components, at least > not as a necessary dependency. You can check [1][2] for details. > > > b. While Elasticsearch has changed from Apache 2.0 to the Server Side > Public License (SSPL), although SSPL is no longer an OSI-approved open > source license, it still allows free use, modification, and distribution, > but imposes some restrictions on commercial use. > > What would you like to express here? The ASF releases open-source software > following OSD[2][3]. SSPL or ELv2 is simply unacceptable. > > Best, > tison. > > [1] https://www.apache.org/licenses/GPL-compatibility.html > [2] https://www.apache.org/legal/resolved.html#category-x > [3] https://news.apache.org/foundation/entry/the-apache-way-to-sustainable > > > > Zhiyong Zhang 于2023年9月5日周二 22:33写道： > > > > > > > On 2023/09/05 05:56:51 Sheng Wu wrote: > > > Several important things > > > > The entire project https://github.com/XiaoMi/mone has passed the internal > > audit of Xiaomi, and the owners and leaders of the entire project are > > consistent with the initiators of the ozhera project. The main donation to > > ASF this time is ozhera-all, and other modules follow the Apache protocol, > > which will not cause protocol or ownership ambiguity. > > > 1. You are mentioning the donation is about > > > `https://github.com/XiaoMi/mone/tree/master/ozhera-all` > > <https://github.com/XiaoMi/mone/tree/master/ozhera-all>, It is a part > > > of the repository, so will others stay out of the ASF? If so, have the > > > project been going through Xiaomi's internal audit about the sharing > > > codes between this part of the whole project? Who owns that? > > > > We hope to complete the internationalization transformation with the help > > of ASF; we are preparing the English documents, and a version will be > > completed by tomorrow; > > > 2. I can't see any English document for the project. Is the community > > > for a global foundation incubating journey? > > > > The user interface currently only has Chinese, and the > > internationalization of the page requires a longer time to iterate, but we > > will complete the transformation of this function in the early stage of > > incubation; > > > 3. More importantly, all screenshots and UIs are only in Chinese as well? > > > > a.We have received full support from Xiaomi's legal affairs and are able > > to submit the SGA; > > b.The project has gradually recruited partners outside of Xiaomi, and the > > initial committers from Xiaomi are also actively participating in the > > construction of other open source communities. These are a group of > > partners who are passionate about open source. I believe that this group of > > partners can continue the project in the long term. > > > 4. Have Xiaomi Inc. agreed on this? Will they submit a SGA? Are the > > > initial committers still working on Xiaomi and going to continue work > > > this project? Will Xiaomi permit their CCLAs? > > > > We have checked in advance, and we hope to do the replacement and upgrade > > during the future incubation period. > > > 5. I can see several incompatible licenses of dependencies existing, > > > including GPLs. Do you have plans to remove or replace them? Have you > > > worked with your mentors to go through licenses of dependencies check? > > > > There is a relatively clear division of labor among the mentors, and the > > mentors will regularly assign us corresponding tasks. Thr
Re: [DISCUSS] Incubating Proposal for OzHera
Inline, my concerns are more with the project status feedback. The project status seems as same as I felt when reviewing the project today. And both from the project tech perspective and also from the experience level of initial committers is also too early to jump into the foundation incubator, before a basic license understanding and requirements and expectations of foundation projects. I highly recommend the project takes a longer time to learn the knowledge and at least build a (small but existing) community that out of Xiaomi to prove the project's real recommended use scenarios. More details inline. Zhiyong Zhang 于2023年9月5日周二 22:33写道： > > > > On 2023/09/05 05:56:51 Sheng Wu wrote: > > Several important things > > The entire project https://github.com/XiaoMi/mone has passed the internal > audit of Xiaomi, and the owners and leaders of the entire project are > consistent with the initiators of the ozhera project. The main donation to > ASF this time is ozhera-all, and other modules follow the Apache protocol, > which will not cause protocol or ownership ambiguity. This doesn't make sense. Apache 2.0 is just a license and it should be based on IP clearance and ownership declaration. These will become two projects, and each of them has different owners, Why suddenly this will not be an issue? > > 1. You are mentioning the donation is about > > `https://github.com/XiaoMi/mone/tree/master/ozhera-all`, It is a part > > of the repository, so will others stay out of the ASF? If so, have the > > project been going through Xiaomi's internal audit about the sharing > > codes between this part of the whole project? Who owns that? > > We hope to complete the internationalization transformation with the help of > ASF; we are preparing the English documents, and a version will be completed > by tomorrow; I am asking whether your community already exists and is ready for the incubator. If you are building an English document today(you have confirmed this), and have no clear documentation, I assume this project is too early. > > 2. I can't see any English document for the project. Is the community > > for a global foundation incubating journey? > > The user interface currently only has Chinese, and the internationalization > of the page requires a longer time to iterate, but we will complete the > transformation of this function in the early stage of incubation; This seems as same as the project is too early to join the foundation. Why so hurry to join rather than being patient to setup the initial community and write good documents What does an incubating project mean for you? > > 3. More importantly, all screenshots and UIs are only in Chinese as well? > > a.We have received full support from Xiaomi's legal affairs and are able to > submit the SGA; > b.The project has gradually recruited partners outside of Xiaomi, and the > initial committers from Xiaomi are also actively participating in the > construction of other open source communities. These are a group of partners > who are passionate about open source. I believe that this group of partners > can continue the project in the long term. What do you mean `recruited`? Does Xiaomi just hire people to do this? > > 4. Have Xiaomi Inc. agreed on this? Will they submit a SGA? Are the > > initial committers still working on Xiaomi and going to continue work > > this project? Will Xiaomi permit their CCLAs? > > We have checked in advance, and we hope to do the replacement and upgrade > during the future incubation period. > > 5. I can see several incompatible licenses of dependencies existing, > > including GPLs. Do you have plans to remove or replace them? Have you > > worked with your mentors to go through licenses of dependencies check? > > There is a relatively clear division of labor among the mentors, and the > mentors will regularly assign us corresponding tasks. Through efficient > project collaboration, we ensure the activity of the community; > At the same time, we can gain more experience and guidance from multiple > mentors, which will further promote the positive cycle development of the > community. > > 6. Why a 10 people PPMC initial team has a mentor team of 6 people? > > Typically, I don't think this is a good practice. Instead, mentors are > > most likely counting on others and will become inactive. > > I hope that ozhera can play its value in the observability of cloud-native > applications. Many components in ozhera (Opentelemetry, Grafana, Prometheus, > MQ, etc.) come from the open source community. We hope to feed back our > experience in the field of application observation to the community through > this platform. The UI design will actively embrace open source like the > b
Re: [DISCUSS] Incubating Proposal for OzHera
Several important things 1. You are mentioning the donation is about `https://github.com/XiaoMi/mone/tree/master/ozhera-all`, It is a part of the repository, so will others stay out of the ASF? If so, have the project been going through Xiaomi's internal audit about the sharing codes between this part of the whole project? Who owns that? 2. I can't see any English document for the project. Is the community for a global foundation incubating journey? 3. More importantly, all screenshots and UIs are only in Chinese as well? 4. Have Xiaomi Inc. agreed on this? Will they submit a SGA? Are the initial committers still working on Xiaomi and going to continue work this project? Will Xiaomi permit their CCLAs? 5. I can see several incompatible licenses of dependencies existing, including GPLs. Do you have plans to remove or replace them? Have you worked with your mentors to go through licenses of dependencies check? 6. Why a 10 people PPMC initial team has a mentor team of 6 people? Typically, I don't think this is a good practice. Instead, mentors are most likely counting on others and will become inactive. 7. How would you process the branding? Including you are sharing UI design. I have concerns this would be another issues with the main project. 8. You are using MySQL and ElasticSearch as storage. The one is on GPL and the other is not longer OSI-approved license anymore. What is your plan on that? 9 What are the differences between you and SkyWalking? What is this new project bringing new to the users? Notice, this is a not a rejection for a similar project, but, if they are nearly same, you will face competitions in the same foundation but already have larger community. Sheng Wu 吴晟 Twitter, wusheng1108 Yu Xiao 于2023年9月5日周二 11:12写道： > > Dear incubator community, > > I would like to propose OzHera[1] as a new apache incubator project, you > can find the proposal[2] of OzHera for more detail. > > OzHera is an application performance observation platform that centers > around applications, > integrating metric monitoring, link tracing, logs, alerts, and other > capabilities. > The Hera platform has the following core features: > > ** Embrace Cloud Native > Complies with the Opentracing standard, integrating multiple star > open-source products such as OpenTelemetry, > Grafana, Prometheus, ES, CAdvisor, etc. At the same time, Hera deeply > adapts to K8S, > providing one-click deployment on K8S through operator. > > ** Precise: Availability Metrics > We have defined corresponding availability metrics for common RPC > (Dubbo, HTTP, etc.) requests. > These request-scope metrics are automatically extracted from tracing > by Hera, and during extraction, > we enhance the ability to recognize business error codes. > A single metric can accurately express the exceptions encapsulated by > RPC and business processing. > > ** Quick: Metrics-Tracing-Logging Linkage > Based on traceId, it links the alarm -> metrics -> link -> log closed loop. > From the moment the alarm card touches the user, the user can quickly > view the link and log situation related to this alarm, > greatly improving the efficiency of problem locating. > > ** Economical > Less than 0.1% storage cost, satisfying 99.9% of tracing demands > OzHera achieves the recognition of abnormal calls (error span, > abnormal business error codes, > error logs, single span time exceeding 1 second, etc.) and ensures the > storage of data for the entire call link of abnormal traces. > For normal traces, we adopt a default random sampling strategy of one > in ten thousand. > > ** Enterprise-level Observable Products > Complete account, permission, application management mechanisms, > allowing users to quickly implement within the enterprise and connect > to the enterprise’s own account, application deployment system, etc. > It can also quickly dock with enterprise office software to achieve > alarm touch. Core links are well decoupled for rapid scaling, > and for large volumes of tracing, we have implemented tail sampling > strategies, > able to support high qps, real-time observable demands of high > timeliness systems. > > [1] https://github.com/XiaoMi/mone/tree/master/ozhera-all > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/OzHeraProposal > > Best, > Yu Xiao > > ASF Member > Apache ShenYu V.P. > Apache Incubator PMC > > - > 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: do we need to go through an Incubator PMC for a build tool?
Hi If we want that jar under asf package on maven central, yes, a new version is required a vote on dev first, then incubator. Meanwhile, if we have all mentors(ipmc members as well) voted, we just need to carry votes to incubator mail list, and another 3 days. Just one thing, if the jar has dependencies, we need to check license compatibility. PJ Fanning 于2023年7月3日 周一17:06写道： > Adding the Pekko mentors to the thread if that's ok. > > It's not a blocker for us to use a snapshot version of the > Pekko-specific build tool but it would be tidier if we could release a > stable version to Maven Central. If this requires us to release a > source artifact via the full voting procedure then that is fine. I > just want to make sure that this is a necessary step before going that > route. > > On Wed, 28 Jun 2023 at 18:38, PJ Fanning wrote: > > > > Hi everyone, > > > > The Apache Pekko community has a tool that is used as part of building > > our web site [1]. > > sbt-paradox-pekko [2] applies the theme to the Pekko web site. It is > > not useful for outside users. > > We require that a Java/Scala jar is published because this tool is > > used in a number of different Pekko projects (ie different Apache git > > repos that the Pekko team maintain). > > We haven't yet released an official 1.0.0 jar and are using a snapshot > jar. > > If we wanted to publish an official 1.0.0 jar, would we need to have > > an Incubator PMC vote on it. We will have a Pekko discussion and > > possibly a vote if it seems appropriate. > > > > Any insights would be appreciated. > > > > Regards, > > PJ > > > > [1] https://pekko.apache.org > > [2] https://github.com/apache/incubator-pekko-sbt-paradox > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1
Checked 1. Compiling `cargo build` from source codes 2. Version correct 3. License and Notice exist for source codes. 4. No License and Notice for binary. So far, I skip the check only due to DISCLAIMER exists. This should be verified before the graduation preparation. Before the vote, I want to ask - What is the relationship between rust source release and source codes in bindings? The default compiling seems don't compile all these bindings, are all these part of the release? I have checked Java binding, the version is locked to 0.37.0 as well. So, I am confused for now Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2023年6月12日周一 17:16写道： > > +1 (binding) > > I checked - > > [x] Download links are valid. > [x] Checksums and signatures. > [x] + incubating in artifacts name > [x] LICENSE/NOTICE files exist + DISCLAIMER exists > [x] No unexpected binary files > [x] All source files have ASF headers > [x] Can compile from source - with `cargo build' > > Thanks for driving this release! Perhaps you can document how to verify a > release candidate on the website. > > Best, > tison. > > > Suyan 于2023年6月7日周三 11:08写道： > > > Hello Incubator PMC, > > > > The Apache OpenDAL community has voted and approved the release of Apache > > OpenDAL(incubating) 0.37.0-rc1. We now kindly request the IPMC members > > review and vote for this release. > > > > OpenDAL is a data access layer that allows users to easily and efficiently > > retrieve data from various storage services in a unified way. > > > > OpenDAL community vote thread: > > > > https://lists.apache.org/thread/v1cw3rtkwbysl2n606n4rqchf7k0x4f4 > > > > Vote result thread: > > > > https://lists.apache.org/thread/4k22z387y3fw33x3spmowlmmtkh8tq7f > > > > The release candidate: > > > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.37.0-rc1/ > > > > This release has been signed with a PGP available here: > > > > https://downloads.apache.org/incubator/opendal/KEYS > > > > Git branch for the release: > > > > https://github.com/apache/incubator-opendal/tree/release-0.37.0-rc1 > > > > Please download, verify, and test. > > > > The VOTE will pass after got 3 binding approve. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > To learn more about apache opendal, please see https://opendal.apache.org/ > > > > Checklist for reference: > > > > [ ] Download links are valid. > > [ ] Checksums and signatures. > > [ ] LICENSE/NOTICE files exist > > [ ] No unexpected binary files > > [ ] All source files have ASF headers > > [ ] Can compile from source > > > > More detailed checklist please refer to: > > https://github.com/apache/incubator-opendal/tree/main/scripts > > > > To compile from the source, please refer to: > > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > > > Thanks. > > > > Sincerely, > > Suyan > > > > - > > 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 OpenDAL (incubating) 0.36.0-rc1 (Round 2)
tison 于2023年6月5日周一 22:36写道： > > > 2. Meanwhile, why the website is a part of source release? > > I suggest we can exclude website materials from the source release > > > Where is the LICENSE and NOTICE of the binary > > If we don't make binary releases, what is the policy for bundle their > LICENSE or NOTICE? First of all, binary is never a release in the ASF. It is just for end user convenience. If end users don't need that, then we don't deliver that. But it doesn't mean the dependency tree disappears. I don't think we follow the policy or the rule. The key point is, we are going to release something, which should be APLv2 compatible and safe for our end users. Policy is only a guidance of what we did before. In another word, how could we know the dependencies of this lib in the runtime are LICENSE safe? > > Justin commented the last time (vote for 0.34.0-rc1): > > > > - LICENSE and NOTICE are not correct, LICENSE information goes in LICENSE > not NOTICE and there is no need to list BSD or MIT licenses. Also the > license text needs to be included not URLs. (Content at URLs can change or > move or be removed). > > - Note " Apache-2.0 WITH LLVM-exception” is not listed at a Category A > license >- NOTICE also includes licenses that are not Category A and are > not allowed to be included in a source release. >- It also looks like the > NOTICE file is listing dependencies. You only need to include what is > bundled in the release, not the licenses of all dependencies. It is unclear > if any 3rd party software is contained in the source release. > > Note the last sentence that "You only need to include what is bundled in > the release" and no source code from other party is bundled in OpenDAL's > source release. > > Best, > tison. > > > Sheng Wu 于2023年6月5日周一 22:27写道： > > > Hi > > > > -1 binding > > > > 1. (The resonse of -1) Unexpected images showing up > > > > > website/blog/2023-03-16-opendal-entered-apache-incubator/opendal-entered-apache.png > > This image includes a vendor logo, I don't think the ASF is granted to > > use that as a part of distribution. > > > > 2. Meanwhile, why the website is a part of source release? > > 3. Where is the LICENSE and NOTICE of the binary? We could choose to > > don't distribute binary tar, but we should make the LICENSEs of > > dependencies clear. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Willem Jiang 于2023年6月5日周一 22:04写道： > > > > > > +1. Here is what I checked: > > > - The checksums and signatures are validated. > > > - The LICENSE and NOTICE files look good to me. > > > - There is a DISCLAIMER file about incubating. > > > - No binary files in the source release > > > - I can build the binary from the source kit. > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Mon, Jun 5, 2023 at 9:54 PM Xuanwo wrote: > > > > > > > > > NOTE: README.md does not include `how to build.` > > > > > > > > Thanks for your NOTE! We have included the instructions on how to > > build in our Contributing Guide. We will ensure that this is made clearer > > in future updates. > > > > > > > > On Mon, Jun 5, 2023, at 21:41, Xiaoqiao He wrote: > > > > > +1(binding) > > > > > > > > > > [x] Download links are valid. > > > > > [x] Checksums and PGP signatures are valid. > > > > > [x] LICENSE files exist. > > > > > [x] NOTICE is included. > > > > > [x] DISCLAIMER is included. > > > > > [x] Source code artifacts have correct names matching the current > > release. > > > > > [x] All source files have license headers if necessary. > > > > > [x] Checked no binary files in source package. > > > > > > > > > > NOTE: README.md does not include `how to build.` (Which Willem was > > > > > concerned about last round.). I try to compile from source with > > `cargo > > > > > build` > > > > > (From tison mentioned above), it works well. IMO it is not a blocker > > issue. > > > > > > > > > > Best Regards, > > > > > - He Xiaoqiao > > > > > > > > > > > > > > > On Sun, Jun 4, 2023 at 6:48 AM tison wrote: > > > > > > > > > >> +1 (binding) > > > > >> > > > > >> I checked - > > > > >>
Re: [VOTE] Release Apache OpenDAL (incubating) 0.36.0-rc1 (Round 2)
Hi -1 binding 1. (The resonse of -1) Unexpected images showing up > website/blog/2023-03-16-opendal-entered-apache-incubator/opendal-entered-apache.png This image includes a vendor logo, I don't think the ASF is granted to use that as a part of distribution. 2. Meanwhile, why the website is a part of source release? 3. Where is the LICENSE and NOTICE of the binary? We could choose to don't distribute binary tar, but we should make the LICENSEs of dependencies clear. Sheng Wu 吴晟 Twitter, wusheng1108 Willem Jiang 于2023年6月5日周一 22:04写道： > > +1. Here is what I checked: > - The checksums and signatures are validated. > - The LICENSE and NOTICE files look good to me. > - There is a DISCLAIMER file about incubating. > - No binary files in the source release > - I can build the binary from the source kit. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Jun 5, 2023 at 9:54 PM Xuanwo wrote: > > > > > NOTE: README.md does not include `how to build.` > > > > Thanks for your NOTE! We have included the instructions on how to build in > > our Contributing Guide. We will ensure that this is made clearer in future > > updates. > > > > On Mon, Jun 5, 2023, at 21:41, Xiaoqiao He wrote: > > > +1(binding) > > > > > > [x] Download links are valid. > > > [x] Checksums and PGP signatures are valid. > > > [x] LICENSE files exist. > > > [x] NOTICE is included. > > > [x] DISCLAIMER is included. > > > [x] Source code artifacts have correct names matching the current release. > > > [x] All source files have license headers if necessary. > > > [x] Checked no binary files in source package. > > > > > > NOTE: README.md does not include `how to build.` (Which Willem was > > > concerned about last round.). I try to compile from source with `cargo > > > build` > > > (From tison mentioned above), it works well. IMO it is not a blocker > > > issue. > > > > > > Best Regards, > > > - He Xiaoqiao > > > > > > > > > On Sun, Jun 4, 2023 at 6:48 AM tison wrote: > > > > > >> +1 (binding) > > >> > > >> I checked - > > >> > > >> [x] Download links are valid. > > >> [x] Checksums and signatures. > > >> [x] + incubating in artifacts name > > >> [x] LICENSE/NOTICE files exist + DISCLAIMER exists > > >> [x] No unexpected binary files > > >> [x] All source files have ASF headers > > >> [x] Can compile from source - with `cargo build' > > >> > > >> Best, > > >> tison. > > >> > > >> > > >> Xuanwo 于2023年6月3日周六 19:50写道： > > >> > > >> > Hello Incubator PMC, > > >> > > > >> > The Apache OpenDAL community has voted and approved the release of > > >> > Apache > > >> > OpenDAL(incubating) 0.36.0-rc1. We now kindly request the IPMC members > > >> > review and vote for this release. > > >> > > > >> > OpenDAL is a data access layer that allows users to easily and > > >> efficiently > > >> > retrieve data from various storage services in a unified way. > > >> > > > >> > OpenDAL community vote thread: > > >> > > > >> > https://lists.apache.org/thread/c211gqq2yl15jbxqk4rcnq1bdqltjm5l > > >> > > > >> > Vote result thread: > > >> > > > >> > https://lists.apache.org/thread/xk5myl10mztcfotn59oo59s4ckvojds6 > > >> > > > >> > The release candidate: > > >> > > > >> > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.36.0-rc1/ > > >> > > > >> > This release has been signed with a PGP available here: > > >> > > > >> > https://downloads.apache.org/incubator/opendal/KEYS > > >> > > > >> > Git branch for the release: > > >> > > > >> > https://github.com/apache/incubator-opendal/tree/release-0.36.0-rc1 > > >> > > > >> > Please download, verify, and test. > > >> > > > >> > The VOTE will pass after got 3 binding approve. > > >> > > > >> > [ ] +1 approve > > >> > [ ] +0 no opinion > > >> > [ ] -1 disapprove with the reason > > >> > > > >> > To learn more about apache opendal, please see > > >> https://openda
Re: [VOTE] Release Apache OpenDAL(incubating) 0.34.0-rc1
gt; >>>>> > >>>>> OpenDAL community vote thread: > >>>>> > >>>>> https://lists.apache.org/thread/nh80zh9y11frx7ls9fn4dvj1hdh2n4pb > >>>>> > >>>>> Vote result thread: > >>>>> > >>>>> https://lists.apache.org/thread/hjkxdvqr1dsrq71cr6j7ltjxvwmn0jg2 > >>>>> > >>>>> The release candidate: > >>>>> > >>>>> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.34.0-rc1/ > >>>>> > >>>>> This release has been signed with a PGP available here: > >>>>> > >>>>> https://downloads.apache.org/incubator/opendal/KEYS > >>>>> > >>>>> Git branch for the release: > >>>>> > >>>>> https://github.com/apache/incubator-opendal/tree/release-0.34.0-rc1 > >>>>> > >>>>> Please download, verify, and test. > >>>>> > >>>>> The VOTE will pass after got 3 binding approve. > >>>>> > >>>>> [ ] +1 approve > >>>>> [ ] +0 no opinion > >>>>> [ ] -1 disapprove with the reason > >>>>> > >>>>> To learn more about apache opendal, please see > >>>> https://opendal.apache.org/ > >>>>> > >>>>> Checklist for reference: > >>>>> > >>>>> [ ] Download links are valid. > >>>>> [ ] Checksums and signatures. > >>>>> [ ] LICENSE/NOTICE files exist > >>>>> [ ] No unexpected binary files > >>>>> [ ] All source files have ASF headers > >>>>> [ ] Can compile from source > >>>>> > >>>>> More detailed checklist please refer to: > >>>>> https://github.com/apache/incubator-opendal/tree/main/scripts > >>>>> > >>>>> To compile from source, please refer to: > >>>>> > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > >>>>> > >>>>> Thanks > >>>>> > >>>>> Xuanwo > >>>>> > >>>>> - > >>>>> 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 > > -- > Xuanwo > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [VOTE] Accept OpenDAL into the Apache Incubator
+1 binding Sheng Wu 吴晟 Twitter, wusheng1108 Xinyu Zhou 于2023年2月22日周三 11:11写道： > > +1, Good luck. > > Regards, > > On Wed, Feb 22, 2023 at 10:12 AM Xiaoqiao He wrote: > > > +1(binding). > > > > Best Regards, > > - He Xiaoqiao > > > > On Wed, Feb 22, 2023 at 9:43 AM Xin Wang wrote: > > > > > +1 > > > Look forward to a growing and healthy community during the incubation > > > period. > > > > > > Willem Jiang 于2023年2月22日周三 09:04写道： > > > > > > > +1(binding). > > > > I'm looking forward to working with this project as a mentor. > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > > > > > On Tue, Feb 21, 2023 at 9:24 PM tison wrote: > > > > > > > > > > Hi all, > > > > > > > > > > Following up on the [DISCUSS] thread on OpenDAL[1], I would like to > > > call > > > > a > > > > > VOTE to accept OpenDAL into the Apache Incubator, please check out > > the > > > > > OpenDAL Proposal from the incubator wiki[2]. > > > > > > > > > > Please cast your vote: > > > > > > > > > > [ ] +1, bring OpenDAL into the Incubator > > > > > [ ] +0, I don't care either way > > > > > [ ] -1, do not bring OpenDAL into the Incubator, because... > > > > > > > > > > The vote will open at least for 72 hours, and only votes from the > > > > Incubator > > > > > PMC members are binding, but votes from everyone are welcome. > > > > > > > > > > [1] https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r > > > > > [2] > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal > > > > > > > > > > Best, > > > > > tison. > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > -- > > > Thanks, > > > Xin > > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal for OpenDAL
.0+wasi-snapshot-preview1 > > > >>> - wasi@0.9.0+wasi-snapshot-preview1 > > > >>> - BSD-3-Clause (3) > > > >>> - encoding_rs@0.8.31 > > > >>> - instant@0.1.12 > > > >>> - subtle@2.4.1 > > > >>> - BSL-1.0 (1): > > > >>> - ryu@1.0.12 > > > >>> - ISC (8): > > > >>> - hyper-rustls@0.23.2 > > > >>> - rustls@0.20.7 > > > >>> - rustls-native-certs@0.6.2 > > > >>> - rustls-pemfile@1.0.1 > > > >>> - sct@0.7.0 > > > >>> - simple_asn1@0.6.2 > > > >>> - untrusted@0.7.1 > > > >>> - webpki@0.22.0 > > > >>> - MIT (242) > > > >>> - ahash@0.7.6 > > > >>> - aho-corasick@0.7.20 > > > >>> - anes@0.1.6 > > > >>> - anyhow@1.0.68 > > > >>> - assert-json-diff@2.0.2 > > > >>> - async-channel@1.8.0 > > > >>> - async-compat@0.2.1 > > > >>> - async-trait@0.1.60 > > > >>> - atty@0.2.14 > > > >>> - autocfg@1.1.0 > > > >>> - base64@0.13.1 > > > >>> - base64@0.21.0 > > > >>> - bincode@2.0.0-rc.2 > > > >>> - bincode_derive@2.0.0-rc.2 > > > >>> - bitflags@1.3.2 > > > >>> - block-buffer@0.10.3 > > > >>> - bumpalo@3.11.1 > > > >>> - byteorder@1.4.3 > > > >>> - bytes@1.3.0 > > > >>> - cast@0.3.0 > > > >>> - cc@1.0.78 > > > >>> - cfg-if@1.0.0 > > > >>> - clap@3.2.23 > > > >>> - clap_lex@0.2.4 > > > >>> - concurrent-queue@2.0.0 > > > >>> - core-foundation@0.9.3 > > > >>> - core-foundation-sys@0.8.3 > > > >>> - cpufeatures@0.2.5 > > > >>> - criterion@0.4.0 > > > >>> - criterion-plot@0.5.0 > > > >>> - crossbeam-channel@0.5.6 > > > >>> - crossbeam-deque@0.8.2 > > > >>> - crossbeam-epoch@0.9.13 > > > >>> - crossbeam-utils@0.8.14 > > > >>> - crypto-common@0.1.6 > > > >>> - ctor@0.1.26 > > > >>> - deadpool@0.9.5 > > > >>> - deadpool-runtime@0.1.2 > > > >>> - diff@0.1.13 > > > >>> - digest@0.10.6 > > > >>> - dirs@4.0.0 > > > >>> - dirs-sys@0.3.7 > > > >>> - dlv-list@0.3.0 > > > >>> - dotenvy@0.15.6 > > > >>> - either@1.8.0 > > > >>> - encoding_rs@0.8.31 > > > >>> - env_logger@0.10.0 > > > >>> - event-listener@2.5.3 > > > >>> - fastrand@1.8.0 > > > >>> - fnv@1.0.7 > > > >>> - form_urlencoded@1.1.0 > > > >>> - futures@0.3.25 > > > >>> - futures-channel@0.3.25 > > > >>> - futures-core@0.3.25 > > > >>> - futures-executor@0.3.25 > > > >>> - futures-io@0.3.25 > > > >>> - futures-lite@1.12.0 > > > >>> - futures-macro@0.3.25 > > > >>> - futures-sink@0.3.25 > > > >>> - futures-task@0.3.25 > > > >>> - futures-timer@3.0.2 > > > >>> - futures-util@0.3.25 > > > >>> - generic-array@0.14.6 > > > >>> - getrandom@0.1.16 > > > >>> - getrandom@0.2.8 > > > >>> - h2@0.3.15 > > > >>> - half@1.8.2 > > > >>> - hashbrown@0.12.3 > > > >>> - hermit-abi@0.1.19 > > > >>> - hermit-abi@0.2.6 > > > >>> - hex@0.4.3 > > > >>> - hmac@0.12.1 > > > >>> - http@0.2.8 > > > >>> - http-body@0.4.5 > > > >>> - http-types@2.12.0 > > > >>> - httparse@1.8.0 > > > >>> - httpdate@1.0.2 > > > >>> - humantime@2.1.0 > > > >>> - hyper@0.14.23 > > > >>> - hyper-rustls@0.23.2 > > > >>> - idna@0.3.0 > > > >>> - indexmap@1.9.2 > > > >>> - infer@0.2.3 > > > >>> - integer-encoding@3.0.4 > > > >>> - io-lifetimes@1.0.3 > > > >>> - ipnet@2.7.0 > > > >>> - is-terminal@0.4.2 > > > >>> - itertools@0.10.5 > > > >>> - itoa@1.0.5 > > > >>> - js-sys@0.3.60 > > > >>> - jsonwebtoken@8.2.0 > > > >>> - lazy_static@1.4.0 > > > >>> - libc@0.2.139 > > > >>> - linux-raw-sys@0.1.4 > > > >>> - lock_api@0.4.9 > > > >>> - log@0.4.17 > > > >>> - matchers@0.1.0 > > > >>> - md-5@0.10.5 > > > >>> - memchr@2.5.0 > > > >>> - memoffset@0.7.1 > > > >>> - mime@0.3.16 > > > >>> - mime_guess@2.0.4 > > > >>> - mio@0.8.5 > > > >>> - nu-ansi-term@0.46.0 > > > >>> - num-bigint@0.4.3 > > > >>> - num-integer@0.1.45 > > > >>> - num-traits@0.2.15 > > > >>> - num_cpus@1.15.0 > > > >>> - once_cell@1.17.0 > > > >>> - oorandom@11.1.3 > > > >>> - openssl-probe@0.1.5 > > > >>> - ordered-float@1.1.1 > > > >>> - ordered-multimap@0.4.3 > > > >>> - os_str_bytes@6.4.1 > > > >>> - output_vt100@0.1.3 > > > >>> - overload@0.1.1 > > > >>> - parking@2.0.0 > > > >>> - parking_lot@0.12.1 > > > >>> - parking_lot_core@0.9.5 > > > >>> - paste@1.0.11 > > > >>> - pem@1.1.0 > > > >>> - percent-encoding@2.2.0 > > > >>> - pin-project@1.0.12 > > > >>> - pin-project-internal@1.0.12 > > > >>> - pin-project-lite@0.2.9 > > > >>> - pin-utils@0.1.0 > > > >>> - plotters@0.3.4 > > > >>> - plotters-backend@0.3.4 > > > >>> - plotters-svg@0.3.3 > > > >>> - ppv-lite86@0.2.17 > > > >>> - pretty_assertions@1.3.0 > > > >>> - proc-macro2@1.0.49 > > > >>> - quick-xml@0.27.1 > > > >>> - quote@1.0.23 > > > >>> - rand@0.7.3 > > > >>> - rand@0.8.5 > > > >>> - rand_chacha@0.2.2 > > > >>> - rand_chacha@0.3.1 > > > >>> - rand_core@0.5.1 > > > >>> - rand_core@0.6.4 > > > >>> - rand_hc@0.2.0 > > > >>> - rayon@1.6.1 > > > >>> - rayon-core@1.10.1 > > > >>> - redox_syscall@0.2.16 > > > >>> - redox_users@0.4.3 > > > >>> - regex@1.7.0 > > > >>> - regex-automata@0.1.10 > > > >>> - regex-syntax@0.6.28 > > > >>> - reqwest@0.11.13 > > > >>> - retain_mut@0.1.9 > > > >>> - rust-ini@0.18.0 > > > >>> - rustix@0.36.6 > > > >>> - rustls@0.20.7 > > > >>> - rustls-native-certs@0.6.2 > > > >>> - rustls-pemfile@1.0.1 > > > >>> - same-file@1.0.6 > > > >>> - schannel@0.1.20 > > > >>> - scopeguard@1.1.0 > > > >>> - sct@0.7.0 > > > >>> - security-framework@2.7.0 > > > >>> - security-framework-sys@2.6.1 > > > >>> - serde@1.0.152 > > > >>> - serde_derive@1.0.152 > > > >>> - serde_json@1.0.91 > > > >>> - serde_qs@0.8.5 > > > >>> - serde_urlencoded@0.7.1 > > > >>> - sha1@0.10.5 > > > >>> - sha2@0.10.6 > > > >>> - sharded-slab@0.1.4 > > > >>> - size@0.4.1 > > > >>> - slab@0.4.7 > > > >>> - smallvec@1.10.0 > > > >>> - socket2@0.4.7 > > > >>> - spin@0.5.2 > > > >>> - syn@1.0.107 > > > >>> - termcolor@1.1.3 > > > >>> - textwrap@0.16.0 > > > >>> - thiserror@1.0.38 > > > >>> - thiserror-impl@1.0.38 > > > >>> - thread_local@1.1.4 > > > >>> - threadpool@1.8.1 > > > >>> - time@0.3.17 > > > >>> - time-core@0.1.0 > > > >>> - time-macros@0.2.6 > > > >>> - tinytemplate@1.2.1 > > > >>> - tinyvec@1.6.0 > > > >>> - tinyvec_macros@0.1.0 > > > >>> - tokio@1.23.1 > > > >>> - tokio-macros@1.8.2 > > > >>> - tokio-rustls@0.23.4 > > > >>> - tokio-util@0.7.4 > > > >>> - tower-service@0.3.2 > > > >>> - tracing@0.1.37 > > > >>> - tracing-core@0.1.30 > > > >>> - tracing-log@0.1.3 > > > >>> - tracing-opentelemetry@0.17.4 > > > >>> - tracing-subscriber@0.3.16 > > > >>> - try-lock@0.2.3 > > > >>> - typenum@1.16.0 > > > >>> - unicase@2.6.0 > > > >>> - unicode-bidi@0.3.8 > > > >>> - unicode-ident@1.0.6 > > > >>> - unicode-normalization@0.1.22 > > > >>> - ureq@2.6.1 > > > >>> - url@2.3.1 > > > >>> - uuid@1.2.2 > > > >>> - valuable@0.1.0 > > > >>> - version_check@0.9.4 > > > >>> - virtue@0.0.8 > > > >>> - waker-fn@1.1.0 > > > >>> - walkdir@2.3.2 > > > >>> - want@0.3.0 > > > >>> - wasi@0.11.0+wasi-snapshot-preview1 > > > >>> - wasi@0.9.0+wasi-snapshot-preview1 > > > >>> - wasm-bindgen@0.2.83 > > > >>> - wasm-bindgen-backend@0.2.83 > > > >>> - wasm-bindgen-futures@0.4.33 > > > >>> - wasm-bindgen-macro@0.2.83 > > > >>> - wasm-bindgen-macro-support@0.2.83 > > > >>> - wasm-bindgen-shared@0.2.83 > > > >>> - web-sys@0.3.60 > > > >>> - winapi@0.3.9 > > > >>> - winapi-i686-pc-windows-gnu@0.4.0 > > > >>> - winapi-util@0.1.5 > > > >>> - winapi-x86_64-pc-windows-gnu@0.4.0 > > > >>> - windows-sys@0.36.1 > > > >>> - windows-sys@0.42.0 > > > >>> - windows_aarch64_gnullvm@0.42.0 > > > >>> - windows_aarch64_msvc@0.36.1 > > > >>> - windows_aarch64_msvc@0.42.0 > > > >>> - windows_i686_gnu@0.36.1 > > > >>> - windows_i686_gnu@0.42.0 > > > >>> - windows_i686_msvc@0.36.1 > > > >>> - windows_i686_msvc@0.42.0 > > > >>> - windows_x86_64_gnu@0.36.1 > > > >>> - windows_x86_64_gnu@0.42.0 > > > >>> - windows_x86_64_gnullvm@0.42.0 > > > >>> - windows_x86_64_msvc@0.36.1 > > > >>> - windows_x86_64_msvc@0.42.0 > > > >>> - winreg@0.10.1 > > > >>> - wiremock@0.5.16 > > > >>> - yansi@0.5.1 > > > >>> - MPL-2.0 (1): > > > >>> - webpki-roots@0.22.6 > > > >>> - Unicode-DFS-2016 (1): > > > >>> - unicode-ident@1.0.6 > > > >>> - Unlicense (8): > > > >>> - aho-corasick@0.7.20 > > > >>> - byteorder@1.4.3 > > > >>> - memchr@2.5.0 > > > >>> - regex-automata@0.1.10 > > > >>> - same-file@1.0.6 > > > >>> - termcolor@1.1.3 > > > >>> - walkdir@2.3.2 > > > >>> - winapi-util@0.1.5 > > > >>> - Zlib (2): > > > >>> - tinyvec@1.6.0 > > > >>> - tinyvec_macros@0.1.0 > > > >>> - Unlicensed (1): > > > >>> - ring@0.16.20 > > > >>> > > > >>> ring is licensed under a mix of [MIT, ISC, and OpenSSL’s > > > licenses]( > > > >>> https://github.com/briansmith/ring/blob/main/LICENSE). OpenSSL > itself > > > is > > > >>> licensed under [Apache 2.0]( > > > >>> https://www.openssl.org/source/apache-license-2.0.txt). So ring is > > > Apache > > > >>> 2.0 compatible. > > > >>> > > > >>> > > > >>> ### Cryptography > > > >>> > > > >>> N/A > > > >>> > > > >>> ## Required Resources > > > >>> > > > >>> ### Mailing Lists > > > >>> > > > >>> - priv...@opendal.apache.org > > > >>> - d...@opendal.apache.org > > > >>> - comm...@opendal.apache.org > > > >>> - iss...@opendal.apache.org > > > >>> - bu...@opendal.apache.org > > > >>> > > > >>> ### Subversion Directory > > > >>> > > > >>> N/A > > > >>> > > > >>> ### Git Repositories > > > >>> > > > >>> From [ > > > >>> > > > > https://github.com/datafuselabs/opendal](https://github.com/datafuselabs/opendal) > > > >>> > > > >>> - [ > > > >>> > > > > https://gitbox.apache.org/asf/repos/incubator-opendal](https://gitbox.apache.org/asf/repos/incubator-opendal) > > > >>> - [ > > > >>> > > > > https://github.com/apache/incubator-opendal](https://github.com/apache/incubator-opendal) > > > >>> > > > >>> ### Issue Tracking > > > >>> > > > >>> The community would like to continue using GitHub Issues. > > > >>> > > > >>> ### Other Resources > > > >>> > > > >>> The community has already chosen GitHub actions as continuous > > > integration > > > >>> tools. > > > >>> > > > >>> ## Initial Committers > > > >>> > > > >>> - Hao Ding [[git...@xuanwo.io](mailto:git...@xuanwo.io)] > > > >>> - Lue Cai [[cai...@bupt.edu.cn](mailto:cai...@bupt.edu.cn)] > > > >>> - Zhuoran Shang [[psi...@outlook.com](mailto:psi...@outlook.com)] > > > >>> - Benwang Li [[libenw1...@gmail.com](mailto:libenw1...@gmail.com)] > > > >>> > > > >>> ## Sponsors > > > >>> > > > >>> ### Champion > > > >>> > > > >>> - tison [ti...@apache.org] > > > >>> > > > >>> ### Nominated Mentors > > > >>> > > > >>> - hexiaoqiao [hexiaoq...@apache.org] > > > >>> - tedliu [ted...@apache.org] > > > >>> - tison [ti...@apache.org] > > > >>> - wusheng [wush...@apache.org] > > > >>> > > > >>> ### Sponsor Entity > > > >>> > > > >>> The Incubator > > > >> > > > >>- > > > >>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 > > > > > > > > > > -- > Best Regards, > - Hulk Lin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)
Hi Tison AFAIK, this is not a failed vote. You are still have more +1 than -1. You could consider whether waiting for another round, or any voted IPMC member would change votes. -1 is veto. tison 于2023年2月14日 周二20:32写道： > Hi Justin, > > Thanks for your information! I made this patch > https://github.com/apache/incubator-kvrocks/pull/1259 to resolve the > license issue. Since we're going to make a new RC with only this change, > could you take a look at the patch whether there still remains some > concerns? Then we can avoid another round of failed vote. > > Best, > tison. > > Justin Mclean 于2023年2月14日 周二15:59写道： > > > Hi, > > > > > It can be a case of The Ship of Theseus. When you take a look at the > > issued > > > files[1][2], you may find a commit history touching them and modifying > > > them. Anyway, it's not an identical copy or one-shot translation. > > > > This has been discussed many times on various lists, translating an > > algorithm from one language to another does not change its license. > > > > > And we keep the origin comments. > > > > Which is also an IP issue. > > > > Kinds Regards, > > Justin > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > -- > Best, > tison. > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [QUESTION] are binary distributions/releases required?
Hi Only source codes(tars) are treated as releases. So generally, you could only put the source tars as the vote releases. Meanwhile, we should check the runtime dependencies about License compatibility, such as no Catalog X or commercial license dependencies in the runtime(especially not optional). Sheng Wu 吴晟 Twitter, wusheng1108 PJ Fanning 于2023年2月8日周三 22:33写道： > > Hi everyone, > The release management guide [1] only mentions 'source releases'. Every > Apache project that I am familiar with also does binary releases. For > applications, this makes sense - having a zip/tgz file that you can download > and extract - that you can then readily start the application using a shell > script. For libs, I'm sure these binary releases can be useful too but I'm > wondering if they are strictly required. > > Apache Pekko is a set of libraries as opposed to an application. Our build > uses the sbt build tool and there isn't anything that I've come across that > would produce something like the binary releases that other Apache projects > release. This means we'd likely have to roll our own solution. > > In terms of prioritising work towards a v1.0.0 release, it's useful to know > if we have items that could be de-prioritised. > > If we do need to create binary releases, are there any guidelines to follow - > or do we just look at other Apache libs and use their binary releases as a > guide? > > Regards, > PJ > > [1] https://incubator.apache.org/guides/releasemanagement.html > > - > 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] KIE proposal acceptance
I noticed the sponsor part of the proposal > Sponsors IBM and Red Hat are the sponsors for the project. I think this sponsor part referring an ASF TLP, which usually be the incubator in here or other TLPs. These two companies may provide support to the developers, but this is not the meaning of the proposal. Sheng Wu 吴晟 Twitter, wusheng1108 Antoine Toulme 于2023年1月9日周一 22:58写道： > > Here is my +1 (binding). I worked with Drools long time ago and am excited to > see KIE take it to the next level! > > Cheers, > > Antoine > > > On Jan 9, 2023, at 06:51, Jason Porter wrote: > > > > I'd like to call a vote for the acceptance of KIE as an Apache Incubator > > project as the conversation around the proposal has ended. The proposal is > > available at [1]. > > > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/KIE+Proposal > > > > Jason Porter > > Software Engineer > > He/Him/His > > > > IBM > > > > > - > 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] Graduate Apache bRPC to a TLP
ly below be and hereby are > > > > appointed to serve as the initial members of the Apache bRPC Project: > > > > * Bear Jiang > > > > * Cai Daojin > > > > * He Lei > > > > * James Ge > > > > * Jean-Baptiste Onofré > > > > * Jerry Tan > > > > * Jiashun Zhu > > > > * Juan Pan > > > > * Lorin Lee > > > > * Von Gosling > > > > * Wang Weibing > > > > * Yao Wang > > > > * Zhangyi Chen > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that James Ge be appointed to > > > > the office of Vice President, Apache bRPC, to serve in accordance with > > > > and subject to the direction of the Board of Directors and the Bylaws of > > > > the Foundation until death, resignation, retirement, removal or > > > > disqualification, or until a successor is appointed; and be it further > > > > RESOLVED, that the Apache bRPC Project be and hereby is tasked with the > > > > migration and rationalization of the Apache Incubator bRPC podling; and > > > > be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > > > bRPC podling encumbered upon the Apache Incubator PMC are hereafter > > > > discharged. > > > > > > [1] https://lists.apache.org/thread/nb3sw03skm2j80rxnv0xxwyl4lnbwky1 > > > > [2] https://incubator.apache.org/projects/brpc.html > > > > [3] https://whimsy.apache.org/roster/ppmc/brpc > > > > [4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-202 > > > > [5] > > > https://github.com/apache/incubator-brpc/wiki/Maturity-Assessment-for-bRPC > > > > [6] https://whimsy.apache.org/pods/project/brpc > > > > [7] > https://github.com/apache/incubator-brpc/issues?q=is%3Aissue+is%3Aclosed > > > > [8] https://github.com/apache/incubator-brpc/pulls?q=is%3Apr+is%3Aclosed > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [DISCUSS] Graduate Apache bRPC（incubating）
Good to me. I did recheck, https://github.com/baidu/brpc-java repository has changed to https://github.com/baidu/starlight, as well as the source codes' package. Thanks, and good luck. Sheng Wu 吴晟 Twitter, wusheng1108 Willem Jiang 于2022年11月9日周三 17:01写道： > > Hi Weibing， > > Thanks for the update. It looks good to me now :) > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, Nov 9, 2022 at 1:15 PM Wang Weibing wrote: > > > > Thanks, Willem. > > > > I have update [1] and [2] adding company information about the PPMC > > members and committers. > > > > [1] > > https://github.com/apache/incubator-brpc/wiki/Maturity-Assessment-for-bRPC > > [2] https://brpc.apache.org/docs/community/committers/ > > > > Best regards > > Weibing > > > > On 2022/11/09 03:59:05 Willem Jiang wrote: > > > I checked the Independency section of the Maturity Assessment for > > > bRPC[1] with the website page[2]. > > > It's hard to tell the contribution if the Affiliation is Apache. > > > Could you update the information about these PPMC members and committers? > > > > > > [1]https://github.com/apache/incubator-brpc/wiki/Maturity-Assessment-for-bRPC > > > [2]https://brpc.apache.org/docs/community/committers/ > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Wed, Nov 9, 2022 at 8:28 AM Jerry Tan wrote: > > > > > > > > It looks like there is no issue with this, > > > > I will keep discussing it for 3 days, and start to vote the next day. > > > > > > > > thanks. > > > > > > > > > > > > On 2022/11/06 16:46:28 Jerry Tan wrote: > > > > > Hi， Dear IPMC members， > > > > > > > > > > > > > > > Apache bRPC has been incubating since 2018-11-13. > > > > > > > > > > Within this time, the bRPC community has made great progress, > > > > > > > > > > has adopted the Apache way and grown with the help of our mentors. > > > > > > > > > > The bRPC community believes that we have met the conditions for > > > > > graduation > > > > > > > > > > and have discussed [1] and voted [2] for graduation with the result > > > > > at [3]. > > > > > > > > > > > > > > > So, we'd like to start the discussion and would appreciate any > > > > > feedback > > > > > toward graduation! > > > > > > > > > > We are happy to answer any questions - below are some facts and > > > > > project > > > > > highlights from the incubation phase as well as the draft resolution. > > > > > > > > > > > > > > > This is also an excellent opportunity to say a big thank you to our > > > > > mentors. > > > > > > > > > > > > > > > I really appreciated the prompt help at any time during incubation > > > > > for the > > > > > many questions we had. Thanks a lot, Von, JB and PanJuan! > > > > > > > > > > > > > > > Cheers > > > > > > > > > > Jerry Tan > > > > > > > > > > > > > > > --- > > > > > > > > > > Project Updates since incubation: > > > > > > > > > > --- > > > > > > > > > > > > > > > 1. We release 1.0.0,1.1.0, 1.2.0, 1.3.0, 4 apache releases, and 0.9.6, > > > > > 0.9.7, 2 disclaim releases; by > > > > > > > > > > different release managers (including Jerry Tan, Zhu Jiashun, Lorin > > > > > Lee, > > > > > > > > > > Wang Weibing, Liu Shuai, Hu Xiguo) (see it at [4]) > > > > > > > > > > > > > > > 2. We add 5 new PPMC members including Jiashun Zhu, Wang Weibing, Cai > > > > > > > > > > Daojin, He Lei, and Lorin Lee. see it at [4]. Now we have 10 PPMC > > > > > members > > > > > altogether, they are from different companies, > > > > > > > > > > Including ByteDance(Ge Jun, He Lei), Baidu(Wang Yao, Wang > > > > > Weibing),Google(Zhu Jiashun), 4Paradigm(Tan Zhongyi), Shopee( Cai > > > > > Daojin), > > > > > Mom
Re: [VOTE] Accept Pekko into the Apache Incubator
+1 binding Welcome Sheng Wu 吴晟 Twitter, wusheng1108 PJ Fanning 于2022年10月19日周三 17:32写道： > > Thanks Claude and Ryan for putting together the proposal. > > +1 binding > > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr > wrote: > > > > I'll even kick off the voting: > > > > +1 binding > > > > On Wed, Oct 19, 2022 at 9:04 AM Claude Warren, Jr > > wrote: > > > > > After reviewing the [DISCUSS] threads concerning bringing Pekko into the > > > incubator [1][2], and finding that there is no further comment, I am > > > calling for a VOTE to accept Pekko into the Apache Incubator. The text of > > > the proposal is included below for convenience, final and definitive text > > > is in the Pekko Proposal from the Incubator wiki.[3] . > > > > > > Thank you for your time and consideration, > > > Claude > > > > > > [1] https://lists.apache.org/thread/1t0x6d815td9dgjxhck51b5txcjm28rr > > > [2] https://lists.apache.org/thread/cjo86gdwvqlqslq68gd0c8hxq6ds6yrz > > > [3] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal > > > > > > *Pekko Proposal* > > > > > > *Abstract* > > > > > > Pekko is a toolkit and an ecosystem for building highly concurrent, > > > distributed, reactive and resilient applications for Java and Scala. > > > > > > *Proposal* > > > > > > Pekko is a toolkit that brings the actor model (popularised by Erlang) to > > > the JVM, providing the basis for building both locally and distributed > > > concurrency. On top of this Pekko provides a rich set of libraries built > > > on > > > top of Actors to solve modern problems, including: > > > > > >- Streams: Fully bi-directional backpressured streams following the > > >Reactive manifesto > > >- HTTP: A fully streamed HTTP client/server built on top of streams > > >that also provides expected tools (such as connection pooling) > > > necessary > > >for highly available web services > > >- connectors: A rich set of connectors for various databases, > > >messaging, persistent services built on top of streams > > >- grpc: A gRPC server/client > > >- projection: Provides abstractions necessary for CQRS pattern such as > > >envelope, necessary for systems such as Kafka. > > > > > > *Background* > > > > > > Pekko is a fork of the Akka project just before its licence changed from > > > Apache 2 to Business Source License 1.1. The project provides a set of > > > tools and frameworks that covers the complex problem space of distributed > > > concurrent systems. It is designed to support the design principles of the > > > Reactive Manifesto by providing components to efficiently scale up systems > > > within a server or scale out across multiple servers, are high > > > performance, > > > resilient to failure, distributed systems without a single point of > > > failure. > > > > > > *Rationale* > > > > > > There is a large cohort of applications and libraries that were dependent > > > upon the original open source version of this project. Numerous developers > > > contributed their time in the belief that the project would stay open > > > source. When the licence was changed the work of those developers was > > > locked up and a vital resource for the cohort of applications and > > > libraries > > > disappeared. Apache Flink is an example of a library that used the > > > original > > > library upon which this project is based. This project is to continue the > > > open source development that was promised under the original Apache 2 > > > licence. We ask that the Apache Foundation accept this project so as to > > > prevent any future incompatible licence switch in the future. > > > > > > Apache has a long standing tradition of not accepting hostile forks. There > > > has been some discussion of whether this project violates that tradition. > > > We believe that it does not. > > > > > > For many years, Lightbend has been a steward for this open source project, > > > attracting contributions from many developers and building a community > > > under the Apache License. It's within their rights to offer their future > > > work under a different licence. The Pekko project will provide the > > > continuity of an Apache-licensed home for long-term support, maintenance >
Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members.
+1 to keep the NOTICE and remove 72 hours waiting. Sheng Wu 吴晟 Twitter, wusheng1108 Calvin Kirs 于2022年10月14日周五 08:37写道： > > On Fri, Oct 14, 2022 at 6:57 AM Dave Fisher wrote: > > > > > > > > Sent from my iPhone > > > > > On Oct 13, 2022, at 3:46 PM, Justin Mclean > > > wrote: > > > > > > Hi, > > > > > > The board recently changed the 72-hour waiting time to add a PMC member > > > to a top level project. We have the same 72-hour waiting time to add PPMC > > > members to a podling. > > > > > > Do we want to consider removing this 72-hour waiting time and just > > > require a PMC to notify the IPMC that they want to add someone? > > > > Let’s just require that they notify that a PPMC member has been added. > +1 > > > > > > 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 > > > > > -- > Best wishes！ > CalvinKirs > > - > 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] Accept Celeborn into the Apache Incubator
+1 binding Good luck, enjoy Sheng Wu 吴晟 Twitter, wusheng1108 张铎(Duo Zhang) 于2022年10月12日周三 13:24写道： > > +1 binding > > Furkan KAMACI 于2022年10月12日周三 12:58写道： > > > > +1 (binding) > > > > Good luck! > > > > On 11 Oct 2022 Tue at 21:57 Xiaoqiao He wrote: > > > > > +1 (binding) > > > > > > On Wed, Oct 12, 2022 at 12:43 Calvin Kirs wrote: > > > > > > > +1 (binding) > > > > > > > > On Wed, Oct 12, 2022 at 11:50 AM Yu Li wrote: > > > > > > > > > > Hi all, > > > > > > > > > > Following up on the [DISCUSS] thread on Celeborn [1] [2], I would like > > > to > > > > > call a VOTE to accept Celeborn into the Apache Incubator, please check > > > > out > > > > > the Celeborn Proposal from the incubator wiki [3]. > > > > > > > > > > Please cast your vote: > > > > > > > > > > [ ] +1, bring Celeborn into the Incubator > > > > > [ ] +0, I don't care either way > > > > > [ ] -1, do not bring Celeborn into the Incubator, because... > > > > > > > > > > The vote will open at least for 72 hours, and only votes from the > > > > Incubator > > > > > PMC are binding, but votes from everyone are welcome. > > > > > > > > > > Best Regards, > > > > > Yu > > > > > > > > > > [1] https://lists.apache.org/thread/rlkzg8m5923vngyon0bwcv97x3m68x4c > > > > > [2] https://lists.apache.org/thread/hjy3gpvocjtls5vp9h1llcvmwkgz3lcy > > > > > [3] > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/CelebornProposal > > > > > > > > > > > > > > > > -- > > > > Best wishes！ > > > > CalvinKirs > > > > > > > > - > > > > 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: package names (pekko related)
Hi I am not sure about Kafka and Netbeans cases, as I was not working inside the foundation back there. For the recent years' new podlings, `org.apache.*` is preferred by the incubator. Sheng Wu 吴晟 Twitter, wusheng1108 PJ Fanning 于2022年10月11日周二 20:14写道： > > Hi everyone, > > I'm creating a new thread to avoid filling the Pekko thread with emails that > are only partially related to the proposal. > > The current Akka code uses packages that start with 'akka.' and a lot of the > people involved with Pekko seem to prefer to keep the use 'pekko.' instead of > 'org.apache.pekko.' when we rename the Akka packages. > > Kafka and Netbeans are examples of Apache projects that don't use > 'org.apache' prefix in their package names. > > Is 'pekko.' a viable option or is there a strong preference within the ASF > and the Incubator PMC for 'org.apache.pekko.'? > > Regards, > PJ > > - > 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] Incubating Proposal for Pekko
I think mentors don't have to be committers. Just some initial committers could be mentors. This is not required. Sheng Wu 吴晟 Twitter, wusheng1108 Claude Warren, Jr 于2022年9月30日周五 16:20写道： > > Is is standard for mentors to be committers on the project? And should > they be listed in both sections. > > Claude > > On Fri, Sep 30, 2022 at 9:15 AM Claude Warren, Jr > wrote: > > > Tison, > > > > I send the email yesterday before submitting the proposal. Thanks for the > > heads up though. > > > > As to the other part, I think I will remove myself from the committer list > > at this time. > > > > On Thu, Sep 29, 2022 at 6:23 PM tison wrote: > > > >> Hi Claude, > >> > >> Thanks for starting this discussion! +1 to this proposal. > >> > >> It answers my previous questions on > >> https://lists.apache.org/thread/hdknoyvr9c0d4j70xqw6t2t7gnbzc7nq a new > >> name + a clear goal. > >> > >> I'm interested to act as a mentor to help with this podling's growth. > >> > >> w.r.t the membership, I notice that Claude Warren and PJ Fanning are > >> listed > >> on both initial committers and mentors, while other mentors don't. Perhaps > >> you should check what's the intention here. > >> > >> Also, Claude Warren (you) and PJ Fanning are Apache members who can become > >> IPMC members with a notice, but it still needs to go through the > >> process[1][2]. > >> > >> Best, > >> tison. > >> > >> [1] > >> > >> https://incubator.apache.org/guides/roles_and_responsibilities.html#incubator_project_management_committee_ipmc > >> [2] https://lists.apache.org/thread/t6k3mg97pyshzoxzjg4c62n166l3crcw > >> > >> > >> > >> Jean-Baptiste Onofré 于2022年9月29日周四 23:36写道： > >> > >> > Hi Claude > >> > > >> > Very interesting. I would be more than happy to mentor this podling (if > >> > accepted of course). > >> > > >> > I will take a deeper look on the proposal wiki page. > >> > > >> > Thanks ! > >> > > >> > Regards > >> > JB > >> > > >> > Le jeu. 29 sept. 2022 à 16:57, Claude Warren, Jr > >> > a écrit : > >> > > >> > > Greetings, > >> > > > >> > > I would like to propose Pekko [1] as a new Apache Incubator project. > >> > > > >> > > Pekko is a toolkit that brings the actor model (popularised by > >> Erlang) to > >> > > the JVM, providing the basis for building both locally and distributed > >> > > concurrency. On top of this Pekko provides a rich set of libraries > >> built > >> > on > >> > > top of Actors to solve modern problems, including: > >> > > > >> > > > >> > >- Streams: Fully bi-directional backpressured streams following the > >> > >Reactive manifesto > >> > >- HTTP: A fully streamed HTTP client/server built on top of streams > >> > that > >> > >also provides expected tools (such as connection pooling) necessary > >> > for > >> > >highly available web services > >> > >- connectors: A rich set of connectors for various databases, > >> > messaging, > >> > >persistent services built on top of streams > >> > >- grpc: A gRPC server/client > >> > >- projection: Provides abstractions necessary for CQRS pattern > >> such as > >> > >envelope, necessary for systems such as Kafka. > >> > > > >> > > > >> > > > >> > > Controversially Pekko is a fork of the Akka project just prior to its > >> > > licence changed from Apache 2 to Business Source License 1.1. > >> > > > >> > > I look forward to your feedback and discussions, > >> > > > >> > > Thank you, > >> > > Claude Warren > >> > > [1] > >> https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal > >> > > > >> > > >> > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [brpc] What is baidu bprc?
Thanks for making this clear. I have updated this with PR, this would not block that pull request. Wait for the update of project renaming. zhongyi tan 于2022年9月19日 周一12:24写道： > After the call, Liu Tao told me that the repo has changed its name from > brpc-java to starlight. > > that's great. > > > > > On Mon, Sep 19, 2022 at 12:18 PM Jerry Tan wrote: > > > Just called the current maintainer of brpc-java ---Liu Tao， > > and he said that he would change its name to a new name for the next > > release, maybe next month. > > brpc-java has changed its project scope, so changing the project name is > > what he preferred. > > > > Thanks. > > > > > > > > On Mon, Sep 19, 2022 at 10:15 AM Jerry Tan wrote: > > > >> thanks， wusheng. > >> > >> we will check it out. > >> > >> On 2022/09/19 01:06:09 Sheng Wu wrote: > >> > Hi brpc and mentors > >> > > >> > I was reviewing a PR[1] in SkyWalking project, which made my attention > >> > about what is com.baidu/brpc-java. > >> > AFAIK, brpc as a podling has been donated into the incubator years > >> > ago, And with check the dependencies of the PR, I can see brpc-java is > >> > still in maintaining mode by using brpc name in the maven > >> > repository[2] > >> > > >> > I am feeling this is a branding issue for a podling. > >> > > >> > [1] https://github.com/apache/skywalking-java/pull/319/ > >> > [2] https://mvnrepository.com/artifact/com.baidu/brpc-java > >> > > >> > Sheng Wu 吴晟 > >> > Twitter, wusheng1108 > >> > > >> > - > >> > To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org > >> > For additional commands, e-mail: dev-h...@brpc.apache.org > >> > > >> > > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org > >> For additional commands, e-mail: dev-h...@brpc.apache.org > >> > >> > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
[brpc] What is baidu bprc?
Hi brpc and mentors I was reviewing a PR[1] in SkyWalking project, which made my attention about what is com.baidu/brpc-java. AFAIK, brpc as a podling has been donated into the incubator years ago, And with check the dependencies of the PR, I can see brpc-java is still in maintaining mode by using brpc name in the maven repository[2] I am feeling this is a branding issue for a podling. [1] https://github.com/apache/skywalking-java/pull/319/ [2] https://mvnrepository.com/artifact/com.baidu/brpc-java Sheng Wu 吴晟 Twitter, wusheng1108 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire Hivemall from Incubator
+1 binding Felix Cheung 于2022年8月29日 周一10:22写道： > +1 (binding) > > > On Sun, Aug 28, 2022 at 7:06 PM Dave Fisher wrote: > > > +1 (binding) > > > > Sent from my iPhone > > > > > On Aug 27, 2022, at 11:57 PM, Calvin Kirs wrote: > > > > > > Hi IPMC, > > > > > > Hivemall has been incubating since 2016-09-13. > > > > > > From last year, activity has been low and the chances of attracting new > > > committers and building a vibrant community seem very slim at this > point. > > > > > > The dev community vote was started by the PPMC for over a month and > > > can be found here[1],[2] > > > > > > I therefore propose to retire Hivemall from the Incubator. > > > > > > I want to start this official vote. > > > > > > Voting will start now and will remain open for at least 72 hours. > > > > > > Notice: Because the dev vote didn't get enough +1's, this vote is not > > > the same as usual, it's not a laze vote. > > > > > > [ ] +1 Retire the project > > > [ ] +0 No opinion. > > > [ ] -1 Do not retire the project because... > > > > > > [1]https://lists.apache.org/thread/3s7bjgqm7864qbwnf1ny3lszklm65sgn > > > [2]https://lists.apache.org/thread/cv267tds166z7vtbzjt46nrz26xhzgvb > > > > > > -- > > > Best wishes！ > > > CalvinKirs > > > > > > - > > > 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 > > > > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [DISCUSS] Incubating Proposal for StreamPark
Hi StreamPark team AFAIK from a Java developer perspective, your GPL and LGPLthings are not hard dependencies. The log component could be easier to be replaced as log4j2, and mysql connector should be possible to be optional, such as you pick Postgre as your major storage option. Please be clear about this before the vote process. Sheng Wu 吴晟 Twitter, wusheng1108 Justin Mclean 于2022年8月24日周三 14:02写道： > > Hi, > > I notice the project has some GPL and LGPL dependancies, this would not be > compatible with the Apache license, unless they are optional and the majority > of users not use them. If they are not optional, how do you intend to remove > these? > > 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: A license check tool offered by Apache SkyWalking Community
AFAIK, we haven't done this. But in theory, we could introduce Apache Catalog A/B/X to support the compatibility check. If you want to help the project to support this, submit an issue here, https://github.com/apache/skywalking/issues. Sheng Wu 吴晟 Twitter, wusheng1108 Xiaofeng 于2022年8月24日周三 13:33写道： > > Hi, > > Will checking license compatible be a feature in the future? > > Regards, > Xiaofeng > > Justin Mclean 于 2022年8月23日周二 16:13写道： > > > Hi, > > > > So taking a quick look at a SkyWalking release [1] I can see a couple of > > minor issues with LICNSE and NOTICE. You may want to fix these. > > > > Hints: > > Is OpenCensus mentioned in LICENSE? > > Does prometheus client_model have a NOTICE file? > > Does mavin-wrapper have a NOTICE file? > > > > Also there is a compiled code (a jar) in the source release. Source > > release cannot include compiled code. > > > > Kind Regards, > > Justin > > > > 1. > > https://www.apache.org/dyn/closer.cgi/skywalking/9.1.0/apache-skywalking-apm-9.1.0-src.tgz > > < > > https://www.apache.org/dyn/closer.cgi/skywalking/9.1.0/apache-skywalking-apm-9.1.0-src.tgz > > > > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A license check tool offered by Apache SkyWalking Community
Justin Mclean 于2022年8月23日周二 15:50写道： > > Hi, > > Also remember that it’s only code that ends up in the release and not all > dependancies that impact the LICENSE and NOTICE files. Agree. The tool would not be perfect, it just reduces the workload from a manual dependencies analysis. Sheng Wu 吴晟 Twitter, wusheng1108 > > 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: A license check tool offered by Apache SkyWalking Community
Yu Xiao 于2022年8月23日周二 15:44写道： > > Hi > > It is very good. > > Will the following features be available in the future ： > > Comparison of license files with dependencies (e.g. license files with > missing some). It is available if you directly use GHA. SkyWalking uses this - GHA https://github.com/apache/skywalking/blob/77ba2d553d77a4acacd8b2498cb09ea983a9baf4/.github/workflows/skywalking.yaml#L57 The tool would resolve the licenses of runtime dependencies and apply this template(https://github.com/apache/skywalking/blob/77ba2d553d77a4acacd8b2498cb09ea983a9baf4/.github/workflows/skywalking.yaml#L81) to do binary license checking(use `git diff`). Sheng Wu 吴晟 Twitter, wusheng1108 > > Best wishes! > > Yu Xiao > Apache ShenYu > > Sheng Wu 于2022年8月23日周二 15:00写道： > > > > Hi podlings > > > > Apache SkyWalking graduated from the incubator years ago, but we still > > remember we were struggling to keep licenses of dependencies well > > organized and listed correctly. > > So, SkyWalking PMC/Committer worked with the community starting to > > build a tool to help with the license header and dependencies checker. > > > > I am honored to share that, this tool is well built and widely used in > > and out of the ASF projects. > > > > https://github.com/apache/skywalking-eyes > > > > Apache SkyWalking eyes is a full-featured license tool to check and > > fix license headers and resolve dependencies' licenses, with various > > languages support. > > No matter whether your source codes are in hybrid license headers, or > > a monorepo requires a consistent tool to check dependencies from > > different dependency management tools. It works. > > > > Also, as GitHub Action is widely used in the ASF projects, SkyWalking > > eyes provide integration with GHA, as well as binary tar and docker > > image[1] for other CI platforms. > > > > We hope this project could help incubating projects, especially new > > podlings, to analyze dependencies easier. > > > > [1] https://hub.docker.com/r/apache/skywalking-eyes > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > - > > 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
A license check tool offered by Apache SkyWalking Community
Hi podlings Apache SkyWalking graduated from the incubator years ago, but we still remember we were struggling to keep licenses of dependencies well organized and listed correctly. So, SkyWalking PMC/Committer worked with the community starting to build a tool to help with the license header and dependencies checker. I am honored to share that, this tool is well built and widely used in and out of the ASF projects. https://github.com/apache/skywalking-eyes Apache SkyWalking eyes is a full-featured license tool to check and fix license headers and resolve dependencies' licenses, with various languages support. No matter whether your source codes are in hybrid license headers, or a monorepo requires a consistent tool to check dependencies from different dependency management tools. It works. Also, as GitHub Action is widely used in the ASF projects, SkyWalking eyes provide integration with GHA, as well as binary tar and docker image[1] for other CI platforms. We hope this project could help incubating projects, especially new podlings, to analyze dependencies easier. [1] https://hub.docker.com/r/apache/skywalking-eyes Sheng Wu 吴晟 Twitter, wusheng1108 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
Thanks for the update. My <1> - <5> should have been resolved. Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2022年8月19日周五 09:40写道： > > > Add words about you have checked with major contributors > > Added words in the "Initial Committers" section based on @benjobs's comment. > > Best, > tison. > > > tison 于2022年8月19日周五 08:59写道： > > > FYI, > > > > > 2. List initial committers with their GitHub accounts. > > > > It's updated in the proposal. Pick here: > > > > * [benjobs](https://github.com/wolfboys) [benj...@apache.org] > > * [Al-assad](https://github.com/Al-assad) [assad@outlook.com] > > * [xinzhuxiansheng](https://github.com/xinzhuxiansheng) [ > > xinzhuxianshen...@gmail.com] > > * [MonsterChenzhuo](https://github.com/MonsterChenzhuo) [ > > monster.zhuoyuc...@gmail.com] > > * [lvshaokang](https://github.com/lvshaokang) [lvshaoka...@gmail.com] > > * [monrg](https://github.com/monrg) [wangmo...@gmail.com] > > * [tamer.ning](https://github.com/GuoNingNing) [tamer.n...@gmail.com] > > > > Best, > > tison. > > > > > > Sheng Wu 于2022年8月19日周五 08:54写道： > > > >> Thanks for updating. I recommend to > >> 1. Fix headers > >> 2. List initial committers with their GitHub accounts. > >> 3. Add words about you have checked with major contributors, only the > >> listed ppl want to join the initial committer team, if you don't have > >> an open discussion(You just mentioned you asked, so I guess they are > >> all not public) > >> > >> Sheng Wu 吴晟 > >> Twitter, wusheng1108 > >> > >> huajie wang 于2022年8月18日周四 23:30写道： > >> > > >> > Hi, Sheng. I'm benjobs the author of the StreamPark project. about the > >> > questions you mentioned: > >> > > >> > 1. Copyright statement problem, we will fix it. > >> > > >> > 2. About the initial committer: Currently there are 59 contributors. I > >> have > >> > tried to contact these 59 contributors. At present, only the 7 > >> contributors > >> > who are willing to become a committer have been contacted, and their > >> code > >> > submission times, code volume and contribution value are ranked high > >> > > >> > 3. About ICLA: I have contacted all the top 20 contributors and will > >> sign > >> > ICLA. Other contributors will try to contact. > >> > > >> > Sheng Wu 于2022年8月18日周四 22:16写道： > >> > > >> > > Several questions > >> > > > >> > > 1. Many source codes in the repository declare `Licensed to the Apache > >> > > Software Foundation (ASF)`[1], which is wrong. As an out-of-foundation > >> > > project, `licensed to the ASF`. Could you correct this? > >> > > The correct header should be like this > >> > > ``` > >> > > /* > >> > > * Copyright 2018 x > >> > > * > >> > > * Licensed under the Apache License, Version 2.0 (the "License"); > >> > > * you may not use this file except in compliance with the License. > >> > > * You may obtain a copy of the License at > >> > > * > >> > > * http://www.apache.org/licenses/LICENSE-2.0 > >> > > * > >> > > * Unless required by applicable law or agreed to in writing, software > >> > > * distributed under the License is distributed on an "AS IS" BASIS, > >> > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or > >> implied. > >> > > * See the License for the specific language governing permissions and > >> > > * limitations under the License. > >> > > */ > >> > > ``` > >> > > 2. `com.streamxhub` is used for the package of source codes, as well > >> > > as `https://streamxhub.com/` <https://streamxhub.com/> < > >> https://streamxhub.com/> is used for > >> > > project website. Is > >> > > streamxhub a company/legal entity? Who or which company owns this > >> > > project? `.com` usually means a company. We may need an SGA in the > >> > > donation process. > >> > > 3. I can't see the initial committers' GitHub accounts, could you make > >> > > them clear in the proposal? > >> > > 4. I can see at least 59 GitHub accounts/contributors contributed to > >>
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
Thanks for updating. I recommend to 1. Fix headers 2. List initial committers with their GitHub accounts. 3. Add words about you have checked with major contributors, only the listed ppl want to join the initial committer team, if you don't have an open discussion(You just mentioned you asked, so I guess they are all not public) Sheng Wu 吴晟 Twitter, wusheng1108 huajie wang 于2022年8月18日周四 23:30写道： > > Hi, Sheng. I'm benjobs the author of the StreamPark project. about the > questions you mentioned: > > 1. Copyright statement problem, we will fix it. > > 2. About the initial committer: Currently there are 59 contributors. I have > tried to contact these 59 contributors. At present, only the 7 contributors > who are willing to become a committer have been contacted, and their code > submission times, code volume and contribution value are ranked high > > 3. About ICLA: I have contacted all the top 20 contributors and will sign > ICLA. Other contributors will try to contact. > > Sheng Wu 于2022年8月18日周四 22:16写道： > > > Several questions > > > > 1. Many source codes in the repository declare `Licensed to the Apache > > Software Foundation (ASF)`[1], which is wrong. As an out-of-foundation > > project, `licensed to the ASF`. Could you correct this? > > The correct header should be like this > > ``` > > /* > > * Copyright 2018 x > > * > > * Licensed under the Apache License, Version 2.0 (the "License"); > > * you may not use this file except in compliance with the License. > > * You may obtain a copy of the License at > > * > > * http://www.apache.org/licenses/LICENSE-2.0 > > * > > * Unless required by applicable law or agreed to in writing, software > > * distributed under the License is distributed on an "AS IS" BASIS, > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > > * See the License for the specific language governing permissions and > > * limitations under the License. > > */ > > ``` > > 2. `com.streamxhub` is used for the package of source codes, as well > > as `https://streamxhub.com/` <https://streamxhub.com/> is used for > > project website. Is > > streamxhub a company/legal entity? Who or which company owns this > > project? `.com` usually means a company. We may need an SGA in the > > donation process. > > 3. I can't see the initial committers' GitHub accounts, could you make > > them clear in the proposal? > > 4. I can see at least 59 GitHub accounts/contributors contributed to > > this project, and the initial committer team has 7 members, how about > > the other 52? Such as GitHub ID(xxyykkxx) #14 on the contributor list. > > He/she has over 12k LOC. Would ppl like him/her to submit ICLA? > > 5. How does this community/entity/org determine the initial committer > > candidate? Would others be happy with the current candidate list? > > Would others like to join the initial team? > > > > > > > > [1] > > https://github.com/streamxhub/streamx/blob/v1.0.0-beta.1/streamx-flink/streamx-flink-core/src/main/java/com/streamxhub/streamx/flink/core/java/function/HBaseQueryFunction.java#L4 > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > Sherlock Homles 于2022年8月18日周四 21:34写道： > > > > > > +1 (non-binding) > > > > > > StreamPark is a very great project. I have used it for a long time. > > > > > > tison 于2022年8月18日周四 21:15写道： > > > > > > > > Thanks for your feedback! I'm going to keep the discussion for a while > > and > > > > start a vote the next week. > > > > > > > > Best, > > > > tison. > > > > > > > > > > > > Mingyu Chen 于2022年8月18日周四 20:23写道： > > > > > > > > > +1 (non-binding) > > > > > Good to see StreamPark to join the Incubator. > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > 此致！Best Regards > > > > > 陈明雨 Mingyu Chen > > > > > > > > > > Email: > > > > > morning...@apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 在 2022-08-18 15:27:26，"Jark Wu" 写道： > > > > > >+1 (non-binding) > > > > > >
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
Sheng Wu 于2022年8月18日周四 22:15写道： > > Several questions > > 1. Many source codes in the repository declare `Licensed to the Apache > Software Foundation (ASF)`[1], which is wrong. As an out-of-foundation > project, `licensed to the ASF`. Could you correct this? > The correct header should be like this > ``` > /* > * Copyright 2018 x > * > * Licensed under the Apache License, Version 2.0 (the "License"); > * you may not use this file except in compliance with the License. > * You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ > ``` > 2. `com.streamxhub` is used for the package of source codes, as well > as `https://streamxhub.com/` is used for project website. Is > streamxhub a company/legal entity? Who or which company owns this > project? `.com` usually means a company. We may need an SGA in the > donation process. > 3. I can't see the initial committers' GitHub accounts, could you make > them clear in the proposal? > 4. I can see at least 59 GitHub accounts/contributors contributed to > this project, and the initial committer team has 7 members, how about > the other 52? Such as GitHub ID(xxyykkxx) #14 on the contributor list. > He/she has over 12k LOC. Would ppl like him/her to submit ICLA? I found this in the doc ``` Once StreamPark is approved to join Apache Incubator, the Initial committers will submit iCLA(s). The code is already licensed under Apache Software 2.0. Since no organization owns StreamPark, there's no entity to sign the SGA. We will ask the top 20 contributors to sign iCLAs for IP clearance. ``` I think <4> should be fine, just feel a little surprised to see a `.com` domain only belonging to an individual group. > 5. How does this community/entity/org determine the initial committer > candidate? Would others be happy with the current candidate list? > Would others like to join the initial team? > > > > [1] > https://github.com/streamxhub/streamx/blob/v1.0.0-beta.1/streamx-flink/streamx-flink-core/src/main/java/com/streamxhub/streamx/flink/core/java/function/HBaseQueryFunction.java#L4 > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > Sherlock Homles 于2022年8月18日周四 21:34写道： > > > > +1 (non-binding) > > > > StreamPark is a very great project. I have used it for a long time. > > > > tison 于2022年8月18日周四 21:15写道： > > > > > > Thanks for your feedback! I'm going to keep the discussion for a while and > > > start a vote the next week. > > > > > > Best, > > > tison. > > > > > > > > > Mingyu Chen 于2022年8月18日周四 20:23写道： > > > > > > > +1 (non-binding) > > > > Good to see StreamPark to join the Incubator. > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > 此致！Best Regards > > > > 陈明雨 Mingyu Chen > > > > > > > > Email: > > > > morning...@apache.org > > > > > > > > > > > > > > > > > > > > > > > > 在 2022-08-18 15:27:26，"Jark Wu" 写道： > > > > >+1 (non-binding) > > > > > > > > > >StreamPark is a nice name. Good luck! > > > > > > > > > >Best, > > > > >Jark Wu > > > > > > > > > >On 2022/08/18 01:50:10 Willem Jiang wrote: > > > > >> It's my pleasure to be the mentor of StreamPark. > > > > >> Please check out the proposal in the incubator wiki page and give > > > > >> your > > > > >> feedback. > > > > >> > > > > >> Willem Jiang > > > > >> > > > > >> Twitter: willemjiang > > > > >> Weibo: 姜宁willem > > > > >> > > > > >> On Wed, Aug 17, 2022 at 11:05 AM tison wrote: > > > > >> > > > > > >> > I follow a previous proposal (Kvrocks) to send a digest to general@ > > > > while > > > > >> > linking the complete proposal to > > > > >> > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > > > > >> > >_< > &
Re: Re: [DISCUSS] Incubating Proposal for StreamPark
Several questions 1. Many source codes in the repository declare `Licensed to the Apache Software Foundation (ASF)`[1], which is wrong. As an out-of-foundation project, `licensed to the ASF`. Could you correct this? The correct header should be like this ``` /* * Copyright 2018 x * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ ``` 2. `com.streamxhub` is used for the package of source codes, as well as `https://streamxhub.com/` is used for project website. Is streamxhub a company/legal entity? Who or which company owns this project? `.com` usually means a company. We may need an SGA in the donation process. 3. I can't see the initial committers' GitHub accounts, could you make them clear in the proposal? 4. I can see at least 59 GitHub accounts/contributors contributed to this project, and the initial committer team has 7 members, how about the other 52? Such as GitHub ID(xxyykkxx) #14 on the contributor list. He/she has over 12k LOC. Would ppl like him/her to submit ICLA? 5. How does this community/entity/org determine the initial committer candidate? Would others be happy with the current candidate list? Would others like to join the initial team? [1] https://github.com/streamxhub/streamx/blob/v1.0.0-beta.1/streamx-flink/streamx-flink-core/src/main/java/com/streamxhub/streamx/flink/core/java/function/HBaseQueryFunction.java#L4 Sheng Wu 吴晟 Twitter, wusheng1108 Sherlock Homles 于2022年8月18日周四 21:34写道： > > +1 (non-binding) > > StreamPark is a very great project. I have used it for a long time. > > tison 于2022年8月18日周四 21:15写道： > > > > Thanks for your feedback! I'm going to keep the discussion for a while and > > start a vote the next week. > > > > Best, > > tison. > > > > > > Mingyu Chen 于2022年8月18日周四 20:23写道： > > > > > +1 (non-binding) > > > Good to see StreamPark to join the Incubator. > > > > > > > > > > > > > > > -- > > > > > > 此致！Best Regards > > > 陈明雨 Mingyu Chen > > > > > > Email: > > > morning...@apache.org > > > > > > > > > > > > > > > > > > 在 2022-08-18 15:27:26，"Jark Wu" 写道： > > > >+1 (non-binding) > > > > > > > >StreamPark is a nice name. Good luck! > > > > > > > >Best, > > > >Jark Wu > > > > > > > >On 2022/08/18 01:50:10 Willem Jiang wrote: > > > >> It's my pleasure to be the mentor of StreamPark. > > > >> Please check out the proposal in the incubator wiki page and give your > > > >> feedback. > > > >> > > > >> Willem Jiang > > > >> > > > >> Twitter: willemjiang > > > >> Weibo: 姜宁willem > > > >> > > > >> On Wed, Aug 17, 2022 at 11:05 AM tison wrote: > > > >> > > > > >> > I follow a previous proposal (Kvrocks) to send a digest to general@ > > > while > > > >> > linking the complete proposal to > > > >> > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > > > >> > >_< > > > >> > > > > >> > Best, > > > >> > tison. > > > >> > > > > >> > > > > >> > > > >> - > > > >> 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: [DISCUSS] Incubating Proposal for StreamPark
Hi, Could you reformat this proposal to follow the proposal template? There is something like project owner, dependencies, initial committers, experienced developers etc. are not clear right now. tison 于2022年8月17日 周三09:15写道： > Hi all, > > I would like to propose StreamPark[1] as a new apache incubator project, > you can find the proposal[2] of StreamPark for more detail. > > StreamPark is a streaming application development platform. Aimed at ease > building and managing streaming applications, StreamPark provides > scaffolding for writing streaming process logic with Apache Flink and > Apache Spark. Also, StreamPark provides a dashboard for controlling and > monitoring streaming tasks. It was initially known as StreamX and renamed > to StreamPark in August 2022. > > StreamPark abstracts the environment and program parameters of task > development and deployment in a convention over configuration manner for > low code development. It initializes a runtime environment and context and > combines it with a series of connectors to simplify development. From the > aspect of a task management platform, StreamPark is a streaming data > management platform based on the JVM platform. > > So far, StreamPark has accumulated a few users, and the accrued download > time is over 5,000. The representative users are Baidu, China Unicom, > Ziroom, Yonghui Supermarket, InMobi, YTO Express, and so on. StreamPark has > built an open-source community with 52 developers and released over ten > versions in the past year. > > The proposed initial committers are interested in joining ASF to increase > the connections in the open-source world. Based on extensive collaboration, > it is possible to build a community of developers and committers that live > longer than the founder. Also, the Apache Brand can help encourage more > organizations to use StreamPark more confidently. > > We believe that the StreamPark project will provide diversity value for the > community if StreamPark is introduced into the Apache incubator. > > I (@tison) will help this project as the champion and many thanks to four > other mentors: > > * Willem Ning Jiang [ningji...@apache.org] > * Stephan Ewen [se...@apache.org] > * Thomas Weise [t...@apache.org] > * Duo Zhang [zhang...@apache.org] > > Best, > tison. > > [1] https://github.com/streamxhub/streamx > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [Branding Issue] Shenyu is still decleared as a project of dromara community
Hi, John In a short version, they are not a legal entity. But they work like one. They worked like a virtual org, including accepting project donation, transfer projects from individual to an org, announce news from an org perspective to present this project. I believe the major reason of not being a legal entity, is that, it is hard to regisr a foundation in China. It is not about supporting projects, guide or providing local support or docs. Those are totally fine. But dromara doesn't provide that. > Dromara > 是由国内顶尖的开源项目作者共同组成的开源社区。提供包括开源网关，分布式事务，流行工具，企业级认证，微服务RPC，运维监控，Agent监控，分布式日志，调度编排等一系列开源产品、解决方案与咨询、技术支持与培训认证服务。技术栈全面开源共建、 保持社区中立，致力于为全球用户提供微服务云原生解决方案。让参与的每一位开源爱好者，体会到开源的快乐。 Dromara开源社区目前拥有10+GVP项目，总star数量超过7万，构建了上万人的开源社区，有成千上万的个人及团队在使用Dromara社区的开源项目。 This is their own statement. It clearly declare (owns projects) John D. Ament 于2022年7月3日 周日00:41写道： > Hi > > My questions have mostly to do with translations, as the source sites are > predominantly in Chinese, not a language I understand. > > On Wed, Jun 29, 2022 at 8:38 PM Sheng Wu > wrote: > > > Hi Shenyu and incubator > > > > Shenyu is going to graduate in next month, I accidentally have a > > chance to review its original org, Dromara, due to some reviews for > > SkyWalking PR. > > > > There are two things concerning me. > > 1. Dromara website[1] still declare Shenyu(even with Apache prefix) on > > its project page. I think this is wrong and confusing end-users. As > > this project has been donated for a long time, why it is still hosted > > there? > > > > > What exactly does it mean for a project to be listed on the projects page > here? I didn't see any descriptive text, but nothing on the page looked > like ownership. I'm not sure if Dromara is a commercial entity or not, but > it's OK for a commercial company to provide support/capabilities for an > Apache project. See AmazonMQ for Apache ActiveMQ as an example of this. > > > > 2. Hutool project[2], another project hosted in dromara community, its > > website declares very clearly Shenyu is a project of Dromara > > community. > > > > Again, is there a better translation/explanation of this? Is this where > it's asserted that Apache ShenYu is owned by Dromara, instead of Apache? > > > > 3. Sa-token project[3], Dromara community project. It posts Shenyu's > > logo as well without Apache prefix, and it links the project to > > gitee[4], which is mostly an official mirror of Shenyu. > > > > Could Shenyu's PMC take care of this? make sure that, Dromara is not a > > big open-source community, and several people in Shenyu PMC team > > actually leads this community as far as I know. > > 1. From Dromara community perspective, it would keep declaring things > > like this. Shenyu has been donated to the foundation. > > 2. All links, especially those you could control in the Dromara > > community's project, should go to the Apache website, or Apache's > > GitHub repository very clearly. > > > > There's a "Start up" button, but I'm guessing this should translate as > "Getting Started". Is the intention of these Getting Started guides > explaining how to run these software components within the context of > Dromara? Or just how to run them in general? > > Mostly the reason I'm asking is because on the landing page for Dromara, it > mentions the organization's purpose is "An organization dedicated to native > solutions for the microservice cloud" which can be built on Apache products > and if they're providing a guide on how to integrate the Apache product > into their own software stack it may make sense that they're listed as an > integrated component. > > Thanks, > > John > > > > > > For members of the PMC team, I hope Shenyu's PMC could take more > > responsibilities to protect the ASF and project branding. This should > > not be hard to find, as you are working inside Dromara community. > > Unless you didn't know this is a branding, this would concern me more, > > as you are going to graduate a TLP. > > > > > > [1] https://dromara.org/projects/ > > [2] https://www.hutool.cn/ > > [3] https://sa-token.dev33.cn/ > > [4] https://gitee.com/Apache-ShenYu/incubator-shenyu > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [Branding Issue] Shenyu is still decleared as a project of dromara community
Thanks for the update. Sheng Wu 吴晟 Twitter, wusheng1108 Yu Xiao 于2022年6月30日周四 12:34写道： > > Hi, > > ShenYu PPMCs have good communication with the dromara community. > > Dromara Community Team clean up about Apache ShenYu links in dromara > website[1]. > > Hutool Team clean up about Apache ShenYu links in hutool website[2]. > > Sa-Token Team clean up about Apache ShenYu links in sa-Token website[3]. > > Finally, ShenYu PPMCs checked all the official websites of the > projects under the dromara community, > no other links found for Apache ShenYu（Or have been cleaned). > > [1] https://dromara.org/projects/ > [2] https://www.hutool.cn/ > [3] https://sa-token.dev33.cn/ > > -- > Best wishes! > > Yu Xiao > Apache ShenYu (Incubating) > > - > 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
[Branding Issue] Shenyu is still decleared as a project of dromara community
Hi Shenyu and incubator Shenyu is going to graduate in next month, I accidentally have a chance to review its original org, Dromara, due to some reviews for SkyWalking PR. There are two things concerning me. 1. Dromara website[1] still declare Shenyu(even with Apache prefix) on its project page. I think this is wrong and confusing end-users. As this project has been donated for a long time, why it is still hosted there? 2. Hutool project[2], another project hosted in dromara community, its website declares very clearly Shenyu is a project of Dromara community. 3. Sa-token project[3], Dromara community project. It posts Shenyu's logo as well without Apache prefix, and it links the project to gitee[4], which is mostly an official mirror of Shenyu. Could Shenyu's PMC take care of this? make sure that, Dromara is not a big open-source community, and several people in Shenyu PMC team actually leads this community as far as I know. 1. From Dromara community perspective, it would keep declaring things like this. Shenyu has been donated to the foundation. 2. All links, especially those you could control in the Dromara community's project, should go to the Apache website, or Apache's GitHub repository very clearly. For members of the PMC team, I hope Shenyu's PMC could take more responsibilities to protect the ASF and project branding. This should not be hard to find, as you are working inside Dromara community. Unless you didn't know this is a branding, this would concern me more, as you are going to graduate a TLP. [1] https://dromara.org/projects/ [2] https://www.hutool.cn/ [3] https://sa-token.dev33.cn/ [4] https://gitee.com/Apache-ShenYu/incubator-shenyu Sheng Wu 吴晟 Twitter, wusheng1108 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Queuing solution for merging patches
Hi I think the key is you set up to date for main branch, which makes CI has to rerun. tison 于2022年6月29日 周三19:39写道： > Hi Sheng, > > Yes. I do _not_ ask INFRA to support it, but to see if there is existing > practice. > > Best, > tison. > > > Sheng Wu 于2022年6月29日周三 19:33写道： > > > Hi Tison > > > > I think there is no hard requirement from infra or Apache perspective. > The > > PMC could decide what they like, and ask Infra team to set them up. > > > > tison 于2022年6月29日 周三19:25写道： > > > > > Hi, > > > > > > There're several solutions around GitHub ecosystem to queuing patches > > > passed reviews and waiting for merged, especially in case to avoid > > semantic > > > conflict; e.g., Mergify or Bors-NG. > > > > > > After enabled branch must be up-to-date with main branch, it introduces > > an > > > issue that multiple patches can race each other and cause unnecessary > CI > > > tasks rerun - two patches can be verified simultaneously, after one > > merged, > > > the other should rerun, which generally cause O(n^2) task instance > while > > > with queuing only O(n) is required. > > > > > > Given that there're existing solutions, I'd like to ask what the best > > > practice for Apache projects host developments on GitHub on this topic. > > Or > > > what support does INFRA provide for the certain case. > > > > > > Best, > > > tison. > > > > > -- > > Sheng Wu 吴晟 > > > > Apache SkyWalking > > Apache Incubator > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > Zipkin > > Twitter, wusheng1108 > > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: Queuing solution for merging patches
Hi Tison I think there is no hard requirement from infra or Apache perspective. The PMC could decide what they like, and ask Infra team to set them up. tison 于2022年6月29日 周三19:25写道： > Hi, > > There're several solutions around GitHub ecosystem to queuing patches > passed reviews and waiting for merged, especially in case to avoid semantic > conflict; e.g., Mergify or Bors-NG. > > After enabled branch must be up-to-date with main branch, it introduces an > issue that multiple patches can race each other and cause unnecessary CI > tasks rerun - two patches can be verified simultaneously, after one merged, > the other should rerun, which generally cause O(n^2) task instance while > with queuing only O(n) is required. > > Given that there're existing solutions, I'd like to ask what the best > practice for Apache projects host developments on GitHub on this topic. Or > what support does INFRA provide for the certain case. > > Best, > tison. > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [VOTE] Graduate Apache ShenYu(Incubating) as a TLP [ROUND 2]
+1 binding Sheng Wu 吴晟 Twitter, wusheng1108 Goson zhang 于2022年6月22日周三 14:45写道： > > +1 (non-binding) > > Good luck! > > XiaoYu 于2022年6月22日周三 14:43写道： > > > Dear Apache Incubator Community, > > > > In the previous vote[1] thread, > > > > I only described the functionality of the project and not the scope of > > the project in the resolution template.It doesn't fit the standard > > template. so I initiate cancel the vote thread[2]. > > > > Under the guidance of our mentors, I refactor the project description > > in this resolution template. > > > > The Apache ShenYu community has a discussion thread [3], > > passed the community vote[4], and the vote result is published [5]. > > We have discussed the graduation for ShenYu in the Incubator Community [6], > > where no issues were raised and lots of positive responses were received. > > > > I would like to start this voting thread to request graduating Apache > > ShenYu (incubating) from the incubator as a TLP. Please provide your vote > > as one of the following options: > > > > [ ] +1 Yes, I support ShenYu to graduate from the Apache incubator. > > > > [ ] +0 No opinion. > > > > [ ] -1 No, the ShenYu project is not ready to graduate, because ... > > > > The VOTE will remain open for at least 72 hours. > > > > > > ** Community ** > > > > - 6 new PPMC members were added, bringing the total number of PPMC > > members to 30 from at least 15+ different organizations. > > > > - 7 new Committers were added, bringing the total number of Committers > > 37. > > > > - 110+ new contributors participate in the community. The number > > of contributors is now 270+ and growing. > > > > - The dev@shenyu.a.o mailing list currently has 350+ subscribers, > > and all major project discussions are happening in the dev@shenyu.a.o. > > > > - 26 Bi-weekly online meetings were held between committers, > > contributors and users. The meeting minutes are recorded on the > > mailing list [7]. > > > > - 1100+ pull requests merged [8], and 700+ issues closed [9] after > > into the apache incubator. > > > > ** Project ** > > > > - 4 releases by 4 release managers. > > > > - ShenYu official website [10] is compliant with Apache Foundation > > requirements [11]. > > > > - Project maturity model is detailed in [12]. > > > > - See ShenYu Project Incubation Status [13] for more info. > > > > ** Brands ,License, and Copyright ** > > > > - We submitted an application for the brand[14] and it has been > > reviewed and approved. > > - Apache ShenYu community maintains project code on GitHub, and all > > modules > > code is under Apache 2.0 license. We have reviewed all the > > dependencies and ensured they do not bring any license issues [15]. All > > the status files, license headers, and copyright are up to date. > > > > ** PMC members ** > > > >- Please see the proposed board resolution below and let us know what > > you > > think. The initial PMC members were passed by the discussion and invitation > > [16]. > > > > [1] https://lists.apache.org/thread/yk6kjx3j2mh9c5xzfojcln5dtrzt87yf > > [2] https://lists.apache.org/thread/53rj96r63sf2vxcdbfqbqbl27r4v9j0c > > [3] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3 > > [4] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog > > [5] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7 > > [6] https://lists.apache.org/thread/cc2myvso0pbyl39yv26bdmzml8jjvpt2 > > [7] https://lists.apache.org/list.html?d...@shenyu.apache.org > > [8] > > https://github.com/apache/incubator-shenyu/pulls?q=is%3Apr+merged%3A%3E%3D2021-05-03+ > > [9] > > https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03 > > [10] https://shenyu.incubator.apache.org/ > > [11] https://whimsy.apache.org/pods/project/shenyu > > [12] https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md > > [13] https://incubator.apache.org/projects/shenyu.html > > [14] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-197 > > [15] https://github.com/apache/incubator-shenyu/blob/master/LICENSE > > [16] https://lists.apache.org/thread/gp1bnjflz7ysgopxk515l9clswgrvnko > > > > > > -- > > > > Establish the Apache ShenYu Project &g
Re: [VOTE] Graduate Apache ShenYu(Incubating) as a TLP
+1 binding. Good luck for your next journey. Justin Mclean 于2022年6月18日 周六09:12写道： > HI, > > +1 (binding) > > Kind Regards, > Justin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [DISCUSS] Graduate Apache ShenYu(Incubating) as Apache TLP
> Apache ShenYu is an easily scalable, hot-swappable, dynamic full lifecycle JAVA API Gateway a -> an Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2022年6月13日周一 22:14写道： > Hi Sheng, > > I think the project description might be a bit long. I suggest > replacing the two sentences description in the resolution with this > sentence 'Apache ShenYu is a easily scalable, hot-swappable, dynamic > full lifecycle JAVA API Gateway.' > > -- > > Zhang Yonglun > Apache ShenYu (Incubating) > Apache ShardingSphere > > Sheng Wu 于2022年6月13日周一 17:22写道： > > > > > Apache ShenYu is a high performance Microservices API gateway > > in Java ecosystem, compatible with a variety of mainstream framework > > systems, supports hot plug. Users can write their own plugin meet the > > current requirement and future needs in a variety of scenarios, > > especially in large-scale scenes. > > > > This seems a very long sentence to describe the ShenYu, could PPMC > provide > > a shorter version? Usually, it is better to a short and clear sentence > > about what it is doing. The features are definitely more than this. > > > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Eason Chen 于2022年6月13日周一 17:05写道： > > > > > +1 > > > Good luck! > > > > > > On Mon, Jun 13, 2022 at 3:16 PM Goson zhang > wrote: > > > > > > > > +1 > > > > Good luck! > > > > > > > > Atri Sharma 于2022年6月13日周一 14:57写道： > > > > > > > > > It has been a pleasure as one of Shenyu's mentors to see the > project > > > > > grow and take the mantle of a popular and active open source > project. > > > > > > > > > > I wish it luck and look forward to continued association with the > > > project. > > > > > > > > > > On Mon, Jun 13, 2022 at 11:05 AM XiaoYu wrote: > > > > > > > > > > > > Dear Apache Incubator Community, > > > > > > > > > > > > Apache ShenYu has been incubating since 2021-05-03. For over a > year, > > > the > > > > > > Apache ShenYu community has made great progress and grown rapidly > > > under > > > > > the > > > > > > guidance of our mentors. We believe the Apache ShenYu project has > > > met the > > > > > > conditions for graduation. Summary statistics on the state of the > > > > > > community are listed below. Please feel free to participate in > the > > > > > > discussion and give more feedback. > > > > > > > > > > > > The Apache ShenYu community has a discussion thread [1], passed > the > > > > > > community vote > > > > > > [2], and the vote result is published [3]. Our assessment is that > > > Apache > > > > > > ShenYu(Incubating) is ready to graduate as a Apache TLP. We would > > > like > > > > > to raise > > > > > > the discussion to IPMC and collect more feedback towards > graduation. > > > > > > > > > > > > ** Community ** > > > > > > > > > > > > - 6 new PPMC members were added, bringing the total number of > > > PPMC > > > > > > members to 30 from at least 15+ different organizations. > > > > > > > > > > > > - 7 new Committers were added, bringing the total number of > > > > > Committers 37. > > > > > > > > > > > > - 110+ new contributors participate in the community. The > number > > > > > > of contributors is now 274 and growing. > > > > > > > > > > > > - The dev@shenyu.a.o mailing list currently has 357 > subscribers, > > > > > > and all major project discussions are happening in the > > > dev@shenyu.a.o. > > > > > > > > > > > > - 26 Bi-weekly online meetings were held between committers, > > > > > > contributors and users. The meeting minutes are recorded on the > > > > > > mailing list [4]. > > > > > > > > > > > > - 1100+ pull requests merged [5], and 700+ issues closed [6] > > > after > > > > > > into the apache incubator. > > > > > > > > > > > > ** Project ** > > > > > > > > > > > > - 4 releases by 4 releas
Re: [DISCUSS] Graduate Apache ShenYu(Incubating) as Apache TLP
Hi This should be a graduation decision. It is up to the community. I just suggest it to be shorter, and one sentence. XiaoYu 于2022年6月13日 周一18:46写道： > Hi Sheng > > > Thanks for the suggestion, maybe it is indeed too long, > > so i provide pull request[1], to optimize its description : > > > Apache ShenYu is a easily scalable, hot-swappable, dynamic full > lifecycle JAVA API Gateway. > > [1] https://github.com/apache/incubator-shenyu-website/pull/597 > > looking forward to your feedback. > > Sheng Wu 于2022年6月13日周一 17:22写道： > > > > > Apache ShenYu is a high performance Microservices API gateway > > in Java ecosystem, compatible with a variety of mainstream framework > > systems, supports hot plug. Users can write their own plugin meet the > > current requirement and future needs in a variety of scenarios, > > especially in large-scale scenes. > > > > This seems a very long sentence to describe the ShenYu, could PPMC > provide > > a shorter version? Usually, it is better to a short and clear sentence > > about what it is doing. The features are definitely more than this. > > > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Eason Chen 于2022年6月13日周一 17:05写道： > > > > > +1 > > > Good luck! > > > > > > On Mon, Jun 13, 2022 at 3:16 PM Goson zhang > wrote: > > > > > > > > +1 > > > > Good luck! > > > > > > > > Atri Sharma 于2022年6月13日周一 14:57写道： > > > > > > > > > It has been a pleasure as one of Shenyu's mentors to see the > project > > > > > grow and take the mantle of a popular and active open source > project. > > > > > > > > > > I wish it luck and look forward to continued association with the > > > project. > > > > > > > > > > On Mon, Jun 13, 2022 at 11:05 AM XiaoYu wrote: > > > > > > > > > > > > Dear Apache Incubator Community, > > > > > > > > > > > > Apache ShenYu has been incubating since 2021-05-03. For over a > year, > > > the > > > > > > Apache ShenYu community has made great progress and grown rapidly > > > under > > > > > the > > > > > > guidance of our mentors. We believe the Apache ShenYu project has > > > met the > > > > > > conditions for graduation. Summary statistics on the state of the > > > > > > community are listed below. Please feel free to participate in > the > > > > > > discussion and give more feedback. > > > > > > > > > > > > The Apache ShenYu community has a discussion thread [1], passed > the > > > > > > community vote > > > > > > [2], and the vote result is published [3]. Our assessment is that > > > Apache > > > > > > ShenYu(Incubating) is ready to graduate as a Apache TLP. We would > > > like > > > > > to raise > > > > > > the discussion to IPMC and collect more feedback towards > graduation. > > > > > > > > > > > > ** Community ** > > > > > > > > > > > > - 6 new PPMC members were added, bringing the total number of > > > PPMC > > > > > > members to 30 from at least 15+ different organizations. > > > > > > > > > > > > - 7 new Committers were added, bringing the total number of > > > > > Committers 37. > > > > > > > > > > > > - 110+ new contributors participate in the community. The > number > > > > > > of contributors is now 274 and growing. > > > > > > > > > > > > - The dev@shenyu.a.o mailing list currently has 357 > subscribers, > > > > > > and all major project discussions are happening in the > > > dev@shenyu.a.o. > > > > > > > > > > > > - 26 Bi-weekly online meetings were held between committers, > > > > > > contributors and users. The meeting minutes are recorded on the > > > > > > mailing list [4]. > > > > > > > > > > > > - 1100+ pull requests merged [5], and 700+ issues closed [6] > > > after > > > > > > into the apache incubator. > > > > > > > > > > > > ** Project ** > > > > > > > > > > > > - 4 releases by 4 release managers. > >
Re: [DISCUSS] Graduate Apache ShenYu(Incubating) as Apache TLP
> Apache ShenYu is a high performance Microservices API gateway in Java ecosystem, compatible with a variety of mainstream framework systems, supports hot plug. Users can write their own plugin meet the current requirement and future needs in a variety of scenarios, especially in large-scale scenes. This seems a very long sentence to describe the ShenYu, could PPMC provide a shorter version? Usually, it is better to a short and clear sentence about what it is doing. The features are definitely more than this. Sheng Wu 吴晟 Twitter, wusheng1108 Eason Chen 于2022年6月13日周一 17:05写道： > +1 > Good luck! > > On Mon, Jun 13, 2022 at 3:16 PM Goson zhang wrote: > > > > +1 > > Good luck! > > > > Atri Sharma 于2022年6月13日周一 14:57写道： > > > > > It has been a pleasure as one of Shenyu's mentors to see the project > > > grow and take the mantle of a popular and active open source project. > > > > > > I wish it luck and look forward to continued association with the > project. > > > > > > On Mon, Jun 13, 2022 at 11:05 AM XiaoYu wrote: > > > > > > > > Dear Apache Incubator Community, > > > > > > > > Apache ShenYu has been incubating since 2021-05-03. For over a year, > the > > > > Apache ShenYu community has made great progress and grown rapidly > under > > > the > > > > guidance of our mentors. We believe the Apache ShenYu project has > met the > > > > conditions for graduation. Summary statistics on the state of the > > > > community are listed below. Please feel free to participate in the > > > > discussion and give more feedback. > > > > > > > > The Apache ShenYu community has a discussion thread [1], passed the > > > > community vote > > > > [2], and the vote result is published [3]. Our assessment is that > Apache > > > > ShenYu(Incubating) is ready to graduate as a Apache TLP. We would > like > > > to raise > > > > the discussion to IPMC and collect more feedback towards graduation. > > > > > > > > ** Community ** > > > > > > > > - 6 new PPMC members were added, bringing the total number of > PPMC > > > > members to 30 from at least 15+ different organizations. > > > > > > > > - 7 new Committers were added, bringing the total number of > > > Committers 37. > > > > > > > > - 110+ new contributors participate in the community. The number > > > > of contributors is now 274 and growing. > > > > > > > > - The dev@shenyu.a.o mailing list currently has 357 subscribers, > > > > and all major project discussions are happening in the > dev@shenyu.a.o. > > > > > > > > - 26 Bi-weekly online meetings were held between committers, > > > > contributors and users. The meeting minutes are recorded on the > > > > mailing list [4]. > > > > > > > > - 1100+ pull requests merged [5], and 700+ issues closed [6] > after > > > > into the apache incubator. > > > > > > > > ** Project ** > > > > > > > > - 4 releases by 4 release managers. > > > > > > > > - ShenYu official website [7] is compliant with Apache Foundation > > > > requirements [8]. > > > > > > > > - Project maturity model is detailed in [9]. > > > > > > > > - See ShenYu Project Incubation Status [10] for more info. > > > > > > > > ** Brands ,License, and Copyright ** > > > > > > > > - We submitted an application for the brand[11] and it has been > > > > reviewed and approved. > > > > - Apache ShenYu community maintains project code on GitHub, and > all > > > modules > > > > code is under Apache 2.0 license. We have reviewed all the > > > > dependencies and ensured they do not bring any license issues [12]. > All > > > > the status files, license headers, and copyright are up to date. > > > > > > > > ** PMC members ** > > > > > > > >- Please see the proposed board resolution below and let us know > what > > > you > > > > think. The initial PMC members were passed by the discussion and > > > invitation > > > > [13]. > > > > > > > > The discussion will remain open for at least 72 hours, looking > forward to > > > > your feedback. > > > > > > > > [1] ht
Re: [HELP WANTED] Is it allowed to make a mirror of the website of an apache project?
I am afraid that is not a good idea. I think you know the ECharts team, as you are/were at Baidu, you had been suffering this. They have/are resolved(ing) this through some DNS solutions. Sheng Wu 吴晟 Twitter, wusheng1108 yangzhg 于2022年6月2日周四 10:31写道： > > HI all > > I'm from Apache Doris (Incubator) > For some reasons, the speed of some Chinese users accessing Apache Doris > sites is very slow. The main content of our website is to use documents. If > I make a mirror of the Apache Doris website to speed up the access of > Chinese users, I will make it clear that this is the mirror of the Apache > Doris website. Is this allowed? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache InLong(Incubating) as a TLP
+1 binding Enjoy your TLP journey. Sheng Wu 吴晟 Twitter, wusheng1108 Eason Chen 于2022年5月25日周三 17:22写道： > > +1 (no-binding) > > Good luck!! > > On Wed, May 25, 2022 at 4:27 PM Goson zhang wrote: > > > > +1 (no-binding) > > > > Good luck!! > > > > tison 于2022年5月25日周三 16:18写道： > > > > > +1 (binding) > > > > > > Good luck! > > > > > > Best, > > > tison. > > > > > > > > > Jerry Shao 于2022年5月25日周三 16:12写道： > > > > > > > +1 (binding). > > > > > > > > Good luck to Inlong. > > > > > > > > Best > > > > Jerry > > > > > > > > 俊平堵 于2022年5月25日周三 14:50写道： > > > > > > > > > +1, good luck to InLong.:) > > > > > > > > > > Charles Zhang 于2022年5月25日 周三下午2:34写道： > > > > > > > > > > > Dear Apache Incubator Community, > > > > > > > > > > > > > > > > > > The InLong community has a discussion thread [1], passed the > > > community > > > > > vote > > > > > > [2], and the vote result is published [3]. We have discussed the > > > > > graduation > > > > > > for InLong in the Incubator Community [4], where no issues were > > > raised > > > > > and > > > > > > lots of positive responses were received. > > > > > > > > > > > > > > > > > > I would like to start this voting thread to request graduating > > > > > > Apache > > > > > > InLong (incubating) from the incubator as a TLP. Please provide your > > > > vote > > > > > > as one of the following options: > > > > > > > > > > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator. > > > > > > > > > > > > [ ] +0 No opinion. > > > > > > > > > > > > [ ] -1 No, the InLong project is not ready to graduate, because ... > > > > > > > > > > > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > > > > > > > > > > > Since incubating in ASF, the project itself has become more mature > > > and > > > > > > > > > > > > stable. The following is a brief summary of the project and > > > > > > community > > > > > > > > > > > > during the incubation: > > > > > > > > > > > > > > > > > > - 11 versions were released by 6 different release managers, of > > > which 5 > > > > > > > > > > > > versions are the original TubeMQ, and 6 versions are after the name > > > was > > > > > > > > > > > > changed to InLong. The release cadence is about 2 months [5]. > > > > > > > > > > > > > > > > > > - 10 new Committers and 3 PPMCs were added during incubating, they > > > are > > > > > from > > > > > > > > > > > > 4 different organizations. All PPMCs and Committers are spread > > > across 8 > > > > > > > > > > > > different organizations [6]. > > > > > > > > > > > > > > > > > > - 101 unique code developers [7]. > > > > > > > > > > > > > > > > > > - Closed more than 2200 issues, with an average of 200 issues per > > > > version > > > > > > > > > > > > [8]. > > > > > > > > > > > > > > > > > > - All the dependencies were reviewed and ensured they do not bring > > > any > > > > > > > > > > > > license issues [9]. > > > > > > > > > > > > > > > > > > - Evaluated the InLong project and self-checked the InLong maturity > > > > model > > > > > > > > > > > > [10] and the pre-graduation Check [11]. > > > > > > > > > > > > > > > > > > - Well and Complete documentation for contributors and users [12]. > > > > > > > > > > > > > > > > > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
Re: [DISCUSSION] Incubating Proposal of Firestorm
Hi Firestorm community Considering what Yu Li is proposing, I would recommend you could do some discussions directly, maybe off the list if you want. Both of the projects are young and very new to the community, it may be not a concern from my perspective(may be concerned by some IPMC), as one/both could fail in the incubating. But with you are going to work on the similar things, the challenge would be for both of your projects to establish the incubating process. Also, when we talk about graduation in the future, it would be my concern of causing confusion to users. Two TLPs are nearly the same is really not a good practice from the foundation level. > We heartfully welcome you to join Firestorm project and community. So, I suggest not just saying joining Firestorm, this may be a simple reaction, I hope you could do more. This is an opportunity to do a bigger and more powerful project supported by Tencent and Alibaba's initial teams. I know it is not easy to do a joint project, but it is actually much better to see you two competing with each other in the next 1-2 years. In the ASF, we hope to create a better project for the whole industry. Sheng Wu 吴晟 Twitter, wusheng1108 Jerry Shao 于2022年5月18日周三 14:38写道： > > Hi Yu， > > IMO, I think we're open and welcome all the contributions. We heartfully > welcome you to join Firestorm project and community. > > Best regards, > Jerry > > Yu Li 于2022年5月18日周三 13:36写道： > > > Hi Jerry, > > > > Good to see the proposal for incubating a uniform remote shuffle service. > > Coincidently, we are preparing an incubating proposal for the same > > direction based on two open source projects Alibaba is driving [1] [2], and > > I'm the champion for that. Our proposal is still not fully prepared because > > the merge of the two projects is still in progress, and I'm writing this > > email to check whether it's possible that we have a joint force to achieve > > the same goal. I believe it will be cool if we could do this together, > > although there will be a lot (more) work to do to make this happen. > > > > Please let me know your thoughts and let's have more discussions if you're > > also interested. Thanks. > > > > Best Regards, > > Yu > > > > [1] https://github.com/flink-extended/flink-remote-shuffle > > [2] https://github.com/alibaba/RemoteShuffleService > > > > > > On Wed, 18 May 2022 at 12:15, Jerry Shao wrote: > > > > > Sure Felix, let me add you to the list. > > > > > > Best, > > > Jerry > > > > > > Felix Cheung 于2022年5月18日周三 11:59写道： > > > > > > > Same here, would love to see if I can help, Jerry. > > > > > > > > > > > > On Mon, May 16, 2022 at 10:31 PM Saisai Shao > > > > wrote: > > > > > > > > > Thanks Weiwei, let me add you to the mentor list. > > > > > > > > > > Best regards, > > > > > Jerry > > > > > > > > > > Weiwei Yang 于2022年5月17日周二 12:18写道： > > > > > > > > > > > +1 > > > > > > This is an interesting project, I'd be happy to help the project's > > > > > > incubation process. > > > > > > Let me know if you need my help, Thanks > > > > > > > > > > > > On Mon, May 16, 2022 at 8:09 PM Saisai Shao < > > sai.sai.s...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Got it, thanks a lot Justin. > > > > > > > > > > > > > > Best regards, > > > > > > > Jerry > > > > > > > > > > > > > > Justin Mclean 于2022年5月17日周二 10:59写道： > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > The new project name doesn’t need to be a registered trademark, > > > but > > > > > you > > > > > > > > would still need to pick a name that is now likely to have any > > > > > > trademark > > > > > > > > issues. > > > > > > > > > > > > > > > > The project may want to get the ASF to register the mark at a > > > later > > > > > > date, > > > > > > > > but it wold be best to talk abut that on the trademarks@ list. > > > > > > > > > > > > > > > > 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: Setting up project website
I remember you need this https://github.com/apache/skywalking-website/blob/master/.asf.yaml Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2022年5月15日周日 20:50写道： > > Hi, > > On Apache Kvrocks (Incubating) project, I just set up the website repo > (main and asf-site branch)[1] and it seems the asf-site branch is properly > configured and static site staff published. > > However, the homepage https://kvrocks.apache.org/ still returns 404 NOT > FOUND. I don't know whether it takes some time to deploy or the setting is > wrong which needs more polishing. > > Best, > tison. > > [1] https://github.com/apache/incubator-kvrocks-website/tree/asf-site - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Multiple entities of software grant agreement
SGA is not required if the project is on a personal repository, this individual's employer(if have) is recommended to submit CCLA(but needs to evaluate by the owner about his contract) But this isn't the Kvrocks case. Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2022年4月25日周一 16:15写道： > > Thanks for your inputs. > > Try to summarize the discussion: > > * Apache requires a SGA from the *current* copyright holder of the software > to grant permission for ASF. > * If the current copyright holder is Meitu, then they should sign a grant > with Exhibit A barely "Kvrocks". > > However, if the current copyright holder is "Kvrocks contributors", since > it's a virtual entity, a certain contributor on behalf of the community > should sign the SGA. > > Did I get it right? Is there some other proposal that got into the > incubator without a SGA from a certain "company". > > Best, > tison. > > > Sheng Wu 于2022年4月25日周一 15:42写道： > > > > but I think it's right that meitu should claim clearly about the > > copyright > > date since the > > > > Do you mean there is no single Meitu employee(s) was > > working/contributed to that project ever since? > > Because the org is virtual on GitHub, and meitu can't sign CCLA or SGA > > to that virtual group back then, I think one way or another, Meitu > > still need to prove the SGA from the transfer date to now. > > It is better for meitu to sign the SGA to declare all > > contributions(from beginning to now), others(individuals) would submit > > their ICLA(or other companies' SGA) for some codes after the transfer. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > hulk 于2022年4月25日周一 15:06写道： > > > > > > Thanks for junping reply. > > > > > > Yes, we also agree that should grant the whole source code repository > > for > > > ASF, > > > but I think it's right that meitu should claim clearly about the > > copyright > > > date since the > > > the repository was moved to another organization after then. > > > > > > So our question is should we need to sign extra other agreements for > > > podling IP Clearance? > > > > > > > > > > > > On Mon, Apr 25, 2022 at 2:57 PM 俊平堵 wrote: > > > > > > > I think SGA here should be the same as other project. > > > > As Craig mentioned above, it is code’s copyright owner ( a legal > > entity or > > > > natural human) to grant permission for ASF. If only for code during > > certain > > > > period, that means some code is not get permitted for Apache which is > > very > > > > weird. :( > > > > > > > > hulk 于2022年4月25日 周一上午11:52写道： > > > > > > > > > Thanks all, > > > > > > > > > > From the meitu side, they think should claim the date clearly > > instead of > > > > > implicitly, > > > > > so I'm not sure whether is ok to add this clarification on SGA or > > not? > > > > > If not, are there other agreements that should be signed for podling > > IP > > > > > Clearance? > > > > > > > > > > On Mon, Apr 25, 2022 at 11:13 AM Sheng Wu > > > > > > > wrote: > > > > > > > > > > > Please check the SGA template of ASF, like Craig mentioned, > > usually, > > > > > > there is no date/timestamp included. > > > > > > The foundation just needs legal approval that the company granted > > to > > > > > > move codes to the foundation, others(like individuals) should > > submit > > > > > > ICLA(s) > > > > > > > > > > > > Sheng Wu 吴晟 > > > > > > Twitter, wusheng1108 > > > > > > > > > > > > hulk 于2022年4月25日周一 10:19写道： > > > > > > > > > > > > > > > I think the key is how they make this conclusion. Was the > > project > > > > > > > > moving to a 3rd party repository, and changing the owner from a > > > > > > > > license perspective? > > > > > > > > > > > > > > Kvrocks has transferred from the meitu to the KvrocksLabs > > > > organization > > > > > > and claimed the copyright belongs to the Kvrocks community. > > > > > > > > > > > > > > > Is there a place/way to track this event? > > > > > &g
Re: Multiple entities of software grant agreement
> but I think it's right that meitu should claim clearly about the copyright date since the Do you mean there is no single Meitu employee(s) was working/contributed to that project ever since? Because the org is virtual on GitHub, and meitu can't sign CCLA or SGA to that virtual group back then, I think one way or another, Meitu still need to prove the SGA from the transfer date to now. It is better for meitu to sign the SGA to declare all contributions(from beginning to now), others(individuals) would submit their ICLA(or other companies' SGA) for some codes after the transfer. Sheng Wu 吴晟 Twitter, wusheng1108 hulk 于2022年4月25日周一 15:06写道： > > Thanks for junping reply. > > Yes, we also agree that should grant the whole source code repository for > ASF, > but I think it's right that meitu should claim clearly about the copyright > date since the > the repository was moved to another organization after then. > > So our question is should we need to sign extra other agreements for > podling IP Clearance? > > > > On Mon, Apr 25, 2022 at 2:57 PM 俊平堵 wrote: > > > I think SGA here should be the same as other project. > > As Craig mentioned above, it is code’s copyright owner ( a legal entity or > > natural human) to grant permission for ASF. If only for code during certain > > period, that means some code is not get permitted for Apache which is very > > weird. :( > > > > hulk 于2022年4月25日 周一上午11:52写道： > > > > > Thanks all, > > > > > > From the meitu side, they think should claim the date clearly instead of > > > implicitly, > > > so I'm not sure whether is ok to add this clarification on SGA or not? > > > If not, are there other agreements that should be signed for podling IP > > > Clearance? > > > > > > On Mon, Apr 25, 2022 at 11:13 AM Sheng Wu > > > wrote: > > > > > > > Please check the SGA template of ASF, like Craig mentioned, usually, > > > > there is no date/timestamp included. > > > > The foundation just needs legal approval that the company granted to > > > > move codes to the foundation, others(like individuals) should submit > > > > ICLA(s) > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > hulk 于2022年4月25日周一 10:19写道： > > > > > > > > > > > I think the key is how they make this conclusion. Was the project > > > > > > moving to a 3rd party repository, and changing the owner from a > > > > > > license perspective? > > > > > > > > > > Kvrocks has transferred from the meitu to the KvrocksLabs > > organization > > > > and claimed the copyright belongs to the Kvrocks community. > > > > > > > > > > > Is there a place/way to track this event? > > > > > > > > > > We didn't track this event in a public place. The lawyer thinks they > > > can > > > > only grant the copyright when all of the contributors are their > > employees > > > > (before 2020.3.23). After that, the copyright should belong to the > > > Kvrocks > > > > community. > > > > > > > > > > On Mon, Apr 25, 2022 at 8:29 AM Sheng Wu > > > > wrote: > > > > >> > > > > >> > While the IPMCs and PPMCs preparing the SGA > > > > >> > > > > >> I think IPMC don't prepare SGA, SGA(s) are from original owners. > > > > >> > > > > >> > Its lawyer said that code contributions from then on belong to the > > > > Kvrocks > > > > >> community. > > > > >> > > > > >> I think the key is how they make this conclusion. Was the project > > > > >> moving to a 3rd party repository, and changing the owner from a > > > > >> license perspective? Is there a place/way to track this event? > > > > >> > > > > >> Sheng Wu 吴晟 > > > > >> Twitter, wusheng1108 > > > > >> > > > > >> tison 于2022年4月25日周一 06:46写道： > > > > >> > > > > > >> > Hi IPMCs, > > > > >> > > > > > >> > Recently we voted and accepted Kvrocks to the Incubator[1]. > > > > >> > > > > > >> > While the IPMCs and PPMCs preparing the SGA, we meet an issue that > > > the > > > > >> > original entity sign a SGA but explicit limit the agreement on > > code > > > > from > > > > >> > 2018 to 2020. > > > > >> > > > > > >> > Its lawyer said that code contributions from then on belong to the > > > > Kvrocks > > > > >> > community. > > > > >> > > > > > >> > The issue is that since the original entity sign such a SGA and > > all > > > > core > > > > >> > contributors sign ICLAs, is there other agreements should be > > signed > > > > for > > > > >> > podling IP Clearance? > > > > >> > > > > > >> > Best, > > > > >> > tison. > > > > >> > > > > > >> > [1] > > > https://lists.apache.org/thread/shxcg56j3x36t75x63voj82s6hhdtrcv > > > > > > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Multiple entities of software grant agreement
Please check the SGA template of ASF, like Craig mentioned, usually, there is no date/timestamp included. The foundation just needs legal approval that the company granted to move codes to the foundation, others(like individuals) should submit ICLA(s) Sheng Wu 吴晟 Twitter, wusheng1108 hulk 于2022年4月25日周一 10:19写道： > > > I think the key is how they make this conclusion. Was the project > > moving to a 3rd party repository, and changing the owner from a > > license perspective? > > Kvrocks has transferred from the meitu to the KvrocksLabs organization and > claimed the copyright belongs to the Kvrocks community. > > > Is there a place/way to track this event? > > We didn't track this event in a public place. The lawyer thinks they can only > grant the copyright when all of the contributors are their employees (before > 2020.3.23). After that, the copyright should belong to the Kvrocks community. > > On Mon, Apr 25, 2022 at 8:29 AM Sheng Wu wrote: >> >> > While the IPMCs and PPMCs preparing the SGA >> >> I think IPMC don't prepare SGA, SGA(s) are from original owners. >> >> > Its lawyer said that code contributions from then on belong to the Kvrocks >> community. >> >> I think the key is how they make this conclusion. Was the project >> moving to a 3rd party repository, and changing the owner from a >> license perspective? Is there a place/way to track this event? >> >> Sheng Wu 吴晟 >> Twitter, wusheng1108 >> >> tison 于2022年4月25日周一 06:46写道： >> > >> > Hi IPMCs, >> > >> > Recently we voted and accepted Kvrocks to the Incubator[1]. >> > >> > While the IPMCs and PPMCs preparing the SGA, we meet an issue that the >> > original entity sign a SGA but explicit limit the agreement on code from >> > 2018 to 2020. >> > >> > Its lawyer said that code contributions from then on belong to the Kvrocks >> > community. >> > >> > The issue is that since the original entity sign such a SGA and all core >> > contributors sign ICLAs, is there other agreements should be signed for >> > podling IP Clearance? >> > >> > Best, >> > tison. >> > >> > [1] https://lists.apache.org/thread/shxcg56j3x36t75x63voj82s6hhdtrcv - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Multiple entities of software grant agreement
> While the IPMCs and PPMCs preparing the SGA I think IPMC don't prepare SGA, SGA(s) are from original owners. > Its lawyer said that code contributions from then on belong to the Kvrocks community. I think the key is how they make this conclusion. Was the project moving to a 3rd party repository, and changing the owner from a license perspective? Is there a place/way to track this event? Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2022年4月25日周一 06:46写道： > > Hi IPMCs, > > Recently we voted and accepted Kvrocks to the Incubator[1]. > > While the IPMCs and PPMCs preparing the SGA, we meet an issue that the > original entity sign a SGA but explicit limit the agreement on code from > 2018 to 2020. > > Its lawyer said that code contributions from then on belong to the Kvrocks > community. > > The issue is that since the original entity sign such a SGA and all core > contributors sign ICLAs, is there other agreements should be signed for > podling IP Clearance? > > Best, > tison. > > [1] https://lists.apache.org/thread/shxcg56j3x36t75x63voj82s6hhdtrcv - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] graduate Apache Doris (Incubating) as a Top Level Project
+1 binding Sheng Wu 吴晟 Twitter, wusheng1108 ling miao 于2022年4月24日周日 16:24写道： > > +1 (non-binding) Glad to see it ~ > > Eason Chen 于2022年4月24日周日 16:06写道： > > > + 1 （non-binding） > > > > On Sun, Apr 24, 2022 at 11:11 AM XiaoYu wrote: > > > > > > + 1 （non-binding） > > > > > > Looking forward to it and wishing the community better the better! > > > > > > Calvin Kirs 于2022年4月24日周日 11:03写道： > > > > > > > > +1 (binding) > > > > Good to see Doris graduation! > > > > > > > > 陈明雨 于2022年4月24日周日 10:26写道： > > > > > > > > > > Dear Incubator Community, > > > > > > > > > > After having the discussion in Doris community[1][2], we have passed > > the community vote[3]. > > > > > > > > > > And then made a discussion in general@incubator[4]. We got a lot of > > positive responses. > > > > > > > > > > And have responded and addressed all suggestions and comments raised. > > > > > > > > > > > > > > > > > > > > > > > > > I would like to start this voting thread to request graduating the > > Doris project from the incubator as a TLP. > > > > > > > > > > Please provide your vote as one of the following options: > > > > > > > > > > > > > > > > > > > > > > > > > [ ] +1 - Recommend graduation of Apache Doris as a TLP > > > > > > > > > > [ ] 0 - I don't feel strongly about it, but don't object > > > > > > > > > > [ ] -1 - Do not recommend the graduation of Apache Doris because… > > > > > > > > > > > > > > > > > > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > > > > > > > > > > > > > > > > > > The following is a brief overview of the progress of the Doris > > project and community since entering the incubator: > > > > > > > > > > 1. Community > > > > > > > > > > - 9 new PPMC members were added, from five different companies, > > bringing the total number of PPMC members to 22. > > > > > > > > > > - 20 new Committers were added (including the new PPMC members), > > bringing the total number of Committers to 33. > > > > > > > > > > - The number of Contributors is now 305 and growing[5]. > > > > > > > > > > - The dev@doris mailing list currently has 328 subscribers, and all > > major project discussions are happening in the dev@doris. > > > > > > > > > > > > > > > > > > > > > > > > > 2. Project > > > > > > > > > > - 7 releases by 6 release managers. All compliance issues have been > > resolved. > > > > > > > > > > - Doris official website[6] is compliant with Apache Foundation > > requirements[7]. > > > > > > > > > > - Project maturity model is detailed in [8]. > > > > > > > > > > - See Doris Project Incubation Status[9] for more info. > > > > > > > > > > > > > > > > > > > > > > > > > [1] https://lists.apache.org/thread/90fd2pd3r6wgn4hnfdo3rd0wqkv23cgr > > > > > > > > > > [2] https://lists.apache.org/thread/xc5qj7m2k1ph0mc97otj0nf8vskdfrzv > > > > > > > > > > [3] https://lists.apache.org/thread/9yklv4vbp39jhrzbcx3qgpcs1osk3lyf > > > > > > > > > > [4] https://lists.apache.org/thread/nbncjl8fdq0bcjop6l4747c8x9c06q00 > > > > > > > > > > [5] https://github.com/apache/incubator-doris > > > > > > > > > > [6] http://doris.incubator.apache.org/ > > > > > > > > > > [7] https://whimsy.apache.org/pods/project/doris > > > > > > > > > > [8] > > https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris > > > > > > > > > > [9] https://incubator.apache.org/projects/doris.html > > > > > > > > > > > > > > > > > > > > > > > > > > > == > > > > > >
Re: [VOTE] Accept Kvrocks into the Apache Incubator
+1 binding Sheng Wu 吴晟 Twitter, wusheng1108 Liang Chen 于2022年4月22日周五 09:19写道： > > +1(binding) > > Regards > Liang > > 在 2022年4月20日星期三，Furkan KAMACI 写道： > > > Hi, > > > > +1 (binding) > > > > Kind Regards, > > Furkan KAMACI > > > > On 20 Apr 2022 Wed at 13:49 Calvin Kirs wrote: > > > > > +1 (binding) > > > Good luck. > > > > > > 张铎(Duo Zhang) 于2022年4月20日周三 18:29写道： > > > > > > > > +1(binding) > > > > > > > > Goson zhang 于2022年4月20日周三 18:27写道： > > > > > > > > > +1 (non-binding) > > > > > > > > > > Good luck! > > > > > > > > > > Willem Jiang 于2022年4月20日周三 14:38写道： > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > Twitter: willemjiang > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > On Wed, Apr 20, 2022 at 7:25 AM Liang Chen < > > chenliang...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > Following up the [DISCUSS] thread on Kvrocks[1], I would like to > > > > > > > call a VOTE to accept Kvrocks into the Apache Incubator, please > > > check > > > > > out > > > > > > > the Kvrocks Proposal from the incubator wiki[2]. > > > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > > > [ ] +1, bring Kvrocks into the Incubator > > > > > > > [ ] +0, I don't care either way > > > > > > > [ ] -1, do not bring Kvrocks into the Incubator, because... > > > > > > > > > > > > > > The vote will open at least for 72 hours, and only votes from the > > > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > > > > > > [1] > > > https://lists.apache.org/thread/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31 > > > > > > > [2] > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal > > > > > > > > > > > > > > Regards > > > > > > > Liang > > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Best wishes！ > > > CalvinKirs > > > > > > - > > > 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: Re:Re: Re: [DISCUSS] Graduate Apache Doris (Incubating) as TLP
Thanks for fixing this. I am good for your graduation, congrats to the team. Sheng Wu 吴晟 Twitter, wusheng1108 陈明雨 于2022年4月20日周三 12:32写道： > > Hi Sheng Wu, > > But according to my understanding of Apache License 2.0, the copied > > source files/path should be listed in the source code's License file > > > We have fixed this issue[1], please review. and welcome to continue > discussions on other issues > > > [1] https://github.com/apache/incubator-doris/pull/9115 > > > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > chenmin...@apache.org > > > > > > 在 2022-04-18 23:45:44，"陈明雨" 写道： > >> But according to my understanding of Apache License 2.0, the copied > >> source files/path should be listed in the source code's License > >> file,Indeed we miss that part, I will add them. > > > > > > > >-- > > > >此致！Best Regards > >陈明雨 Mingyu Chen > > > >Email: > >chenmin...@apache.org > > > > > > > > > > > >At 2022-04-18 23:23:09, "Sheng Wu" wrote: > >>Hi Willem and Mingyu > >> > >>Thanks for updating the status. > >>I read README, License and Notice, yes, they mentioned about source > >>codes are from Impala, > >>and it is fine that two projects can't be merged, this is a pure tech > >>decision, and I don't have an issue about that. > >>But according to my understanding of Apache License 2.0, the copied > >>source files/path should be listed in the source code's License file, > >>which I can't find. > >> > >>Is there something I am missing? > >> > >>Hi JB > >> > >>Sorry I missed your support in the Doris discussion. And good to see > >>your support. > >> > >>Sheng Wu 吴晟 > >>Twitter, wusheng1108 > >> > >>陈明雨 于2022年4月18日周一 22:13写道： > >>> > >>> Hi Sheng Wu, > >>> Thanks for you reply. Our mentor Willem has helped answer some questions, > >>> here I also answer from my perspective: > >>> > >>> > >>> > I just read your graduation discussion on a dev mail list and notice > >>> > >>> > there is only one mentor who confirmed his support. > >>> > >>> > And no mentor voted(from vote summary) for your graduation. > >>> > >>> > Could you check with your mentors? IPMC wants to hear from your mentors. > >>> > >>> > >>> > >>> > >>> Sorry I didn't realize that the graduation vote in the dev mailing group > >>> requires the support of a mentor, > >>> > >>> I will individually ping other mentors and invite them to assist with > >>> reviewing and suggestions. > >>> > >>> > >>> > >>> > >>> > Also, I can't find the discussion(maybe private?) about whether > >>> > >>> > committers should be considered a member of PMC? If you haven't, > >>> > >>> > please do a discussion about this too. > >>> > >>> > >>> > >>> > >>> Yes, we have had a discussion about commiter promotion mechanism[1] in > >>> private@doris, > >>> > >>> and also make it public here:[2] > >>> > >>> > >>> > >>> > >>> > From a code perspective, I remember this podling has some source codes > >>> > >>> > from Impala, the PMC of Impala showed their concerns, what is the > >>> > >>> > status now? Have the license been handled properly? > >>> > >>> > >>> > >>> > >>> We explained this in our discussion[3] on the dev@doris, and I'll > >>> re-explain it here: > >>> > >>> > >>> > >>> > >>> * Relationship with Apache Impala * > >>> > >>> Doris' current query engine is forked from Impala version v0.7 and has > >>> been updated with Impala in the early stages of the project (hands-on > >>> code merge). > >>> > >>> In the Doris Proposal[4], we expressed our desire to decouple the Doris > >>> storage engine from the query engine through a layer of abstract API. So > >>> that the query layer could fully follow Impala's evolution. > >>> > >>> However, as the project progressed, we found
Re: Re: [DISCUSS] Graduate Apache Doris (Incubating) as TLP
Hi Willem and Mingyu Thanks for updating the status. I read README, License and Notice, yes, they mentioned about source codes are from Impala, and it is fine that two projects can't be merged, this is a pure tech decision, and I don't have an issue about that. But according to my understanding of Apache License 2.0, the copied source files/path should be listed in the source code's License file, which I can't find. Is there something I am missing? Hi JB Sorry I missed your support in the Doris discussion. And good to see your support. Sheng Wu 吴晟 Twitter, wusheng1108 陈明雨 于2022年4月18日周一 22:13写道： > > Hi Sheng Wu, > Thanks for you reply. Our mentor Willem has helped answer some questions, > here I also answer from my perspective: > > > > I just read your graduation discussion on a dev mail list and notice > > > there is only one mentor who confirmed his support. > > > And no mentor voted(from vote summary) for your graduation. > > > Could you check with your mentors? IPMC wants to hear from your mentors. > > > > > Sorry I didn't realize that the graduation vote in the dev mailing group > requires the support of a mentor, > > I will individually ping other mentors and invite them to assist with > reviewing and suggestions. > > > > > > Also, I can't find the discussion(maybe private?) about whether > > > committers should be considered a member of PMC? If you haven't, > > > please do a discussion about this too. > > > > > Yes, we have had a discussion about commiter promotion mechanism[1] in > private@doris, > > and also make it public here:[2] > > > > > > From a code perspective, I remember this podling has some source codes > > > from Impala, the PMC of Impala showed their concerns, what is the > > > status now? Have the license been handled properly? > > > > > We explained this in our discussion[3] on the dev@doris, and I'll re-explain > it here: > > > > > * Relationship with Apache Impala * > > Doris' current query engine is forked from Impala version v0.7 and has been > updated with Impala in the early stages of the project (hands-on code merge). > > In the Doris Proposal[4], we expressed our desire to decouple the Doris > storage engine from the query engine through a layer of abstract API. So that > the query layer could fully follow Impala's evolution. > > However, as the project progressed, we found it difficult to achieve this > goal, mainly for the following reasons. > > 1. Impala focus on providing query acceleration on the Hadoop ecosystem, > while Doris focus on a standalone data warehouse or DBMS system. The > difference of targets means that many features do not meet the needs of both > projects. > > 2. Doris has completely refactored the metadata and has its own storage > engine. This required a deep integration of the query layer with the metadata > and the storage engine. We also made a lot of architectural changes for this. > > 3. Doris has now developed a new vectorized execution engine that rewrites > most of the execution node in query layer, which is different from Impala. > > > > > For these reasons, it is difficult for us to continue to follow the Impala > community with code level iterations and integrations. > > Of course, all code references to Impala are fully compliant with the Apache > License, and we explicitly declare the relationship between Doris and Impala > in the NOTICE file[5] and the README file[6] and thank the Impala community > for their help. > > > > > [1] https://lists.apache.org/thread/l0w4xnzwsqvlphf57ksc4yq3o998s0cx > > [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078398 > > [3] https://lists.apache.org/thread/d5qxncy2tog63nq3n6y53f7sym3yl6k4 > > [4] https://cwiki.apache.org/confluence/display/incubator/DorisProposal > > [5] https://github.com/apache/incubator-doris/blob/master/NOTICE.txt > > [6] https://github.com/apache/incubator-doris/blob/master/README.md > > > > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > chenmin...@apache.org > > > > > > At 2022-04-18 20:43:44, "Sheng Wu" wrote: > >Hi Mingyu and Doris team > > > >Glad to see you are moving forward to the graduation. > > > >I just read your graduation discussion on a dev mail list and notice > >there is only one mentor who confirmed his support. > >And no mentor voted(from vote summary) for your graduation. > >Could you check with your mentors? IPMC wants to hear from your mentors. > > > >Also, I can't find the discussion(maybe private?) about whether > >committers should b
