Re: [DISCUSS] Marvin-AI Incubator Proposal
Great, thank you... i will update the wiki and send a vote in the morning On Mon, Aug 20, 2018 at 18:15 William Colen wrote: > Luciano, > > Now I can properly volunteer myself as a mentor. > > Thank you > William > > Em seg, 20 de ago de 2018 às 19:37, William Colen > escreveu: > > > Luciano, I am very happy to see this incubation proposal here. I am > > following this project for a while. Knowing the reputation on the > > committees involved and B2W I know it can be very successful. > > I am waiting for the board aproval for joining IPMC. Once approved I > would > > happly volunteer myself as a mentor. > > > > Em seg, 20 de ago de 2018 às 17:45, Luciano Resende < > luckbr1...@gmail.com> > > escreveu: > > > >> We are still looking for one more mentor before we put this proposal to > a > >> vote, any volunteers? > >> > >> On Wed, Aug 15, 2018 at 12:13 PM Luciano Resende > >> wrote: > >> > >> > We would like to start a discussion on accepting Marvin-AI as an > Apache > >> > Incubator project. > >> > > >> > The proposal is available at the incubator wiki, and also copied > below: > >> > https://wiki.apache.org/incubator/Marvin-AI > >> > > >> > As part of the initial due diligence, we have done a preliminary name > >> > search and the results are available on the JIRA below: > >> > > >> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-144 > >> > > >> > We are also looking for two additional mentors. > >> > > >> > > >> > Thanks in advance for your time reviewing and providing feedback. > >> > > >> > === > >> > > >> > = Marvin-AI = > >> > > >> > == Abstract == > >> > > >> > Marvin-AI is an open-source artificial intelligence (AI) platform that > >> > helps data scientists, prototype and productionalize complex solutions > >> with > >> > a scalable, low-latency, language-agnostic, and standardized > >> architecture > >> > while simplifies the process of exploration and modeling. > >> > > >> > == Proposal == > >> > > >> > Marvin helps non-experienced developers create industry-grade AI > >> > applications. It has three core components: a development environment > >> to > >> > be used during data exploration and hypothesis validation (Toolbox), a > >> > library which should be extended to create Marvin engines, and a Scala > >> > application server which interprets engines (Engine Executor). > >> > A basic premise of Marvin is that it should be language-agnostic, able > >> to > >> > interpret engines implemented in different programming languages. > >> > > >> > == Background == > >> > > >> > The Marvin AI project was initiated as an internal project at B2W > >> Digital > >> > (Brazil), the largest e-commerce company in Latin America. Nowadays, > it > >> is > >> > used by all data scientists within the B2W team. Oftentimes, data > >> > scientists don't have an extensive background in software engineering, > >> yet > >> > are in charge of creating AI applications that need to scale to high > >> > throughput and provide millisecond-level response times. At B2W, > Marvin > >> AI > >> > plays an important role in this process, abstracting advanced software > >> > engineering procedures, allowing data scientists to focus on their > >> > knowledge domain. > >> > > >> > == Rationale == > >> > > >> > With recent advances in computer architecture and a corresponding > >> increase > >> > in the amount of data generated by always-connected devices, AI > >> algorithms > >> > offer a solution to problems that have long troubled modern > >> corporations. > >> > Since AI developers come from various fields, such as statistics, > >> physics, > >> > and math, there exists a strong need for platforms which enable them > to > >> > move from prototypes to enterprise applications. Although some tools > >> claim > >> > to offer this service, in reality, there is no reliable open-source > >> > solution. > >> > > >> > == Initial Goals == > >> > > >> > The initial goals will most likely be to merge the existing codebase > >> into > >> > a single repository, migrate it to Apache, and then integrate with the > >> > Apache development process. Furthermore, we plan for incremental > >> > development and releases, as per Apache guidelines. > >> > > >> > == Current Status == > >> > > >> > === Meritocracy === > >> > > >> > Marvin already works under principles of meritocracy. Today, Marvin > >> > already has some contributors that are part of other institutions. > >> Although > >> > there is no formal process defined to become a committer, contributors > >> that > >> > make major changes/improvements to the platform are naturally granted > >> write > >> > access to the repository. > >> > > >> > > >> > === Community === > >> > > >> > Acceptance into the Apache foundation would substantially boost both > >> > Marvin's user and developer communities. The current community > includes > >> a > >> > few experienced developers that have either academic or professional > >> > experience with AI. The community is largely comprised of data >
Re: [DISCUSS] Marvin-AI Incubator Proposal
Luciano, Now I can properly volunteer myself as a mentor. Thank you William Em seg, 20 de ago de 2018 às 19:37, William Colen escreveu: > Luciano, I am very happy to see this incubation proposal here. I am > following this project for a while. Knowing the reputation on the > committees involved and B2W I know it can be very successful. > I am waiting for the board aproval for joining IPMC. Once approved I would > happly volunteer myself as a mentor. > > Em seg, 20 de ago de 2018 às 17:45, Luciano Resende > escreveu: > >> We are still looking for one more mentor before we put this proposal to a >> vote, any volunteers? >> >> On Wed, Aug 15, 2018 at 12:13 PM Luciano Resende >> wrote: >> >> > We would like to start a discussion on accepting Marvin-AI as an Apache >> > Incubator project. >> > >> > The proposal is available at the incubator wiki, and also copied below: >> > https://wiki.apache.org/incubator/Marvin-AI >> > >> > As part of the initial due diligence, we have done a preliminary name >> > search and the results are available on the JIRA below: >> > >> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-144 >> > >> > We are also looking for two additional mentors. >> > >> > >> > Thanks in advance for your time reviewing and providing feedback. >> > >> > === >> > >> > = Marvin-AI = >> > >> > == Abstract == >> > >> > Marvin-AI is an open-source artificial intelligence (AI) platform that >> > helps data scientists, prototype and productionalize complex solutions >> with >> > a scalable, low-latency, language-agnostic, and standardized >> architecture >> > while simplifies the process of exploration and modeling. >> > >> > == Proposal == >> > >> > Marvin helps non-experienced developers create industry-grade AI >> > applications. It has three core components: a development environment >> to >> > be used during data exploration and hypothesis validation (Toolbox), a >> > library which should be extended to create Marvin engines, and a Scala >> > application server which interprets engines (Engine Executor). >> > A basic premise of Marvin is that it should be language-agnostic, able >> to >> > interpret engines implemented in different programming languages. >> > >> > == Background == >> > >> > The Marvin AI project was initiated as an internal project at B2W >> Digital >> > (Brazil), the largest e-commerce company in Latin America. Nowadays, it >> is >> > used by all data scientists within the B2W team. Oftentimes, data >> > scientists don't have an extensive background in software engineering, >> yet >> > are in charge of creating AI applications that need to scale to high >> > throughput and provide millisecond-level response times. At B2W, Marvin >> AI >> > plays an important role in this process, abstracting advanced software >> > engineering procedures, allowing data scientists to focus on their >> > knowledge domain. >> > >> > == Rationale == >> > >> > With recent advances in computer architecture and a corresponding >> increase >> > in the amount of data generated by always-connected devices, AI >> algorithms >> > offer a solution to problems that have long troubled modern >> corporations. >> > Since AI developers come from various fields, such as statistics, >> physics, >> > and math, there exists a strong need for platforms which enable them to >> > move from prototypes to enterprise applications. Although some tools >> claim >> > to offer this service, in reality, there is no reliable open-source >> > solution. >> > >> > == Initial Goals == >> > >> > The initial goals will most likely be to merge the existing codebase >> into >> > a single repository, migrate it to Apache, and then integrate with the >> > Apache development process. Furthermore, we plan for incremental >> > development and releases, as per Apache guidelines. >> > >> > == Current Status == >> > >> > === Meritocracy === >> > >> > Marvin already works under principles of meritocracy. Today, Marvin >> > already has some contributors that are part of other institutions. >> Although >> > there is no formal process defined to become a committer, contributors >> that >> > make major changes/improvements to the platform are naturally granted >> write >> > access to the repository. >> > >> > >> > === Community === >> > >> > Acceptance into the Apache foundation would substantially boost both >> > Marvin's user and developer communities. The current community includes >> a >> > few experienced developers that have either academic or professional >> > experience with AI. The community is largely comprised of data >> scientists >> > working at B2W and other companies such as Cloudera, MIT, Qume Labs, >> > Laguro.com, and CBYK. Also, there is a meetup group of hundreds of >> users >> > who meet regularly to exchange ideas about Marvin and, more generally, >> AI. >> > >> > Reference to the group: https://www.meetup.com/marvin-ai/members/ >> > >> > === Core Developers === >> > >> > The core developers for Marvin are listed in the
Re: Joining the IPMC
Hi - You are an Apache member. You should message your desire to join the IPMC on private@incubator. You can subscribe there as well. IPMC chair will notice and send the usual board@ ACK. This then goes for the usual 72 hours. Regards, Dave Sent from my iPhone > On Aug 20, 2018, at 4:59 PM, r...@apache.org wrote: > > Hey Everyone! > > My appologies for hijacking the general@, guys. I was guided by > https://incubator.apache.org/guides/pmc.html in order to join IPMC but have > not gotten any response so far. I've been asked recently to become one of the > mentors for an upcoming incubation project @ ASF. This is exciting > opportunity and it would be my pleasure to help out as much as I can by > joining IPMC. I would really appreciate if someone could point out the right > procedure. Thank you! > > Best Regards, > Andriy Redko > > > > > - > 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
Joining the IPMC
Hey Everyone! My appologies for hijacking the general@, guys. I was guided by https://incubator.apache.org/guides/pmc.html in order to join IPMC but have not gotten any response so far. I've been asked recently to become one of the mentors for an upcoming incubation project @ ASF. This is exciting opportunity and it would be my pleasure to help out as much as I can by joining IPMC. I would really appreciate if someone could point out the right procedure. Thank you! Best Regards, Andriy Redko - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)
+1 (binding) I checked the source tar with the git tag and the License files. We need to specify the third party dependencies version as they may have different License in different version. Please fix it in next around release. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Aug 12, 2018 at 8:25 PM, Bolke de Bruin wrote: > Hello Incubator PMC’ers, > > The Apache Airflow community has voted and approved the proposal to release > Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate 4. We > now kindly request the Incubator PMC members to review and vote on this > incubator release. > > Airflow is a platform to programmatically author, schedule, and monitor > workflows. Use Airflow to author workflows as directed acyclic graphs > (DAGs) of tasks. The airflow scheduler executes your tasks on an array of > workers while following the specified dependencies. Rich command line > utilities make performing complex surgeries on DAGs a snap. The rich user > interface makes it easy to visualize pipelines running in production, > monitor progress, and troubleshoot issues when needed. When workflows are > defined as code, they become more maintainable, versionable, testable, and > collaborative. > > After a successful IPMC vote Artifacts will be available at: > > https://www.apache.org/dyn/closer.cgi/incubator/airflow < > https://www.apache.org/dyn/closer.cgi/incubator/airflow> > > Public keys are available at: > > https://www.apache.org/dist/incubator/airflow/ < > https://www.apache.org/dist/incubator/airflow/> > > apache-airflow-1.10.0rc4+incubating-source.tar.gz > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > airflow-1.10.0rc4+incubating-source.tar.gz> > > is a source release that comes with INSTALL instructions. Along with it, > for > convenience, find the binary Python "sdist" as > apache-airflow-1.10.0rc4+incubating-bin.tar.gz * > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > airflow-1.10.0rc4+incubating-bin.tar.gz> > > Vote thread: > https://mail-archives.apache.org/mod_mbox/airflow-dev/ > 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < > https://mail-archives.apache.org/mod_mbox/airflow-dev/ > 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> > > Git tag: > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 > > The vote will be open for at least 72 hours and until the necessary number > of > votes are reached. > > Members please be sure to indicate "(Binding)" with your vote which will > help in tallying the vote(s). > > * Here is my +1 (non-binding) * > > Cheers, > Bolke > > * WARNING: Due to licensing requirements you will need to set > SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when > installing or upgrading. We will try to remove this requirement for the > next release. >
Re: [DISCUSS] Marvin-AI Incubator Proposal
Luciano, I am very happy to see this incubation proposal here. I am following this project for a while. Knowing the reputation on the committees involved and B2W I know it can be very successful. I am waiting for the board aproval for joining IPMC. Once approved I would happly volunteer myself as a mentor. Em seg, 20 de ago de 2018 às 17:45, Luciano Resende escreveu: > We are still looking for one more mentor before we put this proposal to a > vote, any volunteers? > > On Wed, Aug 15, 2018 at 12:13 PM Luciano Resende > wrote: > > > We would like to start a discussion on accepting Marvin-AI as an Apache > > Incubator project. > > > > The proposal is available at the incubator wiki, and also copied below: > > https://wiki.apache.org/incubator/Marvin-AI > > > > As part of the initial due diligence, we have done a preliminary name > > search and the results are available on the JIRA below: > > > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-144 > > > > We are also looking for two additional mentors. > > > > > > Thanks in advance for your time reviewing and providing feedback. > > > > === > > > > = Marvin-AI = > > > > == Abstract == > > > > Marvin-AI is an open-source artificial intelligence (AI) platform that > > helps data scientists, prototype and productionalize complex solutions > with > > a scalable, low-latency, language-agnostic, and standardized architecture > > while simplifies the process of exploration and modeling. > > > > == Proposal == > > > > Marvin helps non-experienced developers create industry-grade AI > > applications. It has three core components: a development environment to > > be used during data exploration and hypothesis validation (Toolbox), a > > library which should be extended to create Marvin engines, and a Scala > > application server which interprets engines (Engine Executor). > > A basic premise of Marvin is that it should be language-agnostic, able to > > interpret engines implemented in different programming languages. > > > > == Background == > > > > The Marvin AI project was initiated as an internal project at B2W Digital > > (Brazil), the largest e-commerce company in Latin America. Nowadays, it > is > > used by all data scientists within the B2W team. Oftentimes, data > > scientists don't have an extensive background in software engineering, > yet > > are in charge of creating AI applications that need to scale to high > > throughput and provide millisecond-level response times. At B2W, Marvin > AI > > plays an important role in this process, abstracting advanced software > > engineering procedures, allowing data scientists to focus on their > > knowledge domain. > > > > == Rationale == > > > > With recent advances in computer architecture and a corresponding > increase > > in the amount of data generated by always-connected devices, AI > algorithms > > offer a solution to problems that have long troubled modern corporations. > > Since AI developers come from various fields, such as statistics, > physics, > > and math, there exists a strong need for platforms which enable them to > > move from prototypes to enterprise applications. Although some tools > claim > > to offer this service, in reality, there is no reliable open-source > > solution. > > > > == Initial Goals == > > > > The initial goals will most likely be to merge the existing codebase into > > a single repository, migrate it to Apache, and then integrate with the > > Apache development process. Furthermore, we plan for incremental > > development and releases, as per Apache guidelines. > > > > == Current Status == > > > > === Meritocracy === > > > > Marvin already works under principles of meritocracy. Today, Marvin > > already has some contributors that are part of other institutions. > Although > > there is no formal process defined to become a committer, contributors > that > > make major changes/improvements to the platform are naturally granted > write > > access to the repository. > > > > > > === Community === > > > > Acceptance into the Apache foundation would substantially boost both > > Marvin's user and developer communities. The current community includes a > > few experienced developers that have either academic or professional > > experience with AI. The community is largely comprised of data scientists > > working at B2W and other companies such as Cloudera, MIT, Qume Labs, > > Laguro.com, and CBYK. Also, there is a meetup group of hundreds of users > > who meet regularly to exchange ideas about Marvin and, more generally, > AI. > > > > Reference to the group: https://www.meetup.com/marvin-ai/members/ > > > > === Core Developers === > > > > The core developers for Marvin are listed in the contributor's list and > > initial PPMC below. These lists include B2W employees, MIT students, > UFSCAR > > researchers, independent contributors, and some employees of other > > companies like Cloudera, Qume Labs, Laguro.com, and CBYK. > > > > === Alignment === > > > > The initial committers
Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)
Hi Bolke The general approach I have used in the past is to find the correct "comment" syntax to allow addition of the license text such that it does not break the language parser. For markdown, that would mean just using an html comment. thanks Hitesh On Mon, Aug 20, 2018 at 10:56 AM Bolke de Bruin wrote: > Appreciated Hitesh. Do you know how to add headers to .MD files? There > seems to be no technical standard way[1]. Is there a way to solve this > elegantly? > > Cheers > Bolke > > [1] > https://alvinalexander.com/technology/markdown-comments-syntax-not-in-generated-output > > > > Sent from my iPhone > > > On 20 Aug 2018, at 19:48, Hitesh Shah wrote: > > > > +1 (binding) > > > > Ran through the basic checks. > > > > Minor nit which can be fixed in the next release: there are a bunch of > > documentation files which could have a license header added (e.g. .md, > > .rst, ) > > > > thanks > > Hitesh > > > >> On Mon, Aug 20, 2018 at 4:08 AM Bolke de Bruin > wrote: > >> > >> Sorry Willem that should be of course. Apologies. > >> > >> Sent from my iPhone > >> > >>> On 20 Aug 2018, at 13:07, Bolke de Bruin wrote: > >>> > >>> Hi William > >>> > >>> You seem to be missing a "4" at the end of the URL? Ah it seems that my > >> original email had a quirk. Would you mind using the below? > >>> > >>> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc4 > >>> > >>> Thanks! > >>> Bolke > >>> > >>> Sent from my iPhone > >>> > On 20 Aug 2018, at 13:03, Willem Jiang > wrote: > > Hi, > > The Git tag cannot be accessed. I can only get the 404 error there. > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > On Sun, Aug 12, 2018 at 8:25 PM, Bolke de Bruin > >> wrote: > > > > Hello Incubator PMC’ers, > > > > The Apache Airflow community has voted and approved the proposal to > >> release > > Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate > >> 4. We > > now kindly request the Incubator PMC members to review and vote on > this > > incubator release. > > > > Airflow is a platform to programmatically author, schedule, and > monitor > > workflows. Use Airflow to author workflows as directed acyclic graphs > > (DAGs) of tasks. The airflow scheduler executes your tasks on an > array > >> of > > workers while following the specified dependencies. Rich command line > > utilities make performing complex surgeries on DAGs a snap. The rich > >> user > > interface makes it easy to visualize pipelines running in production, > > monitor progress, and troubleshoot issues when needed. When workflows > >> are > > defined as code, they become more maintainable, versionable, > testable, > >> and > > collaborative. > > > > After a successful IPMC vote Artifacts will be available at: > > > > https://www.apache.org/dyn/closer.cgi/incubator/airflow < > > https://www.apache.org/dyn/closer.cgi/incubator/airflow> > > > > Public keys are available at: > > > > https://www.apache.org/dist/incubator/airflow/ < > > https://www.apache.org/dist/incubator/airflow/> > > > > apache-airflow-1.10.0rc4+incubating-source.tar.gz > > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > > 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < > > > >> > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > > airflow-1.10.0rc4+incubating-source.tar.gz> > > > > is a source release that comes with INSTALL instructions. Along with > >> it, > > for > > convenience, find the binary Python "sdist" as > > apache-airflow-1.10.0rc4+incubating-bin.tar.gz * > > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > > 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < > > > >> > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > > airflow-1.10.0rc4+incubating-bin.tar.gz> > > > > Vote thread: > > https://mail-archives.apache.org/mod_mbox/airflow-dev/ > > 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < > > https://mail-archives.apache.org/mod_mbox/airflow-dev/ > > 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> > > > > Git tag: > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 > > > > The vote will be open for at least 72 hours and until the necessary > >> number > > of > > votes are reached. > > > > Members please be sure to indicate "(Binding)" with your vote which > >> will > > help in tallying the vote(s). > > > > * Here is my +1 (non-binding) * > > > > Cheers, > > Bolke > > > > * WARNING: Due t
Re: [DISCUSS] Marvin-AI Incubator Proposal
We are still looking for one more mentor before we put this proposal to a vote, any volunteers? On Wed, Aug 15, 2018 at 12:13 PM Luciano Resende wrote: > We would like to start a discussion on accepting Marvin-AI as an Apache > Incubator project. > > The proposal is available at the incubator wiki, and also copied below: > https://wiki.apache.org/incubator/Marvin-AI > > As part of the initial due diligence, we have done a preliminary name > search and the results are available on the JIRA below: > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-144 > > We are also looking for two additional mentors. > > > Thanks in advance for your time reviewing and providing feedback. > > === > > = Marvin-AI = > > == Abstract == > > Marvin-AI is an open-source artificial intelligence (AI) platform that > helps data scientists, prototype and productionalize complex solutions with > a scalable, low-latency, language-agnostic, and standardized architecture > while simplifies the process of exploration and modeling. > > == Proposal == > > Marvin helps non-experienced developers create industry-grade AI > applications. It has three core components: a development environment to > be used during data exploration and hypothesis validation (Toolbox), a > library which should be extended to create Marvin engines, and a Scala > application server which interprets engines (Engine Executor). > A basic premise of Marvin is that it should be language-agnostic, able to > interpret engines implemented in different programming languages. > > == Background == > > The Marvin AI project was initiated as an internal project at B2W Digital > (Brazil), the largest e-commerce company in Latin America. Nowadays, it is > used by all data scientists within the B2W team. Oftentimes, data > scientists don't have an extensive background in software engineering, yet > are in charge of creating AI applications that need to scale to high > throughput and provide millisecond-level response times. At B2W, Marvin AI > plays an important role in this process, abstracting advanced software > engineering procedures, allowing data scientists to focus on their > knowledge domain. > > == Rationale == > > With recent advances in computer architecture and a corresponding increase > in the amount of data generated by always-connected devices, AI algorithms > offer a solution to problems that have long troubled modern corporations. > Since AI developers come from various fields, such as statistics, physics, > and math, there exists a strong need for platforms which enable them to > move from prototypes to enterprise applications. Although some tools claim > to offer this service, in reality, there is no reliable open-source > solution. > > == Initial Goals == > > The initial goals will most likely be to merge the existing codebase into > a single repository, migrate it to Apache, and then integrate with the > Apache development process. Furthermore, we plan for incremental > development and releases, as per Apache guidelines. > > == Current Status == > > === Meritocracy === > > Marvin already works under principles of meritocracy. Today, Marvin > already has some contributors that are part of other institutions. Although > there is no formal process defined to become a committer, contributors that > make major changes/improvements to the platform are naturally granted write > access to the repository. > > > === Community === > > Acceptance into the Apache foundation would substantially boost both > Marvin's user and developer communities. The current community includes a > few experienced developers that have either academic or professional > experience with AI. The community is largely comprised of data scientists > working at B2W and other companies such as Cloudera, MIT, Qume Labs, > Laguro.com, and CBYK. Also, there is a meetup group of hundreds of users > who meet regularly to exchange ideas about Marvin and, more generally, AI. > > Reference to the group: https://www.meetup.com/marvin-ai/members/ > > === Core Developers === > > The core developers for Marvin are listed in the contributor's list and > initial PPMC below. These lists include B2W employees, MIT students, UFSCAR > researchers, independent contributors, and some employees of other > companies like Cloudera, Qume Labs, Laguro.com, and CBYK. > > === Alignment === > > The initial committers strongly believe that by being part of the Apache > Software Foundation, Marvin AI will be part of a comprehensive suite for AI > applications that can process big data and enable enterprises to extract > value from their data lakes. Also, we hope that by integrating with other > Apache projects such as Apache Spark, Apache Hadoop; that this will foster > additional collaboration between these projects furthering the already > existing integration points and expanding the community of contributors. > > > == Known Risks == > > === Orphaned products === > > Given the current maturity of Marvin and how w
Re: [VOTE] Retire Gossip podling
Josh, can we close this vote? -Taylor > On Aug 10, 2018, at 12:22 PM, Josh Elser wrote: > > Thanks, Taylor. Appreciate that! > > On 8/9/18 8:51 PM, P. Taylor Goetz wrote: >> +1 (binding) >> As the champion for this project, I’ll volunteer to take care of the >> retirement tasks. >> -Taylor >>> On Aug 9, 2018, at 6:52 PM, Josh Elser wrote: >>> >>> Hi, >>> >>> The Gossip podling has voted to retire from incubation. >>> >>> DISCUSS: >>> https://lists.apache.org/thread.html/8acab107a15a6bc50253cb20aa633a3ac36b70364294f149660fc6c4@%3Cdev.gossip.apache.org%3E >>> VOTE: >>> https://lists.apache.org/thread.html/d725e5f03ecbd516613b9a75abd9178936e578b38c3793933f571caf@%3Cdev.gossip.apache.org%3E >>> >>> Please see the relevant discussion and vote threads from the dev list >>> above. This is not a unanimous decision (one dissenting voice out of 7), >>> but the podling has been operating with little to no activity for about a >>> year. As such, I think this is the right path forward with the >>> understanding that Gossip can return to the Incubator in the future if >>> there is renewed interest in the project. >>> >>> Please vote to ratify this request for retirement. We'll keep this open for >>> at least 72hrs as customary (until 2018/08/12 2300 GMT). >>> >>> Here is my +1 (binding) >>> >>> - Josh >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > signature.asc Description: Message signed with OpenPGP
[jira] [Updated] (INCUBATOR-217) The release of OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy
[ https://issues.apache.org/jira/browse/INCUBATOR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Hou updated INCUBATOR-217: -- Summary: The release of OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy (was: The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy) > The release of OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy > -- > > Key: INCUBATOR-217 > URL: https://issues.apache.org/jira/browse/INCUBATOR-217 > Project: Incubator > Issue Type: Task >Reporter: Vincent Hou >Priority: Major > > OpenWhisk community is working on its first release 0.9.8-incubating of > OpenWhisk wskdeploy under Apache. An email for VOTE will be sent to the dev > mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache > OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-217) The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy
[ https://issues.apache.org/jira/browse/INCUBATOR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Hou updated INCUBATOR-217: -- Description: OpenWhisk community is working on its first release 0.9.8-incubating of OpenWhisk wskdeploy under Apache. An email for VOTE will be sent to the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy. (was: OpenWhisk community is working on its first release 0.9.0-incubating of OpenWhisk wskdeploy under Apache. An email for VOTE will be sent to the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy.) > The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy > --- > > Key: INCUBATOR-217 > URL: https://issues.apache.org/jira/browse/INCUBATOR-217 > Project: Incubator > Issue Type: Task >Reporter: Vincent Hou >Priority: Major > > OpenWhisk community is working on its first release 0.9.8-incubating of > OpenWhisk wskdeploy under Apache. An email for VOTE will be sent to the dev > mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache > OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-217) The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy
[ https://issues.apache.org/jira/browse/INCUBATOR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Hou updated INCUBATOR-217: -- Summary: The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy (was: The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy and Catalog) > The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy > --- > > Key: INCUBATOR-217 > URL: https://issues.apache.org/jira/browse/INCUBATOR-217 > Project: Incubator > Issue Type: Task >Reporter: Vincent Hou >Priority: Major > > OpenWhisk community is working on its first release 0.9.0-incubating of > OpenWhisk wskdeploy and catalog under Apache. An email for VOTE will be sent > to the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release > Apache OpenWhisk 0.9.0-incubating: main OpenWhisk wskdeploy and Catalog. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-217) The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy
[ https://issues.apache.org/jira/browse/INCUBATOR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Hou updated INCUBATOR-217: -- Description: OpenWhisk community is working on its first release 0.9.0-incubating of OpenWhisk wskdeploy under Apache. An email for VOTE will be sent to the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy. (was: OpenWhisk community is working on its first release 0.9.0-incubating of OpenWhisk wskdeploy and catalog under Apache. An email for VOTE will be sent to the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk wskdeploy and Catalog.) > The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy > --- > > Key: INCUBATOR-217 > URL: https://issues.apache.org/jira/browse/INCUBATOR-217 > Project: Incubator > Issue Type: Task >Reporter: Vincent Hou >Priority: Major > > OpenWhisk community is working on its first release 0.9.0-incubating of > OpenWhisk wskdeploy under Apache. An email for VOTE will be sent to the dev > mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache > OpenWhisk 0.9.8-incubating: OpenWhisk wskdeploy. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept DLab into the Apache Incubator
Sigh, mea culpa I missed this VOTE thread. Better late than never : +1 (binding) - Henry On Mon, Aug 20, 2018, 8:13 AM P. Taylor Goetz wrote: > The 72 hour voting period has elapsed, and with 4 binding +1 votes and no > -1 or 0 votes this vote passes. > > Vote tally (* indicates a binding vote): > > +1: > - Dave Fisher* > - Ted Dunning* > - P. Taylor Goetz* > - Matt Sicker* > > Thanks to all who voted. I will begin the bootstrapping process shortly. > > -Taylor > > > On Aug 15, 2018, at 12:27 PM, P. Taylor Goetz > wrote: > > > > After a brief discussion [1] I would like to call a VOTE to accept DLab > into the Apache Incubator. The full proposal is available on the wiki[2] > and is pasted below in text form as well. > > > > This vote will run at least 72 hours. Please VOTE as follows: > > > > [ ] +1 Accept DLab into the Apache Incubator > > [ ] +0 No opinion > > [ ] -1 Do not accept DLab into the Apache Incubator because… > > > > -Taylor > > > > [1] > https://lists.apache.org/thread.html/9c96873d49f53da33260e21dc698f7c9b82eec256caf97a0e3f54943@%3Cgeneral.incubator.apache.org%3E > > [2] https://wiki.apache.org/incubator/DLabProposal > > > > > > = DLab Proposal = > > > > == Abstract == > > DLab is a platform for creating self-service, exploratory data science > environments in the cloud using best-of-breed data science tools. > > > > DLab includes a self-service web console, used to create and manage > exploratory environments. It allows teams to spin up analytical > environments with just a single click of a mouse. Once established, the > environment can be managed by an analytical team itself, leveraging simple > and easy-to-use web-based interface. > > > > == Proposal == > > In order to work effectively, data scientists rely on a varying suite of > analytics tools that are readily available. However, many of those tools > are non-trivial to set up in terms of hardware provisioning, software > installation, configuration, and deployment. Setting up a collaborative, > multi-tenant development environment for data scientists consumes > substantial IT and DevOps resources, as well as time. These factors often > combine to hinder the agility and effectiveness of data science teams > within an organization. Current solutions are largely closed source and/or > proprietary, and committing to a given solution introduces the potential > for vendor lock-in. > > > > EPAM Systems developed DLab in response to the lack of open source, > permissibly licensed solutions to better enable data science workflows. The > ALv2 was selected to encourage open development and user adoption. DLab was > open sourced on Dec 29, 2016 and is under active development with support > from EPAM Systems. > > > > We believe DLab is a unique solution with no current open source > equivalent. Our primary goals of incubation are to grow and diversify the > DLab community to ensure its long-term sustainability. > > > > == Rationale == > > DLab is a platform that provides data scientists with the ability to > self-provision, without IT support, exploratory and production environments > with their preferred set of tools installed and pre-configured. Tool > options include, but are not limited to: > > > > * Apache Spark > > * Apache Flink (planned) > > * Apache Zeppelin > > * Jupyter > > * TensorFlow + Jupyter > > * Deep Learning + Jupyter > > > > DLab leverages cloud computing providers for virtual hardware > provisioning and currently supports the following: > > > > * Amazon Web Services (AWS) > > * Microsoft Azure > > * Google Compute Platform (GCP) (under development) > > > > DLab offers git-based collaboration tools for data scientists and > developers and integrates with the following git service providers: > > > > * GItHub > > * GitLab > > * BitBucket > > > > Additionally, DLab includes the option to configure the UnGit tool in an > environment to facilitate collaboration. > > Finally, DLab integrates closely with many security and SSO offerings, > including: > > > > * LDAP > > * Microsoft Active Directory > > * AWS Identity Access Management service > > > > DLab was designed from the ground up to be highly configurable, > flexible, and extensible platform. We believe these qualities will > encourage community growth by enabling contributors to easily add new > integrations and extensions. > > > > == Initial Goals == > > The initial goal will be to move the existing codebase to Apache and > integrate with the Apache development process and infrastructure. A primary > goal of incubation will be to grow and diversify the DLab PPMC. We are well > aware that the project community is comprised of individuals from a single > company. We aim to change that during incubation. > > > > == Current Status == > > As previously mentioned, DLab is under active development at EPAM > Systems, and is being used in a number of production deployments: > > > > * [An investment company] is using DLab as an AWS-based analytics > platform for their data scie
[jira] [Resolved] (INCUBATOR-215) The release of OpenWhisk 0.9.0-incubating: OpenWhisk client go and CLI
[ https://issues.apache.org/jira/browse/INCUBATOR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Hou resolved INCUBATOR-215. --- Resolution: Fixed > The release of OpenWhisk 0.9.0-incubating: OpenWhisk client go and CLI > -- > > Key: INCUBATOR-215 > URL: https://issues.apache.org/jira/browse/INCUBATOR-215 > Project: Incubator > Issue Type: Task >Reporter: Vincent Hou >Priority: Major > > OpenWhisk community is working on its first release 0.9.0-incubating of > OpenWhisk client go and cli under Apache. An email for VOTE will be sent to > the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release > Apache OpenWhisk 0.9.0-incubating: main OpenWhisk client go and CLI. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-215) The release of OpenWhisk 0.9.0-incubating: OpenWhisk client go and CLI
[ https://issues.apache.org/jira/browse/INCUBATOR-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586404#comment-16586404 ] Vincent Hou commented on INCUBATOR-215: --- [http://openwhisk.incubator.apache.org/downloads.html] After the votes by openwhisk binding members and Apache IPMC members, Client go library and CLI have been released for the version 0.9.0. > The release of OpenWhisk 0.9.0-incubating: OpenWhisk client go and CLI > -- > > Key: INCUBATOR-215 > URL: https://issues.apache.org/jira/browse/INCUBATOR-215 > Project: Incubator > Issue Type: Task >Reporter: Vincent Hou >Priority: Major > > OpenWhisk community is working on its first release 0.9.0-incubating of > OpenWhisk client go and cli under Apache. An email for VOTE will be sent to > the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release > Apache OpenWhisk 0.9.0-incubating: main OpenWhisk client go and CLI. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept DLab into the Apache Incubator
Awesome. Thanks Cos. I’ll add you as a mentor. -Taylor > On Aug 20, 2018, at 2:11 PM, Konstantin Boudnik wrote: > > Looks like I am bit late and vote is closed, but I still want to cast > my +1 - I have helped this project during my time at EPAM and wish it > all the success! > > If the project needs more mentors at this point - I have some spare > cycles to burn. > > Thanks! > -- > With regards, > Konstantin (Cos) Boudnik > 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 > > Disclaimer: Opinions expressed in this email are those of the author, > and do not necessarily represent the views of any company the author > might be affiliated with at the moment of writing. > > > On Mon, Aug 20, 2018 at 6:13 PM, P. Taylor Goetz wrote: >> The 72 hour voting period has elapsed, and with 4 binding +1 votes and no -1 >> or 0 votes this vote passes. >> >> Vote tally (* indicates a binding vote): >> >> +1: >> - Dave Fisher* >> - Ted Dunning* >> - P. Taylor Goetz* >> - Matt Sicker* >> >> Thanks to all who voted. I will begin the bootstrapping process shortly. >> >> -Taylor >> >>> On Aug 15, 2018, at 12:27 PM, P. Taylor Goetz wrote: >>> >>> After a brief discussion [1] I would like to call a VOTE to accept DLab >>> into the Apache Incubator. The full proposal is available on the wiki[2] >>> and is pasted below in text form as well. >>> >>> This vote will run at least 72 hours. Please VOTE as follows: >>> >>> [ ] +1 Accept DLab into the Apache Incubator >>> [ ] +0 No opinion >>> [ ] -1 Do not accept DLab into the Apache Incubator because… >>> >>> -Taylor >>> >>> [1] >>> https://lists.apache.org/thread.html/9c96873d49f53da33260e21dc698f7c9b82eec256caf97a0e3f54943@%3Cgeneral.incubator.apache.org%3E >>> [2] https://wiki.apache.org/incubator/DLabProposal >>> >>> >>> = DLab Proposal = >>> >>> == Abstract == >>> DLab is a platform for creating self-service, exploratory data science >>> environments in the cloud using best-of-breed data science tools. >>> >>> DLab includes a self-service web console, used to create and manage >>> exploratory environments. It allows teams to spin up analytical >>> environments with just a single click of a mouse. Once established, the >>> environment can be managed by an analytical team itself, leveraging simple >>> and easy-to-use web-based interface. >>> >>> == Proposal == >>> In order to work effectively, data scientists rely on a varying suite of >>> analytics tools that are readily available. However, many of those tools >>> are non-trivial to set up in terms of hardware provisioning, software >>> installation, configuration, and deployment. Setting up a collaborative, >>> multi-tenant development environment for data scientists consumes >>> substantial IT and DevOps resources, as well as time. These factors often >>> combine to hinder the agility and effectiveness of data science teams >>> within an organization. Current solutions are largely closed source and/or >>> proprietary, and committing to a given solution introduces the potential >>> for vendor lock-in. >>> >>> EPAM Systems developed DLab in response to the lack of open source, >>> permissibly licensed solutions to better enable data science workflows. The >>> ALv2 was selected to encourage open development and user adoption. DLab was >>> open sourced on Dec 29, 2016 and is under active development with support >>> from EPAM Systems. >>> >>> We believe DLab is a unique solution with no current open source >>> equivalent. Our primary goals of incubation are to grow and diversify the >>> DLab community to ensure its long-term sustainability. >>> >>> == Rationale == >>> DLab is a platform that provides data scientists with the ability to >>> self-provision, without IT support, exploratory and production environments >>> with their preferred set of tools installed and pre-configured. Tool >>> options include, but are not limited to: >>> >>> * Apache Spark >>> * Apache Flink (planned) >>> * Apache Zeppelin >>> * Jupyter >>> * TensorFlow + Jupyter >>> * Deep Learning + Jupyter >>> >>> DLab leverages cloud computing providers for virtual hardware provisioning >>> and currently supports the following: >>> >>> * Amazon Web Services (AWS) >>> * Microsoft Azure >>> * Google Compute Platform (GCP) (under development) >>> >>> DLab offers git-based collaboration tools for data scientists and >>> developers and integrates with the following git service providers: >>> >>> * GItHub >>> * GitLab >>> * BitBucket >>> >>> Additionally, DLab includes the option to configure the UnGit tool in an >>> environment to facilitate collaboration. >>> Finally, DLab integrates closely with many security and SSO offerings, >>> including: >>> >>> * LDAP >>> * Microsoft Active Directory >>> * AWS Identity Access Management service >>> >>> DLab was designed from the ground up to be highly configurable, flexible, >>> and extensible platform. We believe these qualities will encourage >>> community
Re: [PROPOSAL] Zipkin for Apache Incubator
+1 Glad to see zipkin showing up on the incubator doorstep. I echo Andrew's remarks. OpenZipkin is bringing not only code with vintage, but a healthy community too. I foresee a short trip to TLP. If you need mentors, I'd be a bit of an "absent dad", but could help around setup at least or if there are questions Apach'ing. Thanks, St.Ack P.S. The gitbox repo offerings should make it so you can retain your github-based process. On Fri, Aug 17, 2018 at 2:30 AM Adrian Cole wrote: > I would like to propose Zipkin as an Apache Incubator project. > > The text of the proposal can be found below as well as on the Incubator > wiki: > > https://wiki.apache.org/incubator/ZipkinProposal > > I believe we should have 3 mentors.. currently we have 2 (plus Wu > Sheng and I who are familiar but not mentor-grade :P). If another > person can volunteer to mentor us, would be sweet. > > -Adrian > > = Abstract = > Zipkin is a distributed tracing system. It helps gather timing data > needed to troubleshoot latency problems in microservice architectures. > It manages both the collection and lookup of this data. Zipkin’s > design is based on the Google Dapper paper. > > = Proposal = > Zipkin provides a defined data model and payload type for distributed > trace data collection. It also provides an UI and http api for > querying the data. Its server implements this api and includes > abstractions for storage and transport of trace payloads. The > combination of these parts avoid lock-in to a specific tracing > backend. For example, Zipkin includes integration with different open > source storage mechanisms like Apache Cassandra and Elasticsearch. It > also includes bridges to convert collected data and forward it to > service offerings such as Amazon X-Ray and Google Stackdriver. > Ecosystem offering extend this portability further. > > While primarily focused on the system, Zipkin also includes tracing > libraries which applications use to report timing information. > Zipkin's core organization includes tracer libraries written in Java, > Javascript, Go, PHP and Ruby. These libraries use the formats > mentioned above to report data, as well "B3" which is a header format > needed to send trace identifiers along with production requests. Many > Zipkin libraries can also send data directly to other services such as > Amazon X-Ray and Google Stackdriver, skipping any Zipkin > infrastructure. There are also more Zipkin tracing libraries outside > the core organization than inside it. This is due to the "OpenZipkin" > culture of promoting ecosystem work. > > = Background = > Zipkin began in 2012 at Twitter during a time they were investigating > performance problems underlying the "fail whale" seen by users. The > name Zipkin is from the Turkish word for harpoon: the harpoon that > will kill the failures! Incidentally, Zipkin was not the first tracing > system, it had roots in a former system at Twitter named > BigBrotherBird. It is due to BigBrotherBird that the de-facto tracing > headers we still use today include the prefix "X-B3". > > In 2015, a community of users noticed the project was not healthy in > so far as it hadn't progressed and often didn't accept pull requests, > and the Cassandra backend was stuck on an unmaintained library. For > example, the Apache Incubator H-Trace project started in some ways as > a reaction to the inability to customize the code. The root cause of > this was Twitter moving to internal storage (Manhattan) and also the > project not being managed as a product. By mid 2015, the community > regrouped as OpenZipkin and the codebase moved from Twitter to an org > also named OpenZipkin. This led to fast progress on concerns including > initially a server rewrite and Docker based deployment. > > In 2018, the second version of the data model completed, and along the > way, many new libraries became standard, including javascript, golang > and PHP. The community is dramatically larger than 2015, and Zipkin > remains the most popular tracing system despite heavy competition. > > = Rationale = > Zipkin is a de-facto distributed tracing system, which is more > important as architectures become more fine grained due to popularity > of microservice or even serverless architectures. Applications > transition to use more complex communication including asynchronous > code and service mesh, increasing the need for tools that visualize > the behavior of requests as they map across an architecture. > > Zipkin's server is focused only on distributed tracing. It is meant to > be used alongside existing logging and metrics systems. Generally, the > community optimizes brown field concerns such as interop over breaking > changes such as experimental features. The combination of code and > community make Zipkin a safe and easier choice for various sites to > introduce or grow their observability practice. > > = Initial Goals = > The initial goals are to mature OpenZipkin's community process. For > example, while O
Re: [PROPOSAL] Zipkin for Apache Incubator
+1 After the retirement of the HTrace podling to the attic we are facing a fragmentation or removal of distributed tracing capabilities from a set of related projects (Hadoop, HBase, and Phoenix) that could really use it. When considering a replacement I think if the replacement was also a project under the Apache umbrella this would increase confidence, and I think we can expect a better result with an incubation of Zipkin than we had with HTrace. Sadly, HTrace didn't get off the ground because it failed to develop a sustainable community, yet distributed tracing is so important we took a risk on adopting a early stage podling with an uncertain future. Zipkin is a better bet, given its maturity as software, significant adoption to date, and existing community. A slam dunk, IMHO. On Fri, Aug 17, 2018 at 2:30 AM Adrian Cole wrote: > I would like to propose Zipkin as an Apache Incubator project. > > The text of the proposal can be found below as well as on the Incubator > wiki: > > https://wiki.apache.org/incubator/ZipkinProposal > > I believe we should have 3 mentors.. currently we have 2 (plus Wu > Sheng and I who are familiar but not mentor-grade :P). If another > person can volunteer to mentor us, would be sweet. > > -Adrian > > = Abstract = > Zipkin is a distributed tracing system. It helps gather timing data > needed to troubleshoot latency problems in microservice architectures. > It manages both the collection and lookup of this data. Zipkin’s > design is based on the Google Dapper paper. > > = Proposal = > Zipkin provides a defined data model and payload type for distributed > trace data collection. It also provides an UI and http api for > querying the data. Its server implements this api and includes > abstractions for storage and transport of trace payloads. The > combination of these parts avoid lock-in to a specific tracing > backend. For example, Zipkin includes integration with different open > source storage mechanisms like Apache Cassandra and Elasticsearch. It > also includes bridges to convert collected data and forward it to > service offerings such as Amazon X-Ray and Google Stackdriver. > Ecosystem offering extend this portability further. > > While primarily focused on the system, Zipkin also includes tracing > libraries which applications use to report timing information. > Zipkin's core organization includes tracer libraries written in Java, > Javascript, Go, PHP and Ruby. These libraries use the formats > mentioned above to report data, as well "B3" which is a header format > needed to send trace identifiers along with production requests. Many > Zipkin libraries can also send data directly to other services such as > Amazon X-Ray and Google Stackdriver, skipping any Zipkin > infrastructure. There are also more Zipkin tracing libraries outside > the core organization than inside it. This is due to the "OpenZipkin" > culture of promoting ecosystem work. > > = Background = > Zipkin began in 2012 at Twitter during a time they were investigating > performance problems underlying the "fail whale" seen by users. The > name Zipkin is from the Turkish word for harpoon: the harpoon that > will kill the failures! Incidentally, Zipkin was not the first tracing > system, it had roots in a former system at Twitter named > BigBrotherBird. It is due to BigBrotherBird that the de-facto tracing > headers we still use today include the prefix "X-B3". > > In 2015, a community of users noticed the project was not healthy in > so far as it hadn't progressed and often didn't accept pull requests, > and the Cassandra backend was stuck on an unmaintained library. For > example, the Apache Incubator H-Trace project started in some ways as > a reaction to the inability to customize the code. The root cause of > this was Twitter moving to internal storage (Manhattan) and also the > project not being managed as a product. By mid 2015, the community > regrouped as OpenZipkin and the codebase moved from Twitter to an org > also named OpenZipkin. This led to fast progress on concerns including > initially a server rewrite and Docker based deployment. > > In 2018, the second version of the data model completed, and along the > way, many new libraries became standard, including javascript, golang > and PHP. The community is dramatically larger than 2015, and Zipkin > remains the most popular tracing system despite heavy competition. > > = Rationale = > Zipkin is a de-facto distributed tracing system, which is more > important as architectures become more fine grained due to popularity > of microservice or even serverless architectures. Applications > transition to use more complex communication including asynchronous > code and service mesh, increasing the need for tools that visualize > the behavior of requests as they map across an architecture. > > Zipkin's server is focused only on distributed tracing. It is meant to > be used alongside existing logging and metrics systems. Generally, the > community op
Re: [RESULT] [VOTE] Accept DLab into the Apache Incubator
Looks like I am bit late and vote is closed, but I still want to cast my +1 - I have helped this project during my time at EPAM and wish it all the success! If the project needs more mentors at this point - I have some spare cycles to burn. Thanks! -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing. On Mon, Aug 20, 2018 at 6:13 PM, P. Taylor Goetz wrote: > The 72 hour voting period has elapsed, and with 4 binding +1 votes and no -1 > or 0 votes this vote passes. > > Vote tally (* indicates a binding vote): > > +1: > - Dave Fisher* > - Ted Dunning* > - P. Taylor Goetz* > - Matt Sicker* > > Thanks to all who voted. I will begin the bootstrapping process shortly. > > -Taylor > >> On Aug 15, 2018, at 12:27 PM, P. Taylor Goetz wrote: >> >> After a brief discussion [1] I would like to call a VOTE to accept DLab into >> the Apache Incubator. The full proposal is available on the wiki[2] and is >> pasted below in text form as well. >> >> This vote will run at least 72 hours. Please VOTE as follows: >> >> [ ] +1 Accept DLab into the Apache Incubator >> [ ] +0 No opinion >> [ ] -1 Do not accept DLab into the Apache Incubator because… >> >> -Taylor >> >> [1] >> https://lists.apache.org/thread.html/9c96873d49f53da33260e21dc698f7c9b82eec256caf97a0e3f54943@%3Cgeneral.incubator.apache.org%3E >> [2] https://wiki.apache.org/incubator/DLabProposal >> >> >> = DLab Proposal = >> >> == Abstract == >> DLab is a platform for creating self-service, exploratory data science >> environments in the cloud using best-of-breed data science tools. >> >> DLab includes a self-service web console, used to create and manage >> exploratory environments. It allows teams to spin up analytical environments >> with just a single click of a mouse. Once established, the environment can >> be managed by an analytical team itself, leveraging simple and easy-to-use >> web-based interface. >> >> == Proposal == >> In order to work effectively, data scientists rely on a varying suite of >> analytics tools that are readily available. However, many of those tools are >> non-trivial to set up in terms of hardware provisioning, software >> installation, configuration, and deployment. Setting up a collaborative, >> multi-tenant development environment for data scientists consumes >> substantial IT and DevOps resources, as well as time. These factors often >> combine to hinder the agility and effectiveness of data science teams within >> an organization. Current solutions are largely closed source and/or >> proprietary, and committing to a given solution introduces the potential for >> vendor lock-in. >> >> EPAM Systems developed DLab in response to the lack of open source, >> permissibly licensed solutions to better enable data science workflows. The >> ALv2 was selected to encourage open development and user adoption. DLab was >> open sourced on Dec 29, 2016 and is under active development with support >> from EPAM Systems. >> >> We believe DLab is a unique solution with no current open source equivalent. >> Our primary goals of incubation are to grow and diversify the DLab community >> to ensure its long-term sustainability. >> >> == Rationale == >> DLab is a platform that provides data scientists with the ability to >> self-provision, without IT support, exploratory and production environments >> with their preferred set of tools installed and pre-configured. Tool options >> include, but are not limited to: >> >> * Apache Spark >> * Apache Flink (planned) >> * Apache Zeppelin >> * Jupyter >> * TensorFlow + Jupyter >> * Deep Learning + Jupyter >> >> DLab leverages cloud computing providers for virtual hardware provisioning >> and currently supports the following: >> >> * Amazon Web Services (AWS) >> * Microsoft Azure >> * Google Compute Platform (GCP) (under development) >> >> DLab offers git-based collaboration tools for data scientists and developers >> and integrates with the following git service providers: >> >> * GItHub >> * GitLab >> * BitBucket >> >> Additionally, DLab includes the option to configure the UnGit tool in an >> environment to facilitate collaboration. >> Finally, DLab integrates closely with many security and SSO offerings, >> including: >> >> * LDAP >> * Microsoft Active Directory >> * AWS Identity Access Management service >> >> DLab was designed from the ground up to be highly configurable, flexible, >> and extensible platform. We believe these qualities will encourage community >> growth by enabling contributors to easily add new integrations and >> extensions. >> >> == Initial Goals == >> The initial goal will be to move the existing codebase to Apache and >> integrate with the Apache development process and infrastructure. A primary >> goal of incubation wil
[jira] [Updated] (INCUBATOR-217) The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy and Catalog
[ https://issues.apache.org/jira/browse/INCUBATOR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Hou updated INCUBATOR-217: -- Description: OpenWhisk community is working on its first release 0.9.0-incubating of OpenWhisk wskdeploy and catalog under Apache. An email for VOTE will be sent to the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release Apache OpenWhisk 0.9.0-incubating: main OpenWhisk wskdeploy and Catalog. > The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy and Catalog > --- > > Key: INCUBATOR-217 > URL: https://issues.apache.org/jira/browse/INCUBATOR-217 > Project: Incubator > Issue Type: Task >Reporter: Vincent Hou >Priority: Major > > OpenWhisk community is working on its first release 0.9.0-incubating of > OpenWhisk wskdeploy and catalog under Apache. An email for VOTE will be sent > to the dev mail list of OpenWhisk momentarily, with the title [VOTE] Release > Apache OpenWhisk 0.9.0-incubating: main OpenWhisk wskdeploy and Catalog. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Release Airflow 1.10.0
The vote to release Airflow 1.10.0-incubating, having been open for 8 days is now closed. There were three binding +1s and no -1 votes. +1 (binding): Justin Mclean Jakob Homan Hitesh Shah The release is approved. Thanks to all those who voted. Bolke Sent from my iPhone Begin forwarded message: > From: Bolke de Bruin > Date: 20 August 2018 at 19:56:23 CEST > To: general@incubator.apache.org > Subject: Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4) > > Appreciated Hitesh. Do you know how to add headers to .MD files? There seems > to be no technical standard way[1]. Is there a way to solve this elegantly? > > Cheers > Bolke > > [1] > https://alvinalexander.com/technology/markdown-comments-syntax-not-in-generated-output > > > > Sent from my iPhone > >> On 20 Aug 2018, at 19:48, Hitesh Shah wrote: >> >> +1 (binding) >> >> Ran through the basic checks. >> >> Minor nit which can be fixed in the next release: there are a bunch of >> documentation files which could have a license header added (e.g. .md, >> .rst, ) >> >> thanks >> Hitesh >> >>> On Mon, Aug 20, 2018 at 4:08 AM Bolke de Bruin wrote: >>> >>> Sorry Willem that should be of course. Apologies. >>> >>> Sent from my iPhone >>> On 20 Aug 2018, at 13:07, Bolke de Bruin wrote: Hi William You seem to be missing a "4" at the end of the URL? Ah it seems that my >>> original email had a quirk. Would you mind using the below? https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc4 Thanks! Bolke Sent from my iPhone > On 20 Aug 2018, at 13:03, Willem Jiang wrote: > > Hi, > > The Git tag cannot be accessed. I can only get the 404 error there. > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > >> On Sun, Aug 12, 2018 at 8:25 PM, Bolke de Bruin >>> wrote: >> >> Hello Incubator PMC’ers, >> >> The Apache Airflow community has voted and approved the proposal to >>> release >> Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate >>> 4. We >> now kindly request the Incubator PMC members to review and vote on this >> incubator release. >> >> Airflow is a platform to programmatically author, schedule, and monitor >> workflows. Use Airflow to author workflows as directed acyclic graphs >> (DAGs) of tasks. The airflow scheduler executes your tasks on an array >>> of >> workers while following the specified dependencies. Rich command line >> utilities make performing complex surgeries on DAGs a snap. The rich >>> user >> interface makes it easy to visualize pipelines running in production, >> monitor progress, and troubleshoot issues when needed. When workflows >>> are >> defined as code, they become more maintainable, versionable, testable, >>> and >> collaborative. >> >> After a successful IPMC vote Artifacts will be available at: >> >> https://www.apache.org/dyn/closer.cgi/incubator/airflow < >> https://www.apache.org/dyn/closer.cgi/incubator/airflow> >> >> Public keys are available at: >> >> https://www.apache.org/dist/incubator/airflow/ < >> https://www.apache.org/dist/incubator/airflow/> >> >> apache-airflow-1.10.0rc4+incubating-source.tar.gz >> >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. >> 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < >> >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- >> airflow-1.10.0rc4+incubating-source.tar.gz> >> >> is a source release that comes with INSTALL instructions. Along with >>> it, >> for >> convenience, find the binary Python "sdist" as >> apache-airflow-1.10.0rc4+incubating-bin.tar.gz * >> >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. >> 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < >> >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- >> airflow-1.10.0rc4+incubating-bin.tar.gz> >> >> Vote thread: >> https://mail-archives.apache.org/mod_mbox/airflow-dev/ >> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < >> https://mail-archives.apache.org/mod_mbox/airflow-dev/ >> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> >> >> Git tag: >> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < >> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 >> >> The vote will be open for at least 72 hours and until the necessary >>> number >> of >> votes are reached. >> >> Members please be sure to indicate "(Binding)" with your vote which >>> will >> help in tallying the vote(s). >> >> * Here is my +1 (non-binding) * >>
[jira] [Created] (INCUBATOR-217) The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy and Catalog
Vincent Hou created INCUBATOR-217: - Summary: The release of OpenWhisk 0.9.0-incubating: OpenWhisk wskdeploy and Catalog Key: INCUBATOR-217 URL: https://issues.apache.org/jira/browse/INCUBATOR-217 Project: Incubator Issue Type: Task Reporter: Vincent Hou -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)
Appreciated Hitesh. Do you know how to add headers to .MD files? There seems to be no technical standard way[1]. Is there a way to solve this elegantly? Cheers Bolke [1] https://alvinalexander.com/technology/markdown-comments-syntax-not-in-generated-output Sent from my iPhone > On 20 Aug 2018, at 19:48, Hitesh Shah wrote: > > +1 (binding) > > Ran through the basic checks. > > Minor nit which can be fixed in the next release: there are a bunch of > documentation files which could have a license header added (e.g. .md, > .rst, ) > > thanks > Hitesh > >> On Mon, Aug 20, 2018 at 4:08 AM Bolke de Bruin wrote: >> >> Sorry Willem that should be of course. Apologies. >> >> Sent from my iPhone >> >>> On 20 Aug 2018, at 13:07, Bolke de Bruin wrote: >>> >>> Hi William >>> >>> You seem to be missing a "4" at the end of the URL? Ah it seems that my >> original email had a quirk. Would you mind using the below? >>> >>> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc4 >>> >>> Thanks! >>> Bolke >>> >>> Sent from my iPhone >>> On 20 Aug 2018, at 13:03, Willem Jiang wrote: Hi, The Git tag cannot be accessed. I can only get the 404 error there. https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc Willem Jiang Twitter: willemjiang Weibo: 姜宁willem > On Sun, Aug 12, 2018 at 8:25 PM, Bolke de Bruin >> wrote: > > Hello Incubator PMC’ers, > > The Apache Airflow community has voted and approved the proposal to >> release > Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate >> 4. We > now kindly request the Incubator PMC members to review and vote on this > incubator release. > > Airflow is a platform to programmatically author, schedule, and monitor > workflows. Use Airflow to author workflows as directed acyclic graphs > (DAGs) of tasks. The airflow scheduler executes your tasks on an array >> of > workers while following the specified dependencies. Rich command line > utilities make performing complex surgeries on DAGs a snap. The rich >> user > interface makes it easy to visualize pipelines running in production, > monitor progress, and troubleshoot issues when needed. When workflows >> are > defined as code, they become more maintainable, versionable, testable, >> and > collaborative. > > After a successful IPMC vote Artifacts will be available at: > > https://www.apache.org/dyn/closer.cgi/incubator/airflow < > https://www.apache.org/dyn/closer.cgi/incubator/airflow> > > Public keys are available at: > > https://www.apache.org/dist/incubator/airflow/ < > https://www.apache.org/dist/incubator/airflow/> > > apache-airflow-1.10.0rc4+incubating-source.tar.gz > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < > >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > airflow-1.10.0rc4+incubating-source.tar.gz> > > is a source release that comes with INSTALL instructions. Along with >> it, > for > convenience, find the binary Python "sdist" as > apache-airflow-1.10.0rc4+incubating-bin.tar.gz * > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < > >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > airflow-1.10.0rc4+incubating-bin.tar.gz> > > Vote thread: > https://mail-archives.apache.org/mod_mbox/airflow-dev/ > 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < > https://mail-archives.apache.org/mod_mbox/airflow-dev/ > 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> > > Git tag: > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 > > The vote will be open for at least 72 hours and until the necessary >> number > of > votes are reached. > > Members please be sure to indicate "(Binding)" with your vote which >> will > help in tallying the vote(s). > > * Here is my +1 (non-binding) * > > Cheers, > Bolke > > * WARNING: Due to licensing requirements you will need to set > SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when > installing or upgrading. We will try to remove this requirement for the > next release. > >>
Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)
+1 (binding) Ran through the basic checks. Minor nit which can be fixed in the next release: there are a bunch of documentation files which could have a license header added (e.g. .md, .rst, ) thanks Hitesh On Mon, Aug 20, 2018 at 4:08 AM Bolke de Bruin wrote: > Sorry Willem that should be of course. Apologies. > > Sent from my iPhone > > > On 20 Aug 2018, at 13:07, Bolke de Bruin wrote: > > > > Hi William > > > > You seem to be missing a "4" at the end of the URL? Ah it seems that my > original email had a quirk. Would you mind using the below? > > > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc4 > > > > Thanks! > > Bolke > > > > Sent from my iPhone > > > >> On 20 Aug 2018, at 13:03, Willem Jiang wrote: > >> > >> Hi, > >> > >> The Git tag cannot be accessed. I can only get the 404 error there. > >> > >> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc > >> > >> > >> Willem Jiang > >> > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >>> On Sun, Aug 12, 2018 at 8:25 PM, Bolke de Bruin > wrote: > >>> > >>> Hello Incubator PMC’ers, > >>> > >>> The Apache Airflow community has voted and approved the proposal to > release > >>> Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate > 4. We > >>> now kindly request the Incubator PMC members to review and vote on this > >>> incubator release. > >>> > >>> Airflow is a platform to programmatically author, schedule, and monitor > >>> workflows. Use Airflow to author workflows as directed acyclic graphs > >>> (DAGs) of tasks. The airflow scheduler executes your tasks on an array > of > >>> workers while following the specified dependencies. Rich command line > >>> utilities make performing complex surgeries on DAGs a snap. The rich > user > >>> interface makes it easy to visualize pipelines running in production, > >>> monitor progress, and troubleshoot issues when needed. When workflows > are > >>> defined as code, they become more maintainable, versionable, testable, > and > >>> collaborative. > >>> > >>> After a successful IPMC vote Artifacts will be available at: > >>> > >>> https://www.apache.org/dyn/closer.cgi/incubator/airflow < > >>> https://www.apache.org/dyn/closer.cgi/incubator/airflow> > >>> > >>> Public keys are available at: > >>> > >>> https://www.apache.org/dist/incubator/airflow/ < > >>> https://www.apache.org/dist/incubator/airflow/> > >>> > >>> apache-airflow-1.10.0rc4+incubating-source.tar.gz > >>> > >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > >>> 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < > >>> > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > >>> airflow-1.10.0rc4+incubating-source.tar.gz> > >>> > >>> is a source release that comes with INSTALL instructions. Along with > it, > >>> for > >>> convenience, find the binary Python "sdist" as > >>> apache-airflow-1.10.0rc4+incubating-bin.tar.gz * > >>> > >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > >>> 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < > >>> > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > >>> airflow-1.10.0rc4+incubating-bin.tar.gz> > >>> > >>> Vote thread: > >>> https://mail-archives.apache.org/mod_mbox/airflow-dev/ > >>> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < > >>> https://mail-archives.apache.org/mod_mbox/airflow-dev/ > >>> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> > >>> > >>> Git tag: > >>> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < > >>> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 > >>> > >>> The vote will be open for at least 72 hours and until the necessary > number > >>> of > >>> votes are reached. > >>> > >>> Members please be sure to indicate "(Binding)" with your vote which > will > >>> help in tallying the vote(s). > >>> > >>> * Here is my +1 (non-binding) * > >>> > >>> Cheers, > >>> Bolke > >>> > >>> * WARNING: Due to licensing requirements you will need to set > >>> SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when > >>> installing or upgrading. We will try to remove this requirement for the > >>> next release. > >>> >
Re: [PROPOSAL] Zipkin for Apache Incubator
+1 Here, I hope that the structure helps the community as a whole get involved in changes as they are happening. - Brian
[jira] [Resolved] (INCUBATOR-131) airflow installation issue
[
https://issues.apache.org/jira/browse/INCUBATOR-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved INCUBATOR-131.
Resolution: Invalid
> airflow installation issue
> --
>
> Key: INCUBATOR-131
> URL: https://issues.apache.org/jira/browse/INCUBATOR-131
> Project: Incubator
> Issue Type: Bug
>Reporter: Afroz Hussain
>Priority: Major
>
> Before I tell you about my issue, let me describe my Airflow environment:
> Python Version: Python 2.6.6(tried on 2.7)
> Operating System: RedHat 6.5(tried on RedHat 7.5)
> Python packages: argparse==1.2.1 aws-cfn-bootstrap==1.3
> backports.ssl-match-hostname==3.4.0.2 boto==2.34.0 cas==0.15 chardet==2.0.1
> Cheetah==2.4.1 cloud-init==0.7.2 configobj==4.6.0 ethtool==0.6
> freeipa==2.0.0a0 iniparse==0.3.1 iotop==0.3.2 ipapython==3.0.0 iwlib==1.0
> kerberos==1.1 lockfile==0.9.1 lxml==2.2.3 M2Crypto==0.20.2 Markdown==2.0.1
> matplotlib==0.99.1.1 netaddr==0.7.5 nose==0.10.4 numpy==1.4.1
> ordereddict==1.2 paramiko==1.7.5 policycoreutils-default-encoding==0.1
> prettytable==0.6.1 pycparser==2.14 pycrypto==2.0.1 pycurl==7.19.0
> Pygments==1.1.1 pygpgme==0.1 pyOpenSSL==0.10 pystache==0.5.4
> python-daemon==1.5.5 python-dateutil==1.4.1 python-default-encoding==0.1
> python-dmidecode==3.10.13 python-ldap==2.3.10 python-nss==0.16.0 pytz===2010h
> PyYAML==3.10 requests==1.1.0 rhnlib==2.5.22 rhsm==1.12.5 setools==1.0
> simplejson==2.0.9 six==1.9.0 SSSDConfig==1.12.4 urlgrabber==3.9.1
> urllib3==1.5 yum-metadata-parser==1.1.2
> I am unable to install airflow using "pip install airflow", getting errors as:
> RHEL 6
> Complete output from command python setup.py egg_info:
> Traceback (most recent call last):
> File "", line 1, in
> File "/tmp/pip-build-bI9hiv/pandas/setup.py", line 631, in
> **setuptools_kwargs)
> File "/usr/lib64/python2.6/distutils/core.py", line 113, in setup
> setup_distribution = dist = klass(attrs)
> File "/usr/lib/python2.6/site-packages/setuptools/dist.py", line 221, in
> __init_
> self.fetch_build_eggs(attrs.pop('setup_requires'))
> File "/usr/lib/python2.6/site-packages/setuptools/dist.py", line 245, in
> fetch_build_eggs
> parse_requirements(requires), installer=self.fetch_build_egg
> File "/usr/lib/python2.6/site-packages/pkg_resources.py", line 550, in resolve
> raise VersionConflict(dist,req) # XXX put more info here
> pkg_resources.VersionConflict: (numpy 1.4.1
> (/usr/lib64/python2.6/site-packages), Requirement.parse('numpy>=1.7.0'))
>
> Command "python setup.py egg_info" failed with error code 1 in
> /tmp/pip-build-bI9hiv/pandas
> RHEL 7:
> Complete output from command python setup.py egg_info:
> Running from numpy source directory.
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/setup.py:327: UserWarning: Unrecognized
> setuptools command, proceeding with generating Cython sources and expanding
> templates
> warnings.warn("Unrecognized setuptools command, proceeding with "
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1640:
> UserWarning:
> Atlas (http://math-atlas.sourceforge.net/) libraries not found.
> Directories to search for the libraries can be specified in the
> numpy/distutils/site.cfg file (section [atlas]) or by setting
> the ATLAS environment variable.
> warnings.warn(AtlasNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1649:
> UserWarning:
> Blas (http://www.netlib.org/blas/) libraries not found.
> Directories to search for the libraries can be specified in the
> numpy/distutils/site.cfg file (section [blas]) or by setting
> the BLAS environment variable.
> warnings.warn(BlasNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1652:
> UserWarning:
> Blas (http://www.netlib.org/blas/) sources not found.
> Directories to search for the sources can be specified in the
> numpy/distutils/site.cfg file (section [blas_src]) or by setting
> the BLAS_SRC environment variable.
> warnings.warn(BlasSrcNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1542:
> UserWarning:
> Atlas (http://math-atlas.sourceforge.net/) libraries not found.
> Directories to search for the libraries can be specified in the
> numpy/distutils/site.cfg file (section [atlas]) or by setting
> the ATLAS environment variable.
> warnings.warn(AtlasNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1553:
> UserWarning:
> Lapack (http://www.netlib.org/lapack/) libraries not found.
> Directories to search for the libraries can be specified in the
> numpy/distutils/site.cfg file (section [lapack]) or by setting
> the LAPACK environment variable.
> warnings.warn(LapackNotFoundError.doc)
> /tmp/easy_install-9Yjxgb/numpy-1.11.0/numpy/distutils/system_info.py:1556:
> UserWarning:
Re: [PROPOSAL] Zipkin for Apache Incubator
+1 on the proposal from me. If accepted, I look forward to how the Apache process and community can further strengthen Zipkin and how we can collaborate more. While I have shared some reservations previously about changes in process and policy that will be needed for the Apache release process, I think it is a reasonable change for the long term and I'm willing to adapt and learn. On Sat, Aug 18, 2018, 16:46 José Carlos Chávez wrote: > As expressed many times through different channels, I am strong +1 to this. > I think this new age at zipkin will be so beneficial for the community. > > On 2018/08/17 09:29:47, Adrian Cole wrote: > > I would like to propose Zipkin as an Apache Incubator project.> > > > > The text of the proposal can be found below as well as on the Incubator > wiki:> > > > > https://wiki.apache.org/incubator/ZipkinProposal> > > > > I believe we should have 3 mentors.. currently we have 2 (plus Wu> > > Sheng and I who are familiar but not mentor-grade :P). If another> > > person can volunteer to mentor us, would be sweet.> > > > > -Adrian> > > > > > -- > > *José Carlos* >
[RESULT] [VOTE] Accept DLab into the Apache Incubator
The 72 hour voting period has elapsed, and with 4 binding +1 votes and no -1 or 0 votes this vote passes. Vote tally (* indicates a binding vote): +1: - Dave Fisher* - Ted Dunning* - P. Taylor Goetz* - Matt Sicker* Thanks to all who voted. I will begin the bootstrapping process shortly. -Taylor > On Aug 15, 2018, at 12:27 PM, P. Taylor Goetz wrote: > > After a brief discussion [1] I would like to call a VOTE to accept DLab into > the Apache Incubator. The full proposal is available on the wiki[2] and is > pasted below in text form as well. > > This vote will run at least 72 hours. Please VOTE as follows: > > [ ] +1 Accept DLab into the Apache Incubator > [ ] +0 No opinion > [ ] -1 Do not accept DLab into the Apache Incubator because… > > -Taylor > > [1] > https://lists.apache.org/thread.html/9c96873d49f53da33260e21dc698f7c9b82eec256caf97a0e3f54943@%3Cgeneral.incubator.apache.org%3E > [2] https://wiki.apache.org/incubator/DLabProposal > > > = DLab Proposal = > > == Abstract == > DLab is a platform for creating self-service, exploratory data science > environments in the cloud using best-of-breed data science tools. > > DLab includes a self-service web console, used to create and manage > exploratory environments. It allows teams to spin up analytical environments > with just a single click of a mouse. Once established, the environment can be > managed by an analytical team itself, leveraging simple and easy-to-use > web-based interface. > > == Proposal == > In order to work effectively, data scientists rely on a varying suite of > analytics tools that are readily available. However, many of those tools are > non-trivial to set up in terms of hardware provisioning, software > installation, configuration, and deployment. Setting up a collaborative, > multi-tenant development environment for data scientists consumes substantial > IT and DevOps resources, as well as time. These factors often combine to > hinder the agility and effectiveness of data science teams within an > organization. Current solutions are largely closed source and/or proprietary, > and committing to a given solution introduces the potential for vendor > lock-in. > > EPAM Systems developed DLab in response to the lack of open source, > permissibly licensed solutions to better enable data science workflows. The > ALv2 was selected to encourage open development and user adoption. DLab was > open sourced on Dec 29, 2016 and is under active development with support > from EPAM Systems. > > We believe DLab is a unique solution with no current open source equivalent. > Our primary goals of incubation are to grow and diversify the DLab community > to ensure its long-term sustainability. > > == Rationale == > DLab is a platform that provides data scientists with the ability to > self-provision, without IT support, exploratory and production environments > with their preferred set of tools installed and pre-configured. Tool options > include, but are not limited to: > > * Apache Spark > * Apache Flink (planned) > * Apache Zeppelin > * Jupyter > * TensorFlow + Jupyter > * Deep Learning + Jupyter > > DLab leverages cloud computing providers for virtual hardware provisioning > and currently supports the following: > > * Amazon Web Services (AWS) > * Microsoft Azure > * Google Compute Platform (GCP) (under development) > > DLab offers git-based collaboration tools for data scientists and developers > and integrates with the following git service providers: > > * GItHub > * GitLab > * BitBucket > > Additionally, DLab includes the option to configure the UnGit tool in an > environment to facilitate collaboration. > Finally, DLab integrates closely with many security and SSO offerings, > including: > > * LDAP > * Microsoft Active Directory > * AWS Identity Access Management service > > DLab was designed from the ground up to be highly configurable, flexible, and > extensible platform. We believe these qualities will encourage community > growth by enabling contributors to easily add new integrations and extensions. > > == Initial Goals == > The initial goal will be to move the existing codebase to Apache and > integrate with the Apache development process and infrastructure. A primary > goal of incubation will be to grow and diversify the DLab PPMC. We are well > aware that the project community is comprised of individuals from a single > company. We aim to change that during incubation. > > == Current Status == > As previously mentioned, DLab is under active development at EPAM Systems, > and is being used in a number of production deployments: > > * [An investment company] is using DLab as an AWS-based analytics platform > for their data scientists to provide a convenient way to perform multi-tenant > data analytics. This enables data scientists to easily provision work > environments with integrated data sources based on Elasticsearch, Apache > HBase, and Neo4j, and utilizing Apache
Re: [PROPOSAL] Zipkin for Apache Incubator
That's less chucklesome then but still a good proposal. 5 points from Gryffindor for not changing boilerplate. On 8/20/2018 7:56 AM, Jim Jagielski wrote: > That's boilerplate: > >https://incubator.apache.org/guides/proposal.html >https://wiki.apache.org/incubator/ProjectProposals > >> On Aug 17, 2018, at 9:58 AM, Kevin A. McGrail wrote: >> >> Have to say this made me chuckle: >> >> >> A Excessive Fascination with the Apache Brand >> >> I'm +1 on this proposal. > > - > 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: [PROPOSAL] Zipkin for Apache Incubator
That's boilerplate: https://incubator.apache.org/guides/proposal.html https://wiki.apache.org/incubator/ProjectProposals > On Aug 17, 2018, at 9:58 AM, Kevin A. McGrail wrote: > > Have to say this made me chuckle: > > > A Excessive Fascination with the Apache Brand > > I'm +1 on this proposal. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)
Sorry Willem that should be of course. Apologies. Sent from my iPhone > On 20 Aug 2018, at 13:07, Bolke de Bruin wrote: > > Hi William > > You seem to be missing a "4" at the end of the URL? Ah it seems that my > original email had a quirk. Would you mind using the below? > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc4 > > Thanks! > Bolke > > Sent from my iPhone > >> On 20 Aug 2018, at 13:03, Willem Jiang wrote: >> >> Hi, >> >> The Git tag cannot be accessed. I can only get the 404 error there. >> >> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc >> >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >>> On Sun, Aug 12, 2018 at 8:25 PM, Bolke de Bruin wrote: >>> >>> Hello Incubator PMC’ers, >>> >>> The Apache Airflow community has voted and approved the proposal to release >>> Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate 4. We >>> now kindly request the Incubator PMC members to review and vote on this >>> incubator release. >>> >>> Airflow is a platform to programmatically author, schedule, and monitor >>> workflows. Use Airflow to author workflows as directed acyclic graphs >>> (DAGs) of tasks. The airflow scheduler executes your tasks on an array of >>> workers while following the specified dependencies. Rich command line >>> utilities make performing complex surgeries on DAGs a snap. The rich user >>> interface makes it easy to visualize pipelines running in production, >>> monitor progress, and troubleshoot issues when needed. When workflows are >>> defined as code, they become more maintainable, versionable, testable, and >>> collaborative. >>> >>> After a successful IPMC vote Artifacts will be available at: >>> >>> https://www.apache.org/dyn/closer.cgi/incubator/airflow < >>> https://www.apache.org/dyn/closer.cgi/incubator/airflow> >>> >>> Public keys are available at: >>> >>> https://www.apache.org/dist/incubator/airflow/ < >>> https://www.apache.org/dist/incubator/airflow/> >>> >>> apache-airflow-1.10.0rc4+incubating-source.tar.gz >>> >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. >>> 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- >>> airflow-1.10.0rc4+incubating-source.tar.gz> >>> >>> is a source release that comes with INSTALL instructions. Along with it, >>> for >>> convenience, find the binary Python "sdist" as >>> apache-airflow-1.10.0rc4+incubating-bin.tar.gz * >>> >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. >>> 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < >>> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- >>> airflow-1.10.0rc4+incubating-bin.tar.gz> >>> >>> Vote thread: >>> https://mail-archives.apache.org/mod_mbox/airflow-dev/ >>> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < >>> https://mail-archives.apache.org/mod_mbox/airflow-dev/ >>> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> >>> >>> Git tag: >>> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < >>> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 >>> >>> The vote will be open for at least 72 hours and until the necessary number >>> of >>> votes are reached. >>> >>> Members please be sure to indicate "(Binding)" with your vote which will >>> help in tallying the vote(s). >>> >>> * Here is my +1 (non-binding) * >>> >>> Cheers, >>> Bolke >>> >>> * WARNING: Due to licensing requirements you will need to set >>> SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when >>> installing or upgrading. We will try to remove this requirement for the >>> next release. >>>
Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)
Hi William You seem to be missing a "4" at the end of the URL? Ah it seems that my original email had a quirk. Would you mind using the below? https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc4 Thanks! Bolke Sent from my iPhone > On 20 Aug 2018, at 13:03, Willem Jiang wrote: > > Hi, > > The Git tag cannot be accessed. I can only get the 404 error there. > > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > >> On Sun, Aug 12, 2018 at 8:25 PM, Bolke de Bruin wrote: >> >> Hello Incubator PMC’ers, >> >> The Apache Airflow community has voted and approved the proposal to release >> Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate 4. We >> now kindly request the Incubator PMC members to review and vote on this >> incubator release. >> >> Airflow is a platform to programmatically author, schedule, and monitor >> workflows. Use Airflow to author workflows as directed acyclic graphs >> (DAGs) of tasks. The airflow scheduler executes your tasks on an array of >> workers while following the specified dependencies. Rich command line >> utilities make performing complex surgeries on DAGs a snap. The rich user >> interface makes it easy to visualize pipelines running in production, >> monitor progress, and troubleshoot issues when needed. When workflows are >> defined as code, they become more maintainable, versionable, testable, and >> collaborative. >> >> After a successful IPMC vote Artifacts will be available at: >> >> https://www.apache.org/dyn/closer.cgi/incubator/airflow < >> https://www.apache.org/dyn/closer.cgi/incubator/airflow> >> >> Public keys are available at: >> >> https://www.apache.org/dist/incubator/airflow/ < >> https://www.apache.org/dist/incubator/airflow/> >> >> apache-airflow-1.10.0rc4+incubating-source.tar.gz >> >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. >> 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- >> airflow-1.10.0rc4+incubating-source.tar.gz> >> >> is a source release that comes with INSTALL instructions. Along with it, >> for >> convenience, find the binary Python "sdist" as >> apache-airflow-1.10.0rc4+incubating-bin.tar.gz * >> >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1. >> 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < >> https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- >> airflow-1.10.0rc4+incubating-bin.tar.gz> >> >> Vote thread: >> https://mail-archives.apache.org/mod_mbox/airflow-dev/ >> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < >> https://mail-archives.apache.org/mod_mbox/airflow-dev/ >> 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> >> >> Git tag: >> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < >> https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 >> >> The vote will be open for at least 72 hours and until the necessary number >> of >> votes are reached. >> >> Members please be sure to indicate "(Binding)" with your vote which will >> help in tallying the vote(s). >> >> * Here is my +1 (non-binding) * >> >> Cheers, >> Bolke >> >> * WARNING: Due to licensing requirements you will need to set >> SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when >> installing or upgrading. We will try to remove this requirement for the >> next release. >>
Re: [VOTE] Release Airflow 1.10.0 (new vote based on rc4)
Hi, The Git tag cannot be accessed. I can only get the 404 error there. https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Aug 12, 2018 at 8:25 PM, Bolke de Bruin wrote: > Hello Incubator PMC’ers, > > The Apache Airflow community has voted and approved the proposal to release > Apache Airflow 1.10.0 (incubating) based on 1.10.0 Release Candidate 4. We > now kindly request the Incubator PMC members to review and vote on this > incubator release. > > Airflow is a platform to programmatically author, schedule, and monitor > workflows. Use Airflow to author workflows as directed acyclic graphs > (DAGs) of tasks. The airflow scheduler executes your tasks on an array of > workers while following the specified dependencies. Rich command line > utilities make performing complex surgeries on DAGs a snap. The rich user > interface makes it easy to visualize pipelines running in production, > monitor progress, and troubleshoot issues when needed. When workflows are > defined as code, they become more maintainable, versionable, testable, and > collaborative. > > After a successful IPMC vote Artifacts will be available at: > > https://www.apache.org/dyn/closer.cgi/incubator/airflow < > https://www.apache.org/dyn/closer.cgi/incubator/airflow> > > Public keys are available at: > > https://www.apache.org/dist/incubator/airflow/ < > https://www.apache.org/dist/incubator/airflow/> > > apache-airflow-1.10.0rc4+incubating-source.tar.gz > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > 10.0rc4/apache-airflow-1.10.0rc4+incubating-source.tar.gz < > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > airflow-1.10.0rc4+incubating-source.tar.gz> > > is a source release that comes with INSTALL instructions. Along with it, > for > convenience, find the binary Python "sdist" as > apache-airflow-1.10.0rc4+incubating-bin.tar.gz * > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1. > 10.0rc4/apache-airflow-1.10.0rc4+incubating-bin.tar.gz < > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.10.0rc4/apache- > airflow-1.10.0rc4+incubating-bin.tar.gz> > > Vote thread: > https://mail-archives.apache.org/mod_mbox/airflow-dev/ > 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E < > https://mail-archives.apache.org/mod_mbox/airflow-dev/ > 201807.mbox/%3c4ab16d90-7184-4c05-a125-fbc5c5af7...@gmail.com%3E> > > Git tag: > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc < > https://github.com/apache/incubator-airflow/releases/tag/1.10.0rc>4 > > The vote will be open for at least 72 hours and until the necessary number > of > votes are reached. > > Members please be sure to indicate "(Binding)" with your vote which will > help in tallying the vote(s). > > * Here is my +1 (non-binding) * > > Cheers, > Bolke > > * WARNING: Due to licensing requirements you will need to set > SLUGIFY_USES_TEXT_UNIDECODE=yes in your environment when > installing or upgrading. We will try to remove this requirement for the > next release. >
[jira] [Closed] (INCUBATOR-216) Request to open circleci for SkyWalking project
[ https://issues.apache.org/jira/browse/INCUBATOR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Wu closed INCUBATOR-216. -- Resolution: Invalid > Request to open circleci for SkyWalking project > --- > > Key: INCUBATOR-216 > URL: https://issues.apache.org/jira/browse/INCUBATOR-216 > Project: Incubator > Issue Type: Wish >Reporter: Sheng Wu >Priority: Major > > For better to run CI for the project, we want to try to use > [https://circleci.com/] > Could you open this for the following GitHub repositories > [https://github.com/apache/incubator-skywalking] > [https://github.com/apache/incubator-skywalking-oal-tool] > [https://github.com/apache/incubator-skywalking-ui] > > And make me(GitHub [https://github.com/wu-sheng)] could edit the circleci > settings for these repositories. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Unomi 1.3.0-incubating release [TAKE2]
Hi Justin, Thanks a lot for the review! On Tue, Aug 14, 2018 at 10:20 AM Justin Mclean wrote: > > Hi, > > I’m a little confused why the directory in the source zip is called > unomi-root-1.3.0-incubating. Because of the current build process, I rename the project source manually at the end, but I think we could improve this process. Thanks for catching that. > > But I checked: > - incubating in name > - signature and hashes file (note however that .sha1 is no long considered > secure and you should be using sha 256 or 512) > - DISCLAIMER exists > - LICENSE and NOTICE file OK > - All source files have ASF headers > - No unexpected binary files in source release > - Can compile from source > > BTW Is this file supposed to be in the source release? [1] I think this file should be removed, but it's not a blocking problem for the release. Thanks for the review and the vote! cheers, Serge... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
