Re: [VOTE] Apache CXF Graduation as TLP
Here is my +1. Willem Daniel Kulp wrote: After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 -- Dan (on behalf of the entire Apache CXF team and with permission from the CXF mentors to call this vote.) == Establish the Apache CXF 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, to be known as "Apache CXF Project", related to a framework for creating, deploying, and consuming services based on SOA design principles for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC) is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CXF PMC be and hereby is charged with the creation and maintenance of "Apache CXF"; and be it further RESOLVED, that the office of "Vice President, Apache CXF" 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 CXF PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CXF PMC; 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 CXF PMC: * Ulhas Bhole <[EMAIL PROTECTED]> * Sean O'Callaghan <[EMAIL PROTECTED]> * Dan Diephouse <[EMAIL PROTECTED]> * Freeman Yue Fang <[EMAIL PROTECTED]> * Jarek Gawor <[EMAIL PROTECTED]> * Jeff Genender <[EMAIL PROTECTED]> * Eoghan Glynn <[EMAIL PROTECTED]> * Jim Jagielski <[EMAIL PROTECTED]> * Willem Ning Jiang <[EMAIL PROTECTED]> * Eric Johnson <[EMAIL PROTECTED]> * Peter Jones <[EMAIL PROTECTED]> * Daniel Kulp <[EMAIL PROTECTED]> * Bozhong Lin <[EMAIL PROTECTED]> * Jervis Liu <[EMAIL PROTECTED]> * Jim Ma <[EMAIL PROTECTED]> * James Maode Mao <[EMAIL PROTECTED]> * Benson Margulies <[EMAIL PROTECTED]> * Glen Mazza <[EMAIL PROTECTED]> * Guillaume Nodet <[EMAIL PROTECTED]> * Ajay Paibir <[EMAIL PROTECTED]> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Daniel Kulp be appointed to the office of Vice President, Apache CXF, 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 CXF Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CXF podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator CXF podling encumbered upon the Apache Incubator PMC are hereafter discharged. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Request to join IPMC
Hi, I would like to join the IPMC. I'm a PMC member for Camel, CXF and have also contributed to ServiceMix. Please let me know what you need from me. -- Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Request to join IPMC
Hi, I’m an Apache Member and would like to join the IPMC. I'm a PMC member for Camel, CXF and have also contributed to ServiceMix. Please let me know what you need from me. -- Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request to join IPMC
Hi John, Thanks a lot! 发自我的 iPhone > 在 2016年11月4日，上午10:15，John D. Ament 写道： > > I am about to do the next steps for you. > > John > >> On Thu, Nov 3, 2016 at 10:10 PM Willem Jiang wrote: >> >> Hi, >> >> I would like to join the IPMC. I'm a PMC member for Camel, CXF and have >> also contributed to ServiceMix. Please let me know what you >> need from me. >> >> >> -- >> Willem Jiang >> >> >> Blog: http://willemjiang.blogspot.com (English) >> http://jnn.iteye.com (Chinese) >> 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] RocketMQ Incubation Proposal
Hi Justin, It's great to have you join the mentor team. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, Nov 8, 2016 at 10:53 AM, Justin Mclean wrote: > Hi, > > I’d like my name be added to be a Mentor to the project. Assuming the > project is willing to have me that is :-) > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept RocketMQ into the Apache Incubator
+1 (binding) Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Nov 11, 2016 at 8:28 AM, Stian Soiland-Reyes wrote: > +1 (non-binding) > > On 10 Nov 2016 4:41 pm, "Bruce Snyder" wrote: > > > Subsequent to the discussion on RocketMQ, I would like to call a vote on > > accepting RocketMQ into the Apache Incubator. > > > > [ ] +1 Accept RocketMQ into the Apache Incubator > > [ ] +0 Abstain. > > [ ] -1 Do not accept RocketMQ into the Apache Incubator because... > > > > The proposal is pasted below and also available in the wiki here: > > https://wiki.apache.org/incubator/RocketMQProposal > > > > Also, the ASF voting guidelines are available here: > > http://www.apache.org/foundation/voting.html > > > > Thanks, > > > > Bruce > > > > > > = RocketMQ Proposal = > > > > == Abstract == > > > > RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to > > use message-oriented middleware, especially for processing large amounts > of > > streaming data. > > > > == Proposal == > > > > RocketMQ provides a message model including both pub/sub and P2P and it > > supports both reliable FIFO and strict sequential message queues. It also > > has the ability to accumulate a billion messages in a single queue, > > provides mobile, internet-friendly protocols such as MQTT and HTTP. > > RocketMQ also supports the ability to load data into Apache Hadoop for > > offline storage or to handle stream processing for Apache Storm. > > > > == Background == > > > > RocketMQ was developed at Alibaba in 2011 and has been used in production > > there since that time. It can process the large amounts of events > generated > > by various systems and provides a common repository for many types of > > consumers to access and process those events. RocketMQ also handles > dozens > > of types of events including trade order process, search, social network > > activity stream and data pipeline. Every day at Alibaba, RocketMQ > clusters > > process more than 500 billion events. The Alibaba Group also uses > RocketMQ > > to provide message services for more than 3000 core applications. > > > > RocketMQ was developed to meet Alibaba's particular use cases to provide > > low latency message delivery and high throughput message sending. Alibaba > > has also created its cornerstone product derived from RocketMQ, a > Platform > > as a Service (PaaS) product named the Alibaba Cloud Platform ( > > https://intl.aliyun.com/). More than 100 companies use the RocketMQ > open > > source version today. We believe RocketMQ can benefit more people so, we > > would like to share it via the ASF and begin developing a community of > > developers and users via The Apache Way. > > > > > > == Rationale == > > > > As background description, many organizations can benefit from a low > > latency, reliable, high throughput, distributed platform. Its usage is > > varied and we expect many new use cases to emerge. RocketMQ provides many > > features to support many use cases from enterprise application > integration, > > to web applications to the flourishing of IoT applications. > > > > == Current Status == > > > > === Meritocracy === > > > > The intent of this proposal is to start building a diverse developer and > > user community around RocketMQ following the ASF meritocracy model. Since > > RocketMQ was open sourced, we have solicited contributions via the > website > > and presentations given to user groups and technical audiences and have > > received positive feedback and contributions including clients for C++ > and > > .NET. We plan to continue this support for new contributors and work with > > those who contribute significantly to the project to encourage them to > > become committers. > > > > === Community === > > > > RocketMQ is currently being developed by engineers working for Alibaba > > where it is highly used in a production environment. We also have active > > users in or have received contributions from a diverse set of companies > > including CMBC(China Minsheng Bank), Schneider Electric( > > http://www.schneider-electric.com/), the China Railway Ministry official > > ticketing website, China Union, Sina, Umei (http://sh.jumei.com), > Chinese > > Academy of Sciences and many more. We hope to grow the base of > contributors > > by inviting all those
Re: [DISCUSS] China Contribution. (was: RocketMQ Incubation Proposal)
Hi, As we can see more and more Chinese developer wants to contribute to Apache Software Foundation, but they still need to overcome the language barrier even some technical barriers to really join the community. I'm prefer to use email instead of IM or forums because all the discussion can be accessed from public. But for lot of average Chinese users , they may not use English as their working language, it could be hard for them to write English email. With the help of Google Translator, it could be easy for us to be in the same page if every one use the mailing list to discuss the issues. We tried to setup a cxf-zh google group(there were about 2 hundred people) to encourage the CXF users to discuss question in Chinese during the CXF incubation, but few people uses it after the Great Fire Wall started to block the Services of Google. It's convenient for the people to talk to each other within the QQ group in China, but it's hard for people to catch up the previous talk which happened before he joined the group. So I think we need to encourage Chinese developer to use the mailing list as the major channel to discussion questions and it could be great if email is written in English. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Nov 11, 2016 at 3:00 AM, Gunnar Tapper wrote: > Hi, > > Using the RocketMQ proposal to start a larger discussion. > > Apache Trafodion is another project that has a lot of contribution from > China. > > One of the struggles I've seen is that the contributors aren't that active > on email. Rather, they prefer to use a forum on QQ communicating in > Chinese. > > I'm currently the release manager and I must admit that it's hard not to > see all discussions. Several of us are trying to encourage questions etc > via the email lists but users just prefer Chinese forums. > > I suspect that Apache will see more of this behavior moving forward, > especially as other proposals come in. So, I'm hoping that members in China > can help advise on what can be done to address communication issues like > this. > > Thanks, > > Gunnar > > On Nov 5, 2016 12:21 PM, "Ross Gardler" > wrote: > > Some folks may remember my state of the feather session a couple of years > ago when I called for more awareness of the ASFs role in open source beyond > English speaking countries. This was prompted by a fact finding trip to > China. > > RocketMQ and the team behind it was one of the projects I talked to. We > discussed the Apache way at length, however I have not been involved with > this proposal. > > I'm excited to see this proposal. I hope we can bring this project and > welcome the excellent team I met in China into the foundation. We will need > to work hard to ensure the project is a success. Like other China born > projects we will find that there are cultural differences that we need to > understand, but this would not be the first time we, as a foundation and as > individuals, accept an opportunity to grow in this way. Having met some of > the proposing team I am confident that with the right mentors the project > can succeed. > > Bruce, thanks for stepping up to help. > > Ross > > --- > Twitter: @rgardler > > > From: Bruce Snyder > Sent: Saturday, November 5, 2016 9:21:47 AM > To: general@incubator.apache.org > Subject: Re: [DISCUSS] RocketMQ Incubation Proposal > > Hi John, > > Proposals for new ASF projects are offered to this list for constructive > feedback. I am happy to help steer the RocketMQ proposal and project using > your suggestions. > > First, as explained previously in this discussion thread by Von Gosling, > there was some company IP that was mistakenly committed to the Github > repository and through a '...unlucky... scavenging activity' the history > was > erased, as Von put it. I interpret this to mean that someone's git-fu went > awry which unintentionally caused the history to be removed. Von also gives > further explanation of the project history in a response below. Indeed, > this is an unfortunate situation (and one that I've seen before with git), > but should this prevent the project from coming to the ASF to improve and > grow under the auspices of the ASF and The Apache Way? > > Second, regarding your statement: 'and its a bit surprising, since Bruce is > the chair of one of the competitors' -- All projects at the ASF exist > together regardless of their focus and all projects needs good mentors, > regardless of whether they are seen as competing or not. My interest in > helping the RocketMQ project is no
Re: [DISCUSS] China Contribution. (was: RocketMQ Incubation Proposal)
I cannot agree more with that. It's not easy for the average user to understand the "mailing list rule", all they care is to get the answer as soon as possible. If they can get the answer from localize channel, they won't dig the mailing list. So It could be a good way if the committer or developer can guide them to find the answer in a more public way. As a committer I wants to get touch with more users from different communication channel, and we just need to keep in mind of the "mailing list rule". For the user who don't want to subscribe the mailing list, nabble[1] would be another choice. It just works as a forum to mailing list bridge. Maybe we need to consider to introduce another bridge between the user mailing and stackoverflow. [1]http://camel.465427.n5.nabble.com/ Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Nov 12, 2016 at 3:01 AM, Ted Dunning wrote: > > I actually take a different tack on that. > > I answer questions everywhere and provide a pointer for other fora for > followups. It gives a friendlier feeling, improves searchability and still > encourages the mailing lists. > > My experience is that simply not answering and pushing the OP to the lists > has a low success rate. > > Another approach is to post the answer on the mailing lists and put a link > to that thread on the non-Apache site. That's a bit friendlier, but I > don't think it is as good. > > > > On Fri, Nov 11, 2016 at 10:57 AM, Jeff Genender > wrote: > >> I’m not sure that changes anything… that has been the nature of this >> since the beginning. >> >> For Apache… most happens on the mailing lists for very obvious reasons. >> Doing things outside tand not bringing them to the lists is frowned upon >> because it leaves the rest of the community in the dark. >> >> You see the challenges… they were explicitly discussed in this thread. >> English is unfortunately/fortunately the adaptor of communication to the >> world. Thats not “western arrogance”. Its a fact. Someone has to be the >> mediator and english it is. >> >> If a community wants to extend across borders and get more non-localized >> input, then english will likely be the need. If a project/PMC does not, >> care, then utilize your language de-jour with the understanding of the >> consequences. >> >> I don’t really see a solution beyond that. I guess if you have an area >> where the devs discuss in another language and someone wants to translate >> it to english and bring it to the lists so others can be a part of it, I >> assume that would work. But that seems like a lot of work to me. Do you >> have a better solution? >> >> Jeff >> >> >> > On Nov 11, 2016, at 11:32 AM, Gunnar Tapper >> wrote: >> > >> > A few things... >> > >> > 1. There's a huge thriving Apache community in China that operates >> outside of "everything happens on mailing lists." >> > 2. As a committer in an incubator, I want to have insight into those >> communities. >> > 3. I need to figure out if there's anything that can be done to >> encourage this class of contributors to engage more with the worldwide >> community since they are a huge source of potential committers. >> > 4. The language barrier is a real issue where language-to-English >> translators seem to work fine but not vice versa. >> > >> > So, in essence: new interesting challenges in community building. >> > >> > Gunnar >> > >> > On Fri, Nov 11, 2016 at 10:45 AM, Jeff Genender < >> jgenen...@savoirtech.com <mailto:jgenen...@savoirtech.com>> wrote: >> > and you got your answer…. what changes? >> > >> > Jeff >> > >> > >> > > On Nov 11, 2016, at 10:44 AM, Gunnar Tapper > <mailto:tapper.gun...@gmail.com>> wrote: >> > > >> > > Hang on a second. This was not a discussion about RocketMQ. I asked a >> question on the incubators list from a larger-picture perspective using >> Trafodion and RocketMQ as examples. As noted, neither Raynold nor I are >> part of the RocketMQ incubator so let's not ding that project for opinions >> expressed by individuals. >> > > >> > > Thanks, >> > > >> > > Gunnar >> > > >> > > On Fri, Nov 11, 2016 at 7:50 AM, Jeff Genender > <mailto:jgenen...@apache.org> <mailto:jgenen...@apache.org > jgenen...@apache.org>>> wrote: >>
Re: [DISCUSS] China Contribution.
Yeah, we could remove the barrier by using the technology, instead of build another barrier for the communication. Most Chinese user barely use email for customer service, they just prefer to interaction directly with the people. But email could be more effective way, if we want to exchange ideas with the people who doesn't live in different time zone or we want the discussion be searched by public. I could be great if we let them know about it. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Nov 12, 2016 at 4:17 AM, Gunnar Tapper wrote: > Hi, > > Copy/paste into a Translator, which detected the language automatically: > In practice, the question of the language to use from a list of diffusion > is specious. English it the lingua franca of the 21st century. > > Du kan göra precis samma sak med ett minoritetsspråk som svenska. Språk är > inte längre ett hinder. > > Take a look at how the Minecraft generation (I'm blessed with one) > operates. They have no issues to jump onto servers that use languages they > don't understand and then communicate using Translators. It's pretty > awesome. Real-time translators are coming. See Skype Translator for an > example. > > So, I'd argue that lingua franca is already becoming a thing of the past > as people get more comfortable with the idea of using them in everyday > life. Heck, just take a look at how people interact on Facebook these days > -- the translate function is extremely cool. > > You can view language as a barrier to community building or you can use > technology to remove the barrier. > > Based on this discussion, I am going to add a new section to the main > project page that discusses communication in different languages > encouraging people to write questions in the own language if they're not > comfortable with English -- I rather have the question than no interaction. > > I'll tell them that the community uses translator software when needed and > that responses is likely to be in English so that they can translate back > as needed. A smalll first step but an important one. > > Thanks, > > Gunnar > > > > On Fri, Nov 11, 2016 at 12:30 PM, Emmanuel Lécharny > wrote: > >> En pratique, la question de la langue à utiliser sur une liste de >> diffusion est spécieuse. L'anglais est la Lingua Franca du 21ème siècle. >> >> >> And if you haven't understood what I wrote in my native language, which >> is understood by around 500 million people around the globe, I guess you >> get my implicit point ;-) >> >> >> More seriously, it's not about how good are developpers in english : >> many of the Apache developpers are not english native speakers, and we >> do many mistakes. That does not matter too much : nobody will blame >> anyone for that. At some point, code is not in english, but in C, Java, >> Scala, etc... If you work as an IT person, you already have to face >> english in almost all the technical documents found on internet. Take >> the RFCs for instance : have thay all been translated to chinese ? >> >> >> But the most important thing : we are all about community. It's pretty >> hard to build it if you split it in 2, or more, because there is a >> language issue. It's going to be hard to communicate between a split >> community, way harder than using a very basic english... >> >> >> >> Le 11/11/16 à 07:45, Reynold Xin a écrit : >> > Adding members@ >> > >> > On Thu, Nov 10, 2016 at 10:40 PM, Reynold Xin wrote: >> > >> >> To play devil's advocate: is it OK for Apache projects that consist >> >> primarily of Chinese developers to communicate in Chinese? Or put it >> >> differently -- is it a requirement that all communications must be in >> >> English? >> >> >> >> I can see an inclusiveness argument for having to use English, as >> English >> >> is one of the most common languages. However, many talented software >> >> developers in China don't have the sufficient level of proficiency >> when it >> >> comes to English, as the penetration rate of English in China is much >> lower >> >> than other countries. It is as hard for Chinese speakers to learn >> English >> >> as for English speakers to learn Chinese. >> >> >> >> One can certainly argue forcing everybody to use English will also >> exclude >> >> those Chinese developers, and from the perspective of the number of >&
Re: [DISCUSS] Concur for Apache Incubator
Yeah, the project still looks like an internal project, I hardly can find any document about it. I just went through the github project, there is only just one README. I cannot find any wiki pages or other document talking about the roadmap or high level design. I guess the Raft site[1] could help us understand the Raft Algorithm, but other user or developer still need some information to dive in. [1]https://raft.github.io/ Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Nov 23, 2016 at 10:35 PM, Stian Soiland-Reyes wrote: > I think we should in principle aim for also a larger diversity in the > initial committers for a straight-to-TLP, > https://github.com/hortonworks/concur/graphs/contributors does not > show anyone that is not working for Hortonworks - but the proposed > committers (aka proposed PMC?) have broad ASF experience. > > Perhaps the stay in the incubator would be short before graduation, > after the project shows non-Hortonworks folks are engaged. > > Has this proposal or code base been discussed in any of the Hadoop > lists? I could not find anything in the list archives, but then I'm > not too familiar with Hadoop. Or perhaps it was discussed elsewhere > since development started in April? > > > On 23 November 2016 at 14:19, Greg Stein wrote: > > On Wed, Nov 23, 2016 at 5:43 AM, John D. Ament > > wrote: > > > >> On Wed, Nov 23, 2016 at 6:40 AM Roman Shaposhnik > >> wrote: > >> > >> > On Wed, Nov 23, 2016 at 11:58 AM, Jean-Baptiste Onofré < > j...@nanthrax.net> > >> > wrote: > >> > > Hi Jitendra, > >> > > > >> > > I gonna take a deeper look. > >> > > > >> > > My first feedback would be about the name: Concur is > traveling/expense > >> > > solution (https://www.concursolutions.com/). > >> > > > >> > > To avoid confusion, maybe it would make sense to choose another > name. > >> > > >> > FIWI: these were my thoughts exactly. In fact, for a second there I > >> thought > >> > that SAP was donating Concur codebase. > >> > > >> > >> Good to know I wasn't the only one. > >> > >> Jitendra, So considering how strong of a community this is already and > the > >> success of recent TLP direct projects, what goals do you have for > >> incubation? And why incubation over straight to TLP? > > > > > > It is an external codebase, which sets a high bar. The initial committers > > do seem to mostly have ICLAs (haven't looked at all). The Board would > > likely want to see a large majority of them also being ASF Members, > before > > considering straight-to-TLP. > > > > Cheers, > > -g > > > > -- > Stian Soiland-Reyes > http://orcid.org/-0001-9842-9718 > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Weex to enter the Apache Incubator
+1 （binding） Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Nov 25, 2016 at 6:47 AM, Edward J. Yoon wrote: > Greetings! > > I would like to call a vote for accepting "Weex" for incubation in the > Apache Incubator. The full proposal is available below. We ask the > Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion, and > Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to be > Mentors. > > Please cast your vote: > > [ ] +1, bring Weex into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Weex into Incubator, because... > > This vote will be open at least for 72 hours and only votes from the > Incubator PMC are binding. > > -- > https://wiki.apache.org/incubator/WeexProposal > > = Weex Proposal = > > == Abstract == > Weex is a framework for building Mobile cross-platform high performance UI. > Weex enables developers to use Web-like syntax to build iOS, Android and > Web > UI with a single codebase. > > == Proposal == > Weex provide an uniform Web-like syntax for develop native Mobile App UI. > By > leverage the Javascript engine that enable dynamic update, the process of > App interfce and content update can be simple and controllable just like > Web.Compared with WebView based UI framework which performance are limited, > Weex use build-in native components instead. > > Because of tag based syntax that maintain a consistent style with Web > standards Weex using. Developers write in this language just like writting > in HTML. After transforming to JSBundle by Weex tools, these tags will be > rendered by build-in platform-specific components. The logic part of Weex > syntax write in Javascript which don't need be compiled control these > components. > > The vision of Weex is to complement gap between platform-specific Native UI > and Web technical based UI in Mobile age. The team behind Weex believe that > dynamicly interface update and high performance should be achieved at the > same time when people develop a Mobile App. Meanwhile duplicate work > between > the different platforms should be avoided. > > == Background == > Prior to Weex, in order to develop high performance mobile application we > need write at least three different codebase(iOS, Android, Mobile Web) or > adopt WebView based UI technique(Apache Cordova for example) which can't > satisfy the demand for performance. > > A special task force at Alibaba Inc try to provide a solution for this > problem has been setup since 2013. At first the team release a > cross-platform rendering engine which render a special format JSON to > native > components on different platform. To output this JSON file the team had > build a website which other developer can use to simply design final > interface. > > Although This solution had worked for a while, we found it not able to meet > our UI developer's habits. Most of our UI developer have Web background > which make them used to use tag based language to design App interface. > Meanwhile we found the JSON file lacks of enough flexibility. The following > discussion inspire we start to develop Weex. > > Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest user > volume eCommerce App in China has adapted Weex in a lot of UI. In the > latest > November 11th promotions(Alibaba's annual Singles' Day online shopping > event), UI developers from Alibaba Inc have build more then 1,500 pages > using Weex, 99.6% of all the promotional pages. The ratio of less than one > second page open time is more than 90%, the frame rate is 53.0~58.5(depend > on device) due to the high performance of Weex. In addition to user > experience improvement, the productivity of page development and the > efficiency of content delivery both have been improved. > > After open-source and have got a lot of followers in chinese mobile App > development community, several of popular Apps listed on chinese top charts > have adopted or planning for adopt Weex.(UCWeb, Tmall, YouKu, Suning > etc...) > > == Current Status == > Weex has become an open source project since June 2016. It has been used > at > a lot of Alibaba producted mobile softwares which running on the mobile > phone of millions of users. > > Weex code repository located at GitHub. All development activities have > already happened on GitHub as open source manner. > > == Community == > The community surrounding Weex is a variety of developer which have > different technique background.iOS, Android, Web developer must collaborate > closely to implement most Weex f
Re: [RESTART] [VOTE] Graduate Apache Beam
+1 (binding) Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, Dec 6, 2016 at 9:47 AM, Luciano Resende wrote: > +1 (binding) > > On Mon, Dec 5, 2016 at 3:31 PM Davor Bonaci wrote: > > > Hi everyone, > > Please vote on the draft resolution proposed by the Apache Beam PPMC > below, > > which establishes Apache Beam as a new top-level project at the Apache > > Software Foundation, as follows: > > > > [ ] +1, Graduate Apache Beam from the Incubator. > > [ ] +0, Don't care. > > [ ] -1, Don't graduate Apache Beam from the Incubator because... > > > > Please note that this is a restarted vote, per John's request, to clarify > > the alternatives. The old voting thread is archived [1]. > > > > Before voting, please see the full text of the draft resolution below and > > the corresponding discussion thread [2], and vote only after you feel > ready > > to do so. The vote will be open for at least 72 hours. This is a > procedural > > vote [3]; it is adopted by a simple majority of qualified votes (with no > > minimum). > > > > If approved by the Apache Incubator, the proposed resolution will be > > submitted to the Board of Directors for their consideration. > > > > Thank you! > > > > Davor > > > > [1] > > > > https://lists.apache.org/thread.html/a8e9cecfe93f0e464cc7c1774d2761 > ca14326df1101b7670ca8b1dc3@%3Cgeneral.incubator.apache.org%3E > > [2] > > > > https://lists.apache.org/thread.html/b9c1071b35558846836814575ada3c > dca61c72dc1e672ab994a9c936@%3Cgeneral.incubator.apache.org%3E > > [3] http://apache.org/foundation/voting.html > > > > The full-text of the draft resolution proposed by the Apache Beam PPMC: > > > > X. Establish the Apache Beam 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 a unified programming model for both > >batch and streaming data processing, enabling efficient > >execution across diverse distributed execution engines > >and providing extensibility points for connecting to different > >technologies and user communities. > > > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management > >Committee (PMC), to be known as the "Apache Beam Project", > >be and hereby is established pursuant to Bylaws of the > >Foundation; and be it further > > > >RESOLVED, that the Apache Beam Project be and hereby is > >responsible for the creation and maintenance of software > >related to a unified programming model for both batch and > >streaming data processing, enabling efficient execution across > >diverse distributed execution engines and providing extensibility > >points for connecting to different technologies and user > >communities; and be it further > > > >RESOLVED, that the office of "Vice President, Apache Beam" 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 Beam Project, and to have primary responsibility > >for management of the projects within the scope of > >responsibility of the Apache Beam 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 Beam Project: > > > > * Tyler Akidau > > * Davor Bonaci > > * Robert Bradshaw > > * Ben Chambers > > * Luke Cwik > > * Stephan Ewen > > * Dan Halperin > > * Kenneth Knowles > > * Aljoscha Krettek > > * Maximilian Michels > > * Jean-Baptiste Onofré > > * Frances Perry > > * Amit Sela > > * Josh Wills > > > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Davor Bonaci > >be appointed to the office of Vice President, Apache Beam, to > >serve in accordance with and subjec
Re: [VOTE] Apache Gearpump (incubating) 0.8.3-RC1
I ran the build from source and went through the source code, every thing looks good. Here is my +1. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, Apr 11, 2017 at 5:33 PM, Karol Brejna wrote: > Hi IPMC Community, > > The PPMC vote to release Apache Gearpump (incubating) 0.8.3-RC1 has passed. > We would like to now submit this release candidate to the IPMC. > > The PPMC vote thread is here: > https://lists.apache.org/thread.html/0e1022d2f3b5b2a2b879e4c278d7fc > 44d094058550d47ae7e07702ec@%3Cdev.gearpump.apache.org%3E > > The source and binary tarballs, including signatures, digests, etc. > can be found at: > https://dist.apache.org/repos/dist/dev/incubator/gearpump/0. > 8.3-incubating/RC1/ > > Release artifacts are signed with the key with fingerprint: > 3F12 81A2 DB58 0842 5ABA 6962 D8A8 4FBC 0A83 B291 > > The KEYS file is available here: > https://dist.apache.org/repos/dist/dev/incubator/gearpump/KEYS > > The tag to be voted upon is: > https://git-wip-us.apache.org/repos/asf?p=incubator- > gearpump.git;a=shortlog;h=refs/tags/0.8.3-RC1 > > The release hash is: > https://git-wip-us.apache.org/repos/asf?p=incubator- > gearpump.git;a=commit;h=80f49154428cd18b5a27d946b8c9536124849cc9 > > For information about the contents of this release see: > https://issues.apache.org/jira/browse/GEARPUMP-294?jql= > project%20%3D%20GEARPUMP%20AND%20status%20in%20( > Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%200.8.3 > > This vote will be open for 72 hours (Thursday, April 13, 2017 at 3:00AM > PST). > > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, run the > binary artifacts in the binary release and test. > Please vote: > > [ ] +1 Release this package as gearpump-0.8.3 > [ ] +0 no opinion > [ ] -1 Do not release this package because because... > > Thanks, > Karol > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Graduate Apache RocketMQ from podling to TLP
+1. It's great to see RocketMQ build up a healthy and active community in the Apache Way during podling. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Aug 30, 2017 at 10:13 AM, Von Gosling wrote: > Hello IPMC, > > The recent DISCUSS thread in PPMC, IPMC and VOTE thread in Community on > the topic of Apache RocketMQ graduation have been opened for at least 72 > hours, and I believe all questions have been answered and issues addressed > at this point. > > With the discussion having settled down, I would now like to call for a > recommendation VOTE to present the ASF board with the following resolution > to graduate from incubation and establish Apache RocketMQ as a top-level > project (TLP). > > RocketMQ PPMC DISCUSS thread: > https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d204 > 1453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E < > https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d204 > 1453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E> > > RocketMQ IPMC DISCUSS thread: > https://lists.apache.org/thread.html/2b84fa29cb3e7ce54a683a72e97f30 > 4b19321521b37435909c097e64@%3Cgeneral.incubator.apache.org%3E > https://lists.apache.org/thread.html/81a7710c71ed4d79e940fb0c5fcb06 > 20b31e87297520fd7ceedf0cf2@%3Cgeneral.incubator.apache.org%3E < > https://lists.apache.org/thread.html/81a7710c71ed4d79e940fb0c5fcb06 > 20b31e87297520fd7ceedf0cf2@%3Cgeneral.incubator.apache.org%3E> > > RocketMQ Community VOTE thread: > https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c86 > 7a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E < > https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c86 > 7a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E> > > RocketMQ Community VOTE RESULT thread: > https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e5418 > 7fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E < > https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e5418 > 7fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E> > > > Apache RocketMQ entered incubation in November 2016. Since then there have > been two releases and four committers and one PMC candidate member have > been added to the project. For each release, source and binary artifacts > have been made available. Based on the completed maturity evaluation we > believe that the project is ready to graduate from the incubator. More > checklist info about graduation, please refer to > https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist > <https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist > > > > > Please vote on whether to recommend the following graduation resolution to > the ASF Board. > > [ ] +1, In favor of recommending the following graduation resolution to > the ASF Board to establish Apache RocketMQ as a TLP > [ ] +0, Neither opposed to, nor in favor of, recommending the following > graduation resolution to the Board > [ ] -1, Opposed to recommending the following graduation resolution to > the Board(provide details) > > This VOTE will be open for at least 72 hours. Here is my vote +1. Thanks > to all Mentors and Apache RocketMQ Project members for their support and > contributions again. > > The full text of the resolution is below. If approved by the Apache > Incubator PMC members, the proposed resolution will be submitted to the > Board of Directors for their consideration. > > Establish the Apache RocketMQ 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 a fast, low latency, reliable, scalable, distributed, easy to > use message-oriented middleware, especially for processing large amounts > of streaming data. > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache RocketMQ Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > RESOLVED, that the Apache RocketMQ Project be and hereby is responsible > for the creation and maintenance of software related to a fast, low > latency, reliable, scalable, distributed, easy to use message-oriented > middleware, especially for processing large amounts of streaming data; > and be it further > RESOLVED, that the office of "Vice President, Apache RocketMQ" be and > hereby is created, the
Write access to Incubator Wiki
Hi, May I have the write access of Incubator wiki for editing the page of incubator? My name is njiang, email is ningji...@apache.org Thanks, Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem
Re: Write access to Incubator Wiki
Thanks John & Geertjan. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Oct 11, 2017 at 1:39 AM, John D. Ament wrote: > I'm not sure where Geertjan added you, but I added you to > https://wiki.apache.org/incubator/ContributorsGroup > > John > > On Tue, Oct 10, 2017 at 11:07 AM Geertjan Wielenga < > geertjan.wiele...@googlemail.com> wrote: > > > Done. > > > > Gj > > > > On Tue, Oct 10, 2017 at 3:58 PM, Willem Jiang > > wrote: > > > > > Hi, > > > > > > May I have the write access of Incubator wiki for editing the page of > > > incubator? > > > > > > My name is njiang, email is ningji...@apache.org > > > > > > Thanks, > > > > > > Willem Jiang > > > > > > Blog: http://willemjiang.blogspot.com (English) > > > http://jnn.iteye.com (Chinese) > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > >
Re: [VOTE] Accept Crail into the Apache Incubator
+1 (binding) Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Oct 28, 2017 at 2:12 AM, Pierre Smits wrote: > +1 > > Best regards > > Pierre > > On Fri, 27 Oct 2017 at 13:57 Raphael Bircher > wrote: > > > +1 (binding) > > > > Am .10.2017, 18:01 Uhr, schrieb Luciano Resende : > > > > > Off course, my + 1 > > > > > > On Thu, Oct 26, 2017 at 12:31 PM, Luciano Resende < > luckbr1...@gmail.com> > > > wrote: > > > > > >> Now that the discussion thread on the Crail proposal has ended, please > > >> vote on accepting Crail into into the Apache Incubator. > > >> > > >> The ASF voting rules are described at: > > >>http://www.apache.org/foundation/voting.html > > >> > > >> A vote for accepting a new Apache Incubator podling is a majority vote > > >> for which only Incubator PMC member votes are binding. > > >> > > >> Votes from other people are also welcome as an indication of peoples > > >> enthusiasm (or lack thereof). > > >> > > >> Please do not use this VOTE thread for discussions. > > >> If needed, start a new thread instead. > > >> > > >> This vote will run for at least 72 hours. Please VOTE as follows > > >> [] +1 Accept Crail into the Apache Incubator > > >> [] +0 Abstain. > > >> [] -1 Do not accept Crail into the Apache Incubator because ... > > >> > > >> The proposal below is also on the wiki: > > >> https://wiki.apache.org/incubator/CrailProposal > > >> > > >> === > > >> > > >> Abstract > > >> > > >> Crail is a storage platform for sharing performance critical data in > > >> distributed data processing jobs at very high speed. Crail is built > > >> entirely upon principles of user-level I/O and specifically targets > data > > >> center deployments with fast network and storage hardware (e.g., > 100Gbps > > >> RDMA, plenty of DRAM, NVMe flash, etc.) as well as new modes of > > >> operation > > >> such resource disaggregation or serverless computing. Crail is written > > >> in > > >> Java and integrates seamlessly with the Apache data processing > > >> ecosystem. > > >> It can be used as a backbone to accelerate high-level data operations > > >> such > > >> as shuffle or broadcast, or as a cache to store hot data that is > queried > > >> repeatedly, or as a storage platform for sharing inter-job data in > > >> complex > > >> multi-job pipelines, etc. > > >> > > >> Proposal > > >> > > >> Crail enables Apache data processing frameworks to run efficiently in > > >> next > > >> generation data centers using fast storage and network hardware in > > >> combination with resource (e.g., DRAM, Flash) disaggregation. > > >> > > >> Background > > >> > > >> Crail started as a research project at the IBM Zurich Research > > >> Laboratory > > >> around 2014 aiming to integrate high-speed I/O hardware effectively > into > > >> large scale data processing systems. > > >> > > >> Rational > > >> > > >> During the last decade, I/O hardware has undergone rapid performance > > >> improvements, typically in the order of magnitudes. Modern day > > >> networking > > >> and storage hardware can deliver 100+ Gbps (10+ GBps) bandwidth with a > > >> few > > >> microseconds of access latencies. However, despite such progress in > raw > > >> I/O > > >> performance, effectively leveraging modern hardware in data processing > > >> frameworks remains challenging. In most of the cases, upgrading to > > >> high-end > > >> networking or storage hardware has very little effect on the > > >> performance of > > >> analytics workloads. The problem comes from heavily layered software > > >> imposing overheads such as deep call stacks, unnecessary data copies, > > >> thread contention, etc. These problems have already been addressed at > > >> the > > >> operating system level with new I/O APIs such as RDMA verbs, NVMe, > etc., > > >> allowing applications to bypass software layers during I/O operations
[DISCUSS] Accept ServiceComb into Apache Incubator
avassist MIT: * Mockito * SLF4J * Bridge-method-annotation EPL 1.0: * JUnit * Logback As all dependencies are managed using Apache Maven, none of the external libraries need to be packaged in a source distribution. 3.ServiceComb Service-Center depends on Open-Source Projects(Organized by License) MIT * github.com/Knetic/govaluate * github.com/beorn7/perks * github.com/boltdb/bolt * github.com/couchbase/go-couchbase * github.com/couchbase/gomemcached * github.com/cupcake/rdb * github.com/dustin/go-humanize * github.com/karlseguin/ccache * github.com/kr/pty * github.com/lib/pq * github.com/mattn/go-runewidth * github.com/olekukonko/tablewriter * github.com/onsi/ginkgo * github.com/onsi/gomega * github.com/pelletier/go-toml * github.com/siddontang/go * github.com/siddontang/ledisdb * github.com/siddontang/rdb * github.com/ugorji/go * github.com/urfave/cli * github.com/xiang90/probing * github.com/bgentry/speakeasy * github.com/ghodss/yaml BSD 3-Clause * github.com/beego/x2j * github.com/belogik/goes * github.com/cloudflare/golz4 * github.com/edsrzf/mmap-go * github.com/golang/snappy * github.com/spf13/pflag * github.com/widuu/gojson * golang.org/x/crypto * golang.org/x/net * golang.org/x/text * golang.org/x/time * gopkg.in/cheggaaa/pb.v1 BSD 2-Clause * github.com/gorilla/websocket * github.com/syndtr/goleveldb Apache-2.0 * github.com/bradfitz/gomemcache * google.golang.org/genproto * github.com/astaxie/beego * gopkg.in/yaml.v2 * github.com/cockroachdb/cmux * github.com/casbin/casbin * github.com/coreos/etcd * github.com/coreos/go-semver * github.com/coreos/go-systemd * github.com/jonboulle/clockwork * github.com/prometheus/client_golang * github.com/prometheus/client_model * github.com/prometheus/common * github.com/prometheus/procfs * github.com/hsluoyz/casbin * github.com/coreos/pkg * github.com/garyburd/redigo * github.com/spf13/cobra * github.com/google/btree * github.com/matttproud/golang_protobuf_extensions Copyright (c) 2013, The GoGo Authors. * github.com/gogo/protobuf Copyright 2010 The Go Authors. * github.com/golang/protobuf Service-Center Frontend depends on Open-Source Projects(Organized by License) MIT: * angular * angular-animate * angular-aria * angular-material-data-table * angular-material * angular-messages * angular-mocks * angular-resource * angular-route * angular-sanitize * angular-swagger-ui * angular-translate-loader-static-files * angular-translate * angular-ui-bootstrap * angular-ui-router * bootstrap-less-only * bootstrap-sass-official * chart.js * Components-font-awesome * mmumshad/angular-yamljs * jeremyfa/yaml.js Apache-2.0: * Json-formatter BSD * Angular-charts.js * JS Foundation * jQuery == Required Resources == === Mailing Lists === * priv...@servicecomb.incubator.apache.org (moderated subscriptions) * comm...@servicecomb.incubator.apache.org * d...@servicecomb.incubator.apache.org * iss...@servicecomb.incubator.apache.org === Source Control === * https://git-wip-us.apache.org/repos/asf/incubator-servicecomb-java-chassis.git * https://git-wip-us.apache.org/repos/asf/incubator-servicecomb-service-center.git * https://git-wip-us.apache.org/repos/asf/incubator-servicecomb-saga.git * https://git-wip-us.apache.org/repos/asf/incubator-servicecomb-website.git === Issue Tracking === JIRA Project ServiceComb === Initial Committers === * Ning Jiang * Qi Zhang * Xiang Yin * JiMin Wu * Liubao * Mohammad Asif Siddiqui * Yihua Cui * Roman Shaposhnik * Jean-Baptiste Onofre * Timothy Chen === Additional Interested Contributors === * Jian Zhang cos...@gmail.com * Bing Wang wangbb0...@gmail.com * Ven Jiang venji...@gmail.com * GeekTJS josephy...@gmail.com * Li Zhou eacdy0...@126.com * Haiwei Zhang haiwei...@foxmail.com * Yetiea yet...@gmail.com === Affiliations === * Huawei: Ning Jiang, Qi Zhang, Xiang Yin, JiMin Wu, Liubao, Mohammad Asif Siddiqui, Yihua Cui * Stealth: Roman Shaposhnik * Talend: Jean-Baptiste Onofré * Hyperpilot: Timothy Chen === Sponsors === Champion * Roman Shaposhnik[r...@apache.org] Nominated Mentors * Roman Shaposhnik[r...@apache.org] * Jean-Baptiste Onofre [jbono...@apache.org] * Timothy Chen[tnac...@apache.org] === Sponsoring Entity === * We are requesting the Incubator to sponsor this project. Willem Jiang
Re: [DISCUSS] Accept ServiceComb into Apache Incubator
Hi Let's start a VOTE tomorrow if nobody has big concerns or issued they'd want to clarify before the vote. When drafting this proposal we got lots of useful feedbacks from our mentors. The biggest items to look at during incubation is completing the transition from a company internal project to an independent, diverse community and doing the license review of the various dependencies during the release process. I don't think we have big issue here, and we will try our best to do things in Apache way. For the trademark, Huawei already registered "ServiceComb" in US, European and China. We are happy to donate it to ASF. Willem Jiang On Sat, Nov 4, 2017 at 7:47 AM, Willem Jiang wrote: > Hi Folks, > > I would like to open a DISCUSS thread on the topic of accepting the > ServiceComb Project into the Incubator. > > ServiceComb is a microservice framework that provides a set of tools and > components to make development and deployment of cloud applications easier. > > The draft proposal can be found in the wiki at the following URL: > https://wiki.apache.org/incubator/ServiceCombProposal > > At this stage we could very much appreciate the discussion and feedback > for entering Apache Incubation. The text for the draft proposal is found > below. > > = ServiceComb Proposal = > > == Abstract == > > ServiceComb is a microservice framework that provides a set of tools and > components to make development and deployment of cloud applications easier. > It provides functionalities such as service contract enforcement, service > registration, service discovery, load balance, service reliability (latency > and fault tolerance, flow control and graceful degradation, handler chain > tracing), eventual data consistency and so forth. > > == Proposal == > > The goal of this proposal is to bring the existing ServiceComb codebase > and existing developers into the Apache Software Foundation (ASF) in order > to build a vibrant, diverse and self-governed open source community around > the technology. > So far the major contributors to the project have been affiliated with > Huawei and Huawei is planning to continue market and sell the Cloud Service > Engine leveraging the ServiceComb framework. > ServiceComb is currently a registered trademark owned by Huawei, and > Huawei is happy to donate this trademark to Apache. > > Huawei is submitting this proposal to donate the Service source code and > associated artifacts (documentation, web site content, wiki, etc.) to the > Apache Software Foundation Incubator under the Apache License, Version 2.0 > and is asking Incubator PMC to establish an open source community. These > artifacts are currently available on GitHub at https://github.com/ > ServiceComb/ and include: > * Java Chassis: a multi-protocol (RPC & Restful) microservice framework > which adopts contract-first design > * Service Center: a service registry that enforces service contract upon > service registration and discovery > * Saga: a distributed coordinator to achieve eventual data consistency > based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem > * ServiceComb.github.io: the website repo of ServiceComb. > * The other projects will be moved to another place if ServiceComb is > accepted by Apache as an incubator project. > > == Background == > > Microservices is a variant of the service-oriented architecture (SOA) > architectural style that structures an application as a collection of > loosely coupled services. ServiceComb is an open source microservice > framework initiated as part of Huawei CSE projects (Cloud Service Engine) > which was developed in 2015. It is a part of ServiceStage of Huawei Public > Cloud which is one-stop PaaS platform for enterprises and developers. > Besides ServiceStage, it’s also used in the Huawei Core Network IOT > Platform and Huawei consumer cloud. The number of companies using > ServiceComb to develop their enterprise applications, they are > chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and > the number is over 5 and counting. > > == Rationale == > > ServiceComb has been developed as a total, open source solution for > developing cloud native applications. So far ServiceComb has existed as a > GitHub project with committers mostly working for Huawei. We feel that > moving it to a neutral organization like Apache, with its strong governance > model, is expected to help get more contributions from various > organizations and developers, who may be concerned by exclusive control of > ServiceComb by Huawei. > > == Initial Goals == > > Our initial goals are to bring ServiceComb into the ASF, transition > internal engineering processes into the open, and fo
[VOTE] Accept ServiceComb into the Apache Incubator
Hi All, I would like to start a VOTE to bring the ServiceComb project in as an Apache incubator podling. The ASF voting rules are described: https://www.apache.org/foundation/voting.html A vote for accepting a new Apache Incubator podling is a majority vote for which only Incubator PMC member votes are binding. This vote will run for at least 72 hours. Please VOTE as follows [] +1 Accept ServiceComb into the Apache Incubator [] +0 Abstain. [] -1 Do not accept ServiceComb into the Apache Incubator because ... The proposal is listed below, but you can also access it on the wiki: https://wiki.apache.org/incubator/ServiceCombProposal Best regards, Willem Jiang = ServiceComb Proposal = == Abstract == ServiceComb is a microservice framework that provides a set of tools and components to make development and deployment of cloud applications easier. It provides functionalities such as service contract enforcement, service registration, service discovery, load balance, service reliability (latency and fault tolerance, flow control and graceful degradation, handler chain tracing), eventual data consistency and so forth. == Proposal == The goal of this proposal is to bring the existing ServiceComb codebase and existing developers into the Apache Software Foundation (ASF) in order to build a vibrant, diverse and self-governed open source community around the technology. So far the major contributors to the project have been affiliated with Huawei and Huawei is planning to continue market and sell the Cloud Service Engine leveraging the ServiceComb framework. ServiceComb is currently a registered trademark owned by Huawei, and Huawei is happy to donate this trademark to Apache. Huawei is submitting this proposal to donate the Service source code and associated artifacts (documentation, web site content, wiki, etc.) to the Apache Software Foundation Incubator under the Apache License, Version 2.0 and is asking Incubator PMC to establish an open source community. These artifacts are currently available on GitHub at https://github.com/ServiceComb/ and include: * Java Chassis: a multi-protocol (RPC & Restful) microservice framework which adopts contract-first design * Service Center: a service registry that enforces service contract upon service registration and discovery * Saga: a distributed coordinator to achieve eventual data consistency based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem * ServiceComb.github.io: the website repo of ServiceComb. * The other projects will be moved to another place if ServiceComb is accepted by Apache as an incubator project. == Background == Microservices is a variant of the service-oriented architecture (SOA) architectural style that structures an application as a collection of loosely coupled services. ServiceComb is an open source microservice framework initiated as part of Huawei CSE projects (Cloud Service Engine) which was developed in 2015. It is a part of ServiceStage of Huawei Public Cloud which is one-stop PaaS platform for enterprises and developers. Besides ServiceStage, it’s also used in the Huawei Core Network IOT Platform and Huawei consumer cloud. The number of companies using ServiceComb to develop their enterprise applications, they are chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and the number is over 5 and counting. == Rationale == ServiceComb has been developed as a total, open source solution for developing cloud native applications. So far ServiceComb has existed as a GitHub project with committers mostly working for Huawei. We feel that moving it to a neutral organization like Apache, with its strong governance model, is expected to help get more contributions from various organizations and developers, who may be concerned by exclusive control of ServiceComb by Huawei. == Initial Goals == Our initial goals are to bring ServiceComb into the ASF, transition internal engineering processes into the open, and foster a collaborative development model according to the "Apache Way." Huawei and the current contributors to ServiceComb plan to develop new functionality in an open, community-driven way. To get there, the existing internal build, test and release processes will be refactored to support open development. 1. More specifically, our initial plan of moving ServiceComb to ASF is focused on: 2. open up the governance model in order to simplify and streamline contributions from the community 3. move the existing codebase to Apache 4. integrate with the Apache development process 5. ensure all dependencies are compliant with Apache License version 2.0 6. incremental development and releases per Apache guideline == Current Status == === Meritocracy === We intend to substantially expand the initial developer and user community by running the project in line with the "Apache Way". Users and new contributors will be treated with respect and welcomed. By
Re: [VOTE] Accept ServiceComb into the Apache Incubator
My +1（binding). Willem Jiang On Tue, Nov 14, 2017 at 2:15 PM, Willem Jiang wrote: > Hi All, > > I would like to start a VOTE to bring the ServiceComb project in as an > Apache incubator podling. > > The ASF voting rules are described: > > https://www.apache.org/foundation/voting.html > > A vote for accepting a new Apache Incubator podling is a majority vote for > which only Incubator PMC member votes are binding. > > This vote will run for at least 72 hours. Please VOTE as follows > [] +1 Accept ServiceComb into the Apache Incubator > [] +0 Abstain. > [] -1 Do not accept ServiceComb into the Apache Incubator because ... > > The proposal is listed below, but you can also access it on the wiki: > > https://wiki.apache.org/incubator/ServiceCombProposal > > Best regards, > > Willem Jiang > > = ServiceComb Proposal = > > == Abstract == > > ServiceComb is a microservice framework that provides a set of tools and > components to make development and deployment of cloud applications easier. > It provides functionalities such as service contract enforcement, service > registration, service discovery, load balance, service reliability (latency > and fault tolerance, flow control and graceful degradation, handler chain > tracing), eventual data consistency and so forth. > > == Proposal == > > The goal of this proposal is to bring the existing ServiceComb codebase > and existing developers into the Apache Software Foundation (ASF) in order > to build a vibrant, diverse and self-governed open source community around > the technology. > So far the major contributors to the project have been affiliated with > Huawei and Huawei is planning to continue market and sell the Cloud Service > Engine leveraging the ServiceComb framework. > ServiceComb is currently a registered trademark owned by Huawei, and > Huawei is happy to donate this trademark to Apache. > > Huawei is submitting this proposal to donate the Service source code and > associated artifacts (documentation, web site content, wiki, etc.) to the > Apache Software Foundation Incubator under the Apache License, Version 2.0 > and is asking Incubator PMC to establish an open source community. These > artifacts are currently available on GitHub at https://github.com/ > ServiceComb/ and include: > * Java Chassis: a multi-protocol (RPC & Restful) microservice framework > which adopts contract-first design > * Service Center: a service registry that enforces service contract upon > service registration and discovery > * Saga: a distributed coordinator to achieve eventual data consistency > based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem > * ServiceComb.github.io: the website repo of ServiceComb. > * The other projects will be moved to another place if ServiceComb is > accepted by Apache as an incubator project. > > == Background == > > Microservices is a variant of the service-oriented architecture (SOA) > architectural style that structures an application as a collection of > loosely coupled services. ServiceComb is an open source microservice > framework initiated as part of Huawei CSE projects (Cloud Service Engine) > which was developed in 2015. It is a part of ServiceStage of Huawei Public > Cloud which is one-stop PaaS platform for enterprises and developers. > Besides ServiceStage, it’s also used in the Huawei Core Network IOT > Platform and Huawei consumer cloud. The number of companies using > ServiceComb to develop their enterprise applications, they are > chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and > the number is over 5 and counting. > > == Rationale == > > ServiceComb has been developed as a total, open source solution for > developing cloud native applications. So far ServiceComb has existed as a > GitHub project with committers mostly working for Huawei. We feel that > moving it to a neutral organization like Apache, with its strong governance > model, is expected to help get more contributions from various > organizations and developers, who may be concerned by exclusive control of > ServiceComb by Huawei. > > == Initial Goals == > > Our initial goals are to bring ServiceComb into the ASF, transition > internal engineering processes into the open, and foster a collaborative > development model according to the "Apache Way." Huawei and the current > contributors to ServiceComb plan to develop new functionality in an open, > community-driven way. To get there, the existing internal build, test and > release processes will be refactored to support open development. > > 1. More specifically, our initial plan of moving ServiceComb to ASF is > focused on: > 2. open up th
Re: [VOTE] Resolution to graduate Apache Impala to TLP
+1 (binding) Willem Jiang On Thu, Nov 16, 2017 at 2:55 AM, Ted Dunning wrote: > +1 > > > > On Wed, Nov 15, 2017 at 12:02 PM, Luke Han wrote: > > > +1 (binding) > > > > > > Best Regards! > > - > > > > Luke Han > > > > On Wed, Nov 15, 2017 at 7:08 AM, Gangumalla, Uma < > uma.ganguma...@intel.com > > > > > wrote: > > > > > +1 (binding) > > > > > > Regards, > > > Uma > > > > > > On Nov 8, 2017 8:28 PM, "Jim Apple" wrote: > > > > > > > The graduation of Impala to a TLP has been discussed[0] on > > dev@impala > > > , > > > > voted on[1] on dev@impala, and discussed[2] on > general@incubator. > > > All > > > > threads were open 72 hours or more, and all seem to have > quiesced. > > > > > > > > This is a call for a VOTE to graduate Impala to a TLP. The draft > > > resolution > > > > is below. Please select from: > > > > > > > > [ ] +1: Graduate Impala to a TLP > > > > [ ] +-0: Neither graduate nor do not graduate Impala to a TLP > > > > [ ] -1: Do NOT graduate Impala to a TLP, because ... > > > > > > > > > > > > > > > > > > [0]: < > > > > https://lists.apache.org/thread.html/ > > 2f5db4788aff9b0557354b9106c032 > > > > 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E > > > > > > > > > > > > > [1]: < > > > > https://lists.apache.org/thread.html/ > > a5a7c6895b3e019347d6e4e4cf49d6 > > > > 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E > > > > > > > > > > > > > [2]: < > > > > https://lists.apache.org/thread.html/ > > 6b8598408f76a472532923c5a7fc51 > > > > 0470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > > > > > > > > > > > > > Establish the Apache Impala 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 a high-performance distributed SQL engine. > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee > > > > (PMC), to be known as the "Apache Impala Project", be and hereby > is > > > > established pursuant to Bylaws of the Foundation; and be it > further > > > > > > > > RESOLVED, that the Apache Impala Project be and hereby is > > responsible > > > > for the creation and maintenance of software related to a > > > > high-performance distributed SQL engine; and be it further > > > > > > > > RESOLVED, that the office of "Vice President, Apache Impala" 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 > > Impala > > > > Project, and to have primary responsibility for management of the > > > > projects within the scope of responsibility of the Apache Impala > > > > 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 Impala > > > Project: > > > > > > > > * Alex Behm > > > > * Bharath Vissapragada > > > > * Brock Noland > > > > * Carl Steinbach > > > > * Casey Ching > > > > * Daniel Hecht > > > > * Dimitris Tsirogiannis > > > > * Henry Robinson > > > > * Ishaan Joshi > > > > * Jim Apple > > > > * John R
[RESULT][VOTE] Accept ServiceComb into the Apache Incubator
Hi all, The vote for accepting ServiceComb into Apache Incubator passed with 8 binding "+1" votes, 5 nonbinding "+1" votes, and no "0" or "-1" votes. Binding votes: Jean-Baptiste Onofre Timothy Chen Willem Jiang Dave Fisher Roman Shaposhnik Luke Han Gangumalla Uma Non-binding votes: Liang Chen Charith Elvitigala Vinayakumar B Pierre Smits Sean Yin Thanks to all who voted! Willem Jiang On Tue, Nov 14, 2017 at 2:15 PM, Willem Jiang wrote: > Hi All, > > I would like to start a VOTE to bring the ServiceComb project in as an > Apache incubator podling. > > The ASF voting rules are described: > > https://www.apache.org/foundation/voting.html > > A vote for accepting a new Apache Incubator podling is a majority vote for > which only Incubator PMC member votes are binding. > > This vote will run for at least 72 hours. Please VOTE as follows > [] +1 Accept ServiceComb into the Apache Incubator > [] +0 Abstain. > [] -1 Do not accept ServiceComb into the Apache Incubator because ... > > The proposal is listed below, but you can also access it on the wiki: > > https://wiki.apache.org/incubator/ServiceCombProposal > > Best regards, > > Willem Jiang > > = ServiceComb Proposal = > > == Abstract == > > ServiceComb is a microservice framework that provides a set of tools and > components to make development and deployment of cloud applications easier. > It provides functionalities such as service contract enforcement, service > registration, service discovery, load balance, service reliability (latency > and fault tolerance, flow control and graceful degradation, handler chain > tracing), eventual data consistency and so forth. > > == Proposal == > > The goal of this proposal is to bring the existing ServiceComb codebase > and existing developers into the Apache Software Foundation (ASF) in order > to build a vibrant, diverse and self-governed open source community around > the technology. > So far the major contributors to the project have been affiliated with > Huawei and Huawei is planning to continue market and sell the Cloud Service > Engine leveraging the ServiceComb framework. > ServiceComb is currently a registered trademark owned by Huawei, and > Huawei is happy to donate this trademark to Apache. > > Huawei is submitting this proposal to donate the Service source code and > associated artifacts (documentation, web site content, wiki, etc.) to the > Apache Software Foundation Incubator under the Apache License, Version 2.0 > and is asking Incubator PMC to establish an open source community. These > artifacts are currently available on GitHub at https://github.com/ > ServiceComb/ and include: > * Java Chassis: a multi-protocol (RPC & Restful) microservice framework > which adopts contract-first design > * Service Center: a service registry that enforces service contract upon > service registration and discovery > * Saga: a distributed coordinator to achieve eventual data consistency > based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem > * ServiceComb.github.io: the website repo of ServiceComb. > * The other projects will be moved to another place if ServiceComb is > accepted by Apache as an incubator project. > > == Background == > > Microservices is a variant of the service-oriented architecture (SOA) > architectural style that structures an application as a collection of > loosely coupled services. ServiceComb is an open source microservice > framework initiated as part of Huawei CSE projects (Cloud Service Engine) > which was developed in 2015. It is a part of ServiceStage of Huawei Public > Cloud which is one-stop PaaS platform for enterprises and developers. > Besides ServiceStage, it’s also used in the Huawei Core Network IOT > Platform and Huawei consumer cloud. The number of companies using > ServiceComb to develop their enterprise applications, they are > chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and > the number is over 5 and counting. > > == Rationale == > > ServiceComb has been developed as a total, open source solution for > developing cloud native applications. So far ServiceComb has existed as a > GitHub project with committers mostly working for Huawei. We feel that > moving it to a neutral organization like Apache, with its strong governance > model, is expected to help get more contributions from various > organizations and developers, who may be concerned by exclusive control of > ServiceComb by Huawei. > > == Initial Goals == > > Our initial goals are to bring ServiceComb into the ASF, transition > internal engineering processes into the open, and foster a collaborative &g
Re: [PROPOSAL] SkyWalking - proposal for Apache Incubation
Hi, I just updated the committer information and added affiliation section for it. Initial Committer - Sheng Wu, 吴晟, wushe...@huawei.com - Yongsheng Peng, 彭勇升, pen...@tydic.com - Xin Zhang, 张鑫, zhang...@oneapm.com - Hongtao Gao, 高洪涛, gaohong...@dangdang.com - Yang Bai, 柏杨, jixian...@cainiao.com - Kai Wang, 王凯, wangki...@dangdang.com - Yuntao Li, 李运涛, liyun...@huawei.com - Sheng Wang, 汪盛, marco.w...@huawei.com - Dongxue Si, 司冬雪, ilucky...@cloudwise.com - Kewei Zhang, 张科伟, zhang...@suixingpay.com Affiliations - Huawei: Sheng Wu, Yuntao Li, Sheng Wang - Tydic: Yongsheng Peng - OneAPM: Xin Zhang - dangdang.com: Hongtao Gao, Kai Wang - Alibaba Cainiao: Yang Bai - Cloudwise: Dongxue Si - suixingpay.com: Kewei Zhang Willem Jiang On Thu, Nov 30, 2017 at 10:30 AM, Luke Han wrote: > You should replace these with mail addresss, not GitHub accounts. > > Best Regards! > - > > Luke Han > > On Wed, Nov 29, 2017 at 2:16 PM, 吴晟 wrote: > > > @ in front, represents the GitHub account name of each contributor. That > > is an easy way for us to link and mention someone in github. > > > > > > >
Re: [VOTE] Accept SkyWalking into the Apache Incubator
My +1. Willem Jiang On Mon, Dec 4, 2017 at 9:26 PM, Hao Chen wrote: > +1 > > Hao Chen > > On Mon, Dec 4, 2017 at 9:12 PM, Romain Manni-Bucau > wrote: > > > +1 > > > > Romain Manni-Bucau > > @rmannibucau | Blog | Old Blog | Github | LinkedIn > > > > > > 2017-12-04 13:36 GMT+01:00 Ted Dunning : > > > +1 > > > > > > > > > > > > On Mon, Dec 4, 2017 at 3:17 AM, mck wrote: > > > > > >> > > >> After some discussion on the SkyWalking proposal, I'd like to raise > the > > >> vote on accepting SkyWalking into into the Apache Incubator. > > >> > > >> https://lists.apache.org/thread.html/b4e7205e77fe382b4cd096fb6da28b > > >> 70053e0722b3dd7ae8ac389f8a@%3Cgeneral.incubator.apache.org%3E > > >> > > >> > > >> A vote for accepting a new Apache Incubator podling is a majority vote > > >> for which only Incubator PMC member votes are binding. > > >> Votes from other people are also welcome as an indication of peoples > > >> enthusiasm (or lack thereof). > > >> > > >> Please do not use this VOTE thread for discussions. If needed, start a > > >> new thread instead. > > >> > > >> This vote will run for at least 72 hours. > > >> Please VOTE as follows: > > >>[] +1 Accept SkyWalking > > >>[] +0 Abstain > > >>[] -1 Do not accept Skywalking, because ... > > >> > > >> > > >> The proposal below is also on the wiki: > > >> https://wiki.apache.org/incubator/SkyWalkingProposal > > >> > > >> > > >> = Abstract = > > >> Skywalking is an APM (application performance monitor), especially for > > >> microservice, Cloud Native and container-based architecture systems. > > >> Also known as a distributed tracing system. It provides an automatic > way > > >> to instrument applications: no need to change any of the source code > of > > >> the target application; and an collector with an very high efficiency > > >> streaming module. > > >> > > >> = Proposal = > > >> The goal of this proposal is to bring the existing > > >> [[https://github.com/OpenSkywalking/skywalking|Skywalking]] codebase > > and > > >> existing developers and community into the Apache Software Foundation > > >> (ASF) in order to build a global, diverse and self-governed open > source > > >> community in APM field. > > >> > > >> This project started in Open Source on GitHub about more than 2 years > > >> ago. Beginning with a small SDK and collector. So far the > > >> [[https://github.com/OpenSkywalking/Organization|OpenSkywalking]] > > >> governs the project through the PMC and Committer Team. > > >> > > >> OpenSkywalking is submitting this proposal to donate the Skywalking > > >> sources code and associated artifacts (documentation, web site > content, > > >> wiki, etc.) to the Apache Software Foundation Incubator under the > Apache > > >> License, Version 2.0. These artifacts are currently available on > GitHub > > >> at https://github.com/OpenSkywalking and include: > > >> * Skywalking: The java sniffer(agent) for collecting data, and > > >> collector for analysing and persistence. > > >> * Skywalking-UI: The web UI for skywalking APM > > >> > > >> ''Voted on submitting the proposal to the Incubator. > > >> [[https://github.com/OpenSkywalking/Organization/issues/11|Check > > >> here]]'' > > >> > > >> = Background = > > >> Mircro-service, Cloud Native and container-based architecture system > are > > >> becoming more and more popular, so the traditional monitoring, like > > >> application loggings, can provide less information because of the > > >> distributed isolates the relations. Based on the > > >> [[https://research.google.com/pubs/pub36356.html|Google Dapper > paper]], > > >> many tracing systems born. The OpenSkywalking organisation was created > > >> with Skywalking made based on tracing, but not just tracing, it adds > > >> additional value by reducing the sniffer (agent) cost, analysis and > > >> visualization. > > >> > > >> In 2015, Skywalking project started, when service-oriented > architecture > > >&
Re: [PROPOSAL] ECharts - proposal for Apache Incubation
It's great to see that ECharts be a part of Apache incubating project. As Wu Shen and I are in Beijing, we could share you some experiences of incubating project setup things. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Mon, Jan 8, 2018 at 2:16 PM, Tan,Zhongyi wrote: > > Glad to hear that, > > I will add apache eagle to Echarts proposal document also. > > thanks > > 在 2018/1/8 下午12:31， "Hao Chen" 写入: > > >Great to hear that ECharts is coming to ASF! > > > >ECharts is a great chart library with good documentation and well > >community > >support. In Apache Eagle, we use ECharts a lot for monitoring dashboards > >and data visualization. > > > > > >Welcome and Good luck! > > > > > >Hao Chen > > > > > >On Mon, Jan 8, 2018 at 11:33 AM, Tan,Zhongyi > wrote: > > > >> Hi， wusheng & skywalking team， > >> > >> Glad to hear that your project is already using echarts. > >> If meet any problem or have any feature request, please let us know. > >> Thanks > >> > >> > >> I will update the proposal to add your project there. > >> > >> > >> > >> 在 2018/1/7 下午6:18， "吴晟 Sheng Wu" 写入: > >> > >> >Hi, ECharts community team. > >> > > >> > > >> >Glad your guys bringing the project to Apache. SkyWalking 's next > >>release > >> >will use some ECharts charts for our APM visualization. (already in > >> >developing branch) > >> > > >> > > >> >So if you like, you can put `Apache SkyWalking (Incubating)` in your > >> >"Relationships with Other Apache Products" section. > >> > > >> > > >> >This is a good and useful project. Welcome and gook luck. > >> > > >> > > >> >-- > >> >Sheng Wu > >> >Apache SkyWalking creator and PPMC member > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> >-- Original -- > >> >From: "Tan,Zhongyi";; > >> >Date: Fri, Jan 5, 2018 06:00 PM > >> >To: "general@incubator.apache.org"; > >> > > >> >Subject: [PROPOSAL] ECharts - proposal for Apache Incubation > >> > > >> > > >> > > >> >Hi, Dear Apache Incubator Community, > >> > > >> >Please accept the follow proposal for presentation and discussion: > >> > > >> >https://wiki.apache.org/incubator/EChartsProposal > >> > > >> >ECharts is a charting and data visualization library written in > >> >JavaScript . > >> >It has been an open source project on github since 2013， and is one of > >> >the > >> >most popular repositories in topic of data visualization category in > >> >github. > >> > > >> >Best regards. > >> > > >> > > >> > > >> > > >> >Below is the proposal also. > >> > > >> > > >> > > >> >= ECharts Proposal = > >> > > >> >=== Abstract === > >> > > >> >ECharts is a charting and data visualization library written in > >> >JavaScript. > >> > > >> > > >> >=== Proposal === > >> > > >> >ECharts provides a powerful, interactive charting and data > >>visualization > >> >library > >> >and framework for web browser, mobile App and backend usage. > >> > > >> > > >> >=== Background === > >> > > >> >A primary goal of data visualization is to communicate information > >> >clearly and > >> >efficiently via statistical graphics, plots and other graphics. > >> > > >> >Numerical data may be presented in dots, lines, or bars, to visually > >> >communicate > >> >a quantitative message. Effective visualization helps users to analyze > >> >data . > >> >It makes complex data more readable, understandable.[1] > >> > > >> >Now data visualization concerns mainly about presentation and > >>propagation > >> >in web, > >> >ECharts uses JavaScript as its basic programing language. It brings >
Re: [VOTE] Accept ECharts for Apache Incubation
+1 Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Jan 12, 2018 at 9:13 PM, Kevin A. McGrail wrote: > Hi All, > > I would like to start a VOTE & I vote +1 to bring the ECharts project in > as an Apache incubator podling. > > The ASF voting rules are described: > > https://www.apache.org/foundation/voting.html > > A vote for accepting a new Apache Incubator podling is a majority vote for > which only Incubator PMC member votes are binding. > > This vote will run for at least 72 hours. Please VOTE as follows > [ ] +1 Accept ECharts into the Apache Incubator > [ ] +0 Abstain. > [ ] -1 Do not accept ECharts into the Apache Incubator because ... > > The proposal is listed below, but you can also access it on the wiki: > https://wiki.apache.org/incubator/EChartsProposal > > Regards, > KAM > > > ECharts Proposal > > Abstract > > ECharts is a charting and data visualization library written in JavaScript. > > Proposal > > ECharts provides a powerful, interactive charting and data visualization > library and framework for web browser, mobile App and backend usage. > > Background > > A primary goal of data visualization is to communicate information clearly > and efficiently via statistical graphics, plots and other graphics. > > Numerical data may be presented in dots, lines, or bars, to visually > communicate a quantitative message. Effective visualization helps users to > analyze data .It makes complex data more readable, understandable.[1] > > Now data visualization concerns mainly about presentation and propagation > in web, ECharts uses JavaScript as its basic programing language. It brings > great compatibility across multiple platforms, not only in web browsers, > but also in mobile Apps via embedded web engine or in backend environment > via the techniques of headless browser. > > Rationale > > ECharts encapsulates the underlying data transformation, control flow, > visual encoding and rendering, receiving the visualization requirements > with declarative language, and produces interactive charts and components. > We will highlight the features below to illustrate the power that ECharts > already has, and our concerns and our visions: > > User Diversity: > > ECharts expects that its users are not only web developers, but also > people with lesser programing skills. So ECharts enables users to describe > data and settings with declarative language, which lowers the barrier but > without losing the power, and benefit to transfer and store. > > Configurable Interactions: > > ECharts has provided plenty of interactions and aims at providing more. > Both human interactions and the interactions with upper program are > supported and can be configurable. > > Large Data: > > Although the browser environment and JavaScript bring some performance > limits in visualizing large data or performing animations, ECharts have > been adopting various optimization techniques to rise the upper limit of > the amount of data that it can process, and keep improving the fluency of > interactions and animations. > > Cross-Platform: > > The underlying render engine of ECharts can be switched between > HTMLCanvas, SVG, or VML, which provides good compatibility and brings > opportunities to optimize performance according to different platform and > usage scenarios. Besides, ECharts can also works in backend environment via > headless techniques. > > ECharts can be created using headless browsers to pregenerate reports on > more powerful machines for better performance on resource-limited devices > > Extension and Customization: > > ECharts provides extension mechanisms to make new types of chart and > components, adopt other layout algorithms, or even adopt other render > techniques. Various developers have contributed different types of > extensions based on ECharts.[2] > > Current Status > > ECharts has been an open source project on GitHub[3] since 2013. Currently > it has more than 20k stars, more than 50k monthly downloads[4] in NPM, and > is one of the most popular repositories in topic of data visualization > category in GitHub.[5] And it has been used in many products of Baidu and > other companies such as Alibaba, Tencent, Netease, XinHua News > Agency,National Bureau of Statistics of China, Sina, State Grid Corporation > of China, Lenovo, Ctrip etc. > > Meritocracy > > The ECharts project already operates on meritocratic principles. It was > originally created by Lin Zhifeng in 2013,adding developers worldwide and > has accepted multiple major patches from a diverse s
Re: [VOTE] Retire Wave
+1 (binding) Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, Jan 9, 2018 at 2:56 AM, John D. Ament wrote: > All, > > This is a call to vote for the retirement of the Wave podling. > > The podling has positively voted to retire [1]. I now call upon the IPMC > to confirm this retirement. > > [ ] +1 to retire > [ ] +/- 0 to retire > [ ] -1 don't retire because... > > The podling is working on a migration plan, it seems they will move the > code to github somewhere, and will work on it as seen fit there. > > John > > [1]: > https://lists.apache.org/thread.html/fe4b7a240facbebeded29d7d9d8c73 > 3c0e5e624f07b7a110887c2f16@%3Cwave-dev.incubator.apache.org%3E >
Re: [VOTE] Accept Druid into the Apache Incubator
+1 (binding) Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 23, 2018 at 8:42 PM, Atul K. Gupta wrote: > +1 (non-binding) > > -Original Message- > From: Jyotirmoy Sundi [mailto:sundi...@gmail.com] > Sent: 23 February 2018 02:17 > To: general@incubator.apache.org > Subject: Re: [VOTE] Accept Druid into the Apache Incubator > > +1 Vote > > On 2018/02/22 19:03:55, Julian Hyde wrote: > > Hi all,> > > > > After some discussion on the Druid proposal[1], I'd like to> start a > > vote on accepting Druid into the Apache Incubator,> per the ASF > > policy[2] and voting rules[3].> > > > > A vote for accepting a new Apache Incubator podling is a> majority > > vote for which only Incubator PMC member votes are> binding. Votes > > from other people are also welcome as an> indication of people's > > enthusiasm (or lack thereof).> > > > > Please do not use this VOTE thread for discussions. If> needed, start > > a new thread instead.> > > > > This vote will run for at least 72 hours. Please VOTE as> follows:> [ > > ] +1 Accept Druid into the Apache Incubator> [ ] +0 Abstain> [ ] -1 > > Do not accept Druid into the Apache Incubator> > > because ...> > > > > The proposal is listed below, but you can also access it on> the > > wiki[4].> > > > > Julian> > > > > [1] > > https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c1b3 > > e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E> > > > > [2] > > https://incubator.apache.org/policy/incubation.html#approval_of_propos > > al_by_sponsor> > > > > [3] http://www.apache.org/foundation/voting.html> > > > > [4] https://wiki.apache.org/incubator/DruidProposal> > > > > > > > > > > > > = Druid Proposal => > > > > == Abstract ==> > > > > Druid is a high-performance, column-oriented, distributed> data > > store.> > > > > == Proposal ==> > > > > Druid is an open source data store designed for real-time> exploratory > > analytics on large data sets. Druid's key> features are a > > column-oriented storage layout, a distributed> shared-nothing > > architecture, and ability to generate and> leverage indexing and > > caching structures. Druid is typically> deployed in clusters of tens > > to hundreds of nodes, and has> the ability to load data from Apache > > Kafka and Apache> Hadoop, among other data sources. Druid offers two > > query> > > languages: a SQL dialect (powered by Apache Calcite) and a> > > JSON-over-HTTP API.> > > > > Druid was originally developed to power a slice-and-dice> analytical > > UI built on top of large event streams. The> original use case for > > Druid targeted ingest rates of> millions of records/sec, retention of > > over a year of data,> and query latencies of sub-second to a few > > seconds. Many> people can benefit from such capability, and many > > already> have (see http://druid.io/druid-powered.html). In addition,> > > new use cases have emerged since Druid's original> development, such > > as OLAP acceleration of data warehouse> tables and more highly > > concurrent applications operating> with relatively narrower queries.> > > > > == Background ==> > > > > Druid is a data store designed for fast analytics. It would> typically > > be used in lieu of more general purpose query> systems like Hadoop > > MapReduce or Spark when query latency is> of the utmost importance. > > Druid is often used as a data> store for powering GUI analytical > > applications.> > > > > The buzzwordy description of Druid is a high-performance,> > > column-oriented, distributed data store. What we mean by> this is:> > > > > * "high performance": Druid aims to provide low query> > > latency and high ingest rates possible.> > > * "column-oriented": Druid stores data in a column-oriented> > > format, like most other systems designed for analytics. It> > > can also store indexes along with the columns.> > > * "distributed": Druid is deployed in clusters, typically of> > > tens to hundreds of nodes.> > > * "data store": Druid loads your data and stores a copy of> > > it on the cluster's local disks (and may c
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1
+1 binding. Here are the checks those I did * Build from the src * Apache-rat check[1] * KEYS is good * the checksum and signed info is right * License and NOTICE * Commit is published * DISCLAIMER is in the src and binary kits. [1]https://github.com/apache/incubator-servicecomb-service- center/blob/1.0.0-m1/docs/release/Readme.md Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Feb 28, 2018 at 9:25 PM, Mohammad Asif Siddiqui < mohammad.asif.siddiq...@huawei.com> wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Service-Center > (Incubating) version 1.0.0-m1. > > Apache ServiceComb (Incubating) Community has voted and approved the > release. > > Vote Thread: https://lists.apache.org/thread.html/ > b2d87628d019c069f478c56cadaf794112add210c504e3ac4c3056e5@% > 3Cdev.servicecomb.apache.org%3E > > Result Thread: https://lists.apache.org/thread.html/ > 527a77d1467880602a7d679bd21d281b58fb365fa29b18a96a2a3676@% > 3Cdev.servicecomb.apache.org%3E > > Release Notes: https://github.com/apache/incubator-servicecomb-service- > center/blob/master/docs/release/releaseNotes.md > > Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-service-center/1.0.0-m1/ > > Release Tag: https://github.com/apache/incubator-servicecomb-service- > center/releases/tag/1.0.0-m1 > > Release CommitID: 8d40fc3b10e99c9084a7b62504226007660ad6de > > Keys to Verify the Release Candidate: https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > Guide to build the release from Source: https://github.com/apache/ > incubator-servicecomb-service-center/tree/master/scripts/release > > Voting will start now(Wednesday, February 28, 2018) and will remain open > for next 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0-m1. > [ ] +0 No Opinion. > [ ] -1 Do not release this package because... > > Regards > Asif > > >
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1
Hi Justin Thanks for the vote, here is some thing that I want to clear about the NOTICE file. I just checked some projects Notice file, it looks like some projects[1][2] list the License information about the third party dependencies in the Notice file, and some of them[3] just list bundled NOTICE files. I guess spark and hadoop are trying they best to list all the legal statements of third party dependencies in the NOTICE file to avoid the violation of the Open Source License. Could you give us some guide about how to keep the NOTICE file simple and without introducing any legal issues? As you may know the Service Center project is developed with Go language. Go language need to compile the source code to build whole exe binary. So we list all the third party dependencies code copyrights in the Notice file. I just found there are some guideline about the copyright notification here[4]. "However, elements such as the copyright notifications embedded within BSD and MIT licenses need <https://issues.apache.org/jira/browse/LEGAL-59> not <https://issues.apache.org/jira/browse/LEGAL-62> be duplicated in NOTICE -- it suffices to leave those notices in their original locations." As the lot of Go codes just put the License in the root directory, the source code doesn't have the License header, it could be a challenge for us to do the explicit statement without adding the copyright to NOTICE file. Finally We will add the src postfix to the source zip for user to find out it easily. [1]https://github.com/apache/spark/blob/master/NOTICE [2]https://github.com/apache/hadoop/blob/trunk/NOTICE.txt [3] https://github.com/apache/camel/blob/master/apache-camel/src/main/release/NOTICE.txt [4]http://www.apache.org/dev/licensing-howto.html#guiding-principle Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Mar 2, 2018 at 4:26 PM, Justin Mclean wrote: > Hi, > > -1 (binding) as there is incorrect and far too much information in NOTICE. > License information goes in LICENSE not NOTICE. [1] Also only things that > are actually bundled need to be mentioned not dependancies. [2] > > BTW it's not entirely clear which of the releases artefacts are source > release and what aren’t without carefully looking at them. > > I checked: > - signatures and hash correct > - disclaimer exists > - LICENSE is missing things > - NOTICE is not correct > - no unexpected binaries > - source code have ASF headers > > Thanks, > Justin > > 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps > 2. http://www.apache.org/dev/licensing-howto.html#guiding-principle > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1
Hi Justin, Thanks for pointing out the NOTICE file issue. I think we messed the usage of NOTICE and License file. It looks put the License files in the License directory could be a good way. The NOTICE file you just point is for the servicecomb-website (which is build by), not for the other servicecomb sub project. As we just publish the website in apache, I'm not sure if the website is kind of release. If we treat it as a source release, I guess we don't need to mention those dependencies js License and NOTICE, am I right? Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Mar 3, 2018 at 3:57 PM, Justin Mclean wrote: > Hi., > > For those not wanting to download the release and unpack it, here's the > current NOTICE file [1] > > You’ll note it contains permissive license information (which should be in > the license file), links to web sites rather than pointers to license text > (license information can change over time and again should be in license) > and mentions non bundled items (only bundled items need to be mentioned in > license and notice). > > Take for instance the license link to Font Awesome. It points to version 5 > which isn’t in any release, 4.7 is in a binary release but not the source > release. > > Thanks, > Justin > > 1. https://github.com/apache/incubator-servicecomb-website/ > blob/asf-site/NOTICE > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1
Hi Justin I just checked the code of servicecomb-website, we keep the js and fonts into the repo, so we should treat the repo as source release but the source has the bundled items (js, and fonts). I guess the License statements[1] should be fine, please let me know if I miss anything. For the NOTICE[2], I will the remove the dependencies statements, as they should not be there. [1] https://github.com/apache/incubator-servicecomb-website/blob/asf-site/LICENSE [2] https://github.com/apache/incubator-servicecomb-website/blob/asf-site/NOTICE Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Mar 3, 2018 at 4:36 PM, Willem Jiang wrote: > Hi Justin, > > Thanks for pointing out the NOTICE file issue. I think we messed the > usage of NOTICE and License file. It looks put the License files in the > License directory could be a good way. > > The NOTICE file you just point is for the servicecomb-website (which is > build by), not for the other servicecomb sub project. > As we just publish the website in apache, I'm not sure if the website is > kind of release. > If we treat it as a source release, I guess we don't need to mention those > dependencies js License and NOTICE, am I right? > > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Mar 3, 2018 at 3:57 PM, Justin Mclean > wrote: > >> Hi., >> >> For those not wanting to download the release and unpack it, here's the >> current NOTICE file [1] >> >> You’ll note it contains permissive license information (which should be >> in the license file), links to web sites rather than pointers to license >> text (license information can change over time and again should be in >> license) and mentions non bundled items (only bundled items need to be >> mentioned in license and notice). >> >> Take for instance the license link to Font Awesome. It points to version >> 5 which isn’t in any release, 4.7 is in a binary release but not the source >> release. >> >> Thanks, >> Justin >> >> 1. https://github.com/apache/incubator-servicecomb-website/blob >> /asf-site/NOTICE >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
Re: [VOTE] Release Apache Hivemall (Incubating) v0.5.0 Release Candidate 3
Hi， I found the License files (LICENSE-jafama.txt and LICENSE-smile) are both standate ASLV2, they are the same with LICENSE file. Do we still need to ship them separately? Can we just using the LICENSE file directly? Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Mar 3, 2018 at 11:40 AM, Justin Mclean wrote: > Hi, > > +1 (binding) > > I checked: > - incubating in name > - signatures and hashes correct > - disclaimer exists > - LICENSE and NOTICE good > - all source files have ASF headers > - no unexpected binary files > > I noticed a minor issue is that LICENSE is missing the MIT license for > this file [1] > > Thanks, > Justin > > 1. hivemall-0.5.0-incubating/src/site/resources/css/font-awesome.css > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1
FYI, you can find the LICENSE and NOTICE file of the ServiceComb Service Center here[1][2]. I just create a JIRA[3] to fix the LICENSE and NOTICE file issue in Service Center. We will provide different LICENSE and NOTICE for src and binary releases. [1]https://github.com/apache/incubator-servicecomb-service- center/blob/master/LICENSE [2]https://github.com/apache/incubator-servicecomb-service- center/blob/master/NOTICE [3]https://issues.apache.org/jira/browse/SCB-367 Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Mar 4, 2018 at 8:22 AM, Justin Mclean wrote: > Hi, > > > I just checked the code of servicecomb-website, we keep the js and fonts > > into the repo, so we should treat the repo as source release but the > source > > has the bundled items (js, and fonts). > > AFAICS these are not bundled in the source release (well not for the one > put up to vote on) and I could find them in the binary release(s) either. I > could be missing something but I can’t see them being bundled in the > releases. The LICENSE and NOTICE file needs to reflect what in the release > it goes with not what’s in the entire repo. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Hivemall (Incubating) v0.5.0 Release Candidate 3
Hi, I just checked smile and jafama projects they don't have the NOTICE file. Their License files are standard Apache license (ALv2), we can optimize it in next release. Here is my +1(binding) for the release kit. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Mar 4, 2018 at 11:37 AM, Justin Mclean wrote: > Hi, > > > We included exact copies of LICENSE file of depending projects. > > We can alternatively use LICENSE.ASLv2 Instead of using exact copies > > (if there are no diffs). > > Yes the standard Apache license (ALv2) has the same text so no need to > include it multiple time if that is the case. [1] Note however that a lot > of Apache project bundle 3rd party code so the full license text so they > may have additional text. Also if the ALv2 licensed bit of software has a > NOTICE file you need to include that in NOTICE. > > Thanks, > Justin > > 1. http://www.apache.org/dev/licensing-howto.html#alv2-dep > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1
Hi Justin， We did quick fix for the ServiceCenter LICENSE and NOTICE issue. You can find the LICENSE[1] and NOTICE[2] in the src release, LICENSE[3] and NOTICE[4] in the binary release. Please let us know if those files are OK. If everything is OK, We will start a new vote for the ServiceComb ServiceCenter. [1] https://github.com/apache/incubator-servicecomb-service-center/blob/master/LICENSE [2] https://github.com/apache/incubator-servicecomb-service-center/blob/master/NOTICE [3] https://github.com/apache/incubator-servicecomb-service-center/blob/master/scripts/release/LICENSE [4] https://github.com/apache/incubator-servicecomb-service-center/blob/master/scripts/release/NOTICE Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Mar 4, 2018 at 4:44 PM, Willem Jiang wrote: > > FYI, you can find the LICENSE and NOTICE file of the ServiceComb Service > Center here[1][2]. > > I just create a JIRA[3] to fix the LICENSE and NOTICE file issue in > Service Center. > We will provide different LICENSE and NOTICE for src and binary releases. > > > [1]https://github.com/apache/incubator-servicecomb-service-c > enter/blob/master/LICENSE > [2]https://github.com/apache/incubator-servicecomb-service-c > enter/blob/master/NOTICE > [3]https://issues.apache.org/jira/browse/SCB-367 > > > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > On Sun, Mar 4, 2018 at 8:22 AM, Justin Mclean > wrote: > >> Hi, >> >> > I just checked the code of servicecomb-website, we keep the js and fonts >> > into the repo, so we should treat the repo as source release but the >> source >> > has the bundled items (js, and fonts). >> >> AFAICS these are not bundled in the source release (well not for the one >> put up to vote on) and I could find them in the binary release(s) either. I >> could be missing something but I can’t see them being bundled in the >> releases. The LICENSE and NOTICE file needs to reflect what in the release >> it goes with not what’s in the entire repo. >> >> Thanks, >> Justin >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
Re: Need `mvn submodule` in `mvn release:perform` step
Hi Sheng， Using google with the key word "git submodule maven release", I got the below link[1]. Hope it can help you to solve the issue. [1] https://stackoverflow.com/questions/6938142/how-to-get-maven-release-to-clone-git-submodules Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Mar 11, 2018 at 9:20 AM, 吴晟 Sheng Wu wrote: > Hi incubator, > > > I am facing some issues when I do the SkyWalking first release. I am > following this document http://www.apache.org/dev/ > publishing-maven-artifacts.html#dev-env . But an error occurs in step > 4-STAGE THE RELEASE FOR A VOTE. > > > The reason of this is SkyWalking is using `git submodule` feature, so > after `git clone`, need to run `git submodule init` and `git submodule > update`, but in `mvn release:perform`, don't execute this in default. > > > I need some helps and guides about how to run these `submodule` commands. > Who can help us? Or where should I ask? > > > Thanks. > > > -- > Sheng Wu > Apache SkyWalking creator and PPMC member
Re: [VOTE] Accept Pinot into Apache Incubator
+1 (binding) Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Mar 11, 2018 at 7:51 PM, Pierre Smits wrote: > +1 > > > > Best regards, > > Pierre Smits > > V.P. Apache Trafodion > > On Sun, Mar 11, 2018 at 12:59 AM, Julian Hyde wrote: > > > +1 (binding) > > > > Ironic that Druid — a similar project — has just entered incubation too. > > But of course that is not a conflict. Both are great projects. Good luck! > > > > Julian > > > > > > > On Mar 9, 2018, at 7:37 PM, Carl Steinbach wrote: > > > > > > +1 (binding) > > > > > > On Fri, Mar 9, 2018, 7:29 PM kishore g wrote: > > > > > >> Added Jim Jagielski to the mentor's list. > > >> > > >> On Fri, Mar 9, 2018 at 6:35 PM, Olivier Lamy > wrote: > > >> > > >>> +1 > > >>> > > >>> On 9 March 2018 at 17:11, kishore g wrote: > > >>> > > >>>> Hi all, > > >>>> > > >>>> I would like to call a VOTE to accept Pinot into the Apache > Incubator. > > >>> The > > >>>> full proposal is available on the wiki > > >>>> <https://wiki.apache.org/incubator/PinotProposal> > > >>>> > > >>>> Please cast your vote: > > >>>> > > >>>> [ ] +1, bring Pinot into Incubator > > >>>> [ ] +0, I don't care either way, > > >>>> [ ] -1, do not bring Pinot into Incubator, because... > > >>>> > > >>>> The vote will open at least for 72 hours and only votes from the > > >>> Incubator > > >>>> PMC are binding. > > >>>> > > >>>> Thanks, > > >>>> Kishore G > > >>>> > > >>>> Discussion thread: > > >>>> https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b > > >>>> 22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org > > >>>> > > >>>> > > >>>> = Pinot Proposal = > > >>>> > > >>>> == Abstract == > > >>>> > > >>>> Pinot is a distributed columnar storage engine that can ingest data > in > > >>>> real-time and serve analytical queries at low latency. There are two > > >>> modes > > >>>> of data ingestion - batch and/or realtime. Batch mode allows users > to > > >>>> generate pinot segments externally using systems such as Hadoop. > These > > >>>> segments can be uploaded into Pinot via simple curl calls. Pinot can > > >>> ingest > > >>>> data in near real-time from streaming sources such as Kafka. Data > > >>> ingested > > >>>> into Pinot is stored in a columnar format. Pinot provides a SQL like > > >>>> interface (PQL) that supports filters, aggregations, and group by > > >>>> operations. It does not support joins by design, in order to > guarantee > > >>>> predictable latency. It leverages other Apache projects such as > > >>> Zookeeper, > > >>>> Kafka, and Helix, along with many libraries from the ASF. > > >>>> > > >>>> == Proposal == > > >>>> > > >>>> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of > > >> the > > >>>> development happens at LinkedIn with other contributions from Uber > and > > >>>> Slack. We believe that being a part of Apache Software Foundation > will > > >>>> improve the diversity and help form a strong community around the > > >>> project. > > >>>> > > >>>> LinkedIn submits this proposal to donate the code base to Apache > > >> Software > > >>>> Foundation. The code is already under Apache License 2.0. Code and > > the > > >>>> documentation are hosted on Github. > > >>>> * Code: http://github.com/linkedin/pinot > > >>>> * Documentation: https://github.com/linkedin/pinot/wiki > > >>>> > > >>>> > > >>>> == Background == > > >>>> > > >>>> LinkedIn, similar to other companies, has many applications that > > >> provide
NOTICE file update when bundling an apache 2.0 licensed dependency
Hi, I just have quick question about Update the top-level NOTICE file. When bunding the ASF Product, we need to put the copyright into the NOTICE file[1]. For the other ASF Licensed bundled dependency , we need to analyzed the NOTICE file[2]. But I checked modifications to NOTICE, it just says about the Copyright relocated issue[3]. I'm not sure if we still need to put bundled dependencies NOTICE information into the top-level NOTICE file. I found lots Apache project just put the Licenses information into the NOTICE file Is there an good example to show us how to update the top-level NOTICE file? [1]http://www.apache.org/dev/licensing-howto.html#bundle-asf-product [2]http://www.apache.org/dev/licensing-howto.html#alv2-dep [3]http://www.apache.org/dev/licensing-howto.html#mod-notice Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem
Re: Self Serve & IPMC Members
Yeah, it's really helpful that ASF member can create resources. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, Mar 13, 2018 at 2:36 AM, Chris Lambertus wrote: > > > On Mar 12, 2018, at 6:23 AM, Greg Stein wrote: > > On Mon, Mar 12, 2018 at 6:57 AM, Mark Thomas wrote: > >> On 09/03/18 21:47, Chris Lambertus wrote: >> > My understanding is that any pmc-chair can create resources for any >> project via selfserve.a.o. It does not have to be the pmc chair of that >> specific project, so there should be quite a few people who can create >> these resources at any given time. >> > >... > >> We trust ASF members. They have access to security@ and a bunch of other >> sensitive lists and they should be familiar enough with the foundation >> standards and procedures - or at least self-aware enough to know when >> they don't know. >> > > There's general agreement on that, I believe. ... But, ugh, it appears > that our LDAP schema doesn't easily support this right now :-( > > We'll look into how to make this happen. And open a Jira tracking issue > for it. > > > > > We’ve implemented a workaround for the LDAP issue. Selfserve now allows > Members as well as PMC chairs to create resources. > > -Chris > > > > > > Thanks, > -g > > >
Re: NOTICE file update when bundling an apache 2.0 licensed dependency
For those who may have the same question like me, here is the legal discussion[1] in the Apache which shows some example. [1]https://issues.apache.org/jira/browse/LEGAL-262 Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Mon, Mar 12, 2018 at 4:41 PM, Willem Jiang wrote: > Hi, > > I just have quick question about Update the top-level NOTICE file. > > When bunding the ASF Product, we need to put the copyright into the NOTICE > file[1]. > For the other ASF Licensed bundled dependency , we need to analyzed the > NOTICE file[2]. > But I checked modifications to NOTICE, it just says about the Copyright > relocated issue[3]. I'm not sure if we still need to put bundled > dependencies NOTICE information into the top-level NOTICE file. > > I found lots Apache project just put the Licenses information into the > NOTICE file > Is there an good example to show us how to update the top-level NOTICE > file? > > [1]http://www.apache.org/dev/licensing-howto.html#bundle-asf-product > [2]http://www.apache.org/dev/licensing-howto.html#alv2-dep > [3]http://www.apache.org/dev/licensing-howto.html#mod-notice > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem >
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1 - Second Attempt
Here is my +1 (binding) I did below checks: Checked the signed Keys and checksum. Checked the binary with the examples. Run the rat to verify the License header issue. DISCLAIMER exists Compiled from source Checked for archive matching git tag Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, Mar 20, 2018 at 12:24 PM, Mohammad Asif Siddiqui < asifdxtr...@apache.org> wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Service-Center > (Incubating) version 1.0.0-m1 > Apache ServiceComb (Incubating) Community has voted and approved the > release. > > Vote Thread : https://lists.apache.org/thread.html/ > a69ff6228a961ea920a6189845d6d54fa3764acd0ab5e99c59ac18f1@% > 3Cdev.servicecomb.apache.org%3E > > Result Thread : https://lists.apache.org/thread.html/ > 9b2b6bdb5984dd721016eb673dee2df3a7dd5cf9c7470c1de5c76a02@% > 3Cdev.servicecomb.apache.org%3E > > Release Notes : https://github.com/apache/incubator-servicecomb-service- > center/blob/master/docs/release/releaseNotes.md > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-service-center/1.0.0-m1/ > > Release Tag : https://github.com/apache/incubator-servicecomb-service- > center/releases/tag/1.0.0-m1 > > Release CommitID : 94cea25ba55e763dbe23d0cd4a8da73e37a50539 > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > Guide to build the release from source : https://github.com/apache/ > incubator-servicecomb-service-center/tree/master/scripts/release > > Voting will start now(Tuesday, March 20, 2018) and will remain open for > next 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0-m1. > [ ] +0 No Opinion. > [ ] -1 Do not release this package because... > > Regards > Asif > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.1.0
Hi +1 (binding) Here are the checks I did: Checked the signed Keys and checksum. Checked the binary with the examples. Run the rat to verify the License header issue. DISCLAIMER exists Verify the nexus Staging repo by running the demo example Compiled from source Checked for archive matching git tag Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, Mar 20, 2018 at 12:41 PM, Mohammad Asif Siddiqui < asifdxtr...@apache.org> wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Saga (Incubating) > version 0.1.0 > > Apache ServiceComb (Incubating) Community has voted and approved the > release. > > Vote Thread : https://lists.apache.org/thread.html/ > 46b2a639306ed5260f1aec5a3749eeb9112cc666069842e8aad1862d@% > 3Cdev.servicecomb.apache.org%3E > > Result Thread : https://lists.apache.org/thread.html/ > 1b60c2a2542b9a3358e16b8960c4f925fc7b3c25bc382771b97c5567@% > 3Cdev.servicecomb.apache.org%3E > > Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12321626&version=12342353 > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-saga/0.1.0/ > > Staging Repo : https://repository.apache.org/content/repositories/ > orgapacheservicecomb-1166 > > Release Tag : https://github.com/apache/incubator-servicecomb-saga/ > releases/tag/0.1.0 > > Release CommitID : 708eec092988dfd4a5960ca5f232fb7421d5fbdd > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > Voting will start now ( Tuesday, 20th March, 2018) and will remain open > for next 72 hours, We request all IPMC members to give their vote. > > [ ] +1 Release this package as 0.1.0 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > Regards > Asif > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1
Hi Justin, Thanks for pointing that out. I just filled a JIRA[1] for it and submit quick fix for it. [1]https://issues.apache.org/jira/browse/SCB-427 Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Mar 24, 2018 at 8:22 AM, Justin Mclean wrote: > Hi, > > Sorry but it’s -1 binding from me as the source release contains some > CC-BY licensed content in plain text. [1][2] CC-BY is considered Category B > [3] and can’t be included in a source release. These files also incorrectly > IMO have ASF headers. > > Everything else is good. I checked: > - name includes incubating > - DISCLAIMER exists > - LICENSE and NOTICE all good > - No unexpected binary files > - All source files have ASF headers > - Can compile form source > > Thanks, > Justin. > > 1. apache-servicecomb-incubating-java-chassis-distribution-1.0. > 0-m1-src/etc/eclipse-java-google-style.xml > 2. apache-servicecomb-incubating-java-chassis-distribution-1.0. > 0-m1-src/etc/intellij-java-google-style.xml > 3. https://www.apache.org/legal/resolved.html#category-b > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha (2nd round)
-1. Here are the checkings those I did: I can build the binary from the source kit. We need separate License and NOTICE file for binary and source release. I just checked RAT plugin setting on the parent POM. There are some exclusion of the configuration, protocol even the test data, we need to address these files License issue before doing the release. **/*.yml **/*.config **/*.graphqls **/*.proto **/src/test/resources/** **/*.def Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Mar 23, 2018 at 10:47 AM, 吴晟 Sheng Wu wrote: > Hi All, > This is a call for vote to release Apache SkyWalking (Incubating) version > 5.0.0-alpha > > > > The Apache SkyWalking community has tested, voted and approved the proposed > release of Apache SkyWalking (Incubating) 5.0.0-alpha > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > > Skywalking is an APM (application performance monitor), especially for > microservice, Cloud Native and container-based architecture systems. Also > known as a distributed tracing system. It provides an automatic way to > instrument applications: no need to change any of the source code of the > target application; and an collector with an very high efficiency streaming > module. > > > This is the first and alpha release of version 5. We write a Release > Guide[1] and vote check list[2] by following Apache release and > distribution documents. > > > > Vote Thread: > > > * https://lists.apache.org/thread.html/5abdab49ced0ab10059f99157fb983 > 002352205f0ba6469181ec053f@%3Cdev.skywalking.apache.org%3E > > > Result Thread: > > > * https://lists.apache.org/thread.html/6aaf3f5d2c0c1289796c9b658ac812 > cea2c4b6d619b78dbeb1566a4e@%3Cdev.skywalking.apache.org%3E > > > Release notes: > > > * https://github.com/apache/incubator-skywalking/blob/v5. > 0.0-alpha/CHANGES.md > > > Release Candidate: > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/ > 5.0.0-alpha/ > > > Maven 2 staging repository: > > > * https://repository.apache.org/content/repositories/ > orgapacheskywalking-1005/org/apache/skywalking/apache- > skywalking-apm-incubating/5.0.0-alpha/ > > > Release Tag : > > > * v5.0.0-alpha > > > Release CommitID : > > > * f52d99498f02402d2ce1a0b7b909cd7fcfb3526f > > > Keys to verify the Release Candidate : > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/ > 5.0.0-alpha/KEYS > * http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777 > > corresponding to pen...@apache.org > > > Guide to build the release from source : > > > * https://github.com/apache/incubator-skywalking/blob/v5. > 0.0-alpha/docs/en/How-to-release.md > > > Voting will start now (March 23th, 2018) and will remain open for at least > 72 hours, Request IPMC to give their vote. > [ ] +1 Release this package. > [ ] +0 No opinion. > [ ] -1 Do not release this package because > > > > > > [1] https://github.com/apache/incubator-skywalking/blob/ > master/docs/en/How-to-release.md > [2] https://github.com/apache/incubator-skywalking/blob/ > master/docs/en/How-to-release.md#vote-check > > > > > -- > Sheng Wu > Apache SkyWalking original creator and PPMC member
Re: [DISCUSS] Absent mentors
+1 for taking consideration of release vote. It's quite important process of the podling. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thu, Mar 29, 2018 at 8:03 AM, Roman Shaposhnik wrote: > On Wed, Mar 28, 2018 at 4:15 PM, Ted Dunning > wrote: > > I think the problem is serious. I also think that signoff rate is a > better > > metric in practice than it seems it would be. > > That problem is indeed pretty serious and also pretty chronic. > > As for the metric -- I really think that using mentor turnout on release > voting threads will serve us well. > > > Adding the additional metric seems like a small step that could help. > > > > Being aggressive about removing non-mentors is a very good idea. It is > best > > if mentors remove themselves, but it is imperative that the incubator > has a > > realistic idea about how many mentors there really are. > > Big +1 on the above. Perhaps if we: >1. get a clear indication on release vote turnout (as part of > Incubator report) >2. add to it the sign-off turnout > > We can start at least nagging unresponsive mentors to begin > with and if behaviour doesn't improve -- suggest that podlings > start looking for a replacement. > > Thanks, > Roman. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1 - Second Attempt
+1 (Binding) Checked the release tag, signed key. Build the binary from source. Verify the nexus release by running the company project[1] Checked the src kit by grepping the copyright license header, it looks good. [1]https://github.com/ServiceComb/ServiceComb-Company-WorkShop Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thu, Mar 29, 2018 at 10:28 PM, Mohammad Asif Siddiqui < asifdxtr...@apache.org> wrote: > Minor Correction: > > Voting will start now ( Thursday, 30th March, 2018) and will remain open > for next 72 hours, we request all IPMC members to give their vote. > > > On 2018/03/29 14:23:50, Mohammad Asif Siddiqui > wrote: > > Hi All, > > > > This is a call for vote to release Apache ServiceComb Java-Chassis > (Incubating) version 1.0.0-m1 > > > > Apache ServiceComb (Incubating) Community has voted and approved the > release. > > > > Vote Thread : https://lists.apache.org/thread.html/ > 3614f836e1905fc5d80e65217cf0fb294bd075451cfa311bb68f3342@% > 3Cdev.servicecomb.apache.org%3E > > > > Result Thread : https://lists.apache.org/thread.html/ > 965e7745295679e39c2ea466b445abd87173df9d1482a84491ca84c2@% > 3Cdev.servicecomb.apache.org%3E > > > > Release Notes : https://github.com/apache/incubator-servicecomb-java- > chassis/blob/master/etc/releaseNotes.md > > > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-java-chassis/1.0.0-m1/ > > > > Staging Repo : https://repository.apache.org/content/repositories/ > orgapacheservicecomb-1210 > > > > Release Tag : https://github.com/apache/incubator-servicecomb-java- > chassis/releases/tag/1.0.0-m1 > > > > Release CommitID : b60bf88c053e9ffa63b671a6639195be5179cf90 > > > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > > > Voting will start now ( Thursday, 30th March, 2018) and will remain open > for next 72 hours, Request all PPMC members to give their vote. > > > > [ ] +1 Release this package as 1.0.0-m1 > > [ ] +0 No Opinion > > [ ] -1 Do not release this package because > > > > On the behalf of ServiceComb Team > > Mohammad Asif Siddiqui > > > > - > > 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 ServiceComb Java-Chassis (incubating) version 1.0.0-m1 - Second Attempt
Hi Matt， I checked the vertx NOTICE.md[1] was added since 3.5.1[2], but we are using vertx 3.5.0[3]. BTW For the bundled Apache Licensed dependency, I checked the instruction[4], but it doesn't mention what should be put into the top-level NOTICE file. we will add a reference of it vertx NOTICE.md once we upgrade the vertx version. [1]https://github.com/eclipse/vert.x/blob/master/NOTICE.md [2] https://github.com/eclipse/vert.x/commit/cc05b9ddc558770a476a016578fbcfe97622de4b#diff-ce70fe65be0b8d1cbe0c667387c16c70 [3] https://github.com/apache/incubator-servicecomb-java-chassis/blob/ae28a9faff24e773520f3452dfd80b86dfbe7aa4/java-chassis-dependencies/pom.xml#L35 [4]http://www.apache.org/dev/licensing-howto.html#alv2-dep Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Mar 30, 2018 at 11:43 PM, Matt Sicker wrote: > * Rat check ok (checked exceptions as well) > * Build and tests ok > * Signatures ok > > Question regarding the NOTICE file: shouldn't the vertx classes that are > bundled be noted here? > > On 29 March 2018 at 22:59, Jean-Baptiste Onofré wrote: > > > +1 (binding) > > > > Checked: > > - build > > - signatures and headers > > - DISCLAIMER/LICENSE/NOTICE are present > > > > NB: NOTICE looks very light to me. I would double check if it's complete > > and > > clean for the next release. > > > > Regards > > JB > > > > On 03/29/2018 04:23 PM, Mohammad Asif Siddiqui wrote: > > > Hi All, > > > > > > This is a call for vote to release Apache ServiceComb Java-Chassis > > (Incubating) version 1.0.0-m1 > > > > > > Apache ServiceComb (Incubating) Community has voted and approved the > > release. > > > > > > Vote Thread : https://lists.apache.org/thread.html/ > > 3614f836e1905fc5d80e65217cf0fb294bd075451cfa311bb68f3342@% > > 3Cdev.servicecomb.apache.org%3E > > > > > > Result Thread : https://lists.apache.org/thread.html/ > > 965e7745295679e39c2ea466b445abd87173df9d1482a84491ca84c2@% > > 3Cdev.servicecomb.apache.org%3E > > > > > > Release Notes : https://github.com/apache/incubator-servicecomb-java- > > chassis/blob/master/etc/releaseNotes.md > > > > > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > > servicecomb/incubator-servicecomb-java-chassis/1.0.0-m1/ > > > > > > Staging Repo : https://repository.apache.org/content/repositories/ > > orgapacheservicecomb-1210 > > > > > > Release Tag : https://github.com/apache/incubator-servicecomb-java- > > chassis/releases/tag/1.0.0-m1 > > > > > > Release CommitID : b60bf88c053e9ffa63b671a6639195be5179cf90 > > > > > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > > dist/dev/incubator/servicecomb/KEYS > > > > > > Voting will start now ( Thursday, 30th March, 2018) and will remain > open > > for next 72 hours, Request all PPMC members to give their vote. > > > > > > [ ] +1 Release this package as 1.0.0-m1 > > > [ ] +0 No Opinion > > > [ ] -1 Do not release this package because > > > > > > On the behalf of ServiceComb Team > > > Mohammad Asif Siddiqui > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > -- > > Jean-Baptiste Onofré > > jbono...@apache.org > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > -- > Matt Sicker >
Re: [VOTE] Apache Gobblin 0.12.0 release RC2
Hi Olivier NOTICE file is not supposed to include the copyright unless the License requires. As the MIT License already has the copyright statement, we don't need to specify it in the NOTCE file. I just copy the Justin's comments from the lega issue discussion[1] , it can explain lots of thing. "While including all of NOTICE is the safest/simplest way. INAL but I also think removal of obvious things that have been documented that shouldn't be there is also safe. i.e. - Don't include ASF duplicate ASF copyright/this product developed at the ASF lines [1] - Remove anything that should be in LICENSE (that is already there) i.e. MIT and BSD license information [2] - Remove any copyright lines from MIT and BSD (but not ASL 2.0) permissive licenses, who headers are still in place in their respective files [3] - Only include parts if they are bundled in your release [4] Perhaps also politely ask / provide a patch to the upstream project to fix their NOTICE file? 1. http://www.apache.org/dev/licensing-howto.html#bundle-asf-product 2. http://www.apache.org/dev/licensing-howto.html#permissive-deps 3. http://www.apache.org/dev/licensing-howto.html#mod-notice 4. http://www.apache.org/dev/licensing-howto.html#guiding-principle"; [1]https://issues.apache.org/jira/browse/LEGAL-262 Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Apr 1, 2018 at 8:38 AM, Olivier Lamy wrote: > Hi > the content is simply. > " > > Apache Gobblin > > Copyright 2017-2018 The Apache Software Foundation > > > This product includes software developed at > > The Apache Software Foundation (http://www.apache.org/). > > > This product includes Bootstrap > > Copyright (c) 2011-2015 Twitter, Inc. > > > This product includes the Glyphicons Halflings icon set > > Copyright (c) Jan Kovařík (http://glyphicons.com) > > Licensed under The MIT License (MIT) as a part of the Bootstrap project. > > > This product includes normalize.css > > Copyright (c) Nicolas Gallagher and Jonathan Neal > " > Can you please explain what is the legal problem with such content? > TBH I can see so many similar content in a lot of TLP projects. So why we > should be more rude here than for other projects? > > > On Sun, 1 Apr 2018 at 09:08, Justin Mclean wrote: > > > Hi, > > > > -1 binding as NOTICE should not contain copyrights of bundled 3rd party > > software. The NOTICE file needs to only contain what is required (and > not > > already in LICENSE) and needs to be as small as possible as it affects > > downstream projects. [2] > > > > I checked: > > - incubating in name > > - signatures and hashes good > > - DISCLAIMER exists > > - LICENSE is missing info for fonts [1] > > - NOTICE is incorrect > > - Some .sh files are missing ASF headers > > - Can compile from source > > > > Thanks, > > Justin > > > > 1. > > apache-gobblin-incubating-sources-0.12.0/gobblin-admin/ > src/main/resources/static/fonts/* > > 2. http://www.apache.org/dev/licensing-howto.html#mod-notice > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy >
Re: [DISCUSS] Absent mentors
Yeah, it's easy to vote +1, but vote -1 take lots of time to go through the kits. To be honestly, I learned a lot of License and Notice stuff thing from Justin's -1 vote, I really appreciate that. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Apr 1, 2018 at 7:24 AM, Justin Mclean wrote: > Hi, > > > As for the metric -- I really think that using mentor turnout on release > > voting threads will serve us well. > > My concern with using that as a metric is people will just vote +1 without > doing a thorough check and we may end up with more releases with issues. > > Possibly a better metric is how many mentors voted something other than +1 > on a RC, most releases (other than very simple ones) go through a couple of > RCs before coming to the IPMC. > > Another metric is which project releases get a -1 in the IPMC as those > issue should of been caught by the projects mentors. > > Thanks, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha (3rd round)
Hi, I checked the source code and nexus repo release, they are good. I can build the binary from the source. But when I go through the License files I have some question want to ask 1. There are some CC Licensed file in the binary release License file. spdx-exceptions 2.1.0 spdx-license-ids 3.0.0 I did some research out about it and found it just work like a License check tool. So my question do we bundle it in the release kit? If we just use it as a tool to check license, we don't specify it in the License file. 2. There are lots stand ASL License which are list in the License directory. We could save people some time by reducing the number of stand ASL License file. It can be done on next release https://www.apache.org/legal/resolved.html#category-b Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sat, Mar 31, 2018 at 12:07 PM, 吴晟 Sheng Wu wrote: > Hi All, > This is a call for vote to release Apache SkyWalking (Incubating) version > 5.0.0-alpha. > > > The Apache SkyWalking community has tested, voted and approved the proposed > release of Apache SkyWalking (Incubating) 5.0.0-alpha > > > From last vote: > 1. Separated the NOTICE and LICENSE in source package and distribution > 2. Removed the libraries in source package. > 3. Removed some unnecessary excludes from rat setting. > 4. Added a missing DISCLAIMER file. > > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > > Skywalking is an APM (application performance monitor), especially for > microservice, Cloud Native and container-based architecture systems. > Also known as a distributed tracing system. > It provides an automatic way to instrument applications: > no need to change any of the source code of the target application; > and an collector with an very high efficiency streaming module. > > > Vote Thread: > > > * https://lists.apache.org/thread.html/4459517d990e2d0fa879ced5b65c44 > e047191e8b9301e8b6d67f7927@%3Cdev.skywalking.apache.org%3E > > > Result Thread: > > > * https://lists.apache.org/thread.html/c55adf4fa19d6c9ffa76a8d0cf2465 > 90d95d8dd7dead11331346e10b@%3Cdev.skywalking.apache.org%3E > > > Release notes: > > > * https://github.com/apache/incubator-skywalking/blob/v5. > 0.0-alpha/CHANGES.md > > > Release Candidate: > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/5.0.0-alpha/ > > > Maven 2 staging repository: > > > * https://repository.apache.org/content/repositories/ > orgapacheskywalking-1010/org/apache/skywalking/ > > > Release Tag : > > > * 5.0.0-alpha > > > Release CommitID : > > > * 476ae378bed24690628cc0d16108185b7b5580b6 > > > Keys to verify the Release Candidate : > > > * http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777 > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/ > 5.0.0-alpha/KEYS > > > corresponding to pen...@apache.org > > > Guide to build the release from source : > > > * https://github.com/apache/incubator-skywalking/blob/v5. > 0.0-alpha/docs/en/How-to-build.md#build-from-apache-source-codes > > > Voting will start now (March 31th) and will remain open for at least 72 > hours, Request IPMC to give their vote. > [ ] +1 Release this package. > [ ] +0 No opinion. > [ ] -1 Do not release this package because > > > > -- > Sheng Wu > Apache SkyWalking original creator and PPMC member
Re: Who has the experiences to assemble NOTICE file?
Hi Daisy, As the NOTICE file content is related to License. Current we need to go through the License and NOTICE file one by one. But with the help of maven remote resources plugin[1] that we use, it's easy for us to setup the License and update the NOTICE file by looking up the DEPENDENCE file that the plugin generated. BTW, there are some NOTICE related discussion in the general mailing list recently. Please do not hesitate to ask the specific NOTICE question here. [1] https://github.com/apache/incubator-servicecomb-saga/blob/master/pom.xml#L547 Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Mar 30, 2018 at 10:29 PM, Ying Chun Guo wrote: > Hi, friends > > I'd like to learn from people who has the experience to assemble the legal > NOTICE file before. I need to do this for Apache OpenWhisk repos. I find > manually assembling NOTICE is a complex and error-prone task especially for > a non-legal person like me. Is there a tool to help on that ? Does anyone > share any experiences on that? > > Best regards > Ying Chun Guo (Daisy) > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Who has the experiences to assemble NOTICE file?
Here are the link about the apache-resource-bundles[1] that you may use as well. [1]https://maven.apache.org/apache-resource-bundles/index.html Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Mon, Apr 2, 2018 at 11:13 AM, Willem Jiang wrote: > Hi Daisy, > > As the NOTICE file content is related to License. > Current we need to go through the License and NOTICE file one by one. > > But with the help of maven remote resources plugin[1] that we use, it's > easy for us to setup the License and update the NOTICE file by looking up > the DEPENDENCE file that the plugin generated. > > BTW, there are some NOTICE related discussion in the general mailing list > recently. > Please do not hesitate to ask the specific NOTICE question here. > > > [1]https://github.com/apache/incubator-servicecomb-saga/ > blob/master/pom.xml#L547 > > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Mar 30, 2018 at 10:29 PM, Ying Chun Guo > wrote: > >> Hi, friends >> >> I'd like to learn from people who has the experience to assemble the >> legal NOTICE file before. I need to do this for Apache OpenWhisk repos. I >> find manually assembling NOTICE is a complex and error-prone task >> especially for a non-legal person like me. Is there a tool to help on that >> ? Does anyone share any experiences on that? >> >> Best regards >> Ying Chun Guo (Daisy) >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-alpha(3rd round)
Shipping the CC licensed binary files in Apache binary kit is OK, if they are just for testing we don't need bundle them. Reducing the License file is not the blocking issue, we can fix it in next release. Please create issues to track these questions. It's hard for us to verify the bundled artifact from the compiled file. Now I have another question about the Skywalking UI. How can you find the third part dependencies were bundled? Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Mon, Apr 2, 2018 at 12:42 PM, Gao Hongtao <305653...@qq.com> wrote: > Hi, Willem > > > for question 1 > They are for testing only. Should be removed > > > for question 2 > We can reduce the same Apache license files. > > > We will fix these two in next release. Is that Ok? > Thanks for helps. > > > Hongtao Gao > > > > > > > > ---Original--- > From: "Willem Jiang" > Date: Mon, Apr 2, 2018 06:19 AM > To: "general"; > Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version > 5.0.0-alpha(3rd round) > > > Hi, > > I checked the source code and nexus repo release, they are good. > I can build the binary from the source. > > But when I go through the License files I have some question want to ask > > 1. There are some CC Licensed file in the binary release License file. > spdx-exceptions 2.1.0 > spdx-license-ids 3.0.0 > > I did some research out about it and found it just work like a License > check tool. > So my question do we bundle it in the release kit? If we just use it as a > tool to check license, we don't specify it in the License file. > > 2. There are lots stand ASL License which are list in the License > directory. > We could save people some time by reducing the number of stand ASL License > file. It can be done on next release > > https://www.apache.org/legal/resolved.html#category-b > > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Mar 31, 2018 at 12:07 PM, 吴晟 Sheng Wu > wrote: > > > Hi All, > > This is a call for vote to release Apache SkyWalking (Incubating) version > > 5.0.0-alpha. > > > > > > The Apache SkyWalking community has tested, voted and approved the > proposed > > release of Apache SkyWalking (Incubating) 5.0.0-alpha > > > > > > From last vote: > > 1. Separated the NOTICE and LICENSE in source package and distribution > > 2. Removed the libraries in source package. > > 3. Removed some unnecessary excludes from rat setting. > > 4. Added a missing DISCLAIMER file. > > > > > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > > > > Skywalking is an APM (application performance monitor), especially for > > microservice, Cloud Native and container-based architecture systems. > > Also known as a distributed tracing system. > > It provides an automatic way to instrument applications: > > no need to change any of the source code of the target application; > > and an collector with an very high efficiency streaming module. > > > > > > Vote Thread: > > > > > > * https://lists.apache.org/thread.html/4459517d990e2d0fa879ced5b65c44 > > e047191e8b9301e8b6d67f7927@%3Cdev.skywalking.apache.org%3E > > > > > > Result Thread: > > > > > > * https://lists.apache.org/thread.html/c55adf4fa19d6c9ffa76a8d0cf2465 > > 90d95d8dd7dead11331346e10b@%3Cdev.skywalking.apache.org%3E > > > > > > Release notes: > > > > > > * https://github.com/apache/incubator-skywalking/blob/v5. > > 0.0-alpha/CHANGES.md > > > > > > Release Candidate: > > > > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/ > 5.0.0-alpha/ > > > > > > Maven 2 staging repository: > > > > > > * https://repository.apache.org/content/repositories/ > > orgapacheskywalking-1010/org/apache/skywalking/ > > > > > > Release Tag : > > > > > > * 5.0.0-alpha > > > > > > Release CommitID : > > > > > > * 476ae378bed24690628cc0d16108185b7b5580b6 > > > > > > Keys to verify the Release Candidate : > > > > > > * http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777 > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/ > > 5.0.0-alpha/KEYS > > > > > > corresponding to pen...@apache.org > > > > > > Guide to build the release from source : > > > > > > * https://github.com/apache/incubator-skywalking/blob/v5. > > 0.0-alpha/docs/en/How-to-build.md#build-from-apache-source-codes > > > > > > Voting will start now (March 31th) and will remain open for at least 72 > > hours, Request IPMC to give their vote. > > [ ] +1 Release this package. > > [ ] +0 No opinion. > > [ ] -1 Do not release this package because > > > > > > > > -- > > Sheng Wu > > Apache SkyWalking original creator and PPMC member >
Re: Wiki confilict in April's Incubator report
We got the podling reportmail every month. So I'm confused. Do we need to write the report monthly or quarterly? Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Apr 4, 2018 at 3:27 PM, Huxing Zhang wrote: > Hi, > > Checkout this: http://incubator.apache.org/clutch/ > > Following is my understanding based on it. Please correct me if I am wrong. > > Some of the polling (especially new ones) are reported monthly, while > others are reported quarterly. > > Looking at the link, Myriad is group-3(Mar,Jun,Sep,Dec). > > On Wed, Apr 4, 2018 at 2:15 PM, Javi Roman > wrote: > > Hi, > > > > I'm a little bit confused regarding this month report. The Myriad > > project is not listed in the template for this month. Is this > > something that the project maintainers have to do, or is this > > something automatically done (the template) and we have an error this > > month? > > > > Best regards. > > -- > > Javi Roman > > > > Twitter: @javiromanrh > > GitHub: github.com/javiroman > > Linkedin: es.linkedin.com/in/javiroman > > Big Data Blog: dataintensive.info > > > > > > On Wed, Apr 4, 2018 at 5:43 AM, Huxing Zhang wrote: > >> Hi, > >> > >> It looks like there is some conflict in April's incubator report[1]. > >> > >> I have reverted it. > >> > >> It looks like the only affected podling is Annotator. > >> > >> Thinking about how can avoid it again, shall we have a preview of the > >> diff before saving the changes? > >> > >> [1] https://wiki.apache.org/incubator/April2018 > >> > >> -- > >> 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 > > > > > > -- > Best Regards！ > Huxing > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [ANNOUNCE] Release Apache SkyWalking (incubating) version 5.0.0-alpha
Hi Wu Sheng, You need to seed an announce mail of the Apache SkyWalking (incubating) to annou...@apache.org as an office release announcement. It should have the download links , release note, and the website link just as this [1]. BTW the announce is moderated, so you need to wait for a while to see the mail from the mailing list. [1] https://lists.apache.org/thread.html/89838c76715afe87d7a33499bec18e3ad86bc18657445fd98680b3e3@%3Cannounce.apache.org%3E Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Apr 4, 2018 at 4:59 PM, Sheng Wu wrote: > Hi Sebb. > > Yes, I will adjust the announce mail. And try to include it in our next > release. > > Thanks. > > Sheng Wu > > On 2018/04/04 08:52:37, sebb wrote: > > Also I just realised that the announce message does not have a link to > > the main website. > > > > On 4 April 2018 at 09:50, sebb wrote: > > > On 4 April 2018 at 02:32, 吴晟 Sheng Wu wrote: > > >> Hi all, > > >> > > >> > > >> Apache SkyWalking (incubating) Team is glad to announce the first > release of Apache SkyWalking Incubating 5.0.0-alpha > > >> > > >> > > >> SkyWalking: APM (application performance monitor) tool for > distributed systems, > > >> especially designed for microservices, cloud native and > container-based (Docker, Kubernetes, Mesos) architectures. > > >> Underlying technology is a distributed tracing system. > > >> > > >> > > >> Download Links : http://www.apache.org/dyn/closer.cgi/incubator/ > skywalking/5.0.0-alpha/ > > >> > > > > > > It's better to use the website download page: > > > > > > http://skywalking.apache.org/downloads/ > > > > > > This does not vary between releases, and contains links to other > > > useful information. > > > > > >> Release Notes : https://github.com/apache/ > incubator-skywalking/blob/v5.0.0-alpha/CHANGES.md > > >> > > >> > > >> SkyWalking Resources: > > >> - Issue: https://github.com/apache/incubator-skywalking/issues > > >> - Mailing list: d...@skywalkiing.incubator.apache.org > > >> - Documents: https://github.com/apache/incubator-skywalking/blob/v5. > 0.0-alpha/docs/README.md > > >> > > >> > > >> > > >> > > >> - Apache SkyWalking (incubating) Team > > >> > > >> > > >> = > > >> *Disclaimer* > > >> > > >> > > >> Apache SkyWalking (incubating) is an effort undergoing incubation at > The > > >> Apache Software Foundation (ASF), sponsored by the name of Apache > > >> Incubator PMC. Incubation is required of all newly accepted > > >> projects until a further review indicates that the > > >> infrastructure, communications, and decision making process have > > >> stabilized in a manner consistent with other successful ASF > > >> projects. While incubation status is not necessarily a reflection > > >> of the completeness or stability of the code, it does indicate > > >> that the project has yet to be fully endorsed by the ASF. > > >> > > >> > > >> > > >> > > >> > > >> -- > > >> Sheng Wu > > >> Apache SkyWalking original creator and PPMC member > > > > - > > 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: Wiki confilict in April's Incubator report
Hi John， Thanks for the reply. I can see the ServiceComb report schedule here[1] [1] https://whimsy.apache.org/roster/ppmc/servicecomb Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thu, Apr 5, 2018 at 6:10 PM, John D. Ament wrote: > Podlings report monthly for their first 3 months, then switch to > quarterly. I'm not sure which podling you're referring to below. Huxing > already linked to the clutch report which describes everyones reporting > period, likewise you can see the info on your whimsy roster page. > > John > > On Thu, Apr 5, 2018 at 3:06 AM Willem Jiang > wrote: > > > We got the podling reportmail every month. > > So I'm confused. Do we need to write the report monthly or quarterly? > > > > > > Willem Jiang > > > > Blog: http://willemjiang.blogspot.com (English) > > http://jnn.iteye.com (Chinese) > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, Apr 4, 2018 at 3:27 PM, Huxing Zhang wrote: > > > > > Hi, > > > > > > Checkout this: http://incubator.apache.org/clutch/ > > > > > > Following is my understanding based on it. Please correct me if I am > > wrong. > > > > > > Some of the polling (especially new ones) are reported monthly, while > > > others are reported quarterly. > > > > > > Looking at the link, Myriad is group-3(Mar,Jun,Sep,Dec). > > > > > > On Wed, Apr 4, 2018 at 2:15 PM, Javi Roman > > > wrote: > > > > Hi, > > > > > > > > I'm a little bit confused regarding this month report. The Myriad > > > > project is not listed in the template for this month. Is this > > > > something that the project maintainers have to do, or is this > > > > something automatically done (the template) and we have an error this > > > > month? > > > > > > > > Best regards. > > > > -- > > > > Javi Roman > > > > > > > > Twitter: @javiromanrh > > > > GitHub: github.com/javiroman > > > > Linkedin: es.linkedin.com/in/javiroman > > > > Big Data Blog: dataintensive.info > > > > > > > > > > > > On Wed, Apr 4, 2018 at 5:43 AM, Huxing Zhang > > wrote: > > > >> Hi, > > > >> > > > >> It looks like there is some conflict in April's incubator report[1]. > > > >> > > > >> I have reverted it. > > > >> > > > >> It looks like the only affected podling is Annotator. > > > >> > > > >> Thinking about how can avoid it again, shall we have a preview of > the > > > >> diff before saving the changes? > > > >> > > > >> [1] https://wiki.apache.org/incubator/April2018 > > > >> > > > >> -- > > > >> 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 > > > > > > > > > > > > > > > > -- > > > Best Regards！ > > > Huxing > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > >
Re: [VOTE] Release of Apache Griffin-0.2.0-incubating [RC3]
Hi Matt, I just have different idea about your your explanation. If my code has the compile dependency of the JSON library, as the JSON library code is not bundled in the source code. I don't think we should add the License of JSON library into my License file. If we use the LGPL license jar library in the test. As this LGPL jar is not bundled in our source or binary release. we don't need to update our License and Notice file for it. Please correct me if I'm wrong about it. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, Apr 13, 2018 at 1:09 PM, Matt Sicker wrote: > On 12 April 2018 at 22:43, Lionel Liu wrote: > > > > 2. Only things that are actually bundled in the release should be > mentioned > > in LICENSE. [3][4] > > > > To my understanding, as a source release, all the dependencies are > bundled > > when it is built. > > The dependencies are not bundled in the source code, so we don't need to > > announce any dependencies' licenses in source release? > > > > The idea here is that the LICENSE file only needs to include licenses for > anything that is included in that archive file. So for instance, if you > have source files that are all developed at Apache and have dependencies > that aren't included in the source zip, then you have the most simple > distribution possible here. If you have source files that are licensed > differently (e.g., copied code from an MIT licensed library), then things > start to get complicated. As it is, your source license and notice should > be relatively minimal right now since you're not bundling external > dependencies in said source distribution. > > As for the JSON licensing issue, just take a look at the license. It says > it can't be used for evil. While amusing, that's a terrible restriction to > place on end users because it's extremely vague and violates the tenants of > free software. > > -- > Matt Sicker >
Re: [VOTE] Graduate Traffic Control to a top level project
+1 （binding） Willem Jiang On Sat, Apr 21, 2018 at 2:02 AM, Dave Neuman wrote: > Hello IPMC, > The Traffic Control PMC would like to call a vote to graduate from the > incubator to a top level Apache project! The traffic control community has > voted to graduate [1], voted on our resolution [2], and opened a thread to > discuss our resolution on this list [3]. > > Traffic Control entered the incubator on July 12, 2016. Since then we have > announced 4 releases, nominated 4 new committers, organized 4 summits, had > more than 8,000 commits from 63 different contributors, and -- most > importantly -- we have grown and diversified our community. Apache Traffic > Control is a healthy project that is already acting like an Apache top > level project, and we are ready to take the next step. > > I would like to ask that you please take a moment to vote on our > resolution. Please respond with one of the following: > > [ ] +1 Graduate Traffic Control from the incubator > [ ] +0 No Opinion > [ ] -1 Do not graduate Traffic Control from the incubator (please provide a > reason) > > The vote is open for a minimum of 72 hours and will need at least 3 more +1 > votes than -1 votes from IPMC members to succeed. > > Please do not hesitate to let us know if you have any questions. > > Thanks, > Dave > > [1] > https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa207 > 23eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E > [2] > https://lists.apache.org/thread.html/53c51f3eab45525c4e6c1bc5207265 > 9c751fd9c59001006791e4b0e3@%3Cdev.trafficcontrol.apache.org%3E > [3] > https://lists.apache.org/thread.html/837b7bfd090d84632fe1f314484c32 > f18cddf5030b21289879753403@%3Cgeneral.incubator.apache.org%3E > > > > --- > > Establish the Apache Traffic Control 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 building, monitoring, configuring, and provisioning a large > scale content delivery network (CDN).. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Traffic Control Project", be and > hereby is established pursuant to Bylaws of the Foundation; and be it > further > > RESOLVED, that the Apache Traffic Control Project be and hereby is > responsible for the creation and maintenance of software related to > building, monitoring, configuring, and provisioning a large scale > content delivery network (CDN).; and be it further > > RESOLVED, that the office of "Vice President, Apache Traffic Control" 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 Traffic > Control Project, and to have primary responsibility for management of > the projects within the scope of responsibility of the Apache Traffic > Control 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 Traffic Control > Project: > > * Dan Kirkwood > * David Neuman > * Dewayne Richardson > * Eric Covener > * Eric Friedrich > * Hank Beatty > * Jan van Doorn > * Jeff Elsloo > * Jeremy Mitchell > * Leif Hedstrom > * Mark Torluemke > * Phil Sorber > * Steve Malenfant > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed > to the office of Vice President, Apache Traffic Control, 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 initial Apache Traffic Control PMC be and hereby is > tasked with the creation of a set of bylaws intended to encourage open > development and increased participation in the Apache Traffic Control > Project; and be it further > > RESOLVED, that the Apache Traffic Control Project be and hereby is > tasked with the migration and rationalization of the Apache Incubator > Traffic Control podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > Traffic Control podling encumbered upon the Apache Incubator PMC are > hereafter discharged. >
Re: Is an incubating project allowed to release if it didn'tfollowApache way.
Hi Adam, Thanks for the explanation. Can we add some description about it on the board report? I just went through all the prior board reports[1] I didn't found anything about it. [1]https://whimsy.apache.org/board/minutes/Weex Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Apr 25, 2018 at 10:40 AM, Adam Feng wrote: > Hi, > > I'm Adam, who is a committer of Weex，maybe I can clarify the confusion > of Weex's release process. > > Actually, Weex released its first version in Apache on 2017-06-08, after > that, we faced some license problems. Facebook's BSD+Patents license was > added to Category X[1] and Weex had some dependencies which were using that > license, including our layout engine Yoga[2] (though its newest version > has changed to MIT). > > Some committers found the issue[3] and started working on a new layout > engine, it was a massive work and took more time than we expected, > fortunately it was nearly done. Weex will release next version in May. > > During that time, the community building and development should be > continued, so we added some tags and some "feature notes" to the > community, we will make sure they are clearly labeled as non-Apache > releases. > > Sorry to make you confused. > > [1] https://www.apache.org/legal/resolved.html#category-x > [2] https://github.com/facebook/yoga/tree/master > [3] https://issues.apache.org/jira/projects/WEEX/issues/ > WEEX-69?filter=allopenissues > > > Thanks. > Adam Feng > > On 24 Apr 2018, 7:37 PM +0800, 吴晟 Sheng Wu , wrote: > > Hi, Bertrand > > > > > > Point taken, Thanks for help. > > > > > > Sheng Wu > > > > > > > > ---Original--- > > From: "Bertrand Delacretaz" > Date: Tue, Apr 24, 2018 19:26 PM > > To: "Incubator General"; > > Subject: Re: Is an incubating project allowed to release if it > didn'tfollowApache way. > > > > > > On Tue, Apr 24, 2018 at 12:11 PM, 吴晟 Sheng Wu > wrote: > > > ...SkyWalking didnot face this situation... > > > > Ah yes got it now, sorry - so what I meant is that the podlings who > > are doing such releases should clarify that with their mentors. > > > > I understand (now ;-) SkyWalking is not in this situation. If a > > podling doesn't have specific, documented reasons to do non-Apache > > releases they should not do that. > > > > -Bertrand > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)
Is there any plan for going through the vote process of Binary file? Normally there are lots of work on the License files of Binary durning the first release. Maybe we should need to vote the binary file as well. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, May 9, 2018 at 4:34 PM, Huxing Zhang wrote: > On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz > wrote: > > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang wrote: > >> ...The maven artifact is the most significant for most of the Dubbo > >> users, so we want to include a maven artifact in the release > > > > Binaries are NOT part of Apache Releases, as mentioned earlier in this > thread. > > Yes, we fully understood that. > > Here what I mean "release" does not mean an Apache release, it is > actually a "hybrid" release, which includes: > > * source (following Apache release policy) > * binary (it is optional but still following Apache release policy) > * Maven artifacts under third-party coordinates (Non Apache release) > > > > > Dubbo mentors, I think we need a clear description of how these > > "hybrid" releases are done, to avoid any misunderstandings. > > > > Justin mentioned in this thread that that's been discussed on your dev > > list, so you probably just need to summarize that and include the URL > > in your next Incubator report. > > > > -Bertrand > > -- > Best Regards！ > Huxing > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: scala/play community?
As there are bunch of big data projects which use Scala @asf, I guess here are some of Scala developer could be interested to expose the big data service in an easy way. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, May 16, 2018 at 11:27 PM, Matt Sicker wrote: > I've been involved in Scala and Akka projects before, but not Play, though. > > On 16 May 2018 at 07:43, Jean-Baptiste Onofré wrote: > > > Hi Romain, > > > > AFAIK, we don't have any project for now related to scala@play. > > > > Even if it sounds very interesting, I'm not sure a servlet/jaxrs bridge > > would be enough for a incubator project (especially in term of > community). > > > > Let's see feedback from the others. > > > > Regards > > JB > > > > > > On 16/05/2018 14:40, Romain Manni-Bucau wrote: > > > >> Hi guys, > >> > >> I wonder if we have some scala@play community or not @asf. > >> > >> I will likely try to bring a servlet/jaxrs bridge soon and wonder if > >> proposing it @asf can be interesting (otherwise I just put it on > github). > >> > >> Any inputs welcomed. > >> > >> Romain Manni-Bucau > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog > >> <https://rmannibucau.metawerx.net/> | Old Blog > >> <http://rmannibucau.wordpress.com> | Github < > >> https://github.com/rmannibucau> | > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > >> <https://www.packtpub.com/application-development/java-ee-8- > >> high-performance> > >> > >> > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > -- > Matt Sicker >
Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3
Hi, As there is only one zip file, I guess it just the src distribution. But after went through the file, I found lot of echart js files in the dist directory and the rat jar. So I'm confused what's the purpose of apache-echarts-4.1.0.rc3- incubating.zip Normally we distribute the src and binary files separately. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thu, May 17, 2018 at 7:42 PM, SHUANG SU wrote: > I am pleased to be calling this vote for the release of Apache ECharts > 4.1.0.rc3. > > Apache ECharts community has voted and approved the release. > > Vote thread: > https://lists.apache.org/thread.html/67dffef28ecffd66689ac991ca027c > 0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E > > Results thread: > https://lists.apache.org/thread.html/3a6e627a7e07d5de0856296d44bb40 > 8e17ee6795cc74ef190a7a5d23@%3Cdev.echarts.apache.org%3E > > The release candidate to be voted over is available at: > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc3/ > > The release candidate is signed with a GPG key available at: > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS > > A tagged git repository is available for review at: > https://github.com/apache/incubator-echarts/releases/tag/4.1.0.rc3 > > The Git commit for this release is: > https://gitbox.apache.org/repos/asf?p=incubator-echarts. > git;a=commit;h=f98eb21 > > The Release Note is available in: > https://dist.apache.org/repos/dist/dev/incubator/echarts/4. > 1.0.rc3/RELEASE_NOTE.txt > > Some shell commands for validating the release: > > ```shell > # Download the release: > curl > https://dist.apache.org/repos/dist/dev/incubator/echarts/4. > 1.0.rc3/apache-echarts-4.1.0.rc3-incubating.zip > -o apache-echarts-4.1.0.rc3-incubating.zip > unzip apache-echarts-4.1.0.rc3-incubating.zip -d > apache-echarts-4.1.0.rc3-incubating > /dev/null > > # Rebuild the project: > cd "apache-echarts-4.1.0.rc3-incubating" && npm install && cd .. > node "apache-echarts-4.1.0.rc3-incubating/build/build.js" --release > # (See help: `node "apache-echarts-4.1.0.rc3-incubating/build/build.js" > --help`) > > # Run Apache Rat: > java -jar "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" | > less > # (See help: `java -jar > "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" --help`) > ``` > > > Please vote on releasing this package as: > Apache ECharts 4.1.0.rc3 > > This vote will be open until "2018-05-20T12:33:24.955Z". > > [ ] +1 Release this package > [ ] 0 I don't feel strongly about it, but don't object > [ ] -1 Do not release this package because... > > Anyone can participate in testing and voting, not just committers, please > feel free to try out the release candidate and provide your votes. > > > -- > Su Shuang (100pah) > -- >
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4
Hi, As there are some License issues in the binary distribution (please check the section4 for more information), I had to vote -1 (binding). Here are the verifications which I did 1. check the checksums and verify the KEY. These KEY are not signed by the others, so I got the warning WARNING: This key is not certified with a trusted signature! 2. Checked the License and Notice file of the source distribution. It looks good. 3. Built the source with instruction of README and start the server It works and I can start the standalone server. I also checked the distribution file in the all directory, I can get the binary and source distribution there. 4. Checked the License and Notice file of the binary distribution. There is not version of bundled jars specified in the License file. It could cause some trouble as the License could be changed in different versions of jar distribution. Most of the bundled jars are specified in the License file, but some of them are missed. * com.google.errorprone-error_prone_annotations-2.0.19.jar * com.google.instrumentation-instrumentation-api-0.4.3.jar * com.squareup.okhttp-okhttp-2.5.0.jar * com.squareup.okio-okio-1.6.0.jar * org.apache.distributedlog-distributedlog-core-shaded-4.7.0.jar The javassist jar is not CDDL license, it has multiple licenses ASL,LGPL,MPL (we need to pick one of them). * org.javassist-javassist-3.21.0-GA.jar Willem Jiang On Fri, May 18, 2018 at 11:35 AM, Matteo Merli wrote: > This is the fourth release candidate for Apache Pulsar, version > 2.0.0-rc1-incubating. > > Pulsar is a highly scalable, low latency messaging platform running on > commodity hardware. > It provides simple pub-sub semantics over topics, guaranteed at-least-once > delivery of > messages, automatic cursor management for subscribers, and geo-replication. > > Link to the voting thread on pulsar dev list: > https://lists.apache.org/thread.html/865ac7e993265a31512642c5f29e53 > e65f4199b931a5ae91d07fba77@%3Cdev.pulsar.apache.org%3E > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milestone/12?closed=1 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > Source and binary files: > https://dist.apache.org/repos/dist/dev/incubator/pulsar/ > pulsar-2.0.0-rc1-incubating-candidate-4/ > > SHA-1 checksums: > a959a33500508d0ba690ca177eb39cf83dddf022 > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1014/ > > The tag to be voted upon: > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f > 5eb4118de7) > https://github.com/apache/incubator-pulsar/releases/tag/ > v2.0.0-rc1-incubating-candidate-4 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the the source package, and follow the README to build > and run the Pulsar standalone service. > -- > Matteo Merli > >
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4
Hi Matteo, The PR looks good. I really like the script that does the check. Please make sure you run it as a routine to verify the release kit. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Mon, May 21, 2018 at 8:32 AM, Matteo Merli wrote: > Willem, thanks for catching these issues. > > I have fixed the missing dependencies, specified the exact version of each > of them > and added a script to validate that new changes won't break it later. > https://github.com/apache/incubator-pulsar/pull/1820 > > I will cancel this vote and create a new candidate. > > Matteo > > On Sat, May 19, 2018 at 11:12 PM Willem Jiang > wrote: > > > Hi, > > > > As there are some License issues in the binary distribution (please check > > the section4 for more information), I had to vote -1 (binding). > > > > Here are the verifications which I did > > 1. check the checksums and verify the KEY. > > These KEY are not signed by the others, so I got the warning WARNING: > > This key is not certified with a trusted signature! > > > > 2. Checked the License and Notice file of the source distribution. > > It looks good. > > > > 3. Built the source with instruction of README and start the server > > It works and I can start the standalone server. > > I also checked the distribution file in the all directory, I can get > the > > binary and source distribution there. > > > > 4. Checked the License and Notice file of the binary distribution. > > There is not version of bundled jars specified in the License file. It > > could cause some trouble as the License could be changed in different > > versions of jar distribution. > > > > Most of the bundled jars are specified in the License file, but some of > > them are missed. > > > > * com.google.errorprone-error_prone_annotations-2.0.19.jar > > > > * com.google.instrumentation-instrumentation-api-0.4.3.jar > > > > * com.squareup.okhttp-okhttp-2.5.0.jar > > > > * com.squareup.okio-okio-1.6.0.jar > > > > * org.apache.distributedlog-distributedlog-core-shaded-4.7.0.jar > > > > The javassist jar is not CDDL license, it has multiple licenses > > ASL,LGPL,MPL (we need to pick one of them). > > > > * org.javassist-javassist-3.21.0-GA.jar > > > > > > Willem Jiang > > > > > > On Fri, May 18, 2018 at 11:35 AM, Matteo Merli > wrote: > > > > > This is the fourth release candidate for Apache Pulsar, version > > > 2.0.0-rc1-incubating. > > > > > > Pulsar is a highly scalable, low latency messaging platform running on > > > commodity hardware. > > > It provides simple pub-sub semantics over topics, guaranteed > > at-least-once > > > delivery of > > > messages, automatic cursor management for subscribers, and > > geo-replication. > > > > > > Link to the voting thread on pulsar dev list: > > > https://lists.apache.org/thread.html/865ac7e993265a31512642c5f29e53 > > > e65f4199b931a5ae91d07fba77@%3Cdev.pulsar.apache.org%3E > > > > > > It fixes the following issues: > > > https://github.com/apache/incubator-pulsar/milestone/12?closed=1 > > > > > > *** Please download, test and vote on this release. This vote will stay > > > open > > > for at least 72 hours *** > > > > > > Note that we are voting upon the source (tag), binaries are provided > for > > > convenience. > > > > > > Source and binary files: > > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/ > > > pulsar-2.0.0-rc1-incubating-candidate-4/ > > > > > > SHA-1 checksums: > > > a959a33500508d0ba690ca177eb39cf83dddf022 > > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > > > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b > > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/ > orgapachepulsar-1014/ > > > > > > The tag to be voted upon: > > > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f > > > 5eb4118de7) > > > https://github.com/apache/incubator-pulsar/releases/tag/ > > > v2.0.0-rc1-incubating-candidate-4 > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > > > Please download the the source package, and follow the README to build > > > and run the Pulsar standalone service. > > > -- > > > Matteo Merli > > > > > > > > > -- > Matteo Merli > >
Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC1]
Hi, I did some check on the source zip and binary zip, the License and Notice files looks good. But I also found some issues here. As I cannot build the binary without doing some changes on the pom file, I had to vote -1 (binding) here. Here are the issues that I found: 1. there is bunch of dubbo-2.6.2-SNAPSHOT in the pom.xml file, I guess the maven release plugin doesn't take all of them. .//bom/pom.xml: dubbo-2.6.2-SNAPSHOT .//dependencies-bom/pom.xml: dubbo-2.6.2-SNAPSHOT .//distribution/pom.xml:2.6.2-SNAPSHOT-SNAPSHOT .//pom.xml: dubbo-2.6.2-SNAPSHOT 2. I checked the source zip[1], it is not same with github tag one[2]. There are some log files and empty directories which is not in the git repo, I guess it relates to the builder's workspace. It could be addressed by generate the source release kit in the distribution like we did here[3]. BTW, it's quite important that every one can build the kit by following the instruction. I didn't found the instruction file from the README. 3. I tried to build the source from kit, it looks the check style is enabled when since JDK 1.8 and I just got the out of memory error there. I found there are comment about this check style issue (it takes lots of time and it doesn't work on my box). So I created an issue[4] of it. I can build the source by modify the pom to skip the check style check, but it kind of hiking , so I had to vote -1 (binding) for it. 4. I checked the binary kit, it only includes the jars file of dubbo[5], as we cannot provide the apache maven release now, it could cause some trouble for the user to consume the binary without third party dependencies. Do we have any plan for it ? Another tip for the release check is running some applications which is build on the top of the framework to make sure all the distribution is good. [1] https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip [2]https://github.com/apache/incubator-dubbo/archive/dubbo-2.6.2.zip [3] https://github.com/apache/incubator-servicecomb-saga/blob/master/saga-distribution/src/assembly/src.xml [4]https://github.com/apache/incubator-dubbo/issues/1821 [5] https://github.com/apache/incubator-dubbo/blob/2.6.2-release/distribution/src/assembly/release-bin.xml#L43 Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Fri, May 18, 2018 at 5:26 PM, Jun Liu wrote: > Hello All, > > This is a call for vote to release Apache Dubbo (Incubating) version 2.6.2. > > The Apache Dubbo community has voted on and approved a proposal to release > Apache Dubbo (Incubating) version 2.6.2. > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Apache Dubbo™ (incubating) is a high-performance, java based, open source > RPC framework. Dubbo offers three key functionalities, which include > interface based remote call, fault tolerance & load balancing, and > automatic service registration & discovery. > > Dubbo vote thread: > https://lists.apache.org/thread.html/2292dfa6698c97550419ca547c8cd9 > 71bae8c88c440ef277314c841f@%3Cdev.dubbo.apache.org%3E > > Dubbo vote result thread: > https://lists.apache.org/thread.html/701b3d436920eea3030f2a977eb1d3 > 826774bc96e0b1d8b1d09a2ce8@%3Cdev.dubbo.apache.org%3E > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2 > > Git tag for the release: > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2 > > Hash for the release tag: > afab04c53edab38d52275d2a198ea1aff7a4f41e > > Release Notes: > https://github.com/apache/incubator-dubbo/blob/2.6.2-release/CHANGES.md > > The artifacts have been signed with Key : 28681CB1, which can be found in > the keys file: > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks. > Jun Liu, > The Apache Dubbo (Incubating) Team > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Retire the Slider podling
+1 (binding) Willem Jiang On Tue, May 22, 2018 at 4:28 AM, Vinod Kumar Vavilapalli wrote: > +1 (binding). > > With YARN services in Apache Hadoop 3.1 release, there is a good path > forward. > > Thanks > +Vind > > > On May 20, 2018, at 10:59 AM, Billie Rinaldi wrote: > > > > After a long period of low activity, the Slider PPMC has recently decided > > upon retirement [1]. Please vote on whether we should retire the Slider > > podling. Here is my +1 (binding). > > > > [ ] +1 Retire Slider > > [ ] +0 No opinion > > [ ] -1 Do not retire Slider because ... > > > > This vote will remain open for 72 hours. > > > > [1]: https://s.apache.org/V8SB > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta
Hi, +1 for this release. I checked the signing key, and verify the check sum. Built the binary kit from source. There are bunch of Apache Licenses in the binary kit which are stand Apache Licenses. We can do some clean up these License file in the next release. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, May 20, 2018 at 5:08 PM, 吴晟 Sheng Wu wrote: > Hi, IPMC > I am asking the release vote, again. :) Haven't had one yet. Hope we can > have enough vote in 72 hours. > > > Thanks. > > > > Sheng Wu > Apache SkyWalking > > From Wu Sheng 's phone. > > ---Original--- > From: ".彭勇升"<8082...@qq.com> > Date: Fri, May 18, 2018 10:06 AM > To: "general"; > Subject: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta > > > Hi All, > This is a call for vote to release Apache SkyWalking (Incubating) version > 5.0.0-beta. > > > The Apache SkyWalking community has tested, voted and approved the proposed > release of Apache SkyWalking (Incubating) 5.0.0-beta > > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > > SkyWalking: APM (application performance monitor) tool for distributed > systems, > especially designed for microservices, cloud native and container-based > (Docker, Kubernetes, Mesos) architectures. > Underlying technology is a distributed tracing system. > > > > Vote Thread: > https://lists.apache.org/thread.html/77df7fc536a95d2e3c4121a > 3f2faf61371c31a22f1678a9d45134904@%3Cdev.skywalking.apache.org%3E > > > Result Thread: > https://lists.apache.org/thread.html/ba0939023e7e856b79093be > 1f0b9e4e15520e5f5f67344260cb5c3ff@%3Cdev.skywalking.apache.org%3E > > > Release notes: > * https://github.com/apache/incubator-skywalking/blob/master/ > CHANGES.md#500-beta > Release Candidate: > > > *https://dist.apache.org/repos/dist/dev/incubator/skywalking/5.0.0-beta/ > > > Maven 2 staging repository: > *https://repository.apache.org/content/repositories/orgapach > eskywalking-1011/org/apache/skywalking/ > > > Release Tag : > * v5.0.0-beta > > > Release CommitID : > * 5ddc4e714f2570421779a11f2589ffc32d2b8b21 > > > Keys to verify the Release Candidate : > * http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2EF5026E70A55777 > corresponding to pen...@apache.org > > > Guide to build the release from source : > * https://github.com/apache/incubator-skywalking/blob/master/ > docs/en/How-to-build.md > > > Voting will start now (May 18th, 2018) and will remain open for at least > 72 hours, Request all IPMC members to give their vote. > [ ] +1 Release this package. > [ ] +0 No opinion. > [ ] -1 Do not release this package because…. > > > — > Yongsheng Peng > Apache SkyWalking PPMC member >
Re: [VOTE] Apache Crail 1.0-incubating (RC3)
Hi, I just tried to build from the source kit and got the test error due to missing crail-site.conf. I checked the README and cannot find any note for solving this problem. testRenameFile(org.apache.crail.ClientTest): null/conf/crail-site.conf (No such file or directory) testRenameFile(org.apache.crail.ClientTest) testlookupDirectory(org.apache.crail.ClientTest): null/conf/crail-site.conf (No such file or directory) Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, May 22, 2018 at 3:28 PM, Jonas Pfefferle wrote: > Please vote to approve the source release of Apache Crail 1.0-incubating > (RC3). > This release candidate fixes all issues raised in the last IPMC vote: > - Add DISCLAIMER > - Move IBM copyright from NOTICE file to CREDITS file and fix formatting > of Apache copyright > - Leading directory name in tar/zip file is now > "apache-crail-1.0-incubating-src" > > The podling dev vote thread: > > https://www.mail-archive.com/dev@crail.apache.org/msg00268.html > > The result: > > https://www.mail-archive.com/dev@crail.apache.org/msg00274.html > > Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d > > https://git1-us-west.apache.org/repos/asf?p=incubator-crail. > git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d > > Release files can be found at: > https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/ > > The vote is open for at least 72 hours and passes if a majority of at least > 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Crail 1.0-incubating > [ ] -1 Do not release this package because ... > > Thanks, > Jonas > > > > > > > > - > 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: [IP CLEARANCE] Dubbox documentation
Hi John I'm little confused. For the new incubating projects, it's make sense that the initial code should go through the SGA, and CLA thing. But if the code donation happens few month after the initial code transfer, do we still need to treat the project as a new projects? I found there are some IP Clearance report in CXF(incubating) before it became the TLP. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, May 24, 2018 at 7:59 AM, John D. Ament wrote: > Huxing, > > Please note per the top paragraph of [1] the IP Clearance process is not > for new projects (incubating projects). > > John > > [1]: http://incubator.apache.org/ip-clearance/ > > > On Wed, May 23, 2018 at 5:03 AM Huxing Zhang wrote: > > > The Apache Dubbo (incubating) is receiving a documentation donation > > for the rest support and more protocol support features[1](previously > > known as Dubbox) from Dangdang. > > > > The acceptance vote has passed on the d...@dubbo.apache.org mailing list > > [2] > > > > Please vote to approve this contribution. > > > > This is a lazy consensus majority vote, per the IP clearance process > > [3], open for at least 72 hours. > > > > [1] http://incubator.apache.org/ip-clearance/dubbo-dubbox.html > > [2] > > https://lists.apache.org/thread.html/6aa42da38e6bb32ea4d38444aa5982 > 6b6cc0c7ce6d0c5923e1df3a35@%3Cdev.dubbo.apache.org%3E > > [3] http://incubator.apache.org/ip-clearance/ > > > > -- > > Best Regards！ > > Huxing > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Apache Crail 1.0-incubating (RC3)
I can build the kit after skipping the test and there is a build instruction in the README. I'm sorry I didn't find it at first check. Now I have some trouble to find the signing key from the distribution directory. We normally provide it in the KEY directory. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, May 23, 2018 at 3:23 PM, Jonas Pfefferle wrote: > Hi, > > At the moment there is no way to run the tests without setting up a > configuration for your system (Crail needs hugepage mountpoint, network > interfaces etc). > For that reason we instruct people in the README to build with > "-DskipTests". > > If you want to deploy/configure Crail to run the tests you need to setup > the CRAIL_HOME environment variable and adapt the Crail configuration with > your network settings etc. Check the README for more detailed instructions. > > Thanks, > Jonas > > On Wed, 23 May 2018 10:33:09 +0800 > > Willem Jiang wrote: > >> Hi, >> >> I just tried to build from the source kit and got the test error due to >> missing crail-site.conf. >> I checked the README and cannot find any note for solving this problem. >> >> testRenameFile(org.apache.crail.ClientTest): null/conf/crail-site.conf >> (No >> such file or directory) >> testRenameFile(org.apache.crail.ClientTest) >> testlookupDirectory(org.apache.crail.ClientTest): >> null/conf/crail-site.conf (No such file or directory) >> >> >> Willem Jiang >> >> Blog: http://willemjiang.blogspot.com (English) >> http://jnn.iteye.com (Chinese) >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Tue, May 22, 2018 at 3:28 PM, Jonas Pfefferle >> wrote: >> >> Please vote to approve the source release of Apache Crail 1.0-incubating >>> (RC3). >>> This release candidate fixes all issues raised in the last IPMC vote: >>> - Add DISCLAIMER >>> - Move IBM copyright from NOTICE file to CREDITS file and fix formatting >>> of Apache copyright >>> - Leading directory name in tar/zip file is now >>> "apache-crail-1.0-incubating-src" >>> >>> The podling dev vote thread: >>> >>> https://www.mail-archive.com/dev@crail.apache.org/msg00268.html >>> >>> The result: >>> >>> https://www.mail-archive.com/dev@crail.apache.org/msg00274.html >>> >>> Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d >>> >>> https://git1-us-west.apache.org/repos/asf?p=incubator-crail. >>> git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d >>> >>> Release files can be found at: >>> https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/ >>> >>> The vote is open for at least 72 hours and passes if a majority of at >>> least >>> 3 +1 PMC votes are cast. >>> >>> [ ] +1 Release this package as Apache Crail 1.0-incubating >>> [ ] -1 Do not release this package because ... >>> >>> Thanks, >>> Jonas >>> >>> >>> - >>> 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] Apache Crail 1.0-incubating (RC3)
I found the KEY file from the PPMC voting mail[1]. According to note of from apache key home[2], the Key for release should not be the link. - The KEYS files must be stored in the ASF mirror directories. This ensures that they are archived along with the releases to which they apply. - The KEYS file are needed to check signatures of archived releases. Thus keys should only ever be added to the KEYS file, and never normally removed. Now the LDAP group for a project will change over time, and a committer who signed one or more releases may no longer be in the group. Also if a project moves to the Attic, its LDAP group will be removed. [1]https://www.mail-archive.com/dev@crail.apache.org/msg00268.html [2]https://people.apache.org/keys/ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, May 25, 2018 at 9:09 AM, Willem Jiang wrote: > I can build the kit after skipping the test and there is a build > instruction in the README. I'm sorry I didn't find it at first check. > Now I have some trouble to find the signing key from the distribution > directory. We normally provide it in the KEY directory. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, May 23, 2018 at 3:23 PM, Jonas Pfefferle wrote: > >> Hi, >> >> At the moment there is no way to run the tests without setting up a >> configuration for your system (Crail needs hugepage mountpoint, network >> interfaces etc). >> For that reason we instruct people in the README to build with >> "-DskipTests". >> >> If you want to deploy/configure Crail to run the tests you need to setup >> the CRAIL_HOME environment variable and adapt the Crail configuration with >> your network settings etc. Check the README for more detailed instructions. >> >> Thanks, >> Jonas >> >> On Wed, 23 May 2018 10:33:09 +0800 >> >> Willem Jiang wrote: >> >>> Hi, >>> >>> I just tried to build from the source kit and got the test error due to >>> missing crail-site.conf. >>> I checked the README and cannot find any note for solving this problem. >>> >>> testRenameFile(org.apache.crail.ClientTest): null/conf/crail-site.conf >>> (No >>> such file or directory) >>> testRenameFile(org.apache.crail.ClientTest) >>> testlookupDirectory(org.apache.crail.ClientTest): >>> null/conf/crail-site.conf (No such file or directory) >>> >>> >>> Willem Jiang >>> >>> Blog: http://willemjiang.blogspot.com (English) >>> http://jnn.iteye.com (Chinese) >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>> >>> On Tue, May 22, 2018 at 3:28 PM, Jonas Pfefferle >>> wrote: >>> >>> Please vote to approve the source release of Apache Crail 1.0-incubating >>>> (RC3). >>>> This release candidate fixes all issues raised in the last IPMC vote: >>>> - Add DISCLAIMER >>>> - Move IBM copyright from NOTICE file to CREDITS file and fix formatting >>>> of Apache copyright >>>> - Leading directory name in tar/zip file is now >>>> "apache-crail-1.0-incubating-src" >>>> >>>> The podling dev vote thread: >>>> >>>> https://www.mail-archive.com/dev@crail.apache.org/msg00268.html >>>> >>>> The result: >>>> >>>> https://www.mail-archive.com/dev@crail.apache.org/msg00274.html >>>> >>>> Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d >>>> >>>> https://git1-us-west.apache.org/repos/asf?p=incubator-crail. >>>> git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d >>>> >>>> Release files can be found at: >>>> https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/ >>>> >>>> The vote is open for at least 72 hours and passes if a majority of at >>>> least >>>> 3 +1 PMC votes are cast. >>>> >>>> [ ] +1 Release this package as Apache Crail 1.0-incubating >>>> [ ] -1 Do not release this package because ... >>>> >>>> Thanks, >>>> Jonas >>>> >>>> >>>> - >>>> 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] Pulsar Release 2.0.0-rc1-incubating Candidate 5
my +1. I checked: The sign and check sum for both src and binary distributions. The License and Notice file for src and binary distributions. I can build the binary from source. Here are some minor issues I found, it's not blocker issues please verify them and we can fix it in the next release. 1. It's a little big size for the binary , so I checked the files. It looks like there are java-instance.jar which holds all the jars in the lib directory. I think we need to find a way to avoid shipping the jars twice. 2. There are three different version of Netty in the library, io.netty-netty-3.10.1.Final.jar io.netty-netty-all-4.1.21.Final.jar io.netty-netty-codec-http2-4.1.12.Final.jar as netty 3.x and netty4.x use different package name, we may need to go through all the netty 4.x dependencies. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, May 24, 2018 at 1:21 PM, Matteo Merli wrote: > This is the fifth release candidate for Apache Pulsar, version > 2.0.0-rc1-incubating. > > Pulsar is a highly scalable, low latency messaging platform running on > commodity hardware. > It provides simple pub-sub semantics over topics, guaranteed at-least-once > delivery of > messages, automatic cursor management for subscribers, and geo-replication. > > The only difference from previous candidate is a fix on the LICENSE > attached to bin distribution to correctly reflect all dependencies and > versions. > > Link to the voting thread on pulsar dev list: > https://lists.apache.org/thread.html/81359fe55cb75cd1621a70e9a5a0af > 02fb1a84549ab0046d335182fa@%3Cdev.pulsar.apache.org%3E > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milestone/12?closed=1 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > Source and binary files: > https://dist.apache.org/repos/dist/dev/incubator/pulsar/ > pulsar-2.0.0-rc1-incubating-candidate-5/ > > SHA-1 checksums: > 72ee624c9b1485cc4c12b71e3807c7c05ec900ad > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > c525457db8f9c4ea859c595c93e9207631cda19f > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1017/ > > The tag to be voted upon: > v2.0.0-rc1-incubating-candidate-5 (08708a198606fb934e46f6cb0b614f > 2babf613e4) > https://github.com/apache/incubator-pulsar/releases/tag/ > v2.0.0-rc1-incubating-candidate-5 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the the source package, and follow the README to build > and run the Pulsar standalone service. > > > -- > Matteo Merli > >
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 5
My suggestion is using BOM the manage the third party dependencies which could save you some time to build a uber jar. It's not a blocker issue for the release, but it's a common practice to resolve the version conflicts of third party dependencies. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, May 26, 2018 at 8:22 AM, Sijie Guo wrote: > Thank you Willem. Comments inline > > On Fri, May 25, 2018 at 4:03 PM, Willem Jiang > wrote: > > > my +1. > > > > I checked: > > > > The sign and check sum for both src and binary distributions. > > The License and Notice file for src and binary distributions. > > I can build the binary from source. > > > > Here are some minor issues I found, it's not blocker issues please verify > > them and we can fix it in the next release. > > > > 1. It's a little big size for the binary , so I checked the files. > > It looks like there are java-instance.jar which holds all the jars in the > > lib directory. I think we need to find a way to avoid shipping the jars > > twice. > > > > java-instance.jar is a uber jar including all the dependencies for running > pulsar functions in process mode. > > it is needed for this release, because there are conflicts between > different protobuf/netty versions. so we have to do proper shading to > handle that. > > we are addressing that in master, the situation can be improved in 2.1 > release. > > > > > > 2. There are three different version of Netty in the library, > > io.netty-netty-3.10.1.Final.jar > > io.netty-netty-all-4.1.21.Final.jar > > io.netty-netty-codec-http2-4.1.12.Final.jar > > > > as netty 3.x and netty4.x use different package name, we may need to go > > through all the netty 4.x dependencies. > > > > yeah. pulsar is using 4.1.21, however 3.10.1 and 4.1.12 are coming from its > transitive dependencies. hope that clarifies. > > > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, May 24, 2018 at 1:21 PM, Matteo Merli wrote: > > > > > This is the fifth release candidate for Apache Pulsar, version > > > 2.0.0-rc1-incubating. > > > > > > Pulsar is a highly scalable, low latency messaging platform running on > > > commodity hardware. > > > It provides simple pub-sub semantics over topics, guaranteed > > at-least-once > > > delivery of > > > messages, automatic cursor management for subscribers, and > > geo-replication. > > > > > > The only difference from previous candidate is a fix on the LICENSE > > > attached to bin distribution to correctly reflect all dependencies and > > > versions. > > > > > > Link to the voting thread on pulsar dev list: > > > https://lists.apache.org/thread.html/81359fe55cb75cd1621a70e9a5a0af > > > 02fb1a84549ab0046d335182fa@%3Cdev.pulsar.apache.org%3E > > > > > > It fixes the following issues: > > > https://github.com/apache/incubator-pulsar/milestone/12?closed=1 > > > > > > *** Please download, test and vote on this release. This vote will stay > > > open > > > for at least 72 hours *** > > > > > > Note that we are voting upon the source (tag), binaries are provided > for > > > convenience. > > > > > > Source and binary files: > > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/ > > > pulsar-2.0.0-rc1-incubating-candidate-5/ > > > > > > SHA-1 checksums: > > > 72ee624c9b1485cc4c12b71e3807c7c05ec900ad > > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > > > c525457db8f9c4ea859c595c93e9207631cda19f > > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/ > orgapachepulsar-1017/ > > > > > > The tag to be voted upon: > > > v2.0.0-rc1-incubating-candidate-5 (08708a198606fb934e46f6cb0b614f > > > 2babf613e4) > > > https://github.com/apache/incubator-pulsar/releases/tag/ > > > v2.0.0-rc1-incubating-candidate-5 > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > > > Please download the the source package, and follow the README to build > > > and run the Pulsar standalone service. > > > > > > > > > -- > > > Matteo Merli > > > > > > > > >
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 5
Hi Matteo, I think I can help with that, Please fill an issue to track this question. I can post some reference as a comment to the issue that you can take a look. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, May 27, 2018 at 1:30 PM, Matteo Merli wrote: > Hi Willem, I'm personally not familiar with BOM in Maven but we'll surely > take > a look. We just want to ensure that, out of the box, users won't have to > experience weird runtime errors, due when incompatible versions of some > library > required by different components. > > We'll look into this and few other options to achieve that without > including twice > some of the dependencies in different forms. > > Thank, > Matteo > > On Sat, May 26, 2018 at 7:21 PM Willem Jiang > wrote: > > > My suggestion is using BOM the manage the third party dependencies which > > could save you some time to build a uber jar. > > It's not a blocker issue for the release, but it's a common practice to > > resolve the version conflicts of third party dependencies. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Sat, May 26, 2018 at 8:22 AM, Sijie Guo wrote: > > > > > Thank you Willem. Comments inline > > > > > > On Fri, May 25, 2018 at 4:03 PM, Willem Jiang > > > wrote: > > > > > > > my +1. > > > > > > > > I checked: > > > > > > > > The sign and check sum for both src and binary distributions. > > > > The License and Notice file for src and binary distributions. > > > > I can build the binary from source. > > > > > > > > Here are some minor issues I found, it's not blocker issues please > > verify > > > > them and we can fix it in the next release. > > > > > > > > 1. It's a little big size for the binary , so I checked the files. > > > > It looks like there are java-instance.jar which holds all the jars in > > the > > > > lib directory. I think we need to find a way to avoid shipping the > jars > > > > twice. > > > > > > > > > > java-instance.jar is a uber jar including all the dependencies for > > running > > > pulsar functions in process mode. > > > > > > it is needed for this release, because there are conflicts between > > > different protobuf/netty versions. so we have to do proper shading to > > > handle that. > > > > > > we are addressing that in master, the situation can be improved in 2.1 > > > release. > > > > > > > > > > > > > > 2. There are three different version of Netty in the library, > > > > io.netty-netty-3.10.1.Final.jar > > > > io.netty-netty-all-4.1.21.Final.jar > > > > io.netty-netty-codec-http2-4.1.12.Final.jar > > > > > > > > as netty 3.x and netty4.x use different package name, we may need to > go > > > > through all the netty 4.x dependencies. > > > > > > > > > > yeah. pulsar is using 4.1.21, however 3.10.1 and 4.1.12 are coming from > > its > > > transitive dependencies. hope that clarifies. > > > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Thu, May 24, 2018 at 1:21 PM, Matteo Merli > > wrote: > > > > > > > > > This is the fifth release candidate for Apache Pulsar, version > > > > > 2.0.0-rc1-incubating. > > > > > > > > > > Pulsar is a highly scalable, low latency messaging platform running > > on > > > > > commodity hardware. > > > > > It provides simple pub-sub semantics over topics, guaranteed > > > > at-least-once > > > > > delivery of > > > > > messages, automatic cursor management for subscribers, and > > > > geo-replication. > > > > > > > > > > The only difference from previous candidate is a fix on the LICENSE > > > > > attached to bin distribution to correctly reflect all dependencies > > and > > > > > versions. > > > > > > > > > > Link to the voting thread on pulsar dev list: > > > > > https://lists.apache.org/thread.html/ > 81359fe55cb75cd1621a70e9a5a0af > > > > > 02fb1a84549ab0046d335182fa@%3Cdev.pulsar.apache.
Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc4
Hi I just tried to build the source according to the instruction in the mail, it works. But when I check the source file with github repo[1]. I found there are some directories are missed. I guess we can skip the benchmark, tests, but I'm not sure for the theme directory. Can you explain it? We need to make sure we can build the full function binary from the source release. BTW, it looks there lots of github links in the README.md[2] need to be updated. And echarts need to move the website to echarts.incubator.apache.org from baidu. [1] https://github.com/apache/incubator-echarts [2]https://github.com/apache/incubator-echarts/blob/master/README.md Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, May 29, 2018 at 5:09 PM, SHUANG SU wrote: > After removing some generated files and bin files from 4.1.0.rc3, only > source code kept in the artifact. > I am pleased to be calling this vote for the release of Apache ECharts > 4.1.0.rc4. > > > Apache ECharts community has voted and approved the release. > > Vote thread: > https://lists.apache.org/thread.html/8ebfdd7219cbfed40cd2350e487b99 > be58ec169fb7c5673e21e10dea@%3Cdev.echarts.apache.org%3E > > Results thread: > https://lists.apache.org/thread.html/238ae37a82e2a71698f41a4d878e32 > 5601b88c665f9951d3bf912db4@%3Cdev.echarts.apache.org%3E > > The release candidate to be voted over is available at: > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc4/ > > The release candidate is signed with a GPG key available at: > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS > > The Git commit for this release is: > https://gitbox.apache.org/repos/asf?p=incubator-echarts. > git;a=commit;h=02842e2 > > The Release Note is available in: > https://dist.apache.org/repos/dist/dev/incubator/echarts/4. > 1.0.rc4/RELEASE_NOTE.txt > > Some shell commands for validating the release: > > ```shell > # Download the release: > curl > https://dist.apache.org/repos/dist/dev/incubator/echarts/4. > 1.0.rc4/apache-echarts-4.1.0.rc4-incubating-src.zip > -o apache-echarts-4.1.0.rc4-incubating-src.zip > unzip apache-echarts-4.1.0.rc4-incubating-src.zip -d > apache-echarts-4.1.0.rc4-incubating-src > /dev/null > > # Rebuild the project (Node.js environment is required): > cd "apache-echarts-4.1.0.rc4-incubating-src" && npm install && cd .. > node "apache-echarts-4.1.0.rc4-incubating-src/build/build.js" --release > # (See help: `node "apache-echarts-4.1.0.rc4- > incubating-src/build/build.js" > --help`) > ``` > > > Please vote on releasing this package as: > Apache ECharts 4.1.0.rc4 > > This vote will be open until "2018-06-01T10:02:35.437Z". > > [ ] +1 Release this package > [ ] 0 I don't feel strongly about it, but don't object > [ ] -1 Do not release this package because... > > Anyone can participate in testing and voting, not just committers, please > feel free to try out the release candidate and provide your votes. > > -- > Su Shuang (100pah) > -- >
Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc4
Thanks for the explanation. But if the user want to change the theme he still need to download the theme file himself, even he download the src distribution. Am I right? I think we need to provide more convenience distribution in next release. Here is my +1 vote. BTW, if you want to keep using https://www.echartsjs.com/ you can redirect the site to https://echarts.incubator.apache.org. In this way the user can still access the website with old domain name. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, May 31, 2018 at 12:15 PM, Yi Shen wrote: > My vote is +1 binding. > > But when I check the source file with github repo[1]. I found there are > > some directories are missed. > > I guess we can skip the benchmark, tests, but I'm not sure for the theme > > directory. Can you explain it? > > We need to make sure we can build the full function binary from the > source > > release. > > BTW, it looks there lots of github links in the README.md[2] need to be > > updated. > > And echarts need to move the website to echarts.incubator.apache.org > from > > baidu. > > > Willem, thanks for pointing out the issues. Wenli Zhang has made a request > for the apache website server. We will move the English website to > echarts.incubator.apache.org after that. Not sure if it's ok but we prefer > the Chinese website keep the url https://www.echartsjs.com/ , which is > used > currently > > The theme folder will not be included when building the distribution. It' > more like resources which can be used externally, like geojson data in the > map folder on the GitHub. > > Willem Jiang 于2018年5月31日周四 上午10:19写道： > > > Hi > > > > I just tried to build the source according to the instruction in the > mail, > > it works. > > But when I check the source file with github repo[1]. I found there are > > some directories are missed. > > I guess we can skip the benchmark, tests, but I'm not sure for the theme > > directory. Can you explain it? > > We need to make sure we can build the full function binary from the > source > > release. > > > > BTW, it looks there lots of github links in the README.md[2] need to be > > updated. > > And echarts need to move the website to echarts.incubator.apache.org > from > > baidu. > > > > > > [1] https://github.com/apache/incubator-echarts > > [2]https://github.com/apache/incubator-echarts/blob/master/README.md > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, May 29, 2018 at 5:09 PM, SHUANG SU > wrote: > > > > > After removing some generated files and bin files from 4.1.0.rc3, only > > > source code kept in the artifact. > > > I am pleased to be calling this vote for the release of Apache ECharts > > > 4.1.0.rc4. > > > > > > > > > Apache ECharts community has voted and approved the release. > > > > > > Vote thread: > > > https://lists.apache.org/thread.html/8ebfdd7219cbfed40cd2350e487b99 > > > be58ec169fb7c5673e21e10dea@%3Cdev.echarts.apache.org%3E > > > > > > Results thread: > > > https://lists.apache.org/thread.html/238ae37a82e2a71698f41a4d878e32 > > > 5601b88c665f9951d3bf912db4@%3Cdev.echarts.apache.org%3E > > > > > > The release candidate to be voted over is available at: > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc4/ > > > > > > The release candidate is signed with a GPG key available at: > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS > > > > > > The Git commit for this release is: > > > https://gitbox.apache.org/repos/asf?p=incubator-echarts. > > > git;a=commit;h=02842e2 > > > > > > The Release Note is available in: > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4. > > > 1.0.rc4/RELEASE_NOTE.txt > > > > > > Some shell commands for validating the release: > > > > > > ```shell > > > # Download the release: > > > curl > > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4. > > > 1.0.rc4/apache-echarts-4.1.0.rc4-incubating-src.zip > > > -o apache-echarts-4.1.0.rc4-incubating-src.zip > > > unzip apache-echarts-4.1.0.rc4-incubating-src.zip -d > > > apache-echarts-4.1.0.rc4-incubating-src > /dev/null > > > > > > # Rebuild the project (Node.js environment is required): > > > cd "apache-echarts-4.1.0.rc4-incubating-src" && npm install && cd .. >
Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC2]
Hi, Here are my +1(binding) for this vote. I checked the sign and signature they are OK. The License and Notice file are OK. The release kit has the incubating work I can build the binary from the source kit. Here are some minor issues that I found: 1. The release kit's name should start with Apache. 2. The License of guava is just link, it's better to keep local copy of it as the link could be broken or the License content could be changed. @Jun As the most IPMC has a daily job, so we cannot always stand by for reviewing the kit. You may take advantage of sending the vote before the weekend and provide sophisticated verification in the internal vote thread to speed up the review process. BTW，There are some side projects of Apache Dubbo. Can I know if there are any release plan for these projects? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jun 1, 2018 at 10:41 AM, Jun Liu wrote: > Hello, > > This vote has opened for nearly 72 hours, i am asking again for help to > check and vote on this release candidate. > > Best regards, > Jun > > > On 29 May 2018, at 4:47 PM, Jun Liu wrote: > > > > Hello All, > > > > This is a call for vote to release Apache Dubbo (Incubating) version > 2.6.2. > > > > The Apache Dubbo community has voted on and approved a proposal to > release Apache Dubbo (Incubating) version 2.6.2. > > > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > > > Apache Dubbo™ (incubating) is a high-performance, java based, open > source RPC framework. Dubbo offers three key functionalities, which include > interface based remote call, fault tolerance & load balancing, and > automatic service registration & discovery. > > > > Dubbo vote thread: > > https://lists.apache.org/thread.html/38560cb159a5c32d0cf98485c9fe79 > 1505fbc52d18d86a37713582f0@%3Cdev.dubbo.apache.org%3E < > https://lists.apache.org/thread.html/38560cb159a5c32d0cf98485c9fe79 > 1505fbc52d18d86a37713582f0@%3Cdev.dubbo.apache.org%3E> > > > > Dubbo vote result thread: > > https://lists.apache.org/thread.html/0b1e022a32e136ff0a9b42e7ef7da5 > ccc7d256d175394c2d5858f1cf@%3Cdev.dubbo.apache.org%3E < > https://lists.apache.org/thread.html/0b1e022a32e136ff0a9b42e7ef7da5 > ccc7d256d175394c2d5858f1cf@%3Cdev.dubbo.apache.org%3E> > > > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2 < > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2> > > > > Git tag for the release: > > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2 < > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2> > > > > Hash for the release tag: > > 5eeb240337ccfbc820d4bde023d8cf643f33d735 > > > > Release Notes: > > https://github.com/apache/incubator-dubbo/blob/2.6.2-release/CHANGES.md > <https://github.com/apache/incubator-dubbo/blob/2.6.2-release/CHANGES.md> > > > > The artifacts have been signed with Key : 28681CB1, which can be found > in the keys file: > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS < > https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS> > > > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks. > > Jun Liu, > > on behalf of The Apache Dubbo (Incubating) Team > >
Re: [ANN] Please welcome Justin Mclean as the new Incubator PMC chair!
Congratulations Justin and thanks for John and Justin great helps for the ServiceComb. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jun 4, 2018 at 6:12 PM, Bertrand Delacretaz wrote: > Hi, > > John D. Ament recently announced his desire to step down from the > Incubator PMC chair role. Thank you so much John for your efficient > service here, "retiring" from that is certainly well deserved! > > The Incubator PMC had the difficult task of choosing between a handful > of excellent candidates and has selected Justin as our new chair. The > ASF's Board of Directors has ratified this choice at our May meeting. > > Please join me in welcoming Jusin as our new PMC chair! Justin's been > very active in the Incubator in the last few years, it's great to see > him step up to this role. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Looking for Champion
Hi, I'm willing to be the Mentor. Please count me in. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jun 8, 2018 at 8:59 PM, Dave Fisher wrote: > Hi - > > I’m willing to Champion and Mentor. I have a couple of comments inline. > I’ll look at dependency licenses later today. It’s early for me. > > > > On Jun 7, 2018, at 9:45 PM, Li,De(BDG) wrote: > > > > Hi all, > > > > I am Reed, as a developer worked with the team for Palo (a MPP-based > interactive SQL data warehousing). > > https://github.com/baidu/palo/wiki/Palo-Overview > > > > We propose to contribute Palo as an Apache Incubator project, and > > we are still looking for possible Champion if anyone would like to > volunteer. Thanks a lot. > > > > Best Regards, > > Reed > > > > === > > The draft of the proposal as below: > > > > #Apache Palo > > > > ##Abstract > > > > Palo is a MPP-based interactive SQL data warehousing for reporting and > analysis. > > > > ##Proposal > > > > We propose to contribute the Palo codebase and associated artifacts > (e.g. documentation, web-site content etc.) to the Apache Software > Foundation with the intent of forming a productive, meritocratic and open > community around Palo’s continued development, according to the ‘Apache > Way’. > > > > Baidu owns several trademarks regarding Palo, and proposes to transfer > ownership of those trademarks in full to the ASF. > > > > ###Overview of Palo > > > > Palo’s implementation consists of two daemons: Frontend (FE) and Backend > (BE). > > > > **Frontend daemon** consists of query coordinator and catalog manager. > Query coordinator is responsible for receiving users’ sql queries, > compiling queries and managing queries execution. Catalog manager is > responsible for managing metadata such as databases, tables, partitions, > replicas and etc. Several frontend daemons could be deployed to guarantee > fault-tolerance, and load balancing. > > > > **Backend daemon** stores the data and executes the query fragments. > Many backend daemons could also be deployed to provide scalability and > fault-tolerance. > > > > A typical Palo cluster generally composes of several frontend daemons > and dozens to hundreds of backend daemons. > > > > Users can use MySQL client tools to connect any frontend daemon to > submit SQL query. Frontend receives the query and compiles it into query > plans executable by the Backend. Then Frontend sends the query plan > fragments to Backend. Backend will build a query execution DAG. Data is > fetched and pipelined into the DAG. The final result response is sent to > client via Frontend. The distribution of query fragment execution takes > minimizing data movement and maximizing scan locality as the main goal. > > > > ##Background > > > > At Baidu, Prior to Palo, different tools were deployed to solve diverse > requirements in many ways. And when a use case requires the simultaneous > availability of capabilities that cannot all be provided by a single tool, > users were forced to build hybrid architectures that stitch multiple tools > together, but we believe that they shouldn’t need to accept such inherent > complexity. A storage system built to provide great performance across a > broad range of workloads provides a more elegant solution to the problems > that hybrid architectures aim to solve. Palo is the solution. > > > > Palo is designed to be a simple and single tightly coupled system, not > depending on other systems. Palo provides high concurrent low latency point > query performance, but also provides high throughput queries of ad-hoc > analysis. Palo provides bulk-batch data loading, but also provides near > real-time mini-batch data loading. Palo also provides high availability, > reliability, fault tolerance, and scalability. > > > > ##Rationale > > > > Palo mainly integrates the technology of Google Mesa and Apache Impala. > > > > Mesa is a highly scalable analytic data storage system that stores > critical measurement data related to Google's Internet advertising > business. Mesa is designed to satisfy complex and challenging set of users’ > and systems’ requirements, including near real-time data ingestion and > query ability, as well as high availability, reliability, fault tolerance, > and scalability for large data and query volumes. > > > > Impala is a modern, open-source MPP SQL engine architected from the > ground up for the Hadoop data processing environment. At present, by virtue > of its superior performance and rich functionality，
Re: [VOTE] Accept Warble into the Apache Incubator
+1 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jun 8, 2018 at 10:06 PM, Chris Thistlethwaite wrote: > Hi All, > I'd like to start a vote on accepting Warble into the Apache Incubator. > https://lists.apache.org/thread.html/1d62a2948d047cea38e6f01f92d5f138f8 > 3acd2c9d86349023fb28e4@%3Cgeneral.incubator.apache.org%3E > The ASF voting rules are described: > https://www.apache.org/foundation/voting.html > A vote for accepting a new Apache Incubator podling is a majority > votefor which only Incubator PMC member votes are binding. > This vote will run for at least 72 hours. Please VOTE as follows[ ] +1 > Accept Warble into the Apache Incubator[ ] +0 Abstain.[ ] -1 Do not > accept Warble into the Incubator > The proposal is listed below, but you can also access it on the wiki:ht > tps://wiki.apache.org/incubator/WarbleProposal > > Thank you,Chris T. > > > = Apache Warble Proposal = > == Abstract == > Apache Warble is a distributed endpoint monitoring solution where > the agentis hosted on your own hardware. The aim of Warble is to > produce a more balanced and less binary view of services and > systems, lowering the rates of false positiveswhile also providing > greater insight into possible peering issues and proactive > trendanalysis. ==Proposal == The goal of Warble > will be to bring internal control of distributed monitoring back to > the end user. Warble can be used as an independentservice running > on your own infrastructure monitoring other servicesin your > infrastructure. == Background and Rationale == The > beginning of this project was prompted by the service > pingmybox.com (PMB) going end of life. This brought up conversation > about FOSS services that can monitor internal and external > services. PMB offered a unique code base to build this service upon > a known infrastructure. ===Initial Goals === > Bring PMB code into the ASF, refactor the client/server into a > more reusable structure. Further reuse of code gives us the a great > starting point to build a starting point. ==Current Status > == The software exists as a proprietary service. We wish to > convert this toa FLOSS solution. ==Meritocracy > == The initial PMC list covers new folks coming into the > ASF. ==Community == There exists a large user-base of > software like Warble, as well as existing users of the old propietary > service. It is our hope that wecan convert a great deal of these to > contributors and testers for thenew open source > product. ==Core Developers == The initial set of > developers are a lot of newcomers: > * Daniel Gruno * Chris Thistlethwaite > * Haig Didizian * Andrew > Karetas * Chandler Claxton > * Luke Stevens > * Mike Andescavage > * Chris Lambertus > ==Known Risks ==There are many > existing services that provide external monitoring. Theyare well > established and have large user bases. ===Orphaned Products > === The initial PMC has great interest in open source projects, > though no formal projects have been > run. ===Inexperience with Open Source === Most of > the initial PPMC members are new to the ASF and some are new to open > source projects. However,all are very interested in giving back to > the community and projects. Having said that, there areseveral > people involved with extensive experience in the Apache Way and our > procedures and processes. ===Homogenous Developers > === The initial set of developers are employed by a variety of > companies,located across the world, and used to working on a > variety ofdistributed projects. ===Reliance on Salaried > Developers === We do not expect the interest of the proposed > initial PMC to be directlytied to current employment, but will > actively seek to grow our volunteerbase > regardless. ===Relationships with Other Apache Products > === Not much to say here. Many ASF projects make use of the > proprietaryoffering, we wish to open source it and have people > engage in thedevelopment of the project. There are, at present, > indirect relationships in that some dependencies are built on > Apache software, but these are generally by proxy and does not > merit considering Warble as a sub-projectof an existing > TLP. ==Initial Source == The initial task of the > PMC will be assessing what we wish the project tocontain. The > proprietary vendor is willing to donate the software, > butconsiderable
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m2
+1 (binding) Carrying my vote over form the dev list. For the source code I checked: 1. File name with incubating 2. Signed key and sha file are OK 3. License and Notice file is good 4. RAT check OK 5. DISCLAME file is there 6. No other code in the vendor directory For the binary I checked: 1. File name with incubating 2. Signed key and sha file are OK 3. License for the go files includes the hash commit info 4. License for the frondend js includes the js version 5. Notice file is fine 6. DISCLAME file is right 7. The Server and Frondend can be started with instruction of README. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Jun 12, 2018 at 4:36 PM, Mohammad Asif Siddiqui < asifdxtr...@apache.org> wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Service-Center > (Incubating) version 1.0.0-m2. > Apache ServiceComb (Incubating) Community has voted and approved the > release > > Vote Thread : https://lists.apache.org/thread.html/ > 2c979af45fd37ecf944c783844240f3874b96713997f2fc2a0bd71fc@% > 3Cdev.servicecomb.apache.org%3E > > Result Thread : https://lists.apache.org/thread.html/ > 2b7548c13deec4f563c41d3cc6daab16fd3b691ec9b48bd54caad2d8@% > 3Cdev.servicecomb.apache.org%3E > > Release Notes : https://github.com/apache/incubator-servicecomb-service- > center/blob/master/docs/release/releaseNotes-1.0.0-m2.md > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-service-center/1.0.0-m2/rc-01/ > > Release Tag : https://github.com/apache/incubator-servicecomb-service- > center/releases/tag/1.0.0-m2 > > Release CommitID : b913a2de1b5f7fb2a42ac719fe5891d5f46f349d > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > Guide to build the release from source : https://github.com/apache/ > incubator-servicecomb-service-center/tree/master/scripts/release > > Voting will start now(Tuesday, 12th June, 2018) and will remain open for > next 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0-m2 > [ ] +0 No Opinion > [ ] -1 Do not release this package because... > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.2.0
Carrying my vote over form the dev list. I checked: - incubating in binary and src kit name - signatures and hashes correct - LICENSE is fine (third party jars versions are updated) - NOTICE is OK but has wrong year please fix - no unexpected binary files - source files have headers - can build the kit from source without any error - can run the demo with the instruction of README Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Jun 12, 2018 at 5:12 PM, Mohammad Asif Siddiqui < asifdxtr...@apache.org> wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Saga (Incubating) > version 0.2.0 > > Apache ServiceComb (Incubating) Community has voted and approved the > release. > > Vote Thread : https://lists.apache.org/thread.html/ > fd0c4593d8574563e1a247cf2bed5a72d66a317472e4d9ee597433fc@% > 3Cdev.servicecomb.apache.org%3E > > Result Thread : https://lists.apache.org/thread.html/ > 77f0360d12ca2352c9052a112ba0e4f06c028132909f84d71eca3bcd@% > 3Cdev.servicecomb.apache.org%3E > > Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12321626&version=12342425 > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-saga/0.2.0/rc-01/ > > Staging Repo : https://repository.apache.org/content/repositories/ > orgapacheservicecomb-1271/ > > Release Tag : https://github.com/apache/incubator-servicecomb-saga/ > releases/tag/0.2.0 > > Release CommitID : 1f3c3d1e61a6c7f40df479a43d28b54f335d84ac > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > Voting will start now ( Tuesday, 12th June, 2018) and will remain open for > next 72 hours, We request all IPMC members to give their vote. > > [ ] +1 Release this package as 0.2.0 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.2.0
I mean +1 (binding). Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Jun 13, 2018 at 9:15 AM, Willem Jiang wrote: > Carrying my vote over form the dev list. > > I checked: > - incubating in binary and src kit name > - signatures and hashes correct > - LICENSE is fine (third party jars versions are updated) > - NOTICE is OK but has wrong year please fix > - no unexpected binary files > - source files have headers > - can build the kit from source without any error > - can run the demo with the instruction of README > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Jun 12, 2018 at 5:12 PM, Mohammad Asif Siddiqui < > asifdxtr...@apache.org> wrote: > >> Hello All, >> >> This is a call for vote to release Apache ServiceComb Saga (Incubating) >> version 0.2.0 >> >> Apache ServiceComb (Incubating) Community has voted and approved the >> release. >> >> Vote Thread : https://lists.apache.org/threa >> d.html/fd0c4593d8574563e1a247cf2bed5a72d66a317472e4d9ee59743 >> 3fc@%3Cdev.servicecomb.apache.org%3E >> >> Result Thread : https://lists.apache.org/threa >> d.html/77f0360d12ca2352c9052a112ba0e4f06c028132909f84d71eca3 >> bcd@%3Cdev.servicecomb.apache.org%3E >> >> Release Notes : https://issues.apache.org/jira >> /secure/ReleaseNote.jspa?projectId=12321626&version=12342425 >> >> Release Candidate : https://dist.apache.org/repos/ >> dist/dev/incubator/servicecomb/incubator-servicecomb-saga/0.2.0/rc-01/ >> >> Staging Repo : https://repository.apache.org/ >> content/repositories/orgapacheservicecomb-1271/ >> >> Release Tag : https://github.com/apache/incu >> bator-servicecomb-saga/releases/tag/0.2.0 >> >> Release CommitID : 1f3c3d1e61a6c7f40df479a43d28b54f335d84ac >> >> Keys to verify the Release Candidate : https://dist.apache.org/repos/ >> dist/dev/incubator/servicecomb/KEYS >> >> Voting will start now ( Tuesday, 12th June, 2018) and will remain open >> for next 72 hours, We request all IPMC members to give their vote. >> >> [ ] +1 Release this package as 0.2.0 >> [ ] +0 No Opinion >> [ ] -1 Do not release this package because >> >> On the behalf of ServiceComb Team >> Mohammad Asif Siddiqui >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> >
Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 2
Hi Matto,
I just checked the source code, the License header issue is still there.
pulsar-common/src/main/java/org/apache/pulsar/common/util/
protobuf/ByteBufCoded{Input,Output}Stream.java
There are still bunch different version of netty jars in the lib directory.
My suggestion is we need fix these issues that we found in the last vote
before starting a new vote.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Tue, Jun 12, 2018 at 6:00 AM, Matteo Merli wrote:
> This is the second release candidate for Apache Pulsar, version
> 2.0.1-incubating.
>
> Link to the vote on dev@pulsar list
> https://lists.apache.org/thread.html/620813d66d43a43680d3afd587e72f
> 0d6f9607f1566aa88ef73d359c@%3Cdev.pulsar.apache.org%3E
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware.
> It provides simple pub-sub semantics over topics, guaranteed at-least-once
> delivery of
> messages, automatic cursor management for subscribers, and geo-replication.
>
> This is a patch release that fixes few issues identified in previous
> release 2.0.0-rc1-incubating.
>
> It fixes the following issues:
> https://github.com/apache/incubator-pulsar/milestone/14?closed=1
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> pulsar-2.0.1-incubating-candidate-2/
>
> SHA-1 checksums:
>
> 5acd63f8aa1fa75f386df7b9fd803a943978e609
> apache-pulsar-2.0.1-incubating-bin.tar.gz
> 312bc0f1ae170c1d2dc38b1e362fb50f82c00525
> apache-pulsar-2.0.1-incubating-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1020
>
>
> The tag to be voted upon:
> v2.0.1-incubating-candidate-2 (fd47532380d770e4fd78cabe71dea293fc2f0e06)
> https://github.com/apache/incubator-pulsar/releases/tag/
> v2.0.1-incubating-candidate-2
> <https://github.com/apache/incubator-pulsar/releases/tag/
> v2.0.1-incubating-candidate-1>
>
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
> --
> Matteo Merli
>
>
Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 2
+1 (binding)
I checked:
Signing key, and verify the check sum.
License files and Notice files are OK
I can built the binary kit from source.
Please let me know when you commit the fix of source code license and clean
up the netty version issue.
I will keep an eye on the 2.1 branch to make sure those issue are fixed.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Jun 15, 2018 at 5:22 AM, Matteo Merli wrote:
> Hi WIllem,
>
> the 2.0.1 candidate was already being voted on the dev@pulsar list when
> the
> comments on 1.22.1 release were made here on incubator list, otherwise we
> would have included the changes.
>
> 2.0.1 is a patch release in which we are trying to fix some issues reported
> by
> users in the 2.0.01-rc1 release from a couple of weeks back.
>
> Since at least a couple of issues were impacting users, we were trying to
> get
> a fix out ASAP. In particular we found packaging related issues that
> impacted:
> * Pulsar python client lib
> * Pulsar proxy startup
>
> Master branch is already set on 2.1 release and we just applied few commits
> to fix the non-functioning features.
>
> The idea was to fix netty packaging and protobuf license headers for 2.1,
> for
> which we plan to start the release process by next week.
>
> Matteo
>
> On Wed, Jun 13, 2018 at 6:24 PM Willem Jiang
> wrote:
>
> > Hi Matto,
> >
> > I just checked the source code, the License header issue is still there.
> > pulsar-common/src/main/java/org/apache/pulsar/common/util/
> > protobuf/ByteBufCoded{Input,Output}Stream.java
> >
> > There are still bunch different version of netty jars in the lib
> directory.
> >
> > My suggestion is we need fix these issues that we found in the last vote
> > before starting a new vote.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Jun 12, 2018 at 6:00 AM, Matteo Merli wrote:
> >
> > > This is the second release candidate for Apache Pulsar, version
> > > 2.0.1-incubating.
> > >
> > > Link to the vote on dev@pulsar list
> > > https://lists.apache.org/thread.html/620813d66d43a43680d3afd587e72f
> > > 0d6f9607f1566aa88ef73d359c@%3Cdev.pulsar.apache.org%3E
> > >
> > > Pulsar is a highly scalable, low latency messaging platform running on
> > > commodity hardware.
> > > It provides simple pub-sub semantics over topics, guaranteed
> > at-least-once
> > > delivery of
> > > messages, automatic cursor management for subscribers, and
> > geo-replication.
> > >
> > > This is a patch release that fixes few issues identified in previous
> > > release 2.0.0-rc1-incubating.
> > >
> > > It fixes the following issues:
> > > https://github.com/apache/incubator-pulsar/milestone/14?closed=1
> > >
> > > *** Please download, test and vote on this release. This vote will stay
> > > open
> > > for at least 72 hours ***
> > >
> > > Note that we are voting upon the source (tag), binaries are provided
> for
> > > convenience.
> > >
> > > Source and binary files:
> > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> > > pulsar-2.0.1-incubating-candidate-2/
> > >
> > > SHA-1 checksums:
> > >
> > > 5acd63f8aa1fa75f386df7b9fd803a943978e609
> > > apache-pulsar-2.0.1-incubating-bin.tar.gz
> > > 312bc0f1ae170c1d2dc38b1e362fb50f82c00525
> > > apache-pulsar-2.0.1-incubating-src.tar.gz
> > >
> > > Maven staging repo:
> > > https://repository.apache.org/content/repositories/
> orgapachepulsar-1020
> > >
> > >
> > > The tag to be voted upon:
> > > v2.0.1-incubating-candidate-2 (fd47532380d770e4fd78cabe71dea2
> 93fc2f0e06)
> > > https://github.com/apache/incubator-pulsar/releases/tag/
> > > v2.0.1-incubating-candidate-2
> > > <https://github.com/apache/incubator-pulsar/releases/tag/
> > > v2.0.1-incubating-candidate-1>
> > >
> > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> > >
> > > Please download the the source package, and follow the README to build
> > > and run the Pulsar standalone service.
> > > --
> > > Matteo Merli
> > >
> > >
> >
> --
> Matteo Merli
>
>
Re: [VOTE] Release Apache ServiceComb Java-Chassis (Incubating) version 1.0.0-m2
Hi， Carrying my +1 vote from the dev mailing list. I checked - incubating in binary and src kit name - signatures and hashes correct - LICENSE is fine - NOTICE is OK. - no unexpected binary files - source files have headers - can build the kit from source without any error - can run the company demo with the java chassis release candidate. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Jun 19, 2018 at 12:10 AM, Mohammad Asif Siddiqui < asifdxtr...@apache.org> wrote: > Hi All, > > This is a call for vote to release Apache ServiceComb Java-Chassis > (Incubating) version 1.0.0-m2 > > Apache ServiceComb (Incubating) Community has voted and approved the > release. > > Vote Thread : https://lists.apache.org/thread.html/ > 587081b895bf02d69bea82a24760fa59cb93f50dbe07064d0e630d4a@% > 3Cdev.servicecomb.apache.org%3E > > Result Thread : https://lists.apache.org/thread.html/ > c9e5c5289c26f82e9c4b9046f097ba5f9a863e3376836d9ad72ef134@% > 3Cdev.servicecomb.apache.org%3E > > Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12321626&version=12342355 > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-java-chassis/1.0.0-m2/rc-02/ > > Staging Repo : https://repository.apache.org/content/repositories/ > orgapacheservicecomb-1303/ > > Release Tag : https://github.com/apache/incubator-servicecomb-java- > chassis/releases/tag/1.0.0-m2 > > Release CommitID : 95e87f4791218c45ddb9b8eed0a4073873432034 > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > Voting will start now ( Monday, 18th June, 2018) and will remain open for > atleast 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0-m2 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Amaterasu (incubating) 0.2.0 (rc3)
Hi Yaniv, I just checked the source tar, it has the ama-key and ama-key.pub. I'm not sure what's ama key used to. We normally don't ship any public key in the release kit, and should never ship private key in the release kit, Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Jun 19, 2018 at 7:58 AM, Yaniv Rodenski wrote: > Hi all, > > Just a kind reminder that we are still in need for reviews/votes, if anyone > else can help with the vote, that would be lovely. > > Thanks in advance > Yaniv > > On Tue, 19 Jun 2018 at 12:56 am, Davor Bonaci wrote: > > > +1 (binding), carried over. > > > > On Thu, Jun 14, 2018 at 9:37 PM, Yaniv Rodenski wrote: > > > > > Hi, > > > > > > I've removed the md5's, and will update the Amaterasu release procedure > > > accordingly. > > > > > > Cheers, > > > Yaniv > > > > > > On Fri, Jun 15, 2018 at 1:04 AM, Henk P. Penning > wrote: > > > > > > > On Thu, 14 Jun 2018, Yaniv Rodenski wrote: > > > > > > > > Date: Thu, 14 Jun 2018 16:32:19 +0200 > > > >> From: Yaniv Rodenski > > > >> To: general@incubator.apache.org > > > >> Subject: [VOTE] Release Apache Amaterasu (incubating) 0.2.0 (rc3) > > > >> > > > > > > > > Please remove the .md5's ; see policy : > > > > > > > > https://www.apache.org/dev/release-distribution#sigs-and-sums > > > > > > > > This does NOT affect the VOTE ; please continue ... > > > > > > > > Regards, > > > > > > > > Henk Penning > > > > > > > > _ > > > > Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ > > > > Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ > > > > Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ > > > > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ > > > > > > > > > > > > The Apache Amaterasu (incubating) community has voted on and > approved a > > > >> proposal to release Apache Amaterasu 0.2.0-rc3. > > > >> > > > >> We now kindly request that the Incubator PMC members review and vote > > on > > > >> this incubator release candidate. > > > >> > > > >> Apache Amaterasu is a Configuration Managment and Deployment > Framework > > > for > > > >> Big Data Pipelines. > > > >> > > > >> The vote thread is at: > > > >> http://mail-archives.apache.org/mod_mbox/amaterasu-dev/20180 > > > >> 5.mbox/%3CCAKm_ > > > >> 3C0qT7pYPjZm_C4JRiruQasW6be2F1xLx%2Bf2zfQvxBWJTA%40mail.gmail.com > %3E > > > >> > > > >> and the result is at: > > > >> http://mail-archives.apache.org/mod_mbox/amaterasu-dev/20180 > > > >> 6.mbox/%3CCAKm_3C1qYgM9%3DaOxt7JNo4R23UvoeP%3DhUi7GQpiVEc5Ad > > > >> vAwMg%40mail.gmail.com%3E > > > >> > > > >> > > > >> This is the first incubator release and it includes much-awaited > > > >> improvements such as YARN support, PySpark and SparkSQL support and > > > >> stability improvements. > > > >> > > > >> All distribution packages, including signatures, digests, etc. can > be > > > >> found at: > > > >> > > > >> https://dist.apache.org/repos/dist/dev/incubator/amaterasu/ > 0.2.0rc3/ > > > >> > > > >> > > > >> This release has been signed with PGP key corresponding to > > > >> ya...@apache.org, which is included in the repository's KEYS file ( > > > >> https://dist.apache.org/repos/dist/dev/incubator/amaterasu/KEYS). > > > >> > > > >> The release candidate has been tagged in git with > > > >> version-0.2.0-incubating-rc3: > > > >> https://github.com/apache/incubator-amaterasu/releases/tag/ > > > >> version-0.2.0-incubating-rc3 > > > >> > > > >> Please review and vote. The vote will be open for at least 72 hours. > > > >> > > > >> Thank you very much, > > > >> Yaniv > > > >> > > > >> > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > -- > > > Yaniv Rodenski > > > > > > +61 477 778 405 > > > ya...@shinto.io > > > > > > -- > Yaniv Rodenski > > +61 477 778 405 > ya...@shinto.io >
Re: [VOTE] Release Apache Amaterasu (incubating) 0.2.0 (rc3)
I went through the code, and found there are some java and scala codes. I'm not sure if you publish the jars into nexus, but I guess the key may used to sign the artifact jars . As the private key is leaked, I had to vote -1 for this release. Please take good care of the key when you do the release. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Jun 20, 2018 at 10:21 AM, Yaniv Rodenski wrote: > Hi Willem, > > Thanks for that, this is really strange as the key was deleted from the > source a while back and is not there in the repository (I've just double > verified looking at the git repo). I will investigate why it does come out > in the source tar.gz file. > > However, this key is a private key added by mistake by one of our > contributors and belonged to him (and since was decommissioned). In this > situation, is this a blocking issue? If so, we will release a new RC and > restart the voting. > > Thanks in advance, > Yaniv > > On Wed, Jun 20, 2018 at 11:45 AM, Willem Jiang > wrote: > > > Hi Yaniv, > > > > I just checked the source tar, it has the ama-key and ama-key.pub. > > I'm not sure what's ama key used to. > > We normally don't ship any public key in the release kit, and should > never > > ship private key in the release kit, > > > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Jun 19, 2018 at 7:58 AM, Yaniv Rodenski wrote: > > > > > Hi all, > > > > > > Just a kind reminder that we are still in need for reviews/votes, if > > anyone > > > else can help with the vote, that would be lovely. > > > > > > Thanks in advance > > > Yaniv > > > > > > On Tue, 19 Jun 2018 at 12:56 am, Davor Bonaci > wrote: > > > > > > > +1 (binding), carried over. > > > > > > > > On Thu, Jun 14, 2018 at 9:37 PM, Yaniv Rodenski > > wrote: > > > > > > > > > Hi, > > > > > > > > > > I've removed the md5's, and will update the Amaterasu release > > procedure > > > > > accordingly. > > > > > > > > > > Cheers, > > > > > Yaniv > > > > > > > > > > On Fri, Jun 15, 2018 at 1:04 AM, Henk P. Penning > > > wrote: > > > > > > > > > > > On Thu, 14 Jun 2018, Yaniv Rodenski wrote: > > > > > > > > > > > > Date: Thu, 14 Jun 2018 16:32:19 +0200 > > > > > >> From: Yaniv Rodenski > > > > > >> To: general@incubator.apache.org > > > > > >> Subject: [VOTE] Release Apache Amaterasu (incubating) 0.2.0 > (rc3) > > > > > >> > > > > > > > > > > > > Please remove the .md5's ; see policy : > > > > > > > > > > > > https://www.apache.org/dev/release-distribution#sigs-and- > sums > > > > > > > > > > > > This does NOT affect the VOTE ; please continue ... > > > > > > > > > > > > Regards, > > > > > > > > > > > > Henk Penning > > > > > > > > > > > > _ > > > > > > Henk P. Penning, ICT-beta R Uithof MG-403_/ > \_ > > > > > > Faculty of Science, Utrecht UniversityT +31 30 253 4106 / > \_/ \ > > > > > > Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ > \_/ > > > > > > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl > \_/ > > > > > > > > > > > > > > > > > > The Apache Amaterasu (incubating) community has voted on and > > > approved a > > > > > >> proposal to release Apache Amaterasu 0.2.0-rc3. > > > > > >> > > > > > >> We now kindly request that the Incubator PMC members review and > > vote > > > > on > > > > > >> this incubator release candidate. > > > > > >> > > > > > >> Apache Amaterasu is a Configuration Managment and Deployment > > > Framework > > > > > for > > > > > >> Big Data Pipelines. > > > > > >> > > > > > >> The vote thread is at: > > > > > >> http://mail-archives.apache.org/mod_mbox/amaterasu-dev/20180 > > > >
Re: Private area for incubating projects
Hi,
I just checked the group list[1], there is no xxx-pmc if the xxx is
incubating project.
I guess you need to find another way to store the private information.
[1]http://people.apache.org/committers-by-project.html
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Tue, Jun 26, 2018 at 4:19 PM, Huxing Zhang wrote:
> Hi,
>
> I would like to store some private information for Dubbo(incubating)
> project, which only the PPMC member can access(read/write).
>
> I have checked [1], it says:
>
> The PMC may also have a private area under
> https://svn.apache.org/repos/private/pmc/{pmc} in which case
> membership of the corresponding LDAP committee group gives both read
> and write access.
>
> When I am trying to check it out for Dubbo, I got denied:
>
> svn co https://svn.apache.org/repos/private/pmc/dubbo
> Authentication realm: <https://svn.apache.org:443> ASF Members
> Password for 'huxing': xx
>
> svn: E170013: Unable to connect to a repository at URL
> 'https://svn.apache.org/repos/private/pmc/dubbo'
> svn: E175013: Access to '/repos/private/pmc/dubbo' forbidden
>
> Am I missing something here?
>
> [1] http://people.apache.org/committers-by-project.html
>
> --
> Best Regards！
> Huxing
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
Re: [VOTE] Accept Doris into the Apache Incubator
+1 (binding) Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jul 6, 2018 at 3:22 AM, Dave Fisher wrote: > Hi All, > > I would like to start a VOTE to bring the Doris project as an Apache > incubator podling. > > The ASF voting rules are described: > > https://www.apache.org/foundation/voting.html > > A vote for accepting a new Apache Incubator podling is a majority vote for > which > only Incubator PMC member votes are binding. > > This vote will run for at least 72 hours. Please VOTE as follows > [] +1 Accept Doris into the Apache Incubator > [] +0 Abstain. > [] -1 Do not accept Doris into the Apache Incubator because ... > > The proposal is listed below, but you can also access it on the wiki: > > https://wiki.apache.org/incubator/DorisProposal > > Best regards, > Dave > > = Apache Doris = > > == Abstract == > > Doris is a MPP-based interactive SQL data warehousing for reporting and > analysis. > > == Proposal == > > We propose to contribute the Doris codebase and associated artifacts (e.g. > documentation, web-site content etc.) to the Apache Software Foundation, > and aim to build an open community around Doris’s continued development in > the ‘Apache Way’. > > === Overview of Doris === > > Doris’s implementation consists of two daemons: Frontend (FE) and Backend > (BE). > > **Frontend daemon** consists of query coordinator and catalog manager. > Query coordinator is responsible for receiving users’ sql queries, > compiling queries and managing queries execution. Catalog manager is > responsible for managing metadata such as databases, tables, partitions, > replicas and etc. Several frontend daemons could be deployed to guarantee > fault-tolerance, and load balancing. > > **Backend daemon** stores the data and executes the query fragments. Many > backend daemons could also be deployed to provide scalability and > fault-tolerance. > > A typical Doris cluster generally composes of several frontend daemons and > dozens to hundreds of backend daemons. > > Users can use MySQL client tools to connect any frontend daemon to submit > SQL query. Frontend receives the query and compiles it into query plans > executable by the Backend. Then Frontend sends the query plan fragments to > Backend. Backend will build a query execution DAG. Data is fetched and > pipelined into the DAG. The final result response is sent to client via > Frontend. The distribution of query fragment execution takes minimizing > data movement and maximizing scan locality as the main goal. > > == Background == > > At Baidu, Prior to Doris, different tools were deployed to solve diverse > requirements in many ways. And when a use case requires the simultaneous > availability of capabilities that cannot all be provided by a single tool, > users were forced to build hybrid architectures that stitch multiple tools > together, but we believe that they shouldn’t need to accept such inherent > complexity. A storage system built to provide great performance across a > broad range of workloads provides a more elegant solution to the problems > that hybrid architectures aim to solve. Doris is the solution. > > Doris is designed to be a simple and single tightly coupled system, not > depending on other systems. Doris provides high concurrent low latency > point query performance, but also provides high throughput queries of > ad-hoc analysis. Doris provides bulk-batch data loading, but also provides > near real-time mini-batch data loading. Doris also provides high > availability, reliability, fault tolerance, and scalability. > > == Rationale == > > Doris mainly integrates the technology of Google Mesa and Apache Impala. > > Mesa is a highly scalable analytic data storage system that stores > critical measurement data related to Google's Internet advertising > business. Mesa is designed to satisfy complex and challenging set of users’ > and systems’ requirements, including near real-time data ingestion and > query ability, as well as high availability, reliability, fault tolerance, > and scalability for large data and query volumes. > > Impala is a modern, open-source MPP SQL engine architected from the ground > up for the Hadoop data processing environment. At present, by virtue of its > superior performance and rich functionality， Impala has been comparable to > many commercial MPP database query engine. Mesa can satisfy the needs of > many of our storage requirements, however Mesa itself does not provide a > SQL query engine; Impala is a very good MPP SQL query engine, but the lack > of a perfect distributed storage engine. So in the end we chose the > combination of these two technologies. > > Learning from Mesa’s
Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta2 [RC1]
+1 binding. Here are what I checked: - Key and signed information are good - can build from source - Rat check looks good - DISCLAIMER exists - LICENSE file looks good - NOTICE is OK Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Jul 8, 2018 at 10:50 PM, 吴晟 Sheng Wu wrote: > Hi All, > This is a call for vote to release Apache SkyWalking (Incubating) version > 5.0.0-beta2. > > > The Apache SkyWalking community has tested, voted and approved the proposed > release of Apache SkyWalking (Incubating) 5.0.0-beta2 > > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > > SkyWalking: APM (application performance monitor) tool for distributed > systems, > especially designed for microservices, cloud native and container-based > (Docker, Kubernetes, Mesos) architectures. > Underlying technology is a distributed tracing system. > > > Vote Thread: > > https://lists.apache.org/thread.html/4b7cd6fd45418f740cbc34b5307209 > d9779c31837f8556d5ae6c3ee5@%3Cdev.skywalking.apache.org%3E > > > Result Thread: > https://lists.apache.org/thread.html/83d8c2e2e791b8775caa66e1a7f81a > 9dd5439b848abe18141eabed3d@%3Cdev.skywalking.apache.org%3E > > > Release notes: > > > * https://github.com/apache/incubator-skywalking/blob/ > master/CHANGES.md#500-beta2 > > > Release Candidate: > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/ > 5.0.0-beta2-RC1/ > * sha512 checksums >- sha512 a58f4d8a44ddd2083441edf88454c701443d3c9150990668f0832a49718e > 72f45a5d16b676656c3da4b4fd3d9e5bf12e7b1fbd220ead3b6f0483ea7382e1152e > apache-skywalking-apm-incubating-5.0.0-beta2-src.tgz >- sha512 9d53f93380e6c0e06fbcb0ad025e94dde0784b94b2ea9aadd7a139cef504 > 52e04178f1e05f5f8d0a748031fecf65b94436c487b5d53d009a5fbfa2194b746fcc > apache-skywalking-apm-incubating-5.0.0-beta2.tar.gz >- sha512 2997e96cc818e70686218c0cdadc602f1be0058cba14e1467da91c90c2d9 > 278b77fc1c7ea9dc529b6cc7db110e75500297f9c40251735adf0d1ed6b7ede8db74 > apache-skywalking-apm-incubating-5.0.0-beta2.zip > > > Maven 2 staging repository: > > > * https://repository.apache.org/content/repositories/ > orgapacheskywalking-1014/org/apache/skywalking/ > > > Release Tag : > > > * https://github.com/apache/incubator-skywalking/tree/v5.0.0-beta2-RC1 > > > Release CommitID : > > > * https://github.com/apache/incubator-skywalking/tree/ > 2bc785bd51adf79dcf4b312b590e156baed698ac > * Git submodule >* skywalking-ui: https://github.com/apache/ > incubator-skywalking-ui/tree/3ecf33899e28ac106e1d421c089c4c4a4d79c23d >* apm-protocol/apm-network/src/main/proto: https://github.com/apache/ > incubator-skywalking-data-collect-protocol/tree/ > c02c12af12116121e25155d1f3fca0fadee5f2e9 > > > Keys to verify the Release Candidate : > > > * https://dist.apache.org/repos/dist/dev/incubator/skywalking/ > 5.0.0-beta2-RC1/KEYS corresponding to wush...@apache.org > > > Guide to build the release from source : > > > * https://github.com/apache/incubator-skywalking/blob/ > master/docs/en/How-to-build.md > > > > Voting will start now (2018/7/8) and will remain open for at least 72 > hours, Request all PPMC members to give their vote. > [ ] +1 Release this package. > [ ] +0 No opinion. > [ ] -1 Do not release this package because > > > > > -- > Sheng Wu > Apache SkyWalking
Re: [DISCUSS] Graduate Apache HAWQ (incubating) as a TLP
Just a quick question for the PMC size 45. >From the report, I can see there are 12 PPMC member, but the PMC size is same with the Committer size. I guess that could be a typo, am I right? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jul 6, 2018 at 9:54 AM, Roman Shaposhnik wrote: > Hi! > > HAWQ community seems to be ready to graduate. What > do fellow IPMC members think? > > Details on the community are below and here's a link to > the DISCUSS thread: > https://lists.apache.org/thread.html/67a2d52ef29cbf9e93d8050ed0193c > c110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E > > Thanks, > Roman. > > -- Forwarded message -- > From: Radar Lei > Date: Tue, Jun 19, 2018 at 2:40 AM > Subject: [DISCUSS] Graduate Apache HAWQ (incubating) as a TLP > To: dev > > > Hi All, > > With the 2.3.0.0-incubating release officially out, the Apache HAWQ > community and its mentors believe it is time to consider graduation to the > TLP: > https://lists.apache.org/thread.html/b4a0b5671ce377b3d51c9b7 > ab00496a1eebfcbf1696ce8b67e078c64@%3Cdev.hawq.apache.org%3E > > Apache HAWQ entered incubation in September of 2015, since then, the HAWQ > community learned a lot about how to do things in Apache ways. Now we have > a healthy and engaged community, ready to help with all questions from the > HAWQ community. We delivered four releases including two binary releases, > now we can do self-driving releases in good cadence. The PPMC has > demonstrated a good understanding of growing the community by electing 12 > individuals as committers and PPMC members. The PPMC addressed the maturity > issues one by one followed by Apache Project Maturity Model, currently all > the License and IP issues are resolved. This demonstrated our understanding > of ASF's IP policies. > > All in all, I believe this project is qualified as a true TLP and we should > recognize this fact by formally awarding it such a status. This thread > means to open up the very same discussion that we had among the mentors and > HAWQ community to the rest of the IPMC. It is a DISCUSS thread so feel free > to ask questions. > > To get you all going, here are a few data points which may help: > > Project status: > http://incubator.apache.org/projects/hawq.html > > Project website: > http://hawq.incubator.apache.org/ > > Project documentation: >http://hawq.incubator.apache.org/docs/userguide/2.3.0.0-inc > ubating/overview/HAWQOverview.html >http://hawq.apache.org/#download > > Maturity assessment: > https://cwiki.apache.org/confluence/display/HAWQ/ASF+Maturity+Evaluation > > DRAFT of the board resolution is at the bottom of this email > > Proposed PMC size: 45 members > > Total number of committers: 45 members > > PMC affiliation (* indicated chair): >Pivotal (20) > * Oushu (7) >Amazon (3) >Hashdata (2) >Autonomic (1) >Confluent (1) >Datometry (1) >Hortonworks (1) >Microsoft (1) >PETUUM (1) >Privacera (1) >Qubole (1) >Snowflake (1) >State Street (1) >Unifi (1) >Visa (1) >ZEDEDA (1) > > 1549 commits on develop > 1375 PR”s on GitHub > 63 contributors across all branches > > 1624 issues created > 1350 issues resolved > > dev list averaged ~53 msgs/month over last 12 months > user list averaged ~6 msgs/month over last 12 months > 129 unique posters > > > committer affiliations: > active > pivotal.io > oushu.io > hashdata.cn > occasional > amazon.com > autonomic.ai > confluent.io > datometry.com > hortonworks.com > microsoft.com > petuum.com > privacera.com > qubole.com > snowflake.net > statestreet.com > unifisoftware.com > visa.com > zededa.com > > > Thanks, > Radar > > > > ## Resolution to create a TLP from graduating Incubator podling > > X. Establish the Apache HAWQ 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 Hadoop native SQL query engine that >combines the key technological advantages of MPP database >with the scalability and convenience of Hadoop. > >NOW, THEREFORE, BE IT RESOLVED, that a Project Ma
Re: [DISCUSS] Graduate Apache HAWQ (incubating) as a TLP
Hi Radar, OK, I think I got the answer. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jul 13, 2018 at 2:14 PM, Radar Lei wrote: > Hi Willem, > > I did a check but didn't find the '12 PPMC member' is mentioned, would you > specify which report it is in? The only similar one I found is we mentioned > 'HAWQ New Committers (12)' in ASF Maturity Evaluation > <https://cwiki.apache.org/confluence/display/HAWQ/ASF+Maturity+Evaluation > >. > > For the PMC size 45, we make the proposal because of the total committer > number 45 is pretty close with current PPMC member number 38, so we chose > to make the PMC=Committers as the graduation resolution. > > Hope this answers your question. Thanks. > > > Regards, > Radar > > On Thu, Jul 12, 2018 at 9:22 AM, Willem Jiang > wrote: > > > Just a quick question for the PMC size 45. > > From the report, I can see there are 12 PPMC member, but the PMC size is > > same with the Committer size. > > I guess that could be a typo, am I right? > > > > > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Fri, Jul 6, 2018 at 9:54 AM, Roman Shaposhnik wrote: > > > > > Hi! > > > > > > HAWQ community seems to be ready to graduate. What > > > do fellow IPMC members think? > > > > > > Details on the community are below and here's a link to > > > the DISCUSS thread: > > > https://lists.apache.org/thread.html/ > 67a2d52ef29cbf9e93d8050ed0193c > > > c110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E > > > > > > Thanks, > > > Roman. > > > > > > -- Forwarded message -- > > > From: Radar Lei > > > Date: Tue, Jun 19, 2018 at 2:40 AM > > > Subject: [DISCUSS] Graduate Apache HAWQ (incubating) as a TLP > > > To: dev > > > > > > > > > Hi All, > > > > > > With the 2.3.0.0-incubating release officially out, the Apache HAWQ > > > community and its mentors believe it is time to consider graduation to > > the > > > TLP: > > > https://lists.apache.org/thread.html/b4a0b5671ce377b3d51c9b7 > > > ab00496a1eebfcbf1696ce8b67e078c64@%3Cdev.hawq.apache.org%3E > > > > > > Apache HAWQ entered incubation in September of 2015, since then, the > HAWQ > > > community learned a lot about how to do things in Apache ways. Now we > > have > > > a healthy and engaged community, ready to help with all questions from > > the > > > HAWQ community. We delivered four releases including two binary > releases, > > > now we can do self-driving releases in good cadence. The PPMC has > > > demonstrated a good understanding of growing the community by electing > 12 > > > individuals as committers and PPMC members. The PPMC addressed the > > maturity > > > issues one by one followed by Apache Project Maturity Model, currently > > all > > > the License and IP issues are resolved. This demonstrated our > > understanding > > > of ASF's IP policies. > > > > > > All in all, I believe this project is qualified as a true TLP and we > > should > > > recognize this fact by formally awarding it such a status. This thread > > > means to open up the very same discussion that we had among the mentors > > and > > > HAWQ community to the rest of the IPMC. It is a DISCUSS thread so feel > > free > > > to ask questions. > > > > > > To get you all going, here are a few data points which may help: > > > > > > Project status: > > > http://incubator.apache.org/projects/hawq.html > > > > > > Project website: > > > http://hawq.incubator.apache.org/ > > > > > > Project documentation: > > >http://hawq.incubator.apache.org/docs/userguide/2.3.0.0-inc > > > ubating/overview/HAWQOverview.html > > >http://hawq.apache.org/#download > > > > > > Maturity assessment: > > > https://cwiki.apache.org/confluence/display/HAWQ/ASF+ > Maturity+Evaluation > > > > > > DRAFT of the board resolution is at the bottom of this email > > > > > > Proposed PMC size: 45 members > > > > > > Total number of committers: 45 members > > > > > > PMC affiliation (* indicated chair): > > >Pivotal (20) > > > * Oushu (7) > > >Amazon (3) > > >Hashdata (2) > > >Auton
Re: [VOTE] Graduate Apache HAWQ (incubating)
+1 binding. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Jul 28, 2018 at 10:13 AM, Roman Shaposhnik wrote: > Hi! > > after a very positive discussion in the HAWQ community > and at the IPMC level: > https://lists.apache.org/thread.html/67a2d52ef29cbf9e93d8050ed0193c > c110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E > https://lists.apache.org/thread.html/3a142d758ef5ae119e42107189 > 3615992ea5ee937b5d02007f5e@%3Cgeneral.incubator.apache.org%3E > > I'd like to bring the following resolution for a formal vote. > > Please vote on the resolution pasted below to graduate > Apache HAWQ from the incubator to top level project. > > [ ] +1 Graduate Apache HAWQ from the Incubator. > [ ] +0 Don't care. > [ ] -1 Don't graduate Apache HAWQ from the Incubator because... > > This vote will be open for at least 72 hours. > > Many thanks to our mentors and everyone else for the support, > Roman (on behalf of the Apache HAWQ PPMC). > > ## Resolution to create a TLP from graduating Incubator podling > > X. Establish the Apache HAWQ 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 Hadoop native SQL query engine that >combines the key technological advantages of MPP database >with the scalability and convenience of Hadoop. > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management >Committee (PMC), to be known as the "Apache HAWQ Project", >be and hereby is established pursuant to Bylaws of the >Foundation; and be it further > >RESOLVED, that the Apache HAWQ Project be and hereby is >responsible for the creation and maintenance of software >related to Hadoop native SQL query engine that >combines the key technological advantages of MPP database >with the scalability and convenience of Hadoop; >and be it further > >RESOLVED, that the office of "Vice President, Apache HAWQ" 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 HAWQ Project, and to have primary responsibility >for management of the projects within the scope of >responsibility of the Apache HAWQ 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 HAWQ Project: > > * Alan Gates > * Alexander Denissov > * Amy Bai > * Atri Sharma > * Bhuvnesh Chaudhary > * Bosco > * Chunling Wang > * David Yozie > * Ed Espino > * Entong Shen > * Foyzur Rahman > * Goden Yao > * Gregory Chase > * Hong Wu > * Hongxu Ma > * Hubert Zhang > * Ivan Weng > * Jesse Zhang > * Jiali Yao > * Jun Aoki > * Kavinder Dhaliwal > * Lav Jain > * Lei Chang > * Lili Ma > * Lirong Jian > * Lisa Owen > * Ming Li > * Mohamed Soliman > * Newton Alex > * Noa Horn > * Oleksandr Diachenko > * Paul Guo > * Radar Da Lei > * Roman Shaposhnik > * Ruilong Huo > * Shivram Mani > * Shubham Sharma > * Tushar Pednekar > * Venkatesh Raghavan > * Vineet Goel > * Wen Lin > * Xiang Sheng > * Yi Jin > * Zhanwei Wang > * Zhenglin Tao > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lei Chang >be appointed to the office of Vice President, Apache HAWQ, 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, >
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0
Just forward my +1 (binding) vote from d...@servicecomb.apache.org. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Jul 29, 2018 at 1:50 AM, Mohammad Asif Siddiqui < asifdxtr...@apache.org> wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Service-Center > (Incubating) version 1.0.0 > > Apache ServiceComb (Incubating) Community has voted and approved the > release. > > Vote Thread : https://lists.apache.org/thread.html/ > f17a41eb20f36ca4eea7ed1624ebaf66bc8488ebce819e9207017ae1@% > 3Cdev.servicecomb.apache.org%3E > > Result Thread : https://lists.apache.org/thread.html/ > 43474f7082c63abbfa4a102a30704531d127a810e9c1dc6072b5f4c5@% > 3Cdev.servicecomb.apache.org%3E > > Release Notes : https://github.com/apache/incubator-servicecomb-service- > center/blob/master/docs/release/releaseNotes-1.0.0.md > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-service-center/1.0.0/rc-03/ > > Release Tag : https://github.com/apache/incubator-servicecomb-service- > center/releases/tag/1.0.0 > > Release CommitID : fc38b272a288cf322fa309402a98a89dc6b591f4 > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > Guide to build the release from source : https://github.com/apache/ > incubator-servicecomb-service-center/tree/master/scripts/release > > Voting will start now(Saturday, 28th July, 2018) and will remain open for > at-least 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0 > [ ] +0 No Opinion > [ ] -1 Do not release this package because... > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ServiceComb Java-Chassis (Incubating) version 1.0.0
Just forward my +1 (binding) vote from d...@servicecomb.apache.org. I checked: - hashes and signatures are good - DISCLAIMER exists , NOTICE/LICENSE looks good - can build the kit from source - git tag is write - Running the Company example with the stage repo without any error. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Jul 29, 2018 at 1:41 AM, Mohammad Asif Siddiqui < asifdxtr...@apache.org> wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Java-Chassis > (Incubating) version 1.0.0 > > Apache ServiceComb (Incubating) Community has voted and approved the > release. > > Vote Thread : https://lists.apache.org/thread.html/ > cce5f584cf644e62381440813bda26a1d87a84cb0b5304ae1ebeedd8@% > 3Cdev.servicecomb.apache.org%3E > > Result Thread : https://lists.apache.org/thread.html/ > 8c61031d9c81592440c124b6d6f70fc1e9bb194e465018ea2deeb1a4@% > 3Cdev.servicecomb.apache.org%3E > > Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12321626&version=12342426 > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > servicecomb/incubator-servicecomb-java-chassis/1.0.0/rc-01/ > > Staging Repo : https://repository.apache.org/content/repositories/ > orgapacheservicecomb-1326/ > > Release Tag : https://github.com/apache/incubator-servicecomb-java- > chassis/releases/tag/1.0.0 > > Release CommitID : 2d8645355febc215b33818770ae18468aba6146a > > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > dist/dev/incubator/servicecomb/KEYS > > Voting will start now ( Saturday, 28th July, 2018) and will remain open > for atleast 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5
Hi Sijie I just have a quick question for the apache-pulsar-io-connectors- 2.1.0-incubating-bin.tar.gz. I guess the source is from apache-pulsar-2.1.0-incubating-src.tar.gz, but I need to know how to build this artifact. BTW, it looks like the License of apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz doesn't reflect the bundled third party dependencies. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jul 26, 2018 at 2:17 AM, Sijie Guo wrote: > This is the 5th release candidate for Apache Pulsar, version > 2.1.0-incubating. > > Link to the vote on dev@pulsar list: > https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416 > b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E > > Pulsar is a highly scalable, low latency messaging platform running on > commodity hardware. > It provides simple pub-sub semantics over topics, guaranteed at-least-once > and effective-once delivery of messages, automatic cursor management for > subscribers, and geo-replication. > > This is a feature release, introducing following new features: > > - Pulsar I/O: a serverless connector framework built on top of Pulsar > Functions. > - TieredStorage: offloads bookkeeper ledgers to a cold storage (like S3). > - Stateful Function: Pulsar Functions supports storing state back to > bookkeeper. > - Go Client: a Go client wrapping over existing cpp client. > - Avro and Protobuf schema are supported. > > Full list of changes and fixes are available: > > https://github.com/apache/incubator-pulsar/milestone/13?closed=1 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > Source and binary files: > https://dist.apache.org/repos/dist/dev/incubator/pulsar/ > pulsar-2.1.0-incubating-candidate-5/ > > SHA-1 checksums: > > f0f6b6d7c48d119da36fc4fa1f934fd1f9ba8498 > ./apache-pulsar-2.1.0-incubating-bin.tar.gz > > b6a968249a7c5d21be89ece27895b862efda9a92 > ./apache-pulsar-2.1.0-incubating-src.tar.gz > > ddcf929eb18082ff2b9979507054453e8e803ed3 > ./apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz > > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1025/ > > The tag to be voted upon: > v2.1.0-incubating-candidate-5 (75f79b77f55fbad351cb517e7f3b8ba4ab2dc177) > https://github.com/apache/incubator-pulsar/releases/tag/ > v2.1.0-incubating-candidate-5 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the the source package, and follow the README to build > and run the Pulsar standalone service. > > A few notes for voting 2.1.0 release: > > - For compiling source distribution, use "mvn clean install > -Dmaven.gitcommitid.skip=true > [-DskipTests]". > - Starting from this release, Pulsar is shipping RPM & DEB packages for > pulsar non-java clients. > - Starting from this release, Pulsar is shipping a binary distribution > called `apache-pulsar-io-connectors` > including all built-in connectors. Each connector is packaged with all > their dependencies and > a META-INF/DEPEDENCIES file with licensing information for > all dependencies. > - Since there are a lot of features introduced in 2.1, You can use the > instructions documented in the link for > validating the binary release candidate: > https://github.com/apache/incubator-pulsar/wiki/Release- > Candidate-Validation > > - Sijie >
Re: [VOTE]- Release Apache Weex (Incubating) 0.19.0 [RC3]
+1 (binding) Checking the License and Notice file. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Jul 31, 2018 at 8:03 PM, Hanks Zhang wrote: > Dear IPMC members, > > Since there is no -1 binding here, I think this vote thread should be > continued. > > As discussed before, I revised some messages (SHA and KEYS). > > The SHA of apache-weex-incubating-0.19.0-RC3-src.tar.gz is: > 4BF8D1D5 AA369711 9D16CC9C 52A42DEF 88FDAB97 7044B1B6 415E87AB FAEC435D > 1B1AFCFC > 810B8851 7B98900B 2918C43A D9483D3C C1DBFC72 7BC14E8C 710D86BA > > All KEYS have been added to this file: > https://dist.apache.org/repos/dist/release/incubator/weex/KEYS > > > The vote will be continued until timeout or a necessary number of votes are > reached. > > Please vote accordingly: > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Best Regards, > Hanks >
