Re: [VOTE] Superset Proposal for Apache Incubator
t;>> decisions, particularly those who are not deeply skilled at >> > writing SQL. >> > > >>>> The challenge of visualizing huge amounts of data >> interactively >> > and in >> > > >>>> real-time >> > > >>>> >> > > >>>> Superset was first developed as a data visualization solution >> > for >> > > >> Druid.io >> > > >>>> as a way to visualize billions of rows of data. Since then, >> > usage of >> > > >>>> Superset has expanded to address data visualization use cases >> > across SQL >> > > >>>> speaking data sources as well. >> > > >>>> >> > > >>>> Our rationale for developing Superset as an Apache project is >> > detailed >> > > >> in >> > > >>>> the Rationale Section. We believe that the Apache brand and >> > community >> > > >>>> process will help us attract more contributors to this >> project, >> > and help >> > > >>>> grow the footprint of the project through usage at other >> > organizations >> > > >> and >> > > >>>> within other applications. Establishing consensus among users >> > and >> > > >>>> developers will result in a more valuable tool for everyone. >> > > >>>> >> > > >>>> == Documentation == >> > > >>>> References to further reading material: >> > > >>>> * [[http://airbnb.io/superset/|Superset Documentation]] >> > > >>>> * [[ >> > > >>>> https://medium.com/airbnb-engineering/caravel-airbnb-s-data- >> > > >>>> exploration-platform-15a72aa610e5#.npqmmbu25|Blog >> > > >>>> Post: Superset: Airbnb’s Data Exploration Platform]] >> > > >>>> * [[ >> > > >>>> https://medium.com/airbnb-engineering/superset-scaling-data- >> > > >>>> access-and-visual-insights-at-airbnb-3ce3e9b88a7f#. >> > a505zvb1t|Blog >> > > >>>> Post: Superset: Scaling Data Access & Visual Insights at >> > Airbnb]] >> > > >>>> >> > > >>>> == Initial Source == >> > > >>>> The origin of the proposed code base can be found at >> > > >>>> https://github.com/airbnb/superset. The code base is >> > primarily in >> > > >>>> Python. >> > > >>>> >> > > >>>> == Source and Intellectual Property Submission Plan == >> > > >>>> We do not expect any complications for the submission of the >> > Superset >> > > >> code >> > > >>>> base. Our code is already in Github and there is only a >> single >> > code >> > > >> base. >> > > >>>> >> > > >>>> == External Dependencies == >> > > >>>> List of Python packages, from the Python Package Index (Pypi): >> > > >>>> >> > > >>>> * boto3 >> > > >>>> * celery >> > > >>>> * cryptography >> > > >>>> * flask-appbuilder >> > > >>>> * flask-cache >> > > >>>> * flask-migrate >> > > >>>> * flask-script >> > > >>>> * flask-sqlalchemy >> > > >>>> * flask-testing >> > > >>>> * humanize >> > > >>>> * gunicorn >> > > >>>> * markdown >> > > >>>> * pandas >> > > >>>> * parsedatetime >> > > >>>> * pydruid >> > > >>>> * PyHive >> > > >>>> * python-dateutil >> > > >>>> * requests >> > > >>>> * simplejson >> > > >>>> * six >> > > >>>> * sqlalchemy >> > > >>>> * sqlalchemy-utils >> > > >>>> * sqlparse >> > > >>>> * thrift >> > > >>>> * thrift-sasl >> > > >>>> * werkzeug >> > > >>>> >> > > >>>> List of Javascript packages, from NPM: >> > > >>>> * autobind-decorator >> > > >>>> * bootstrap >> > > >>>> * bootstrap-datepicker >> > > >>>> * brace >> > > >>>> * brfs >> > > >>>> * cal-heatmap >> > > >>>> * classnames >> > > >>>> * d3 >> > > >>>> * d3-cloud >> > > >>>> * d3-sankey >> > > >>>> * d3-scale >> > > >>>> * d3-tip >> > > >>>> * datamaps >> > > >>>> * datatables-bootstrap3-plugin >> > > >>>> * datatables.net-bs >> > > >>>> * font-awesome >> > > >>>> * gridster >> > > >>>> * immutability-helper >> > > >>>> * immutable >> > > >>>> * jquery >> > > >>>> * lodash.throttle >> > > >>>> * mapbox-gl >> > > >>>> * moment >> > > >>>> * moments >> > > >>>> * mustache >> > > >>>> * nvd3 >> > > >>>> * react >> > > >>>> * react-ace >> > > >>>> * react-bootstrap >> > > >>>> * react-bootstrap-table >> > > >>>> * react-dom >> > > >>>> * react-draggable >> > > >>>> * react-gravatar >> > > >>>> * react-grid-layout >> > > >>>> * react-map-gl >> > > >>>> * react-redux >> > > >>>> * react-resizable >> > > >>>> * react-select >> > > >>>> * react-syntax-highlighter >> > > >>>> * reactable >> > > >>>> * redux >> > > >>>> * redux-localstorage >> > > >>>> * redux-thunk >> > > >>>> * shortid >> > > >>>> * style-loader >> > > >>>> * supercluster >> > > >>>> * topojson >> > > >>>> * victory >> > > >>>> * viewport-mercator-project >> > > >>>> >> > > >>>> == Cryptography == >> > > >>>> The proposal does not include cryptographic code. >> > > >>>> >> > > >>>> == Required Resources == >> > > >>>> >> > > >>>> === Mailing List === >> > > >>>> There is a current mailing list as a Google Group >> > “airbnb_superset” that >> > > >>>> we >> > > >>>> are planning on deprecating as the Apache.org become ready to >> > serve our >> > > >>>> community. >> > > >>>> >> > > >>>> * superset-private >> > > >>>> * superset-dev >> > > >>>> * superset-user >> > > >>>> >> > > >>>> === Subversion Directory === >> > > >>>> Git is the preferred source control system. >> > > >>>> http://svn.apache.org/repos/asf/incubator/superset >> > > >>>> >> > > >>>> == Git Repository == >> > > >>>> Git is the preferred source control system, we’re assuming >> > > >>>> https://github.com/apache/incubator-superset based on the >> > naming scheme >> > > >>>> >> > > >>>> == Issue Tracking == >> > > >>>> JIRA Superset (SUPERSET). If possible, we’d like to use Github >> > issues & >> > > >>>> PRs >> > > >>>> to manage our project as much as possible. It’s been said that >> > there are >> > > >>>> ways to keep Github’s issues in sync with Jira, allowing us to >> > get best >> > > >> of >> > > >>>> both worlds. If that is not possible, we will comply to using >> > Jira. >> > > >>>> >> > > >>>> == Other Resources == >> > > >>>> We currently use a set of Github integrated services that are >> > free to >> > > >> the >> > > >>>> open source community, like Travis-ci, Code Climate, >> Coveralls, >> > > >>>> Landscape.io, Requires.io, david-dm and Gitter. We would like >> > to keep >> > > >>>> using >> > > >>>> these services as they allow us to scale contributions and >> > optimize our >> > > >>>> development flows. These services require some elevated rights >> > on the >> > > >>>> Github repository in order to set up or tune and we would like >> > for the >> > > >>>> committers to have the required rights. >> > > >>>> >> > > >>>> >> > > >>>> == Initial Committers == >> > > >>>> >> > > >>>> * Maxime Beauchemin <maxime.beauche...@airbnb.com> - PPMC & >> > Committer >> > > >>>> * Alanna Scott <alanna.sc...@airbnb.com> - PPMC & Committer >> > > >>>> * Bogdan Kyryliuk <b.kyryl...@gmail.com> - PPMC & Committer >> > > >>>> * Vera Liu <vera@airbnb.com> - Committer >> > > >>>> * Jeff Feng <jeff.f...@airbnb.com> - PPMC & Committer >> > > >>>> * Ashutosh Chauhan <hashut...@apache.org> - Mentor & >> Committer >> > > >>>> * Nishant Bangarwa <nbanga...@hortonworks.com> - PPMC & >> > Committer >> > > >>>> * Slim Bouguerra <sbougue...@hortonworks.com> - Committer >> > > >>>> * Priyank Shah <ps...@hortonworks.com> - Committer >> > > >>>> * Harsha Chintalapani <schintalap...@hortonworks.com> - >> > Committer >> > > >>>> * Daniel Dai <da...@apache.org> - Champion & Committer >> > > >>>> * Luke Han <luke@apache.org> - Mentor >> > > >>>> >> > > >>>> == Affiliations == >> > > >>>> The initial committers are employees of Airbnb Inc. and >> > Hortonworks. >> > > >>>> >> > > >>>> == Sponsors == >> > > >>>> >> > > >>>> === Champion === >> > > >>>> Daniel Dai <da...@apache.org> >> > > >>>> >> > > >>>> === Nominated Mentors === >> > > >>>> * Ashutosh Chauhan <hashut...@apache.org> >> > > >>>> * Luke Han <luke@apache.org> >> > > >>>> >> > > >>>> === Sponsoring Entity === >> > > >>>> Incubator PMC >> > > >>>> >> > > >>> >> > > >>> >> > > >> >> > > >> > > >> > > >> > - >> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > > For additional commands, e-mail: general-h...@incubator.apache.org >> > > >> > > >> > > >> > > >> > >> > - >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > For additional commands, e-mail: general-h...@incubator.apache.org >> > >> > >> -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Proposal for an Apache Hama sub-project
Thanks for your proposal. I of course think Apache Hama can be used for scheduling sync and async communication/computation networks with various topologies and resource allocation. However, I'm not sure whether this approach is also fit for modern microservice architecture? In my opinion, this can be discussed and cooked in Hama community as a sub-project until it's mature enough (CC'ing general@i.a.o. I'll be happy to read more feedbacks from ASF incubator community). P.S., It seems you referred to incubation proposal template. There's no need to add me as initial committer (I don't have much time to actively contribute to your project). And, I recently quit Samsung Electronics and joined to $200 billion sized O2O e-commerce company as a CTO. -Original Message- From: Sachin Ghai [mailto:sachin.g...@impetus.co.in] Sent: Monday, February 27, 2017 5:16 PM To: d...@hama.apache.org Subject: Proposal for an Apache Hama sub-project Hama Community, I would like to propose a sub-project for Apache Hama and initiate discussion around the proposal. The proposed sub-project named 'Scalar' is a scalable orchestration, training and serving system for machine learning and deep learning. Scalar would leverage Apache Hama to automate the distributed training, model deployment and prediction serving. More details about the proposal are listed below as per Apache project proposal template: Abstract Scalar is a general purpose framework for simplifying massive scale big data analytics and deep learning modelling, deployment, serving with high performance. Proposal It is a goal of Scalar to provide an abstraction framework which allows user to easily scale the functions of training a model, deploying a model and serving the prediction from underlying machine learning or deep learning framework. It is also the characteristic of its execution framework to orchestrate heterogeneous workload graphs utilizing Apache Hama, Apache Hadoop, Apache Spark and TensorFlow resources. Background The initial Scalar code was developed in 2016 and has been successfully beta tested for one of the largest insurance organizations in a client specific PoC. The motivation behind this work is to build a framework that provides abstraction on heterogeneous data science frameworks and helps users leverage them in the most performant way. Rationale There is a sudden deluge of machine learning and deep learning frameworks in the industry. As an application developer, it becomes a hard choice to switch from one framework to another without rewriting the application. Also, there is additional plumbing to be done to retrieve the prediction results for each model in different frameworks. We aim to provide an abstraction framework which can be used to seamlessly train and deploy the model at scale on multiple frameworks like TensorFlow, Apache Horn or Caffe. The abstraction further provides a unified layer for serving the prediction in the most performant, scalable and efficient way for a multi-tenant deployment. The key performance metrics will be reduction in training time, lower error rate and lower latency time for serving models. Scalar consists of a core engine which can be used to create flows described in terms of state, sequences and algorithms. The engine invokes execution context of Apache Hama to train and deploy models on target framework. Apache Hama is used for a variety of functions including parameter tuning and scheduling computations on a distributed cluster. A data object layer provides access to data from heterogeneous sources like HDFS, local, S3 etc. A REST API layer is utilized for serving the prediction functions to client applications. A caching layer in the middle acts as a latency improver for various functions. Initial Goals Some current goals include: * Build community. * Provide general purpose API for machine learning and deep learning training, deployment and serving. * Serve the predictions with low latency. * Run massive workloads via Apache Hama on TensorFlow, Apache Spark and Caffe. * Provide CPU and GPU support on-premise or on cloud to run the algorithms. Current Status Meritocracy The core developers understand what it means to have a process based on meritocracy. We will provide continuous efforts to build an environment that supports this, encouraging community members to contribute. Community A small community has formed within the Apache Hama project community and companies such as enterprise services and product company and artificial intelligence startup. There is a lot of interest in data science serving systems and Artificial intelligence simplification systems. By bringing Scalar into Apache, we believe that the community will grow even bigger. Core Developers Edward J. Yoon, Sachin Ghai, Ishwardeep Singh, Rachna Gogia, Abhishek Soni, Nikunj Limbaseeya, Mayur Choubey Known Risks Orphaned Products Apache Hama is already a core open source component being utilized at Samsung
[RESULT][VOTE] Weex to enter the Apache Incubator
Thanks all. This vote passes with 8 binding +1s, 9 non-binding +1s, and no -1. -- Binding +1 votes: Niclas Hedhman Stian Soiland-Reyes John D. Ament Bertrand Delacretaz Willem Jiang Luke Han Stephan Ewen Henry Saputra Non-binding +1 votes: Xiaorui Wang Feng Jia Feng Longda Xinyu Zhou Hust Fxj Emilian Bold Huxing Zhang zhendong Bryant Wu -- Best Regards, Edward J. Yoon -Original Message- From: Edward J. Yoon [mailto:edward.y...@samsung.com] Sent: Friday, November 25, 2016 7:47 AM To: general@incubator.apache.org Subject: [VOTE] Weex to enter the Apache Incubator Greetings! $B!!(B I would like to call a vote for accepting "Weex" for incubation in the Apache Incubator. The full proposal is available below. We ask the Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion, and Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to be Mentors. Please cast your vote: [ ] +1, bring Weex into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Weex into Incubator, because... This vote will be open at least for 72 hours and only votes from the Incubator PMC are binding. -- https://wiki.apache.org/incubator/WeexProposal = Weex Proposal = == Abstract == Weex is a framework for building Mobile cross-platform high performance UI. Weex enables developers to use Web-like syntax to build iOS, Android and Web UI with a single codebase. == Proposal == Weex provide an uniform Web-like syntax for develop native Mobile App UI. By leverage the Javascript engine that enable dynamic update, the process of App interfce and content update can be simple and controllable just like Web.Compared with WebView based UI framework which performance are limited, Weex use build-in native components instead. Because of tag based syntax that maintain a consistent style with Web standards Weex using. Developers write in this language just like writting in HTML. After transforming to JSBundle by Weex tools, these tags will be rendered by build-in platform-specific components. The logic part of Weex syntax write in Javascript which don't need be compiled control these components. The vision of Weex is to complement gap between platform-specific Native UI and Web technical based UI in Mobile age. The team behind Weex believe that dynamicly interface update and high performance should be achieved at the same time when people develop a Mobile App. Meanwhile duplicate work between the different platforms should be avoided. == Background == Prior to Weex, in order to develop high performance mobile application we need write at least three different codebase(iOS, Android, Mobile Web) or adopt WebView based UI technique(Apache Cordova for example) which can't satisfy the demand for performance. A special task force at Alibaba Inc try to provide a solution for this problem has been setup since 2013. At first the team release a cross-platform rendering engine which render a special format JSON to native components on different platform. To output this JSON file the team had build a website which other developer can use to simply design final interface. Although This solution had worked for a while, we found it not able to meet our UI developer's habits. Most of our UI developer have Web background which make them used to use tag based language to design App interface. Meanwhile we found the JSON file lacks of enough flexibility. The following discussion inspire we start to develop Weex. Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest user volume eCommerce App in China has adapted Weex in a lot of UI. In the latest November 11th promotions(Alibaba's annual Singles' Day online shopping event), UI developers from Alibaba Inc have build more then 1,500 pages using Weex, 99.6% of all the promotional pages. The ratio of less than one second page open time is more than 90%, the frame rate is 53.0~58.5(depend on device) due to the high performance of Weex. In addition to user experience improvement, the productivity of page development and the efficiency of content delivery both have been improved. After open-source and have got a lot of followers in chinese mobile App development community, several of popular Apps listed on chinese top charts have adopted or planning for adopt Weex.(UCWeb, Tmall, YouKu, Suning etc...) == Current Status == Weex has become an open source project since June 2016. It has been used at a lot of Alibaba producted mobile softwares which running on the mobile phone of millions of users. Weex code repository located at GitHub. All development activities have already happened on GitHub as open source manner. == Community == The community surrounding Weex is a variety of developer which have different technique background.iOS, Android, Web developer must collaborate closely to implement most Weex feature. Currently total 61 contributors involved in the GitHub development process. Weex repository has received 791 pull requ
Re: 回复：[VOTE] Weex to enter the Apache Incubator
吴志华(天施), Of course, you can cast your vote. But your vote is non-binding. And this list's subscribers are from various countries. Always use text as your email format and create the email signature as english nickname. Thanks. On Tue, Nov 29, 2016 at 12:49 AM, 吴志华(天施) <zhihua@alibaba-inc.com> wrote: >BryantWuhuaz...@gmail.com (Alibaba Inc)。Weex Init > developer > Can I vote for Weex Project? I love Weex so > much。--发件人：Daniel > Gruno <humbed...@apache.org>发送时间：2016年11月28日(星期一) 23:17收件人：general > <general@incubator.apache.org>主 题：Re: 回复：[VOTE] Weex to enter the Apache > Incubator > > On 11/28/2016 04:06 PM, 吴志华(天施) wrote: >> >> +1 (binding) > > For binding +1s, we generally require a name we can compare with our > Apache Phonebook to make sure you are on the IPMC. I was unable to find > you as a committer, could you please tell me your apache ID? > > With regards, > Daniel. > >> --发件人：Stephan >> Ewen <se...@apache.org>发送时间：2016年11月28日(星期一) 18:02收件人：general >> <general@incubator.apache.org>主 题：Re: [VOTE] Weex to enter the Apache >> Incubator >> +1 (binding) >> >> >> On Sun, Nov 27, 2016 at 1:44 AM, Luke Han <luke...@gmail.com> wrote: >> >>> +1 binding >>> >>> Get Outlook for iOS >>> >>> >>> >>> >>> On Sat, Nov 26, 2016 at 8:41 PM +0800, "Willem Jiang" < >>> willem.ji...@gmail.com> wrote: >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> +1 （binding） >>> >>> >>> Willem Jiang >>> >>> Blog: http://willemjiang.blogspot.com (English) >>> http://jnn.iteye.com (Chinese) >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>> >>> On Fri, Nov 25, 2016 at 6:47 AM, Edward J. Yoon >>> wrote: >>> >>> > Greetings! >>> > >>> > I would like to call a vote for accepting "Weex" for incubation in the >>> > Apache Incubator. The full proposal is available below. We ask the >>> > Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion, >>> and >>> > Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to >>> be >>> > Mentors. >>> > >>> > Please cast your vote: >>> > >>> > [ ] +1, bring Weex into Incubator >>> > [ ] +0, I don't care either way, >>> > [ ] -1, do not bring Weex into Incubator, because... >>> > >>> > This vote will be open at least for 72 hours and only votes from the >>> > Incubator PMC are binding. >>> > >>> > -- >>> > https://wiki.apache.org/incubator/WeexProposal >>> > >>> > = Weex Proposal = >>> > >>> > == Abstract == >>> > Weex is a framework for building Mobile cross-platform high performance >>> UI. >>> > Weex enables developers to use Web-like syntax to build iOS, Android and >>> > Web >>> > UI with a single codebase. >>> > >>> > == Proposal == >>> > Weex provide an uniform Web-like syntax for develop native Mobile App UI. >>> > By >>> > leverage the Javascript engine that enable dynamic update, the process of >>> > App interfce and content update can be simple and controllable just like >>> > Web.Compared with WebView based UI framework which performance are >>> limited, >>> > Weex use build-in native components instead. >>> > >>> > Because of tag based syntax that maintain a consistent style with Web >>> > standards Weex using. Developers write in this language just like >>> writting >>> > in HTML. After transforming to JSBundle by Weex tools, these tags will be >>> > rendered by build-in platform-specific components. The logic part of Weex >>> > syntax write in Javascript which don't need be compiled control these >>> > components. >>> > >>> > The vision of Weex is to complement gap between platform-specific Native >>> UI >>> > and Web technical based UI in Mobile age. The team behind Weex believe >>> that >>> > dynamicly interface update and high performance should
[VOTE] Weex to enter the Apache Incubator
Greetings! $B!!(B I would like to call a vote for accepting "Weex" for incubation in the Apache Incubator. The full proposal is available below. We ask the Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion, and Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to be Mentors. Please cast your vote: [ ] +1, bring Weex into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Weex into Incubator, because... This vote will be open at least for 72 hours and only votes from the Incubator PMC are binding. -- https://wiki.apache.org/incubator/WeexProposal = Weex Proposal = == Abstract == Weex is a framework for building Mobile cross-platform high performance UI. Weex enables developers to use Web-like syntax to build iOS, Android and Web UI with a single codebase. == Proposal == Weex provide an uniform Web-like syntax for develop native Mobile App UI. By leverage the Javascript engine that enable dynamic update, the process of App interfce and content update can be simple and controllable just like Web.Compared with WebView based UI framework which performance are limited, Weex use build-in native components instead. Because of tag based syntax that maintain a consistent style with Web standards Weex using. Developers write in this language just like writting in HTML. After transforming to JSBundle by Weex tools, these tags will be rendered by build-in platform-specific components. The logic part of Weex syntax write in Javascript which don't need be compiled control these components. The vision of Weex is to complement gap between platform-specific Native UI and Web technical based UI in Mobile age. The team behind Weex believe that dynamicly interface update and high performance should be achieved at the same time when people develop a Mobile App. Meanwhile duplicate work between the different platforms should be avoided. == Background == Prior to Weex, in order to develop high performance mobile application we need write at least three different codebase(iOS, Android, Mobile Web) or adopt WebView based UI technique(Apache Cordova for example) which can't satisfy the demand for performance. A special task force at Alibaba Inc try to provide a solution for this problem has been setup since 2013. At first the team release a cross-platform rendering engine which render a special format JSON to native components on different platform. To output this JSON file the team had build a website which other developer can use to simply design final interface. Although This solution had worked for a while, we found it not able to meet our UI developer's habits. Most of our UI developer have Web background which make them used to use tag based language to design App interface. Meanwhile we found the JSON file lacks of enough flexibility. The following discussion inspire we start to develop Weex. Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest user volume eCommerce App in China has adapted Weex in a lot of UI. In the latest November 11th promotions(Alibaba's annual Singles' Day online shopping event), UI developers from Alibaba Inc have build more then 1,500 pages using Weex, 99.6% of all the promotional pages. The ratio of less than one second page open time is more than 90%, the frame rate is 53.0~58.5(depend on device) due to the high performance of Weex. In addition to user experience improvement, the productivity of page development and the efficiency of content delivery both have been improved. After open-source and have got a lot of followers in chinese mobile App development community, several of popular Apps listed on chinese top charts have adopted or planning for adopt Weex.(UCWeb, Tmall, YouKu, Suning etc...) == Current Status == Weex has become an open source project since June 2016. It has been used at a lot of Alibaba producted mobile softwares which running on the mobile phone of millions of users. Weex code repository located at GitHub. All development activities have already happened on GitHub as open source manner. == Community == The community surrounding Weex is a variety of developer which have different technique background.iOS, Android, Web developer must collaborate closely to implement most Weex feature. Currently total 61 contributors involved in the GitHub development process. Weex repository has received 791 pull requests until Nov 2016. Beyond committer from Alibaba Inc, Weex community welcome anybody join us. Nowaday Evan You from Vue Technology LLC, Wang Run Xiang from Aipai Inc and lots of GitHub users have contributed source code or document to Weex. Weex syntax is inspired a lot from Web framework Vue.js. For better future of both Weex, we have cooperated with Vue.js community from begin of Weex. The main author of Vue.js Evan You have became committer & mentor of Weex in the first half of 2016. At the time of this writing (Nov 2016) Weex GitHub star number is 8249, watch number
RE: [DISCUSS] Weex for Apache Incubator
Okay, if there is no more feedback then I'll send out a VOTE thread tomorrow. :-) Thanks! -- Best Regards, Edward J. Yoon -Original Message- From: hedh...@gmail.com [mailto:hedh...@gmail.com] On Behalf Of Niclas Hedhman Sent: Wednesday, November 23, 2016 9:07 AM To: general@incubator.apache.org Subject: Re: [DISCUSS] Weex for Apache Incubator Additional note to Weex community; Beside everything discussed, there is nothing impossible about changing name during or even after incubation. Apache Zest is discussing a name change right now, as Eclipse Zest was missed in the name search previously and we want to avoid the name clash. Cheers Niclas On Tue, Nov 22, 2016 at 10:07 PM, Bertrand Delacretaz < bdelacre...@apache.org> wrote: > On Tue, Nov 22, 2016 at 2:45 PM, Daniel Gruno <humbed...@apache.org> > wrote: > > ...Whether it means something funny in $language, who cares... :) > > We don't really care at the ASF or Incubator PMC level but it's fair > to warn people when that happens. > > It's like when you're traveling, it's good to know in advance if your > name means something funny in that country...to be prepared for > people's reactions when you say your name ;-) > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Weex for Apache Incubator
I personally felt that Weex is suggestive of "we ex-"., and thought not bad for UI/UX project. e.g., We experience, We experts, ... -- Best Regards, Edward J. Yoon -Original Message- From: Markus Geiß [mailto:markus.ge...@live.de] Sent: Monday, November 21, 2016 11:04 PM To: general@incubator.apache.org Subject: RE: [DISCUSS] Weex for Apache Incubator Hey ... I'm a native German speaker too ... The referenced word is pronounced with a short 'i' and is referring to something a boy would do alone at night ... Given that Weex is pronounced with a long 'i', it could lead to some fun situations. Cheers Markus -Original Message- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Monday, November 21, 2016 02:55 PM To: Incubator General <general@incubator.apache.org> Subject: Re: [DISCUSS] Weex for Apache Incubator On Sun, Nov 20, 2016 at 11:17 PM, Edward J. Yoon <edward.y...@samsung.com> wrote: > ...We'd like to start a discussion on accepting the Weex... A native German speaker tells me Weex means or sounds something between LOL and NSFW in German - if that's correct that's probably not a good name for an Apache project. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Weex for Apache Incubator
Great, thanks for volunteering, Niclas! On Mon, Nov 21, 2016 at 5:18 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > I volunteer as mentor. I have been a bit inactive of the Weex proposal, but > my recent addition to the Incubator PMC was for this purpose. > > Cheers > Niclas > > On Mon, Nov 21, 2016 at 2:01 PM, Bertrand Delacretaz <bdelacre...@apache.org >> wrote: > >> Hi, >> >> On Sun, Nov 20, 2016 at 11:17 PM, Edward J. Yoon >> <edward.y...@samsung.com> wrote: >> > === Nominated Mentors === >> ... >> > * Longda Feng (Apache Storm) >> >> >> As per http://people.apache.org/phonebook.html?uid=longda Longda >> doesn't seem to be an Incubator PMC member - that's required for being >> a mentor. >> >> -Bertrand >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Weex for Apache Incubator
roid, Alibaba Inc) * Jin-JiangZhao zhaojinji...@me.com (Web/Node , Alibaba Inc) * Tai-ChengHuang iskenhu...@gmail.com (Web/Node, Alibaba Inc) * FengYin cxfe...@gmail.com(iOS, Alibaba Inc) * YuanYin zsh...@sina.com (Android, Alibaba Inc) * BobNing ningli928@1 6 3.com(iOS, Alibaba Inc) * WeiZheng sospar...@gmail.com (Android, Alibaba Inc) * YorkShen shenyua...@gmail.com (Android, Alibaba Inc) * SaiHe tekk...@gmail.com(Web, Alibaba Inc) * BonoLvlvs...@gmail.com (Web/Node, Alibaba Inc) * GurisXie 279483...@qq.com (Testing, Alibaba Inc) * AtomTong tong_huab...@qq.com (Testing, Alibaba Inc) == Meritocracy == The intent of this proposal is to start building a diverse developer and user community around Weex following the ASF meritocracy model.After Weex becoming an OpenSource project, we have been working to make an open governance structure for project leadership to encourage individual and company involvement and contributions. == Alignment == The Weex community believes that the Apache Software Foundation promotes and enforces the sort of community that will best serve the future of the project. It is also believed that Weex can enhance the ASF by expand the technical scope of ASF in Mobile age. == Relationships with Other Apache Products == We think Weex is an effective supplement to Apache Cordova. Both Apache Cordova and Weex help developer for leveraging Web development technique in Mobile age. Boot developer the ability of delivering consistent content to different platform. With our sincere heart and determination to open source, we will always keep an open mind for Apache community. == Known Risks == === Difficult to refuse platform-specific features === "Write Once Run Everywhere" is one of original goal of Weex. But as Weex provides more feature, we have received more suggestions for implement single platform exclusive feature. === Inexperience with build international community === Although we are full of passion about build a successful Opensource project and a community, Weex initial team lack of experience about participate in international community. After consulting with our mentors, we know modesty will be our code of conduct in Apache community. === Homogeneous and Reliance on salaried developers === Since the Weex Project has been mainly developed to date by Alibaba Inc, the vast majority of initial committers to the project are from Alibaba Mobile engineering team. As an Opensource project, Weex project has received lots bug fixes and enhancements from other developers(not Alibaba Employee). We will continue to encourage more independent developers to participate in Weex. We know Apache Way is about people, not corporations. After Weex developer community grows, we hope the contribution ratio from Alibaba salaried developer will decrease. == Source Code == * Main repository: https://github.com/alibaba/weex * Weex transformer: https://github.com/weexteam/weex-transformer * Weex toolkit: https://github.com/weexteam/weex-toolkit * Weex loader: https://github.com/weexteam/weex-loader * Gulp Weex: https://github.com/weexteam/gulp-weex == Documentation == * English Document: http://alibaba.github.io/weex/doc/ * Chinese Document(English first, currently only partially docs have been translate to Chinese): https://github.com/weexteam/article/wiki/Weex$BCfJ8J8[c(B == External Dependencies == * semver(http://semver.org/) developed by Tom Preston-Werner, licensed under the Creative Commons - CC BY 3.0 License. * core-js(https://github.com/zloirock/core-js) developed by Denis Pushkarev, licensed under the MIT License. * vuejs(https://github.com/vuejs/vue) developed by Yuxi Evan You , licensed under the MIT License. * scroll-to (https://github.com/component/scroll-to) developed by TooTallNate, licensed under the MIT License. * Chrome V8(https://developers.google.com/v8/) developed by Google Inc & V8 project authors, licensed under BSD License. * css-layout(https://github.com/facebook/css-layout) developed by Facebook Inc., licensed under the BSD License. == Required Resources == * Mailing Lists * priv...@weex.incubator.apache.org * d...@weex.incubator.apache.org * comm...@weex.incubator.apache.org * Git Repos * https://git-wip-us.apache.org/repos/asf/weex.git * Issue Tracking * JIRA Weex (WEEX) * Continuous Integration * Jenkins builds on https://builds.apache.org/ * Web * http://weex.incubator.apache.org/ * wiki at http://cwiki.apache.org == Sponsors == === Champion === * Edward J. Yoon (ASF member, Apache Hama) === Nominated Mentors === * Luke Han (Apache Kylin) * Longda Feng (Apache Storm) * Willem Jiang (Apache Camel) == Sponsoring Entity == * The Apache Incubator == Next Goals == * License all Weex source code and documentation to the Apache Software Foundation. (We already using Apache license for our main code re
Re: [VOTE] Accept OpenWhisk into the Apache Incubator
ons for developers
>> on where to get NAXSI code (under GPL)
>> ZeroMQ / ØMQ - Linked Dynamically in separate module
>> libzmq - LGPL license with SPECIAL EXCEPTION GRANTED BY
>> COPYRIGHT HOLDERS - https://github.com/zeromq/libzmq
>> czmq - High Level C binding for libzmq - MPL v2 license
>> https://github.com/zeromq/czmq
>>
>>
>> == Trademarks ==
>>
>> IBM is pursuing trademarking of the OpenWhisk name in the following
>> jurisdictions: Canada, France, WIPO (i.e., Australia, China, CTM
>> (EUIPO), India, Mexico, Russian Federation, Switzerland, United States
>> of America). IBM plans to transfer all filings and trademark ownership
>> to ASF.
>>
>> == Cryptography ==
>>
>> Please note that the file
>>
>> https://github.com/openwhisk/openwhisk/blob/master/common/scala/src/main/scala/whisk/common/Crypt.scala
>> makes use of the Java javax.crypto.* libraries to implement
>> encrypt/decrypt functions. Primarily this is used to encrypt/decrypt
>> user keys or secrets when being passed or stored between or by
>> OpenWhisk components.
>>
>> In addition, the API Gateway modules (api-gateway-hmac) relies on
>> OpenSSL (openssl/evp.h, openssl/hmac.h).
>>
>> == Required Resources ==
>>
>> Resources that infrastructure will be asked to supply for this project.
>>
>> Over the course of the incubator we would like to develop staging and
>> playground server environments for testing and developer experience.
>> The following environment would be desirable for an initial staging
>> (and separate playground):
>>
>> * CI Test Cluster requirements:
>> 3 VMs, Catalog (CouchDB/Cloudant), Router (Nginx), Registry
>> 2 VMs, Master (Controller + Consul), Message Bus (Kafka)
>> 10 VMs, Invokers
>> Each VM assumes 4 CPUs, 8GB Memory, 80GB additional storage
>> * Mechanics:
>> Scripts that invoke Ansible playbooks for build, deploy (run)
>> and clean are provided.
>> The various architectural components are started via Docker
>> containers (either natively, within a single Vagrant VM, or across
>> multiple, designated VM roles) using user configured (or defaulted)
>> endpoints and (guest) authorization credentials.
>> In addition, the user/developer may choose to use the default
>> ephemeral CouchDB (via Docker container) for the OpenWhisk catalog or
>> switch to use a native CouchDB or a remote Cloudant database.
>>
>> In addition, we would like to host a VM with a Node.js server that
>> provides Command Line Tutorials, along with demo samples.
>>
>> == Mailing lists ==
>>
>> Initially, we would start with the following recommended initial
>> podling mailing lists:
>>
>> priv...@openwhisk.incubator.apache.org,
>> dev@{podling}.incubator.apache.org
>>
>> We would add more as we transition off exiting mailings lists and
>> through the course of incubation.
>>
>> == Git Repository ==
>>
>> As a community we would like to keep the master repository as well as
>> issue tracking on GitHub. We will be working closely with ASF Infra.
>> team to implement all the required pieces like ensure to send push and
>> issue notifications through ASF controlled mailing lists. During
>> incubation we will work closely with Infra to support GitHub master
>> repositories. We also understand that we have to support a way of
>> providing patches, which does not require a GitHub account for
>> contributors who are not willing or not able abide by GitHub’s terms
>> and conditions. It is our understanding that this approach has been
>> signed off by Greg Stein, ASF’s Infrastructure Administrator.
>> gstein sez: the podling can only graduate within an approved
>> repository system. The IPMC may have a differing opinion, but from an
>> Infra perspective: the OpenWhisk podling can continue with their usage
>> of a GitHub repository, but faces a clear obstacle: GitHub "as master
>> [as allowed by the Foundation]" must be approved and working before
>> the graduation, or they must migrate their primary to the Foundation's
>> Git repository (at git-wip) before they graduate.
>>
>> If we need to adapt our repo. paths to conform to Apache guidelines
>> (and perhaps necessitated by a move the the Apache named repo.) It is
>> conventional to use all lower case, dash-separated (-) repository
>> names. The repository should be prefixed with incubator and later
>> renamed assuming the project is promoted to a TLP.
>>
>> If we need to move the project codebase from its existing GitHub repo.
>> as part of incubation, we would like to preserve the directory names
>> as they appear today and adopt the “apache” as part of the URI path as
>> we have seen other projects adopt.
>>
>> This would mean all existing repositories which are now of the form:
>>
>> * https://github.com/openwhisk/openwhisk
>> * https://github.com/openwhisk/openwhisk-catalog
>> * https://githun.com/openwhisk/openwhisk-package-rss
>> * etc.
>>
>> would now take the form:
>>
>> * https://github.com/apache/openwhisk/openwhisk
>> * https://github.com/apache/openwhisk/openwhisk-catalog
>> * https://githun.com/apache/openwhisk/openwhisk-package-rss
>> * and so on ...
>>
>> == Issue Tracking ==
>>
>> We would like to explore the possibility of continuing to use GitHub
>> issue tracking (as project milestones, epics and features are all
>> nicely tracked via ZenHub boards) as we understand that this may now
>> be possible. We will provide any linkage or support for JIRA issue
>> tracking if that is required in order to track any “pull” requests
>> within GitHub.
>>
>> == Other Resources ==
>>
>> We would like to preserve our existing automated TravisCI automated
>> testing from GitHub. The project uses a continuous CD/CI process
>> currently that we would like to continue to support via multiple
>> stages that run progressive stress and performance tests that are also
>> automated.
>>
>> == Initial Committers ==
>>
>> The following is the proposed list of initial committers, email
>> address [, GitHub ID)]:
>>
>> * Bertrand Delacretaz, bdelacre...@apache.org, bdelacretaz
>> * Carlos Santana, csant...@us.ibm.com, csantanapr
>> * Carsten Ziegeler, cziege...@apache.org, cziegeler
>> * Chetan Mehrotra, chet...@adobe.com, chetanmeh
>> * Christian Bickel, cbic...@de.ibm.com, christianbickel
>> * Daisy Guo, guoyi...@cn.ibm.com, daisy-ycguo
>> * David Liu, david@cn.ibm.com, lzbj
>> * Dragos Dascalita Haut, ddas...@adobe.com, ddragosd
>> * Jeremias Werner, jerew...@de.ibm.com, jeremiaswerner
>> * Markus Thommes, markus.thoem...@de.ibm.com, markusthoemmes
>> * Matt Rutkowski, mrutk...@us.ibm.com, mrutkows
>> * Nicholas Speeter, nwspe...@us.ibm.com, nwspeete-ibm
>> * Paul Castro, cast...@us.ibm.com, paulcastro
>> * Perry Cheng, pe...@us.ibm.com, perryibm
>> * Philippe Sutor, psu...@us.ibm.com, psutor
>> * Rodric Rabbah, rab...@us.ibm.com, rabbah
>> * Sergio Fernández, wik...@apache.org, wikier
>> * Stephen Fink, sjf...@us.ibm.com, sjfink
>> * Tony Ffrench, tffre...@us.ibm.com, tonyfrench
>> * Vincent Hou, s...@us.ibm.com, houshengbo
>> * Edward J. Yoon, edward.y...@samsung.com, edwardyoon
>>
>> Although this list of initial committers appears long, OpenWhisk is a
>> complete platform which consists of many services supporting many
>> environments, programming languages and integrations. This diversity
>> in needs is reflected by the size of the initial committers group.
>> OpenWhisk also supports an end user ecosystem including CLI, Tooling,
>> Package Catalog, “curated” Packages, samples, etc. along with the
>> intention of tying in API gateway (e.g., OpenAPI) and other event
>> source integrations.
>>
>> We hope to add many more committers who provide expertise and the
>> various areas OpenWhisk uses to efficiently provide an exceptional
>> Serverless platform with compelling content.
>>
>> == Affiliations ==
>>
>> Additional TBD during the proposal process
>>
>> == Sponsors ==
>>
>> Additional TBD during the proposal process.
>>
>> == Sponsoring Entity ==
>>
>> OpenWhisk would ask that the Apache Incubator be the sponsor.
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
--
Best Regards, Edward J. Yoon
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] OpenWhisk Proposal
Awesome. Let me in. On Fri, Nov 4, 2016 at 10:35 PM, Felix Meschberger <fmesc...@adobe.com> wrote: > Hi all > > I have made some additions to the OpenWhisk Proposal [1]: > > - restructured the API Gateway references: It is expected >that the API Gateway will be refactored with additional >code donated by IBM during incubation. > - added a note on the API Gateway’s dependency on OpenSSL > - added a note on Trademarks IBM is currently pursuing and >intends to transfer to ASF > - fixed some typos > > With these changes and no discussions over the course of the recent weeks, I > would propose we could could vote for OpenWhisk to become an incubating > project over the course of next weeks. > > Of course we are still open to welcome interested people to become initial > committers to OpenWhisk Servlerless Runtime and API Gateway ! > > WDYT ? > > Regards > Felix > > [1] https://wiki.apache.org/incubator/OpenWhiskProposal > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Seek one Champion for incubating Weex project
Thanks for welcome. Jut FYI, creating the editable proposal page on the wiki ( maybe https://wiki.apache.org/incubator/WeexProposal ) allows easy collaboration! To get edit permission to edit Wiki, please send a mail to general@i.a.o. Thanks. On Fri, Nov 4, 2016 at 12:14 PM, Longda Feng <lon...@apache.org> wrote: > Yoon, Thank you very much. It will be our pleasure to have you as a > champion. > > I think we can discuss the project and draw up a plan in the next > weeks. Let's keep in touch. > > Thanks > Longda > > > -- > From:Jinjiang Zhao <zhaojinji...@me.com> > Send Time:2016年11月4日(星期五) 10:59 > To:general <general@incubator.apache.org> > Cc:general <general@incubator.apache.org>; weex-apache > <weex-apa...@list.alibaba-inc.com>; Stephan Ewen <se...@apache.org>; > luke.hq <luke...@gmail.com>; hedhman <hedh...@gmail.com>; willem.jiang > <willem.ji...@gmail.com>; Longda Feng <lon...@apache.org>; Casey > Bisson <casey.bis...@joyent.com>; bryan <br...@joyent.com> > Subject:Re: Seek one Champion for incubating Weex project > > Great! It will be our pleasure to have you as a champion. Maybe we can keep > in touch and we are glad to show you more details about Weex :-) > > Thanks. > > Jinjiang > > On Nov 04, 2016, at 05:35 AM, "Edward J. Yoon" <edward.y...@samsung.com> > wrote: > > Weex team, > > I'm recently developing a cross-platform runtime javascript framework and > its backend service [1], so I'm very interested in learning this project. If > you think we can make some synergy, feel free to add me as a mentor, or > champion. I can help. > > 1. http://121.78.112.135/draft.html > > -- > Best Regards, Edward J. Yoon > > > -Original Message- > From: Benjamin Young [mailto:byo...@bigbluehat.com] > Sent: Thursday, November 03, 2016 11:13 PM > To: general@incubator.apache.org > Cc: weex-apache; Stephan Ewen; luke...@gmail.com; hedh...@gmail.com; willem. > ji...@gmail.com; Longda Feng > Subject: Re: Seek one Champion for incubating Weex project > > Hi Jinjiang and Longda, > > > Were you all able to find a Champion for the Incubator? I'd hate to see this > great project miss out on benefiting from the Apache Way. > > > Please let us know if you're still in need of help finding a Champion or > Mentors. > > > Thanks! > > Benjamin > > > -- > > http://bigbluehat.com/ > > http://linkedin.com/in/benjaminyoung > > > From: 略쏩쉭 <zhaojinji...@me.com> > Sent: Tuesday, October 11, 2016 5:18:03 PM > To: general@incubator.apache.org > Cc: weex-apache; Stephan Ewen; luke...@gmail.com; hedh...@gmail.com; willem. > ji...@gmail.com; Longda Feng > Subject: Re: Seek one Champion for incubating Weex project > > Hi I'am Jinjiang Zhao from Weex team. > > Weex hope to help more people build their mobile apps with high perf easier > and faster. Just write once run any platforms. Also it uses HTML, CSS, > JavaScript syntax and is more friendly for frontend developers. > Very glad to know every guys. > > Thanks. > > Jinjiang > > 瞳 2016쾨10墩11휑，09:54，Longda Feng <lon...@apache.org> 畇돛： > Hi > The Weex team are looking forward to one champion for Weex > project(https://alibaba.github.io/weex/). > > > Any help is appreciated. > > > Weex is a framework for building Mobile cross-platform UI. Weex > allowsdevelopers to build iOS, Android and Web user interface with a > singlecodebase. > > > The project is pretty hot in github https://alibaba.github.io/weex > ,there are more than 7000 stars on it, there are more than 200 > membersin the Weex forum. We want to donate this project to the ASF > andincubate this project in ASF. At the same time, due to there is > fewproject in the UI field, If the project can incubate in the ASF, > Ithink more wonderful projects in these field will join ASF in > thefuture. > > > Right now, there are 4 mentors in our project, but we are seeking > onechampion for our project. If you are interested in this project > orwant to help us, please feel free to contact us. > > > > > Thanks > Longda > > > The following is the Weex proposal > Weex Proposal > === > > ## Abstract > Weex is a framework for building Mobile cross-platform UI. > > ## Proposal > Weex allows developers to build iOS,Android and Web user interfacewith > a single codebase. Compared with WebView based UI framework > whichperformance and features are limited, Weex preserves its > lightweightdevelopment pattern and improve
RE: Seek one Champion for incubating Weex project
Weex team, I'm recently developing a cross-platform runtime javascript framework and its backend service [1], so I'm very interested in learning this project. If you think we can make some synergy, feel free to add me as a mentor, or champion. I can help. 1. http://121.78.112.135/draft.html -- Best Regards, Edward J. Yoon -Original Message- From: Benjamin Young [mailto:byo...@bigbluehat.com] Sent: Thursday, November 03, 2016 11:13 PM To: general@incubator.apache.org Cc: weex-apache; Stephan Ewen; luke...@gmail.com; hedh...@gmail.com; willem. ji...@gmail.com; Longda Feng Subject: Re: Seek one Champion for incubating Weex project Hi Jinjiang and Longda, Were you all able to find a Champion for the Incubator? I'd hate to see this great project miss out on benefiting from the Apache Way. Please let us know if you're still in need of help finding a Champion or Mentors. Thanks! Benjamin -- http://bigbluehat.com/ http://linkedin.com/in/benjaminyoung From: 略쏩쉭 <zhaojinji...@me.com> Sent: Tuesday, October 11, 2016 5:18:03 PM To: general@incubator.apache.org Cc: weex-apache; Stephan Ewen; luke...@gmail.com; hedh...@gmail.com; willem. ji...@gmail.com; Longda Feng Subject: Re: Seek one Champion for incubating Weex project Hi I'am Jinjiang Zhao from Weex team. Weex hope to help more people build their mobile apps with high perf easier and faster. Just write once run any platforms. Also it uses HTML, CSS, JavaScript syntax and is more friendly for frontend developers. Very glad to know every guys. Thanks. Jinjiang > 瞳 2016쾨10墩11휑，09:54，Longda Feng <lon...@apache.org> 畇돛： > > Hi > > The Weex team are looking forward to one champion for Weex project > (https://alibaba.github.io/weex/). > > > > Any help is appreciated. > > > > Weex is a framework for building Mobile cross-platform UI. Weex allows > developers to build iOS, Android and Web user interface with a single > codebase. > > > > The project is pretty hot in github https://alibaba.github.io/weex , > there are more than 7000 stars on it, there are more than 200 members > in the Weex forum. We want to donate this project to the ASF and > incubate this project in ASF. At the same time, due to there is few > project in the UI field, If the project can incubate in the ASF, I > think more wonderful projects in these field will join ASF in the > future. > > > > Right now, there are 4 mentors in our project, but we are seeking one > champion for our project. If you are interested in this project or > want to help us, please feel free to contact us. > > > > > > Thanks > > Longda > > > > The following is the Weex proposal > > Weex Proposal > > === > > > ## Abstract > > Weex is a framework for building Mobile cross-platform UI. > > > ## Proposal > > Weex allows developers to build iOS,Android and Web user interface > with a single codebase. Compared with WebView based UI framework which > performance and features are limited, Weex preserves its lightweight > development pattern and improve the user experience by high-quality > native view and native features at the same time.. > > > Weex provide a tag based language which maintained a consistent style > with Web standards. Developers write in this language just like > writting in HTML. After transforming to JSBundle by Weex build-in > tools, these tag will be render to higher-level platform-specific > components using Weex SDK. > > > Because Weex use JavaScript as UI operation and data processing > language which don't need compile before execute in user's Mobile > phone. Interface implemented by Weex is "Dynamic". At the time of this > writing , another famed dynamic Native UI framework is React Native > which developed by Facebook Inc . > > > Weex and React Native share some common features but have different > language syntax. React Native use specific JSX , whereas Weex use > vanilla Javascript .React Native set target that to replace whole > Mobile App development process, whereas Weex allow developer choose > which page in Mobile App should be implemented by Weex freely. At > principle level React Native adopt "Learn Once, Write Anywhere", > whereas Weex keep "Write Once, Run Everywhere" on different platform > development environment. > > > We think Weex is an effective supplement to Apache Cordova. Both > Apache Cordova and Weex help developer for leveraging Web development > technique in Mobile age. Boot developer the ability of delivering > consistent content to different platform. With our sincere heart and > determination to open source , we will always keep an open mind for > Apache Cordova community. > > > ##
RE: [VOTE] Accept NetBeans into the Apache Incubator
+1 (binding) -- Best Regards, Edward J. Yoon -Original Message- From: Sergio Fernandez [mailto:wik...@apache.org] Sent: Wednesday, September 28, 2016 3:36 PM To: general@incubator.apache.org Subject: Re: [VOTE] Accept NetBeans into the Apache Incubator +1 (binding) On Tue, Sep 27, 2016 at 10:30 PM, Ate Douma <a...@douma.nu> wrote: > Hi everyone, > > Now that the discussion thread on the NetBeans Proposal has ended, > please vote on accepting NetBeans into the Apache Incubator. > > The ASF voting rules are described at: >http://www.apache.org/foundation/voting.html > > A vote for accepting a new Apache Incubator podling is a majority vote > for which only Incubator PMC member votes are binding. > > Votes from other people are also welcome as an indication of peoples > enthusiasm (or lack thereof). > > Please do not use this VOTE thread for discussions. > If needed, start a new thread instead. > > This vote will run for at least 72 hours. Please VOTE as follows > [] +1 Accept NetBeans into the Apache Incubator > [] +0 Abstain. > [] -1 Do not accept NetBeans into the Apache Incubator because ... > > > The proposal is listed below, but you can also access it on the wiki: >https://wiki.apache.org/incubator/NetBeansProposal > > > Thanks, > Ate. > > == Abstract == > > NetBeans is an open source development environment, tooling platform, and > application framework, used by 1.5 million individuals each month. > > == Proposal == > Apache NetBeans will continue to focus on the areas it has focused on while > sponsored by Sun Microsystems and Oracle. It will continue to primarily > focus on > providing tools for the Java ecosystem, while also being focused on tools > for > other ecosystems, languages and technologies, such as JavaScript, PHP, and > C/C++. It will continue to actively support its community by means of > mailing > lists, tutorials, and documentation. > > == Background == > NetBeans started in 1995/96 in Prague, in the Czech Republic, as a student > project. Sun Microsystems acquired and open sourced it in 2000 and, with > the > acquisition of Sun Microsystems by Oracle in 2010, became part of Oracle. > Throughout its history in Sun Microsystems and Oracle, NetBeans has been > free > and open source and has been leveraged by its sponsor as a mechanism for > driving > the Java ecosystem forward. > > == Rationale == > Although NetBeans is already open source, moving it to a neutral place like > Apache, with its strong governance model, is expected to help get more > contributions from various organizations. For example, large companies are > using > NetBeans as an application framework to build internal or commercial > applications and are much more likely to contribute to it once it moves to > neutral Apache ground. At the same time, though Oracle will relinquish its > control over NetBeans, individual contributors from Oracle are expected to > continue contributing to NetBeans after it has been contributed to Apache, > together with individual contributors from other organizations, as well as > self-employed individual contributors. > > == Initial Goals == > The initial goals of the NetBeans contribution under the Apache umbrella > are to > establish a new home for an already fully functioning project and to open > up the > governance model so as to simplify and streamline contributions from the > community. > > == Current Status == > Meritocracy: NetBeans has been run by Oracle, with the majority of code > contributions coming from Oracle. The specific reason for moving to Apache > is to > expand the diversity of contributors and to increase the level of > meritocracy in > NetBeans. Apache NetBeans will be actively seeking new contributors and > will > welcome them warmly and provide a friendly and productive environment for > purposes of providing a development environment, tooling environment, and > application framework. > > Community: NetBeans has approximately 1.5 million active users around > the > world, in extremely diverse structures and organizations. NetBeans is used > by > teachers and instructors at schools and universities to teach Java and > other > languages. It is used by students as an educational tool. It is used by > large > organizations who base their software on the application framework beneath > NetBeans. It is used by web developers for creating web sites and by > developers > using a range of tools, languages, and technologies to be productive and > efficient software developers. > > Core Developers: The core developers will come from a range of > organizations, including Oracle, which will continue its investment in > Ne
Question about some library dependencies.
Hi, In HORN podling, we consider about using Aparapi, a Java-to-OpenCL conversion tool from AMD [1] for support SIMD and GPUs. I wonder whether aparapi.jar and native libaparapi.so binary files can be included in Apache release tarball. Thanks! 1. https://github.com/aparapi/aparapi/blob/master/LICENSE.TXT#L14 -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release apache-singa-incubating-0.3.0 (RC3)
+1 (binding) -- Best Regards, Edward J. Yoon -Original Message- From: Anh Dinh [mailto:dinh...@comp.nus.edu.sg] Sent: Monday, April 18, 2016 12:55 PM To: general@incubator.apache.org Subject: [VOTE] Release apache-singa-incubating-0.3.0 (RC3) Hi all, The SINGA community has voted on and approved a proposal to release Apache SINGA 0.3.0 (incubating). This release candidate (RC3) addressed the issue with the previous release candidate which contains Creative Common licensed file: https://issues.apache.org/jira/browse/SINGA-159 The vote thread is at: http://mail-archives.apache.org/mod_mbox/singa-dev/201604.mbox/%3CCAAbkU4QROZh4qh1qorR0XMNGvwg5sMad-9JqggByO6vUVnxmtQ%40mail.gmail.com%3E and the result is at: http://mail-archives.apache.org/mod_mbox/singa-dev/201604.mbox/%3CCAAbkU4S_G-BmQ3jzjFbz%2BBtGQC-az_CjKwPM7usCWwBdBp8%2B0w%40mail.gmail.com%3E We ask the IPMC to vote on this release. The artifacts to be voted on are located at: https://dist.apache.org/repos/dist/dev/incubator/singa/0.3.0/ The hashes of the artifacts are as follows: MD5: 45 4C 7A BB 17 C7 D6 47 77 85 92 58 59 DF B7 F5 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/dinhtta.asc and the signature file is: https://dist.apache.org/repos/dist/dev/incubator/singa/0.3.0/apache-singa-incubating-0.3.0-RC3.tar.gz.asc The Github tag is at: https://github.com/apache/incubator-singa/releases/tag/v0.3.0-rc3 with commit ID: d547a861068973db7d8fc82f9c733e95307a40f1 To check the license, you can use the Apache Rat tool following ``` ./configure make rat ``` The result is in rat_check file. The vote is open for at least 72 hours, or until the necessary number of votes (3 +1) is reached. [ ] +1 Release this package as Apache SINGA 0.3.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... Regards, Anh. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Zeppelin from the Incubator
..@apache.org <javascript:;>> > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lee Moon Soo > > > be appointed to the office of Vice President, Apache Zeppelin, to > > > serve in accordance with and subject to the direction of the > > > Board of Directors and the Bylaws of the Foundation until > > > death, resignation, retirement, removal or disqualification, > > > or until a successor is appointed; and be it further > > > > > > RESOLVED, that the initial Apache Zeppelin PMC be and hereby is > > > tasked with the creation of a set of bylaws intended to > > > encourage open development and increased participation in the > > > Apache Zeppelin Project; and be it further > > > > > > RESOLVED, that the Apache Zeppelin Project be and hereby > > > is tasked with the migration and rationalization of the Apache > > > Incubator Zeppelin podling; and be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache > > > Incubator Zeppelin podling encumbered upon the Apache Incubator > > > Project are hereafter discharge. > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > <javascript:;> > > For additional commands, e-mail: general-h...@incubator.apache.org > <javascript:;> > > > > > -- Best Regards, Edward J. Yoon
RE: [VOTE] Graduate TinkerPop from Incubator
+1 (binding) -- Best Regards, Edward J. Yoon -Original Message- From: Jean-Baptiste Onofre [mailto:j...@nanthrax.net] Sent: Wednesday, April 06, 2016 3:04 PM To: general@incubator.apache.org Subject: Re: [VOTE] Graduate TinkerPop from Incubator +1 (binding) Regards JB On 04/05/2016 01:11 PM, Stephen Mallette wrote: > The Apache TinkerPop community has discussed graduation to a top level > project and achieved consensus: > > https://s.apache.org/PKhX > > Please vote on the resolution that follows to graduate Apache TinkerPop > from incubator to top level project. This vote will be open for at least 72 > hours. > > Thanks, > > Stephen Mallette on behalf of the Apache TinkerPop PPMC > > == > X. Establish the Apache TinkerPop Project > > WHEREAS, the Board of Directors deems it to be in the best > interests of the Foundation and consistent with the > Foundation's purpose to establish a Project Management > Committee charged with the creation and maintenance of > open-source software, for distribution at no charge to > the public, related to a graph computing framework for graph > databases and graph analytic systems > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache TinkerPop Project", > be and hereby is established pursuant to Bylaws of the > Foundation; and be it further > > RESOLVED, that the Apache TinkerPop Project be and hereby is > responsible for the creation and maintenance of software > related to a graph computing framework for graph databases > and graph analytic systems. > > RESOLVED, that the office of "Vice President, Apache TinkerPop" be > and hereby is created, the person holding such office to > serve at the direction of the Board of Directors as the chair > of the Apache TinkerPop Project, and to have primary responsibility > for management of the projects within the scope of > responsibility of the Apache TinkerPop Project; and be it further > > RESOLVED,that the persons listed immediately below be and > hereby are appointed to serve as the initial members of the > Apache TinkerPop Project Management Committee: > > * Daniel Gruno <humbed...@apache.org> > * Daniel Kuppitz <dkupp...@apache.org> > * James Thornton <esp...@apache.org> > * Hadrian Zbarcea <hadr...@apache.org> > * Marko Rodriguez <ok...@apache.org> > * Stephen Mallette <spmalle...@apache.org> > * Ted Wilmes <twil...@apache.org> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephen Mallette > be appointed to the office of Vice President, Apache TinkerPop, to > serve in accordance with and subject to the direction of the > Board of Directors and the Bylaws of the Foundation until > death, resignation, retirement, removal or disqualification, > or until a successor is appointed; and be it further > > RESOLVED, that the initial Apache TinkerPop PMC be and hereby is > tasked with the creation of a set of bylaws intended to > encourage open development and increased participation in the > Apache TinkerPop Project; and be it further > > RESOLVED, that the Apache TinkerPop Project be and hereby > is tasked with the migration and rationalization of the Apache > Incubator TinkePop podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator TinkerPop podling encumbered upon the Apache Incubator > Project are hereafter discharged. > -- Jean-Baptiste Onofre jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Beam into the Apache Incubator
>>> Kubernetes >> > >>>>>> (http://kubernetes.io/). With Dataflow, we have tried to be >> > >>>> increasingly >> > >>>>>> open and forward-looking; we have published a paper in the VLDB >> > >>>>>> conference describing the Dataflow model >> > >>>>>> (http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf) and were quick >> to >> > >>>>>> release the Dataflow SDK as open source software with the launch >> of >> > >>>>>> Cloud Dataflow. Our submission to the Apache Software Foundation >> is >> > >>>>>>a >> > >>>>>> logical extension of our commitment to open source software. >> > >>>>>> >> > >>>>>> === Homogeneous Developers === >> > >>>>>> >> > >>>>>> The majority of committers in this proposal belong to Google due >> to >> > >>> the >> > >>>>>> fact that Dataflow has emerged from several internal Google >> > >>>>>>projects. >> > >>>>>> This proposal also includes committers outside of Google who are >> > >>>>>> actively involved with other Apache projects, such as Hadoop, >> Flink, >> > >>>> and >> > >>>>>> Spark. We expect our entry into incubation will allow us to >> expand >> > >>> the >> > >>>>>> number of individuals and organizations participating in Dataflow >> > >>>>>> development. Additionally, separation of the Dataflow SDK from >> > >>>>>>Google >> > >>>>>> Cloud Dataflow allows us to focus on the open source SDK and model >> > >>> and >> > >>>>>> do what is best for this project. >> > >>>>>> >> > >>>>>> === Reliance on Salaried Developers === >> > >>>>>> >> > >>>>>> The Dataflow SDK and Dataflow runners have been developed >> primarily >> > >>> by >> > >>>>>> salaried developers supporting the Google Cloud Dataflow project. >> > >>> While >> > >>>>>> the Dataflow SDK and Cloud Dataflow have been developed by >> different >> > >>>>>> teams (and this proposal would reinforce that separation) we >> expect >> > >>> our >> > >>>>>> initial set of developers will still primarily be salaried. >> > >>>> Contribution >> > >>>>>> has not been exclusively from salaried developers, however. For >> > >>>> example, >> > >>>>>> the contrib directory of the Dataflow SDK >> > >>>>>> ( >> > >>>>>> >> > >>>>> >> > >>>> >> > >>> >> > >>> >> > https://github.com/GoogleCloudPlatform/DataflowJavaSDK/tree/master/contr >> > >>>ib >> > >>>>>> ) >> > >>>>>> contains items from free-time contributors. Moreover, seperate >> > >>>> projects, >> > >>>>>> such as ScalaFlow (https://github.com/darkjh/scalaflow) have been >> > >>>>>> created around the Dataflow model and SDK. We expect our reliance >> on >> > >>>>>> salaried developers will decrease over time during incubation. >> > >>>>>> >> > >>>>>> === Relationship with other Apache products === >> > >>>>>> >> > >>>>>> Dataflow directly interoperates with or utilizes several existing >> > >>>> Apache >> > >>>>>> projects. >> > >>>>>> >> > >>>>>> * Build >> > >>>>>> * Apache Maven >> > >>>>>> * Data I/O, Libraries >> > >>>>>> * Apache Avro >> > >>>>>> * Apache Commons >> > >>>>>> * Dataflow runners >> > >>>>>> * Apache Flink >> > >>>>>> * Apache Spark >> > >>>>>> >> > >>&
RE: How to trigger GitHub mirror
Hi, you can use this https://issues.apache.org/jira/servicedesk/customer/portal/1 to request Github Integration. See also http://www.apache.org/dev/infra-contact. -- Best Regards, Edward J. Yoon -Original Message- From: Zachary Jaffee [mailto:z...@case.edu] Sent: Thursday, January 28, 2016 3:12 PM To: d...@fineract.incubator.apache.org Cc: general@incubator.apache.org Subject: Re: How to trigger GitHub mirror Are you sure that you made the commit? I Just cloned the apache repo directly, and I only saw that a git init had been done. There is an ASF github bot that has the ability to merge across the mirrors. On Thu, Jan 28, 2016 at 12:53 AM, Markus Geiß <markus.ge...@live.de> wrote: > Hey all, > hope this finds you well. ; o) > > I've pushed the initial code for Fineract to the Apache git repo at master > and wandering > how I can trigger the GitHub mirror to reflect these changes. > > Best, > > Markus > > .::YAGNI likes a DRY KISS::. -- Zach Jaffee B.S. Computer Science Case Western Reserve University Class of 2017 Operations Director | WRUW FM 91.1 Cleveland Secretary | Recruitment Chair | Phi Kappa Theta Fraternity (917) 881-0646 zjaffee.com github.com/ZJaffee - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Apache Dataflow Incubator Proposal
Pls add me to "Additional Interested Contributors" section too. :-) -- Best Regards, Edward J. Yoon -Original Message- From: Jean-Baptiste Onofr� [mailto:j...@nanthrax.net] Sent: Thursday, January 21, 2016 2:39 PM To: general@incubator.apache.org Subject: Re: [DISCUSS] Apache Dataflow Incubator Proposal Cool ! I added you on the proposal. Regards JB On 01/21/2016 12:20 AM, ksobkowiak wrote: > It's a great news the project is going to move to Apache. I'd be interested > in contributing too > > Regards > Krzysztof > > > > -- > View this message in context: http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-Apache-Dataflow -Incubator-Proposal-tp47985p48025.html > Sent from the Apache Incubator - General mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Jean-Baptiste Onofr� jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Apache Dataflow Incubator Proposal
Wow .. great news! -- Best Regards, Edward J. Yoon -Original Message- From: Johan Edstrom [mailto:seij...@gmail.com] Sent: Thursday, January 21, 2016 8:56 AM To: general@incubator.apache.org Subject: Re: [DISCUSS] Apache Dataflow Incubator Proposal Looking forward, also interested in contributing. > On Jan 20, 2016, at 4:54 PM, Hugo Louro <hmclo...@gmail.com> wrote: > > Hello everyone, > > Very compelling proposal; congrats! I would be interested in contributing > to this project from the beginning. > > Looking forward to it. > > Best, > Hugo > > On Wed, Jan 20, 2016 at 3:24 PM, Prasanth Jayachandran < > pjayachand...@hortonworks.com> wrote: > >> Hi Jean >> >> I’d be interested in contributing as well. >> >> Thanks >> Prasanth Jayachandran >> >>> On Jan 20, 2016, at 5:20 PM, ksobkowiak <krzys.sobkow...@gmail.com> >> wrote: >>> >>> It's a great news the project is going to move to Apache. I'd be >> interested >>> in contributing too >>> >>> Regards >>> Krzysztof >>> >>> >>> >>> -- >>> View this message in context: >> http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-Apache-Dataflow-Incubator-Proposal-tp47985p48025.html >>> Sent from the Apache Incubator - General mailing list archive at >> Nabble.com. >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform
Hello, looks interesting. Please excuse my ignorance quick question, Tempo will only support RhythmOS? -- Best Regards, Edward J. Yoon -Original Message- From: Hadrian Zbarcea [mailto:hzbar...@gmail.com] Sent: Tuesday, January 12, 2016 10:35 AM To: general@incubator.apache.org Cc: t...@litbit.com Subject: Re: [PROPOSAL] Tempo - A proposal for an enterprise IoT platform With a bit of delay due to the Holidays season, I think it's time to continue this thread. The code has been available for a while to mentors and those who requested. I assume the mentors did take a look at it, I certainly did. The code looks clean and the idea sound. Plus the IoT field is one that matures fast and I consider a good fit for ASF technologies. There is the outstanding issue of changing the name as it seems unlikely to graduate as Tempo. There is a proposal to incubate it under the "iota" name (whatever the capitalization). Tony, if you could update the proposal to reflect that (or whatever name you choose) it'd be great. After that, assuming no other objections or concerns, I would suggest starting a vote. Cheers, Hadrian On 12/25/2015 09:49 PM, Roman Shaposhnik wrote: > Hi Tony! > > Has there been any activity around this proposal? I find it really > interesting, > and just like Hadrian I really would love to see the code on GitHub > (although > it is NOT a pre-requisite to being consider for ASF Incubator). > > Thanks, > Roman. > > P.S. Greetings from your past life managing JavaStudio ;-) > > > On Wed, Dec 2, 2015 at 3:50 PM, Hadrian Zbarcea <hadr...@apache.org> wrote: >> Hi Tony, >> >> It is a very interesting proposal and I would like to help out as well. I >> do >> have a bit of experience of the IoT field, both part of my ASF >> contributions >> and other work I did. I volunteer to be a mentor or champion. Looks like >> one >> of your understated goals is to grow a community and I agree the ASF is the >> right place for that. >> >> You mentioned the code being available on github, but I couldn't find it >> where I thought it could be [1]. Would it be possible to make the code >> available to potential mentors? I think it would speed up the process and >> you would get more support faster. >> >> There were also a number of positive answers to your email on the incubator >> list, but you were not cc'ed, so if you're not subscribed to the list you >> might have missed them. >> >> It's a great idea, thanks for considering the ASF incubator and it could >> have great success given the growth of IoT. >> >> Best Regards, >> Hadrian >> >> [1] https://github.com/litbit >> >> >> >> On 12/02/2015 03:34 PM, Tony Faustini wrote: >>> >>> To: general@incubator.apache.org >>> >>> Hi All, Litbit is an enterprise IoT company comprised of individuals >>> that have worked for Yahoo, Apple, Microsoft, Sun Microsystems, Intel, >>> Cisco Systems and 365 Main. We are working with some of the world's >>> leading companies providing them with an enterprise IoT platform. We >>> value the open source community and the way it is changing enterprise >>> software. We are eager to build an open source community around Tempo >>> which powers RhythmOS our commercial offering. >>> >>> Thanks >>> -Tony Faustini (Litbit Co) >>> >>> >>> Tempo - A Proposal for Apache Incubator >>> >>> Abstract >>> >>> The Apache Foundation has been very successful in bringing together >>> key software components that have enabled people to interact with each >>> other via a variety of content platforms and it will no doubt continue >>> to do so. At the same time modern society is becoming increasingly >>> dependent on devices that interact with each other and with people. >>> The amount of data that will be produced by devices will be orders of >>> magnitude greater than what has been produced by humans in the past. >>> In addition, the orchestration of devices and people will be an >>> important area of growth for the foreseeable future. This new dynamic >>> will eventually become manifest in a growing number of Apache projects >>> that enable this to occur. Our wish is to contribute to this movement >>> by contributing the Tempo system to the Open Source Community via the >>> Apache Foundation. Tempo is an open platform to interconnect any and >>> all devices, sensors, people, and applications, henceforth referred to >>> as points, through a scalable, secure, and modular architecture, >>&g
Re: [VOTE] Accept S2Graph into Apache Incubation
iliar with the S2Graph codebase. We will work to attract >>> > them as future committers during the incubation phase, following a >>> > merit-based approach. >>> > >>> > === Reliance on Salaried Developers === >>> > Kakao invested in S2Graph as the distributed graph database solution >>> > on top of HBase and some of its key engineers are working full time on >>> > the project. We look forward to other Apache developers and >>> > researchers contributing to the project. Also key to addressing the >>> > risk associated with relying on Salaried developers from a single >>> > entity is to increase the diversity of the contributors and actively >>> > lobby for Domain experts in the graph database space to contribute. >>> > Apache S2Graph intends to do this. >>> > >>> > === Relationships with Other Apache Products === >>> > S2Graph has a strong relationship and dependency with Apache HBase and >>> > Apache Spark. Being part of Apache’s Incubation community, could help >>> > with a closer collaboration among these two projects and as well as >>> > others. >>> > >>> > In terms of graph processing frameworks, S2Graph and Apache Giraph >>> > look similar. However, their goals are apparently different to each >>> > other. Giraph aims at analytical batch processing on immutable graph >>> > data sets. In contrast, S2Graph is designed for OLTP-like workloads on >>> > graph data sets, and S2Graph provides INSERT/UPDATE operations too. >>> > >>> > >>> > === An Excessive Fascination with the Apache Brand === >>> > S2Graph is proposing to enter incubation at Apache in order to help >>> > efforts to diversify the committer-base, not so much to capitalize on >>> > the Apache brand. The S2Graph project is in production use already >>> > inside Kakao, but is not expected to be a Kakao product for external >>> > customers. As such, the S2Graph project is not seeking to use the >>> > Apache brand as a marketing tool. >>> > >>> > == Documentation == >>> > Information about S2Graph can be found at >>> > https://github.com/kakao/s2graph. The following links provide more >>> > information about S2Graph in open source: >>> > * S2Graph web site: https://steamshon.gitbooks.io/s2graph-book/content/ >>> > * Codebase at Github: https://github.com/kakao/s2graph >>> > * Issue Tracking: https://github.com/kakao/s2graph/issues >>> > * User community: https://groups.google.com/forum/#!forum/s2graph >>> > >>> > == Initial Source == >>> > >>> > The S2Graph codebase is currently hosted on Github: >>> > https://github.com/kakao/s2graph. >>> > >>> > === Source and Intellectual Property Submission Plan === >>> > >>> > Currently, the S2Graph codebase is distributed under the Apache 2.0 >>> > License. >>> > >>> > == External Dependencies == >>> > >>> > Beyond relying on Apache HBase, S2Graph has the following external >>> > dependencies: >>> > * Asynchbase (BSD) >>> > * Play Framework (Apache 2.0 license) >>> > * Scala (http://www.scala-lang.org/license.html) >>> > * Spark (Apache 2.0 license) >>> > * Kafka (Apache 2.0 license) >>> > >>> > == Required Resources == >>> > >>> > === Mailing list === >>> > >>> > We will migrate our mailing lists to the following: >>> > * us...@s2graph.incubator.apache.org >>> > * d...@s2graph.incubator.apache.org >>> > * priv...@s2graph.incubator.apache.org >>> > * comm...@s2graph.incubator.apache.org >>> > >>> > === Source control === >>> > >>> > The S2Graph team would like to use Git for source code control, due to >>> > our current use of Git. We request a writeable Git repo for S2Graph, >>> > and mirroring to be set up to Github through INFRA. >>> > >>> > === Issue Tracking === >>> > >>> > S2Graph currently uses the github issue tracking system associated >>> > with its github repo (https://github.com/kakao/s2graph/issues). We >>> > will migrate to the Apache JIRA >>> > (http://issues.apache.org/jira/browse/S2Graph). >>> > >>> > === Other Resources === >>> > >>> > * Jenkins/Hudson for builds and test running. >>> > * Wiki for documentation purposes. >>> > * Blog to improve project dissemination. >>> > >>> > == Initial Committers == >>> > >>> > * Doyung Yoon >>> > * Daewon Jeong >>> > * Jaesang Kim >>> > * Hwansung Yu >>> > * Min-Seok Kim >>> > * Chul Kang >>> > * Luke Han >>> > * Alexander Bezzubov >>> > >>> > == Affiliations == >>> > >>> > * Doyung Yoon, Kakao >>> > * Daewon Jeong, Kakao >>> > * Jaesang Kim, Kakao >>> > * Hwansung Yu, Kakao >>> > * Min-Seok Kim, Kakao >>> > * Chul Kang, Kakao, >>> > * Luke Han, Ebay Inc. >>> > * Alexander Bezzubov, NFLabs >>> > >>> > == Sponsors == >>> > >>> > === Champion === >>> > Hyunsik Choi >>> > >>> > === Nominated Mentors === >>> > * Andrew Purtell - Apache Member, Salesforce >>> > * Sergio Fernández - Apache Member, Redlink >>> > * Hyunsik Choi - Apache Member, Gruter Inc. >>> > * Seetharam Venkatesh - IPMC, Hortonworks Inc. >>> > >>> > === Sponsoring Entity === >>> > >>> > * The Apache Incubator >>> > >>> > - >>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> > For additional commands, e-mail: general-h...@incubator.apache.org >>> > >>> > >>> >> >> >> >> -- >> Julien > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Kudu into the Apache Incubator
ere exists an unrelated open source project by the same name related to >> > deployments on Microsoft’s Azure cloud service. We have been in contact >> > with legal counsel from Microsoft and have obtained their approval for >> the >> > use of the Kudu name. >> > >> > >> > >> > Cloudera currently owns several domain names related to Kudu (getkudu.io >> , >> > kududb.io, et al) which will be transferred to the ASF and redirected to >> > the official page during incubation. >> > >> > >> > >> > Portions of Kudu are protected by pending or published patents owned by >> > Cloudera. Given the protections already granted by the Apache License, we >> > do not anticipate any explicit licensing or transfer of this intellectual >> > property. >> > >> > == External Dependencies == >> > >> > The full set of dependencies and licenses are listed in >> > https://github.com/cloudera/kudu/blob/master/LICENSE.txt >> > >> > and summarized here: >> > >> > * '''Twitter Bootstrap''': Apache 2.0 >> > * '''d3''': BSD 3-clause >> > * '''epoch JS library''': MIT >> > * '''lz4''': BSD 2-clause >> > * '''gflags''': BSD 3-clause >> > * '''glog''': BSD 3-clause >> > * '''gperftools''': BSD 3-clause >> > * '''libev''': BSD 2-clause >> > * '''squeasel''':MIT license >> > * '''protobuf''': BSD 3-clause >> > * '''rapidjson''': MIT >> > * '''snappy''': BSD 3-clause >> > * '''trace-viewer''': BSD 3-clause >> > * '''zlib''': zlib license >> > * '''llvm''': University of Illinois/NCSA Open Source (BSD-alike) >> > * '''bitshuffle''': MIT >> > * '''boost''': Boost license >> > * '''curl''': MIT >> > * '''libunwind''': MIT >> > * '''nvml''': BSD 3-clause >> > * '''cyrus-sasl''': Cyrus SASL license (BSD-alike) >> > * '''openssl''': OpenSSL License (BSD-alike) >> > >> > * '''Guava''': Apache 2.0 >> > * '''StumbleUpon Async''': BSD >> > * '''Apache Hadoop''': Apache 2.0 >> > * '''Apache log4j''': Apache 2.0 >> > * '''Netty''': Apache 2.0 >> > * '''slf4j''': MIT >> > * '''Apache Commons''': Apache 2.0 >> > * '''murmur''': Apache 2.0 >> > >> > >> > '''Build/test-only dependencies''': >> > >> > * '''CMake''': BSD 3-clause >> > * '''gcovr''': BSD 3-clause >> > * '''gmock''': BSD 3-clause >> > * '''Apache Maven''': Apache 2.0 >> > * '''JUnit''': EPL >> > * '''Mockito''': MIT >> > >> > == Cryptography == >> > >> > Kudu does not currently include any cryptography-related code. >> > >> > == Required Resources == >> > >> > === Mailing lists === >> > >> > * priv...@kudu.incubator.apache.org (PMC) >> > * comm...@kudu.incubator.apache.org (git push emails) >> > * iss...@kudu.incubator.apache.org (JIRA issue feed) >> > * d...@kudu.incubator.apache.org (Gerrit code reviews plus dev >> discussion) >> > * u...@kudu.incubator.apache.org (User questions) >> > >> > >> > === Repository === >> > >> > * git://git.apache.org/kudu >> > >> > === Gerrit === >> > >> > We hope to continue using Gerrit for our code review and commit workflow. >> > The Kudu team has already been in contact with Jake Farrell to start >> > discussions on how Gerrit can fit into the ASF. We know that several >> other >> > ASF projects and podlings are also interested in Gerrit. >> > >> > >> > >> > If the Infrastructure team does not have the bandwidth to support Gerrit, >> > we will continue to support our own instance of Gerrit for Kudu, and make >> > the necessary integrations such that commits are properly authenticated >> and >> > maintain sufficient provenance to uphold the ASF standards (e.g. via the >> > solution adopted by the AsterixDB podling). >> > >> > == Issue Tracking == >> > >> > We would like to import our current JIRA project into the ASF JIRA, such >> > that our historical commit messages and code comments continue to >> reference >> > the appropriate bug numbers. >> > >> > == Initial Committers == >> > >> > * Adar Dembo a...@cloudera.com >> > * Alex Feinberg a...@strlen.net >> > * Andrew Wang w...@apache.org >> > * Dan Burkert d...@cloudera.com >> > * David Alves dral...@apache.org >> > * Jean-Daniel Cryans jdcry...@apache.org >> > * Mike Percy mpe...@apache.org >> > * Misty Stanley-Jones mi...@apache.org >> > * Todd Lipcon t...@apache.org >> > >> > The initial list of committers was seeded by listing those contributors >> who >> > have contributed 20 or more patches in the last 12 months, indicating >> that >> > they are active and have achieved merit through participation on the >> > project. We chose not to include other contributors who either have not >> yet >> > contributed a significant number of patches, or whose contributions are >> far >> > in the past and we don’t expect to be active within the ASF. >> > >> > == Affiliations == >> > >> > * Adar Dembo - Cloudera >> > * Alex Feinberg - Forward Networks >> > * Andrew Wang - Cloudera >> > * Dan Burkert - Cloudera >> > * David Alves - Cloudera >> > * Jean-Daniel Cryans - Cloudera >> > * Mike Percy - Cloudera >> > * Misty Stanley-Jones - Cloudera >> > * Todd Lipcon - Cloudera >> > >> > == Sponsors == >> > >> > === Champion === >> > >> > * Todd Lipcon >> > >> > === Nominated Mentors === >> > >> > * Jake Farrell - ASF Member and Infra team member, Acquia >> > * Brock Noland - ASF Member, StreamSets >> > * Michael Stack - ASF Member, Cloudera >> > * Jarek Jarcec Cecho - ASF Member, Cloudera >> > * Chris Mattmann - ASF Member, NASA JPL and USC >> > * Julien Le Dem - Incubator PMC, Dremio >> > * Carl Steinbach - ASF Member, LinkedIn >> > >> > === Sponsoring Entity === >> > >> > The Apache Incubator >> > >> -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Apache Metrics, Not Apache Humans
momentary issue or concern -- though a more general concern about how Apache should evolve. I personally think that the complex human emotions is important evolutionary mechanism. The machine or math can't. On Monday, 16 November 2015, Marko Rodriguez <okramma...@gmail.com> wrote: > Hi, > > I was talking with Daniel Gruno and wrote the following ideas to him. Note > that these are just ideas and not based on any real momentary issue or > concern -- though a more general concern about how Apache should evolve. > > Apache should NOT use a binary "podling" / "top-level" model. All projects > should simply have a "health score" and that health score is derived from > measurables. Because of Apache Infrastructure's centralized server model > (email lists, version control, distributions, homepages, etc.), it has the > ability to gather metrics such as, for example, the distribution of pushes > to the repository, the branch factor of the mailing list, the centrality of > the project in the Central Maven repository dependency graph, the number of > non-sequisters (dead-end conversations) in the email chain, the length of > discussions in JIRA, etc. etc. Which metrics are important? Who care -- > just make up things to glean from the wealth of information you already > have access to. Watch... > > Next, the Apache members subjectively say which projects they think are > "good" (healthy). This can even be a global vote including everyone in the > world and (should be) dynamic over time as projects evolve with time. > Either way, lets say, the ranking says Apache Hadoop, Apache Solr, Apache > Commons, etc. are the (collective subjective's) "best" Apache projects. > Now, there should exist a multi-dimensional projection of the > aforementioned gleaned statistics what will have Hadoop, Solr, Commons, > etc. close to one another in metric-space (clustered). Likewise, low > ranking projects should be close to one another in this space and far from > Hadoop, Solr, Commons, etc. Find that projection and that is your "healthy > metric space." > > From here, all Apache projects have a computed "healthy" score(s) and when > users go to download, lets say, Lucene, they go: "Cool. This is a healthy > project." (it has a HEALTH.txt file distributed with it, lets say). What > that means is that Lucene, at that release was in the "healthy" cluster of > the metric space. This model has various benefits: > > 1. There is no need to have philosophical arguments (not grounded > in measurables) about what rules a project should follow (bounded by law). > - Perhaps a project that is exclusive, but is X is still > in the "healthy" subspace. > - Perhaps having bad documentation is a "unhealthy" even > though Apache doesn't care about documentation. > - Perhaps too much discussion causes a project to become > "unhealthy." > - Perhaps … who knows? … let the statistics do the talking. > - Apache becomes a breeding ground for different models > of open source (bounded by law), not just "The Apache Way." > - And these models are measurable! Let us study > the act of open source. > 2. "Top-level" projects can fall from grace. > - Currently, all "top-level" projects are "equal." This > should by dynamic as the mighty do fall. > - It is possible for what are now "podlings" to be > "healthy" as they simply are coming into Apache. > - "The student is the master." > - Hadoop 1.2.1 might be the healthiest version of Hadoop > (as I tend to believe). "Hadoop" is not a thing eternal. > 3. Less work for people. > - No more VOTEing on graduation. > - No more amorphous aesthetic arguments about "The Apache > Way." > - No more long winded contradictory documentation about > how things should be done (bounded by law). > > The Apache Way should be about metrics, not about philosophy as different > paths lead to the same mountain top <--- See! Is that random Buddhist > saying that everyone just "believes" even true? :) Get the human out of the > loop! > > Thanks for reading, > Marko. > > http://markorodriguez.com > > P.S. The same should hold true for educational degrees. I graduate and now > forever I'm an expert in computers? Medical doctors too! A 90 year old > doctor can do surgery on me?!?!… Binary graduation is not "real." Metrics, > metrics, metrics --- we live in a world where this is possible. For every > "thing" good comes and goes, up and down… -- Best Regards, Edward J. Yoon
Re: [VOTE] Graduate Groovy from the Incubator
> Cédric Champeau <cedric.champ...@gmail.com> >> > Paul King <pa...@asert.com.au> >> > Guillaume Laforge <glafo...@gmail.com> >> > Pascal Schumacher <pascalschumac...@gmx.net> >> > Jochen Theodorou <blackd...@gmx.org> >> > Andrew Bayer <andrew.ba...@gmail.com> >> > Konstantin Boudnik <c...@apache.org> >> > >> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Guillaume Laforge be >> > appointed to the office of Vice President, Apache Groovy, to serve in >> > accordance with and subject to the direction of the Board of Directors >> > and the Bylaws of the Foundation until death, resignation, retirement, >> > removal or disqualification, or until a successor is appointed; and be >> > it further >> > >> > RESOLVED, that the Apache Groovy Project be and hereby is tasked with >> > the migration and rationalization of the Apache Incubator Groovy >> > podling; and be it further >> > >> > RESOLVED, that all responsibilities pertaining to the Apache Incubator >> > Groovy podling encumbered upon the Apache Incubator Project are >> > hereafter discharged. >> >> >> -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: 回复： [VOTE] Graduate Apache Kylin from the Apache Incubator
immediately below be and >> >hereby are appointed to serve as the initial members of the >> >Apache Kylin Project: >> > >> > * Dayue Gao >> > * Jason Zhong >> > * Julian Hyde >> > * Luke Han >> > * Henry Saputra >> > * Hongbin Ma >> > * Hua Huang >> > * Owen O'Malley >> > * P. Taylor Goetz >> > * Qianhao Zhou >> > * Shaofeng Shi >> > * Song Yi >> > * Ted Dunning >> > * Xu Jiang >> > * Yang Li >> > * Yerui Sun < sunyerui at apache dot org> >> > >> > >> >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luke Han >> >be appointed to the office of Vice President,Apache Kylin, to >> serve >> >in accordance with and subject to the direction of the Board of >> >Directors and the Bylaws of the Foundation until death, >> >resignation, retirement, removal or disqualification, or until >> >a successor is appointed; and be it further >> > >> >RESOLVED, that the initial Apache Kylin Project be and hereby >> >is tasked with the creation of a set of bylaws intended to >> >encourage open development and increased participation in the >> >Kylin Project; and be it further >> > >> >RESOLVED, that the initial Apache Kylin Project be and hereby >> >is tasked with the migration and rationalization of the Apache >> >Incubator Kylin podling; and be it further >> > >> >RESOLVED, that all responsibility pertaining to the Apache >> >Incubator Kylin podling encumbered upon the Apache Incubator >> >PMC are hereafter discharged. >> > >> > >> > - - - end - - - >> > >> > >> > - >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > <javascript:;> >> > For additional commands, e-mail: general-h...@incubator.apache.org >> > <javascript:;> >> > >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache SINGA 0.1.0 (incubating)
+1 The final release is generally w/o any suffix, e.g., "-SNAPSHOT", "-RC*". So, if the vote closes positive, the binary files will need to be renamed and digitally signed again, before upload them on the distribution sites. On Wed, Oct 7, 2015 at 9:42 AM, Thejas Nair <thejas.n...@gmail.com> wrote: > +1 > Examined the LICENSE, NOTICE, README, and DISCLAIMER files. Checked the > signatures and checksum. > > The sha256 checksum matches what is in the email, however, the .sha256 > file seems like a different binary file. The .md5 hash is the only hash > most projects seem to publish, so that might be sufficient in this case as > well. > > > > On Tue, Oct 6, 2015 at 10:25 AM, Alan Gates <alanfga...@gmail.com> wrote: > >> +1 >> >> I looked at the signatures, the LICENSE, NOTICE, and DISCLAIMER files, >> checked for any binary files in the distro, and checked that source files >> have the appropriate license header. >> >> Alan. >> >> Wang Wei <wang...@comp.nus.edu.sg> >> September 29, 2015 at 19:47 >> Hi all, >> >> The SINGA community has voted on and approved a proposal to release Apache >> SINGA 0.1.0 (incubating). >> >> The vote thread is at: >> >> http://mail-archives.apache.org/mod_mbox/singa-dev/201509.mbox/%3CCAJz0iLsZRgSuPyrMitpt5EdXvaqf4%2BDiF00Xyg2SLb3YEqkDMw%40mail.gmail.com%3E >> >> and the result is at: >> >> http://mail-archives.apache.org/mod_mbox/singa-dev/201509.mbox/%3CCAJz0iLtGNDT8O31V9QOhrapzFf8Nt0XSjckGR%2BxFHrfrFKraPA%40mail.gmail.com%3E >> >> We ask the IPMC to vote on this release. >> >> The artifacts to be voted on are located here: >> https://dist.apache.org/repos/dist/dev/incubator/singa/ >> >> The hashes of the artifacts are as follows: >> apache-singa-incubating-0.1.0-RC2.tar.gz.md5: 63 0F DF E0 74 E0 E1 1F 89 >> F6 0E DF 9E 66 50 73 >> apache-singa-incubating-0.1.0-RC2.tar.gz.sha256: EE7CF820 70DB46F5 >> 20FC39A1 >> F85B5B73 865503BD 36280917 5369EB9F 5FA7199E >> >> Release artifacts are signed with the following key: >> https://people.apache.org/keys/committer/dinhtta.asc >> >> and the signature file is: >> apache-singa-incubating-0.1.0-RC2.tar.gz.asc >> >> >> The vote is open for at least 72 hours, or until the necessary number of >> votes (3 +1) is reached. >> >> [ ] +1 Release this package as Apache SINGA 0.1.0-incubating >> [ ] 0 I don't feel strongly about it, but I'm okay with the release >> [ ] -1 Do not release this package because... >> >> Thanks. >> >> Regards, >> Wei Wang >> >> > -- Best Regards, Edward J. Yoon
Re: [RESULT][VOTE] Accept Rya into the Apache Incubator
Congratz! On Fri, Sep 18, 2015 at 11:39 PM, Adam Fuchs <afu...@apache.org> wrote: > The vote for accepting Rya into the incubator passes with 5 binding +1s and > 4 non-binding +1s. I will work with the mentors to start the ball rolling. > > Binding +1: > Rob Vesse > Andy Seaborne > Chris Nauroth > Sean Busbey > Venkatesh Seetharam > > Nonbinding +1: > Atri Sharma > Josh Elser > Adina Crainiceanu > Phillip Rhodes > > Thanks! > Adam -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Move HAWQ, HORN to different reporting group
+1 On Wed, Sep 9, 2015 at 10:35 AM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > Makes perfect sense! Thanks, Marvin. > > Thanks, > Roman. > > On Sun, Sep 6, 2015 at 9:34 PM, Marvin Humphrey <mar...@rectangular.com> > wrote: >> Greets, >> >> Our podlings are unevenly distributed among the 3 reporting groups, >> resulting in a heavy load once every three months. >> >> * 1 (Jan, Apr, July, Oct): 18 podlings >> * 2 (Feb, May, Aug, Nov): 21 podlings >> * 3 (Mar, Jun, Sep, Dec): 32 podlings >> >> HAWQ and HORN were initially placed in group 3, but I've taken the >> liberty of moving them to group 1. This means that after monthly >> reports in Oct, Nov, and Dec, they will start reporting quarterly with >> a Jan report. >> >> The groups don't need to be perfectly balanced and so IMO we don't >> need to move other podlings around, but I'd prefer not to worsen the >> imbalance when scheduling new podlings. >> >> Marvin Humphrey >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Horn into the ASF incubator
Hi, Thank you for everyone for participating and warm welcome for the Horn project proposal. The vote has passed with the following result (✓ means IPMC): +1s: Edward J. Yoon ✓ Behroz Sikander Minho Kim Chris Aniszczyk John D. Ament ✓ JongYoon Lim Tommaso Teofili ✓ Atri Sharma Moonsoo Lee Jan Iversen ✓ Chia-Hung Lin Bertrand Delacretaz ✓ Amareshwari Sriramadasu ✓ Alex Karasulu ✓ Jake Farrell ✓ Luciano Resende ✓ Hitesh Shah ✓ Seetharam Venkatesh ✓ 0s: None -1s: None I will continue with the bootstrap process to bring Horn into Apache incubator next week. Thank you again for those participated in the VOTE. Thanks. On Wed, Sep 2, 2015 at 12:27 PM, Seetharam Venkatesh <venkat...@innerzeal.com> wrote: > +1 > > On Tue, Sep 1, 2015 at 11:20 AM Hitesh Shah <hit...@apache.org> wrote: > >> +1 >> >> — Hitesh >> >> On Aug 31, 2015, at 4:13 PM, Edward J. Yoon <edwardy...@apache.org> wrote: >> >> > Hi folks, >> > >> > I would like to call a vote to accept Horn, as a new Apache Incubator >> > project. The full proposal is available at the end of this mail and as >> > a https://wiki.apache.org/incubator/HornProposal (the changes from >> > initial discussion draft are addition of 2 committers from cldi-kaist >> > team and Rich as a mentor). >> > >> > The VOTE is open for at least the next 72 hours: >> > >> > [ ] +1 Accept Horn into the Apache Incubator >> > [ ] 0 >> > [ ] -1 Do not accept Horn into the Apache Incubator bc .. >> > >> > I'd like to get the voting started w/ my own +1 >> > >> > Thanks! >> > >> > == Abstract == >> > >> > Horn [hɔ:n] (korean meaning of Horn is a "Spirit") is a neuron-centric >> > programming APIs and execution framework for large-scale deep >> > learning, built on top of Apache Hama. >> > >> > == Proposal == >> > >> > It is a goal of the Horn to provide a neuron-centric programming APIs >> > which allows user to easily define the characteristic of artificial >> > neural network model and its structure, and its execution framework >> > that leverages the heterogeneous resources on Hama and Hadoop YARN >> > cluster. >> > >> > == Background == >> > >> > The initial ANN code was developed at Apache Hama project by a >> > committer, Yexi Jiang (Facebook) in 2013. The motivation behind this >> > work is to build a framework that provides more intuitive programming >> > APIs like Google's MapReduce or Pregel and supports applications >> > needing large model with huge memory consumptions in distributed way. >> > >> > == Rationale == >> > >> > While many of deep learning open source softwares such as Caffe, >> > DeepDist, DL4j, and NeuralGiraph are still data or model parallel >> > only, we aim to support both data and model parallelism and also >> > fault-tolerant system design. The basic idea of data and model >> > parallelism is use of the remote parameter server to parallelize model >> > creation and distribute training across machines, and the BSP >> > framework of Apache Hama for performing asynchronous mini-batches. >> > Within single BSP job, each task group works asynchronously using >> > region barrier synchronization instead of global barrier >> > synchronization, and trains large-scale neural network model using >> > assigned data sets in BSP paradigm. Thus, we achieve data and model >> > parallelism. This architecture is inspired by Google's !DistBelief >> > (Jeff Dean et al, 2012). >> > >> > == Initial Goals == >> > >> > Some current goals include: >> > >> > * builds new community >> > * provides more intuitive programming APIs >> > * needs both data and model parallelism support >> > * must run natively on both Hama and Hadoop2 >> > * needs also GPUs and InfiniBand support (FPGAs if possible) >> > >> > == Current Status == >> > >> > === Meritocracy === >> > >> > The core developers understand what it means to have a process based >> > on meritocracy. We will provide continuous efforts to build an >> > environment that supports this, encouraging community members to >> > contribute. >> > >> > === Community === >> > >> > A small community has formed within the Apache Hama project community, >> > universities, and companies such as deep learning startup, instant >> > messenger service company, and
[RESULT][VOTE] Accept Horn into the ASF incubator
Sorry but again, Thank you for everyone for participating and warm welcome for the Horn project proposal. The vote has passed with the following result (✓ means IPMC): +1s: Edward J. Yoon ✓ Behroz Sikander Minho Kim Chris Aniszczyk John D. Ament ✓ JongYoon Lim Tommaso Teofili ✓ Atri Sharma Moonsoo Lee Jan Iversen ✓ Chia-Hung Lin Bertrand Delacretaz ✓ Amareshwari Sriramadasu ✓ Alex Karasulu ✓ Jake Farrell ✓ Luciano Resende ✓ Hitesh Shah ✓ Seetharam Venkatesh ✓ 0s: None -1s: None I will continue with the bootstrap process to bring Horn into Apache incubator next week. Thank you again for those participated in the VOTE. Thanks. On Fri, Sep 4, 2015 at 4:48 PM, Edward J. Yoon <edwardy...@apache.org> wrote: > Hi, > > Thank you for everyone for participating and warm welcome for the Horn > project proposal. The vote has passed with the following result (✓ > means IPMC): > > +1s: > > Edward J. Yoon ✓ > Behroz Sikander > Minho Kim > Chris Aniszczyk > John D. Ament ✓ > JongYoon Lim > Tommaso Teofili ✓ > Atri Sharma > Moonsoo Lee > Jan Iversen ✓ > Chia-Hung Lin > Bertrand Delacretaz ✓ > Amareshwari Sriramadasu ✓ > Alex Karasulu ✓ > Jake Farrell ✓ > Luciano Resende ✓ > Hitesh Shah ✓ > Seetharam Venkatesh ✓ > > 0s: > None > > -1s: > None > > I will continue with the bootstrap process to bring Horn into Apache > incubator next week. Thank you again for those participated in the > VOTE. > > Thanks. > > On Wed, Sep 2, 2015 at 12:27 PM, Seetharam Venkatesh > <venkat...@innerzeal.com> wrote: >> +1 >> >> On Tue, Sep 1, 2015 at 11:20 AM Hitesh Shah <hit...@apache.org> wrote: >> >>> +1 >>> >>> — Hitesh >>> >>> On Aug 31, 2015, at 4:13 PM, Edward J. Yoon <edwardy...@apache.org> wrote: >>> >>> > Hi folks, >>> > >>> > I would like to call a vote to accept Horn, as a new Apache Incubator >>> > project. The full proposal is available at the end of this mail and as >>> > a https://wiki.apache.org/incubator/HornProposal (the changes from >>> > initial discussion draft are addition of 2 committers from cldi-kaist >>> > team and Rich as a mentor). >>> > >>> > The VOTE is open for at least the next 72 hours: >>> > >>> > [ ] +1 Accept Horn into the Apache Incubator >>> > [ ] 0 >>> > [ ] -1 Do not accept Horn into the Apache Incubator bc .. >>> > >>> > I'd like to get the voting started w/ my own +1 >>> > >>> > Thanks! >>> > >>> > == Abstract == >>> > >>> > Horn [hɔ:n] (korean meaning of Horn is a "Spirit") is a neuron-centric >>> > programming APIs and execution framework for large-scale deep >>> > learning, built on top of Apache Hama. >>> > >>> > == Proposal == >>> > >>> > It is a goal of the Horn to provide a neuron-centric programming APIs >>> > which allows user to easily define the characteristic of artificial >>> > neural network model and its structure, and its execution framework >>> > that leverages the heterogeneous resources on Hama and Hadoop YARN >>> > cluster. >>> > >>> > == Background == >>> > >>> > The initial ANN code was developed at Apache Hama project by a >>> > committer, Yexi Jiang (Facebook) in 2013. The motivation behind this >>> > work is to build a framework that provides more intuitive programming >>> > APIs like Google's MapReduce or Pregel and supports applications >>> > needing large model with huge memory consumptions in distributed way. >>> > >>> > == Rationale == >>> > >>> > While many of deep learning open source softwares such as Caffe, >>> > DeepDist, DL4j, and NeuralGiraph are still data or model parallel >>> > only, we aim to support both data and model parallelism and also >>> > fault-tolerant system design. The basic idea of data and model >>> > parallelism is use of the remote parameter server to parallelize model >>> > creation and distribute training across machines, and the BSP >>> > framework of Apache Hama for performing asynchronous mini-batches. >>> > Within single BSP job, each task group works asynchronously using >>> > region barrier synchronization instead of global barrier >>> > synchronization, and trains large-scale neural network model using >>> > assigned data sets in BSP paradigm. Thus, we achieve data and mo
Re: [DISCUSS] Rya Incubator Proposal
Hello, I would like to help this project as a mentor if you're OK. I researched this topic for a long time. On Fri, Sep 4, 2015 at 6:08 AM, Adina Crainiceanu <ad...@usna.edu> wrote: > Josh, > > Thank you for volunteering to be out mentor. > > >> As specified in the proposal, I'm happy to volunteer as a mentor >> (currently a member, haven't officially requested to join IPMC). >> >> >> >> >>> === Inexperience with Open Source === >>> >>> The initial committers have various degrees of experience with open source >>> projects - from very new to experienced. This project was open source >>> within government from the beginning. We do not expect to have >>> difficulties >>> in operating under Apache's development process. >>> >> >> This statement struck me as a little odd. While I understand that you >> tried to operate as an open source project, it seems impossible by >> definition to be open source. My biggest concern would just be that you are >> aware that you will have difficulties transitioning to a real open codebase >> and growing a community in the open. > > > We are aware that it will be different and more difficult functioning in a > real open source environment, but we are enthusiastic and committed to > making it work. With the help of our mentors, we hope to be successful. > > >> >> == Initial Source == >>> >>> The code is currently available in a private Github repository. >>> https://github.com/LAS-NCSU/rya >>> >> >> What's the plan to make this a non-private repo? >> > > We are working on it right now. Initially we though that the code will be > made publicly available by bringing it to ASF, but we are working to make > the current repository public. > > > Thank you, > Adina > > > -- > Dr. Adina Crainiceanu > http://www.usna.edu/Users/cs/adina/ -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HAWQ into the Apache Incubator
+1 (binding) On Tuesday, September 1, 2015, Amol Kekre <a...@datatorrent.com> wrote: > +1 (non-binding) > > Amol > > > On Mon, Aug 31, 2015 at 3:03 PM, Justin Mclean <justinmcl...@me.com > <javascript:;>> wrote: > > > +1 (binding) > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > <javascript:;> > > For additional commands, e-mail: general-h...@incubator.apache.org > <javascript:;> > > > > > -- Best Regards, Edward J. Yoon
Re: [DISCUSS] Horn Incubation Proposal
Hi, If there are no more comments/concerns, I plan to call for a vote soon. Thanks! On Wed, Aug 26, 2015 at 9:37 PM, Edward J. Yoon edwardy...@apache.org wrote: More diverse volunteers for Horn project will be added, from cldi-kaist team who is ranked 7th in the ImageNet ILSVRC last year. We're also seeking one more mentor (instead of me). Thanks. P.S., I'm CC'ing current volunteers. If you're still not on the list please subscribe so you can see what's going on. On Fri, Aug 21, 2015 at 2:23 PM, Edward J. Yoon edwardy...@apache.org wrote: multiple worker groups for asynchronous training---data parallelism; and multiple workers in one group for synchronous training---model parallelism. So, it's basically execution of the multiple asynchronous BSP (Bulk Synchronous Parallel) jobs. This can be simply handled within only single BSP job using region barriers as mentioned in proposal. Moreover, since Apache Hama is a general-purpose BSP framework on top of HDFS, it provides the data partition, locality optimization, job/task scheduling, messaging and fault tolerance in scalable way by nature. For the programming model, currently Horn proposes to support feed-forward There are plenty of rooms for collaborations indeed... Yeah, but still it can be more improved. Maybe we can discuss the simplified programming APIs and many others e.g., support GPUs together in the future. On Fri, Aug 21, 2015 at 1:13 PM, ooibc oo...@comp.nus.edu.sg wrote: Hi, I am an initial committer of Apache(incubating) SINGA (http://singa.incubator.apache.org/) Both SINGA and the proposal follow the general parameter-server architecture: workers for computing gradients; servers for parameter updating. SINGA has implemented the model and data parallelism discussed in the Horn' proposal: multiple worker groups for asynchronous training---data parallelism; and multiple workers in one group for synchronous training---model parallelism. One feature of SINGA's architecture is that it can be extended to organize the servers in a hierarchical topology, which may help to reduce the communication bottleneck of servers organized in a flat topology. For the programming model, currently Horn proposes to support feed-forward models, e.g., MLP, auto-encoder, while SINGA supports all three categories of the known models, feed-forward models (eg MLP, CNN), energy models (eg RBM, DBM), and recurrent models (eg. RNN). SINGA provides good support for users to code, e.g., implement new parameter updating protocols or layers, and is being integrated with HDFS as well. We will submit the first release and full documentation to the mentors this weekend, and if ok, we will announce the first full release soon. The GPU version is scheduled for October release. Technical papers: http://www.comp.nus.edu.sg/~ooibc/singa-mm15.pdf http://www.comp.nus.edu.sg/~ooibc/singaopen-mm15.pdf and project website (which has more details than the Apache web site): http://www.comp.nus.edu.sg/~dbsystem/singa/ There are plenty of rooms for collaborations indeed... regards beng chin www.comp.nus.edu.sg/~ooibc On 2015-08-21 08:27, Edward J. Yoon wrote: Hi all, We'd like to propose Horn (혼), a fully distributed system for large-scale deep learning as an Apache Incubator project and start the discussion. The complete proposal can be found at: https://wiki.apache.org/incubator/HornProposal Any advices and helps are welcome! Thanks, Edward. = Horn Proposal = == Abstract == (tentatively named Horn [hɔ:n], korean meaning of Horn is a Spirit) is a neuron-centric programming APIs and execution framework for large-scale deep learning, built on top of Apache Hama. == Proposal == It is a goal of the Horn to provide a neuron-centric programming APIs which allows user to easily define the characteristic of artificial neural network model and its structure, and its execution framework that leverages the heterogeneous resources on Hama and Hadoop YARN cluster. == Background == The initial ANN code was developed at Apache Hama project by a committer, Yexi Jiang (Facebook) in 2013. The motivation behind this work is to build a framework that provides more intuitive programming APIs like Google's MapReduce or Pregel and supports applications needing large model with huge memory consumptions in distributed way. == Rationale == While many of deep learning open source softwares such as Caffe, DeepDist, and NeuralGiraph are still data or model parallel only, we aim to support both data and model parallelism and also fault-tolerant system design. The basic idea of data and model parallelism is use of the remote parameter server to parallelize model creation and distribute training across machines, and the BSP framework of Apache Hama for performing asynchronous mini-batches. Within single BSP job, each task group works asynchronously using region barrier synchronization
Re: [DISCUSS] Horn Incubation Proposal
More diverse volunteers for Horn project will be added, from cldi-kaist team who is ranked 7th in the ImageNet ILSVRC last year. We're also seeking one more mentor (instead of me). Thanks. P.S., I'm CC'ing current volunteers. If you're still not on the list please subscribe so you can see what's going on. On Fri, Aug 21, 2015 at 2:23 PM, Edward J. Yoon edwardy...@apache.org wrote: multiple worker groups for asynchronous training---data parallelism; and multiple workers in one group for synchronous training---model parallelism. So, it's basically execution of the multiple asynchronous BSP (Bulk Synchronous Parallel) jobs. This can be simply handled within only single BSP job using region barriers as mentioned in proposal. Moreover, since Apache Hama is a general-purpose BSP framework on top of HDFS, it provides the data partition, locality optimization, job/task scheduling, messaging and fault tolerance in scalable way by nature. For the programming model, currently Horn proposes to support feed-forward There are plenty of rooms for collaborations indeed... Yeah, but still it can be more improved. Maybe we can discuss the simplified programming APIs and many others e.g., support GPUs together in the future. On Fri, Aug 21, 2015 at 1:13 PM, ooibc oo...@comp.nus.edu.sg wrote: Hi, I am an initial committer of Apache(incubating) SINGA (http://singa.incubator.apache.org/) Both SINGA and the proposal follow the general parameter-server architecture: workers for computing gradients; servers for parameter updating. SINGA has implemented the model and data parallelism discussed in the Horn' proposal: multiple worker groups for asynchronous training---data parallelism; and multiple workers in one group for synchronous training---model parallelism. One feature of SINGA's architecture is that it can be extended to organize the servers in a hierarchical topology, which may help to reduce the communication bottleneck of servers organized in a flat topology. For the programming model, currently Horn proposes to support feed-forward models, e.g., MLP, auto-encoder, while SINGA supports all three categories of the known models, feed-forward models (eg MLP, CNN), energy models (eg RBM, DBM), and recurrent models (eg. RNN). SINGA provides good support for users to code, e.g., implement new parameter updating protocols or layers, and is being integrated with HDFS as well. We will submit the first release and full documentation to the mentors this weekend, and if ok, we will announce the first full release soon. The GPU version is scheduled for October release. Technical papers: http://www.comp.nus.edu.sg/~ooibc/singa-mm15.pdf http://www.comp.nus.edu.sg/~ooibc/singaopen-mm15.pdf and project website (which has more details than the Apache web site): http://www.comp.nus.edu.sg/~dbsystem/singa/ There are plenty of rooms for collaborations indeed... regards beng chin www.comp.nus.edu.sg/~ooibc On 2015-08-21 08:27, Edward J. Yoon wrote: Hi all, We'd like to propose Horn (혼), a fully distributed system for large-scale deep learning as an Apache Incubator project and start the discussion. The complete proposal can be found at: https://wiki.apache.org/incubator/HornProposal Any advices and helps are welcome! Thanks, Edward. = Horn Proposal = == Abstract == (tentatively named Horn [hɔ:n], korean meaning of Horn is a Spirit) is a neuron-centric programming APIs and execution framework for large-scale deep learning, built on top of Apache Hama. == Proposal == It is a goal of the Horn to provide a neuron-centric programming APIs which allows user to easily define the characteristic of artificial neural network model and its structure, and its execution framework that leverages the heterogeneous resources on Hama and Hadoop YARN cluster. == Background == The initial ANN code was developed at Apache Hama project by a committer, Yexi Jiang (Facebook) in 2013. The motivation behind this work is to build a framework that provides more intuitive programming APIs like Google's MapReduce or Pregel and supports applications needing large model with huge memory consumptions in distributed way. == Rationale == While many of deep learning open source softwares such as Caffe, DeepDist, and NeuralGiraph are still data or model parallel only, we aim to support both data and model parallelism and also fault-tolerant system design. The basic idea of data and model parallelism is use of the remote parameter server to parallelize model creation and distribute training across machines, and the BSP framework of Apache Hama for performing asynchronous mini-batches. Within single BSP job, each task group works asynchronously using region barrier synchronization instead of global barrier synchronization, and trains large-scale neural network model using assigned data sets in BSP paradigm. Thus, we achieve data and model parallelism
[DISCUSS] Horn Incubation Proposal
Hi all, We'd like to propose Horn (혼), a fully distributed system for large-scale deep learning as an Apache Incubator project and start the discussion. The complete proposal can be found at: https://wiki.apache.org/incubator/HornProposal Any advices and helps are welcome! Thanks, Edward. = Horn Proposal = == Abstract == (tentatively named Horn [hɔ:n], korean meaning of Horn is a Spirit) is a neuron-centric programming APIs and execution framework for large-scale deep learning, built on top of Apache Hama. == Proposal == It is a goal of the Horn to provide a neuron-centric programming APIs which allows user to easily define the characteristic of artificial neural network model and its structure, and its execution framework that leverages the heterogeneous resources on Hama and Hadoop YARN cluster. == Background == The initial ANN code was developed at Apache Hama project by a committer, Yexi Jiang (Facebook) in 2013. The motivation behind this work is to build a framework that provides more intuitive programming APIs like Google's MapReduce or Pregel and supports applications needing large model with huge memory consumptions in distributed way. == Rationale == While many of deep learning open source softwares such as Caffe, DeepDist, and NeuralGiraph are still data or model parallel only, we aim to support both data and model parallelism and also fault-tolerant system design. The basic idea of data and model parallelism is use of the remote parameter server to parallelize model creation and distribute training across machines, and the BSP framework of Apache Hama for performing asynchronous mini-batches. Within single BSP job, each task group works asynchronously using region barrier synchronization instead of global barrier synchronization, and trains large-scale neural network model using assigned data sets in BSP paradigm. Thus, we achieve data and model parallelism. This architecture is inspired by Google's !DistBelief (Jeff Dean et al, 2012). == Initial Goals == Some current goals include: * builds new community * provides more intuitive programming APIs * needs both data and model parallelism support * must run natively on both Hama and Hadoop2 * needs also GPUs and InfiniBand support (FPGAs if possible) == Current Status == === Meritocracy === The core developers understand what it means to have a process based on meritocracy. We will provide continuous efforts to build an environment that supports this, encouraging community members to contribute. === Community === A small community has formed within the Apache Hama project and some companies such as instant messenger service company and mobile manufacturing company. And many people are interested in the large-scale deep learning platform itself. By bringing Horn into Apache, we believe that the community will grow even bigger. === Core Developers === Edward J. Yoon, Thomas Jungblut, and Dongjin Lee == Known Risks == === Orphaned Products === Apache Hama is already a core open source component at Samsung Electronics, and Horn also will be used by Samsung Electronics, and so there is no direct risk for this project to be orphaned. === Inexperience with Open Source === Some are very new and the others have experience using and/or working on Apache open source projects. === Homogeneous Developers === The initial committers are from different organizations such as, Microsoft, Samsung Electronics, and Line Plus. === Reliance on Salaried Developers === Few will be worked as a full-time open source developer. Other developers will also start working on the project in their spare time. === Relationships with Other Apache Products === * Horn is based on Apache Hama * Apache Zookeeper is used for distributed locking service * Natively run on Apache Hadoop and Mesos * Horn can be somewhat overlapped with Singa podling (If possible, we'd also like to use Singa or Caffe to do the heavy lifting part). === An Excessive Fascination with the Apache Brand === Horn itself will hopefully have benefits from Apache, in terms of attracting a community and establishing a solid group of developers, but also the relation with Apache Hama, a general-purpose BSP computing engine. These are the main reasons for us to send this proposal. == Documentation == Initial plan about Horn can be found at http://blog.udanax.org/2015/06/googles-distbelief-clone-project-on.html == Initial Source == The initial source code has been release as part of Apache Hama project developed under Apache Software Foundation. The source code is currently hosted at https://svn.apache.org/repos/asf/hama/trunk/ml/src/main/java/org/apache/hama/ml/ann/ == Cryptography == Not applicable. == Required Resources == === Mailing Lists === * horn-private * horn-dev === Subversion Directory === * Git is the preferred source control system: git://git.apache.org/horn === Issue Tracking === * a JIRA issue tracker, HORN == Initial Committers and Affiliations
Re: [DISCUSS] Horn Incubation Proposal
multiple worker groups for asynchronous training---data parallelism; and multiple workers in one group for synchronous training---model parallelism. So, it's basically execution of the multiple asynchronous BSP (Bulk Synchronous Parallel) jobs. This can be simply handled within only single BSP job using region barriers as mentioned in proposal. Moreover, since Apache Hama is a general-purpose BSP framework on top of HDFS, it provides the data partition, locality optimization, job/task scheduling, messaging and fault tolerance in scalable way by nature. For the programming model, currently Horn proposes to support feed-forward There are plenty of rooms for collaborations indeed... Yeah, but still it can be more improved. Maybe we can discuss the simplified programming APIs and many others e.g., support GPUs together in the future. On Fri, Aug 21, 2015 at 1:13 PM, ooibc oo...@comp.nus.edu.sg wrote: Hi, I am an initial committer of Apache(incubating) SINGA (http://singa.incubator.apache.org/) Both SINGA and the proposal follow the general parameter-server architecture: workers for computing gradients; servers for parameter updating. SINGA has implemented the model and data parallelism discussed in the Horn' proposal: multiple worker groups for asynchronous training---data parallelism; and multiple workers in one group for synchronous training---model parallelism. One feature of SINGA's architecture is that it can be extended to organize the servers in a hierarchical topology, which may help to reduce the communication bottleneck of servers organized in a flat topology. For the programming model, currently Horn proposes to support feed-forward models, e.g., MLP, auto-encoder, while SINGA supports all three categories of the known models, feed-forward models (eg MLP, CNN), energy models (eg RBM, DBM), and recurrent models (eg. RNN). SINGA provides good support for users to code, e.g., implement new parameter updating protocols or layers, and is being integrated with HDFS as well. We will submit the first release and full documentation to the mentors this weekend, and if ok, we will announce the first full release soon. The GPU version is scheduled for October release. Technical papers: http://www.comp.nus.edu.sg/~ooibc/singa-mm15.pdf http://www.comp.nus.edu.sg/~ooibc/singaopen-mm15.pdf and project website (which has more details than the Apache web site): http://www.comp.nus.edu.sg/~dbsystem/singa/ There are plenty of rooms for collaborations indeed... regards beng chin www.comp.nus.edu.sg/~ooibc On 2015-08-21 08:27, Edward J. Yoon wrote: Hi all, We'd like to propose Horn (혼), a fully distributed system for large-scale deep learning as an Apache Incubator project and start the discussion. The complete proposal can be found at: https://wiki.apache.org/incubator/HornProposal Any advices and helps are welcome! Thanks, Edward. = Horn Proposal = == Abstract == (tentatively named Horn [hɔ:n], korean meaning of Horn is a Spirit) is a neuron-centric programming APIs and execution framework for large-scale deep learning, built on top of Apache Hama. == Proposal == It is a goal of the Horn to provide a neuron-centric programming APIs which allows user to easily define the characteristic of artificial neural network model and its structure, and its execution framework that leverages the heterogeneous resources on Hama and Hadoop YARN cluster. == Background == The initial ANN code was developed at Apache Hama project by a committer, Yexi Jiang (Facebook) in 2013. The motivation behind this work is to build a framework that provides more intuitive programming APIs like Google's MapReduce or Pregel and supports applications needing large model with huge memory consumptions in distributed way. == Rationale == While many of deep learning open source softwares such as Caffe, DeepDist, and NeuralGiraph are still data or model parallel only, we aim to support both data and model parallelism and also fault-tolerant system design. The basic idea of data and model parallelism is use of the remote parameter server to parallelize model creation and distribute training across machines, and the BSP framework of Apache Hama for performing asynchronous mini-batches. Within single BSP job, each task group works asynchronously using region barrier synchronization instead of global barrier synchronization, and trains large-scale neural network model using assigned data sets in BSP paradigm. Thus, we achieve data and model parallelism. This architecture is inspired by Google's !DistBelief (Jeff Dean et al, 2012). == Initial Goals == Some current goals include: * builds new community * provides more intuitive programming APIs * needs both data and model parallelism support * must run natively on both Hama and Hadoop2 * needs also GPUs and InfiniBand support (FPGAs if possible) == Current Status
Re: [VOTE] Graduate Ignite from the Incubator
. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.0-incubating
On behalf of the Apache Zeppelin (incubating) PPMC I have contacted the original author and he agreed to contribute this code, with the proper Apache 2.0 licence header, directly to the Apache Zeppelin (incubating) codebase as a separate patch. So it is going to be resolved completely, together with 2 other issues raised here, over the next release. Edward J. Yoon, does this explanation and actions taken make you more comfortable with changing your opinion\vote? +1 On Wed, Jul 22, 2015 at 2:25 PM, Alexander Bezzubov abezzu...@nflabs.com wrote: Got it, thank you very much, Justin, for the explanation! On behalf of the Apache Zeppelin (incubating) PPMC I have contacted the original author and he agreed to contribute this code, with the proper Apache 2.0 licence header, directly to the Apache Zeppelin (incubating) codebase as a separate patch. So it is going to be resolved completely, together with 2 other issues raised here, over the next release. Edward J. Yoon, does this explanation and actions taken make you more comfortable with changing your opinion\vote? Please let us know. Thanks in advance. -- Kind regards, Alexander On Wed, Jul 22, 2015 at 1:20 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Regarding the issue raised by Edward - we were under impression that this particular contribution is covered by https://github.com/apache/incubator-zeppelin/blob/master/NOTICE#L53 (as we use the code from https://code.google.com/p/selenium/issues/detail?id=1361 that was not merged to the selenium, keeping the attribution) It depends on how that original code is licensed and if you have permission to use the code from the author. I don't know the exact particulars, and it may be fine, but it seem unclear to me. This probably doesn’t have to be sorted in the this release but would need to be sorted before graduation, but other IPMC member may hold different opinions. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- -- Kind regards, Alexander. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
+1 On Tue, Jul 21, 2015 at 8:36 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the automated and managed flow of information between systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Ignite Project: Semyon Boikov (sboi...@apache.org) Konstantin Boudnik (c...@apache.org) Branko Čibej (br...@apache.org) Ognen Duzlevski (mak...@apache.org) Sergey Evdokimov (sevdoki...@apache.org) Alexey Goncharuk (agoncha...@apache.org) Nikita Ivanov (nivano...@apache.org) Sergey Khisamov (s...@apache.org) Valentin Kulichenko (vkuliche...@apache.org) Alexey Kuznetsov (akuznet...@apache.org) Gianfranco Murador (mura...@apache.org) Andrey Novikov (anovi...@apache.org) Vladimir Ozerov (voze...@apache.org) Dmitriy Setrakyan (dsetrak...@apache.org) Roman Shaposhnik (r...@apache.org) Ilya Sterin (iste...@apache.org) Nikolai Tikhonov (ntikho...@apache.org) Irina Vasilinets (ivasilin...@apache.org) Anton Vinogradov (a...@apache.org) Sergey Vladykin (svlady...@apache.org) Evans Ye (evan...@apache.org) Yakov Zhdanov (yzhda...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dmitriy Setrakyan be appointed to the office of Vice President, Apache Ignite, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Ignite PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Ignite Project; and be it further RESOLVED, that the Apache Ignite Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Ignite podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Ignite podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.0-incubating
Has the author of zeppelin-server/src/test/java/com/webautomation/ScreenCaptureHtmlUnitDriver.java signed a ICLA? It looks like came from Selenium community - https://groups.google.com/forum/#!searchin/selenium-developers/Ivan$20Vasiliev$20%7Csort:relevance/selenium-developers/PTR_j4xLVRM/k2yVq01Fa7oJ If license header can't be attached discretionally by a third party, I don't think this can be included. -1 (binding) I think it'd be nice to fix every LICENSE and NOTICE issues. On Sun, Jul 19, 2015 at 9:33 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, +1 binding Please fix the LICENSE/NOTICE issues are fixed for next release. Given everything involved is Apache comparable it's more a documentation issue but still important to get right. If you need a hand or need it reviewed before your next release just ask. The LICENSE/NOTICE issues and missing DISCLAIMER from the binary files is more serious and IMO they shouldn’t be released but I’ll leave that up to the PMC/IPMC. I checked: - signatures and hashes good - incubating in source file - DISCLAIMER exists - LICENSE isn’t correct (see below) - NOTICE also has issues (see below) - All source has apache headers (except one) - No unexpected binary files - Can compile from source LICENSE and NOTICE issues - LICENSE states Copyright 2014, NFLabs inc.” when it should be ASF and specified in the NOTICE file. - NOTICE contains Font Awesome (SIL + MIT), Ace (BSD), Simple line icons (MIT) but there is no need for these to be in NOTICE [1] - LICENSE should contain things mentioned in NOTICE [1] - Has the author of zeppelin-server/src/test/java/com/webautomation/ScreenCaptureHtmlUnitDriver.java signed a ICLA? I notice it’s missing a header and it’s not 100% clear to me what it’s licensing is. For the binary release: - Missing NOTICE and DISCLAIMER from top level directory - Unadorned LICENSE and NOTICE in META_INF or jar and war so not correct, please see [2]. There's several NOTICE files in the libs jars that would have an impact on the binary NOTICE file [3] Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps 2. http://www.apache.org/dev/licensing-howto.html#binary 3. http://www.apache.org/dev/licensing-howto.html#alv2-dep - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Trafodion into Apache Incubator
+1 good luck! On Wednesday, May 20, 2015, Justin Erenkrantz jus...@erenkrantz.com wrote: On Tue, May 19, 2015 at 2:27 PM, Stack st...@duboce.net javascript:; wrote: Following the discussion earlier in the thread [1], I would like to call a VOTE to accept Trafodion as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached to this mail. The VOTE is open for at least the next 72 hours: [ ] +1 accept Trafodion into the Apache Incubator [ ] ±0 Abstain [ ] -1 because... +1. Good luck! -- justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; -- Best Regards, Edward J. Yoon
RE: Re: [DISCUSS] [PROPOSAL] Singa for Apache Incubator
Just out of curious. My coworker is working on implementing DNN on Apache Hama (which supports general-purpose BSP computing and Pregel-like graph framework). If Hama is leveraging InfiniBand and GPUs in the future, what will be the major difference bt Hama-based DistBelief clone and Singa project? And, how much performance difference bt async and sync? Thanks. -- Best Regards, Edward J. Yoon -Original Message- From: 윤진석 [mailto:edward.y...@samsung.com] Sent: Wednesday, February 11, 2015 8:32 AM To: edward.y...@samsung.com Subject: Re: Re: [DISCUSS] [PROPOSAL] Singa for Apache Incubator --- Original Message --- Sender : Thejas Nairthejas.n...@gmail.com Date : 2015-02-04 08:58 (GMT+09:00) Title : Re: [DISCUSS] [PROPOSAL] Singa for Apache Incubator The Relationship with Other Apache Products section has been updated. The reference to H2O in that section has been removed, and other projects have been added. Thanks for the feedback! On Wed, Jan 28, 2015 at 10:27 AM, Thejas Nair wrote: Thanks for pointing that out Henry! Yes, looks like H20 is not an apache project, I should have verified that. I will edit that, and revisit that section along with the folks in Singa community. On Tue, Jan 27, 2015 at 6:55 PM, Henry Saputra wrote: Quick immediate comment that Apache H2O is not really Apache project. I assume you are referring to https://github.com/h2oai/h2o (or https://github.com/h2oai/h2o-dev) ? - Henry On Tue, Jan 27, 2015 at 5:29 PM, Thejas Nair wrote: Hello everyone, I would like to propose the inclusion of Singa as an Apache Incubator project. Here is the proposal - https://wiki.apache.org/incubator/SingaProposal Please review the proposal and give feedback. I am planning to start a vote after 7 days if the proposal looks good. We are also seeking additional Apache mentors for the project. Thanks, Thejas == Singa Incubator Proposal Abstract SINGA is a distributed deep learning platform. Proposal SINGA is an efficient, scalable and easy-to-use distributed platform for training deep learning models, e.g., Deep Convolutional Neural Network and Deep Belief Network. It parallelizes the computation (i.e., training) onto a cluster of nodes by distributing the training data and model automatically to speed up the training. Built-in training algorithms like Back-Propagation and Contrastive Divergence are implemented based on common abstractions of deep learning models. Users can train their own deep learning models by simply customizing these abstractions like implementing the Mapper and Reducer in Hadoop. Background Deep learning refers to a set of feature (or representation) learning models that consist of multiple (non-linear) layers, where different layers learn different levels of abstractions (representations) of the raw input data. Larger (in terms of model parameters) and deeper (in terms of number of layers) models have shown better performance, e.g., lower image classification error in Large Scale Visual Recognition Challenge. However, a larger model requires more memory and larger training data to reduce over-fitting. Complex numeric operations make the training computation intensive. In practice, training large deep learning models takes weeks or months on a single node (even with GPU). Rational Deep learning has gained a lot of attraction in both academia and industry due to its success in a wide range of areas such as computer vision and speech recognition. However, training of such models is computationally expensive, especially for large and deep models (e.g., with billions of parameters and more than 10 layers). Both Google and Microsoft have developed distributed deep learning systems to make the training more efficient by distributing the computations within a cluster of nodes. However, these systems are closed source softwares. Our goal is to leverage the community of open source developers to make SINGA efficient, scalable and easy to use. SINGA is a full fledged distributed platform, that could benefit the community and also benefit from the community in their involvement in contributing to the further work in this area. We believe the nature of SINGA and our visions for the system fit naturally to Apache's philosophy and development framework. Initial Goals We have developed a system for SINGA running on a commodity computer cluster. The initial goals include, * improving the system in terms of scalability and efficiency, e.g., using Infiniband for network communication and multi-threading for one node computation. We would consider extending SINGA to GPU clusters later. * benchmarking with larger datasets (hundreds of millions of training instances) and models (billions of parameters). * adding more built-in deep learning models. Users can train the built-in models on their datasets directly. Current Status
RE: Re: [DISCUSS] [PROPOSAL] Singa for Apache Incubator
I think that, one of the big differences is that Singa is written in C++. Awesome, I'd be the first client. And anything from architectural viewpoint? -- Best Regards, Edward J. Yoon -Original Message- From: Ted Dunning [mailto:ted.dunn...@gmail.com] Sent: Wednesday, February 11, 2015 8:37 AM To: general@incubator.apache.org Subject: Re: Re: [DISCUSS] [PROPOSAL] Singa for Apache Incubator On Tue, Feb 10, 2015 at 3:33 PM, Edward J. Yoon edward.y...@samsung.com wrote: My coworker is working on implementing DNN on Apache Hama (which supports general-purpose BSP computing and Pregel-like graph framework). If Hama is leveraging InfiniBand and GPUs in the future, what will be the major difference bt Hama-based DistBelief clone and Singa project? And, how much performance difference bt async and sync? I think that, one of the big differences is that Singa is written in C++. Another is that Singa runs now. The present tense is always very powerful when it comes to software. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Incubator Wiki] Update of SingaProposal by ThejasNair
Interesting! but the https://github.com/nudles/singa returns 404. And it looks like Parameter Server project is core. On Thu, Dec 18, 2014 at 2:38 PM, Apache Wiki wikidi...@apache.org wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Incubator Wiki for change notification. The SingaProposal page has been changed by ThejasNair: https://wiki.apache.org/incubator/SingaProposal?action=diffrev1=1rev2=2 JIRA Singa (SINGA) == Initial Committers == - * Beng Chin Ooi (oo...@comp.nus.edu.sg) + * Beng Chin Ooi (ooibc @comp.nus.edu.sg) - * Kian Lee Tan (ta...@comp.nus.edu.sg) + * Kian Lee Tan (tankl @comp.nus.edu.sg) - * Gang Chen (c...@zju.edu.cn) + * Gang Chen (cg @zju.edu.cn) - * Wei Wang (wang...@comp.nus.edu.sg) + * Wei Wang (wangwei @comp.nus.edu.sg) - * Dinh Tien Tuan Anh (dinh...@comp.nus.edu.sg) + * Dinh Tien Tuan Anh (dinhtta @comp.nus.edu.sg) - * Jinyang Gao (jinyang@comp.nus.edu.sg) + * Jinyang Gao (jinyang.gao @comp.nus.edu.sg) - * Sheng Wang (wan...@comp.nus.edu.sg) + * Sheng Wang (wangsh @comp.nus.edu.sg) - * Kaiping Zheng (kaip...@comp.nus.edu.sg) + * Kaiping Zheng (kaiping @comp.nus.edu.sg) - * Zhaojing Luo (zhaoj...@comp.nus.edu.sg) + * Zhaojing Luo (zhaojing @comp.nus.edu.sg) - * Zhongle Xie (zhon...@comp.nus.edu.sg) + * Zhongle Xie (zhongle @comp.nus.edu.sg) == Affiliations == * Beng Chin Ooi, National University of Singapore - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-h...@incubator.apache.org -- Best Regards, Edward J. Yoon
Re: P. An Excessive Fascination with the Apache Brand
Agree with Upayavira. And, I think the mentors need to be more diverse. Sometimes I can predict the result of vote. On Mon, Dec 22, 2014 at 11:42 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Dec 22, 2014 at 5:21 AM, Jim Jagielski j...@jagunet.com wrote: What we *REALLY* want are projects that are interested more in The Apache Way than in the Apache Brand. What is The Apache Way, anyway? There's no coherent, authoritative definition -- and therefore, transgressions are inevitable. Proposition: It is impossible to define The Apache Way while following The Apache Way. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fwd: [jira] [Closed] (INFRA-8696) Access to Jenkins
Mentors, if incubator project can use the Jenkins, Please add fegaras and moon to Jenkins. -- Forwarded message -- From: David Nalley (JIRA) j...@apache.org Date: Mon, Nov 24, 2014 at 11:10 PM Subject: [jira] [Closed] (INFRA-8696) Access to Jenkins To: edwardy...@apache.org [ https://issues.apache.org/jira/browse/INFRA-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley closed INFRA-8696. --- Resolution: Not a Problem Granting access to Jenkins is not an infra task. Please talk to your PMC Chair and refer him/her to: http://wiki.apache.org/general/Jenkins#How_do_I_get_an_account Access to Jenkins - Key: INFRA-8696 URL: https://issues.apache.org/jira/browse/INFRA-8696 Project: Infrastructure Issue Type: Wish Components: Jenkins Reporter: Edward J. Yoon Can someone please add fegaras and moon to Jenkins. -- This message was sent by Atlassian JIRA (v6.3.4#6332) -- Best Regards, Edward J. Yoon
Re: [ANNOUNCE] Moon Soo Lee joins the MRQL PPMC
Mentors, We don't have permission to access the ID request form page. Please add Lee Moon Soo as a new MRQL committer. Thanks. On Wed, Apr 23, 2014 at 9:35 AM, Edward J. Yoon edwardy...@apache.org wrote: Please read the guidelines for new committers[1], and send a signed ICLA[2] either by postal mail, fax or by emailing a scan of the signed copy to secret...@apache.org. 1. http://www.apache.org/dev/new-committers-guide.html 2. http://www.apache.org/licenses/icla.txt On Thu, Apr 17, 2014 at 8:22 AM, moon soo Lee leemoon...@gmail.com wrote: Thanks. Hope i can understand and participate more about MRQL! On Thursday, April 17, 2014, Edward J. Yoon edwardy...@apache.org wrote: Congratz! Sent from my iPhone On 2014. 4. 17., at 오전 12:57, Alan Cabrera l...@toolazydogs.comjavascript:; wrote: Contrats! Regards, Alan On Apr 16, 2014, at 8:25 AM, Leonidas Fegaras fega...@cse.uta.edujavascript:; wrote: Greetings, The MRQL PPMC has voted to offer membership to Moon Soo Lee as an MRQL committer and PPMC member and he has accepted. Moon has provided various patches to MRQL, including refactoring the directory structure for using MRQL on Eclipse, changing the Test class to work with Junit, and rewriting the test queries/programs. In addition, Moon is building an MRQL driver for the open source project, Zeppelin. Welcome Moon! -- Best Regards, Edward J. Yoon CEO at DataSayer Co., Ltd. -- Best Regards, Edward J. Yoon CEO at DataSayer Co., Ltd. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Meerkat as a Hama sub-module or sub-project
Thanks Ted. I generally agree with your suggestion. On Mon, Apr 28, 2014 at 5:45 PM, Ted Dunning ted.dunn...@gmail.com wrote: Edward, Sub-projects are generally frowned on. Incubator projects can graduate eventually to a top-level project, but starting a project as a sub is not so good. The incubator docs on this are pretty good reading. But if the committer community for your real-time BSP is (or can be) the same as the committer community for Hama itself, you might want to just fold this new code directly into Hama itself. No need in that case for a separate project. If the committer community is very different, then a separate project is warranted. I don't think that the Hama development is such a high bandwidth thing that splitting is required. To my mind that says that joining groups together is better than breaking them apart. Together, the two efforts can feed off each other. Apart, they could each run down due to lack of interest. You will know much better than any of us the details of your communities. On Mon, Apr 28, 2014 at 4:23 AM, Edward J. Yoon edwardy...@apache.orgwrote: Hi guys, As some people already might know, I'm recently working on real-time data processing project on top of Hama BSP model, called Meerkat[1] (currently only few developers (from two organizations, Kakaotalk and DataSayer) are involved in this project). According to our internal study, Storm-like DAG-style and fault-tolerant streaming processing framework can be implemented on top of Hama BSP model. And, furthermore, we're thinking, it may be possible to connect to other BSP applications using some smart input and output formats in the future e.g., streaming graph or learning BSP applications. Thus, we believe that we may be able to have an next-generation architecture that processes and analyzes the data rapidly in real-time, beyond complex old-style data collecting, storing, ordering, processing, and analyzing architecture. Does it make sense to you? If so, I'd like to start to move from github to ASF soon, although this is very *early* stage. Because, it's highly related with Apache Hama and others. Hama sub-module or sub-project, (or Apache incubator?). Which is best you think? I'm also CC'ing general@i.a.o to see more feedbacks (from Apache big data OSS communities). 1. https://github.com/datasayer/meerkat -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon CEO at DataSayer Co., Ltd. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Meerkat as a Hama sub-module or sub-project
Hi guys, As some people already might know, I'm recently working on real-time data processing project on top of Hama BSP model, called Meerkat[1] (currently only few developers (from two organizations, Kakaotalk and DataSayer) are involved in this project). According to our internal study, Storm-like DAG-style and fault-tolerant streaming processing framework can be implemented on top of Hama BSP model. And, furthermore, we're thinking, it may be possible to connect to other BSP applications using some smart input and output formats in the future e.g., streaming graph or learning BSP applications. Thus, we believe that we may be able to have an next-generation architecture that processes and analyzes the data rapidly in real-time, beyond complex old-style data collecting, storing, ordering, processing, and analyzing architecture. Does it make sense to you? If so, I'd like to start to move from github to ASF soon, although this is very *early* stage. Because, it's highly related with Apache Hama and others. Hama sub-module or sub-project, (or Apache incubator?). Which is best you think? I'm also CC'ing general@i.a.o to see more feedbacks (from Apache big data OSS communities). 1. https://github.com/datasayer/meerkat -- Best Regards, Edward J. Yoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Slider into the incubator
+1 (non binding) On Thu, Apr 17, 2014 at 10:01 PM, Steve Loughran ste...@hortonworks.com wrote: I'd like to call a vote on accepting Slider into the incubator https://wiki.apache.org/incubator/SliderProposal [ ] +1 Accept Slider into the Incubator [ ] +0 Indifferent to the acceptance of Slider [ ] -1 Do not accept Slider because … The vote will be open until Thursday April 24 13:00 UTC -Steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- Best Regards, Edward J. Yoon CEO at DataSayer Co., Ltd. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Graduation resolution does not allow for committers != PMC
I always was curious about if podling has both a group of PPMC members and a group of committers. When consider TLP graduation, all committers should be PPMC members? On Fri, Apr 4, 2014 at 6:59 PM, sebb seb...@gmail.com wrote: There have been a couple of graduations recently where (I think) the podling expected to be able to specify the initial list of committers as different from the PMC. In at least one case the podling did not realise that the names on the board resolution comprise the initial PMC. I think there are two issues here: - clarify that the board resolution names really are the whole PMC and nothing but the PMC (!) The resolution template itself likely cannot be changed, but there must be descriptions of the process somewhere that can be improved. - consider whether it is necessary to allow creation of a TLP with additional initial committers not on the PMC. If so, what is the process? If not, probably a good idea to ensure it is clearly stated how the PMC can add the additional committers once the TLP resources have been created by Infra. Thoughts? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Edward J. Yoon (@eddieyoon) Chief Executive Officer DataSayer, Inc. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Tajo from the Incubator
+1 On Sat, Feb 22, 2014 at 12:44 PM, Mattmann, Chris A (3980) chris.a.mattm...@jpl.nasa.gov wrote: Hi Everyone, After a successful community VOTE [1] in which 4 IPMC members already VOTEd positively for graduation, I'm now calling an IPMC VOTE to graduate Tajo from the Incubator. Apache Tajo has seen successful Incubator releases, has added new contributors, has discussed their project on list and consistent with the Apache ways. There is a great momentum in the community and I am wholeheartedly recommending its graduation from the Incubator. Please VOTE below on the graduation of Apache Tajo from the Incubator. The graduation resolution is pasted below. I'll leave the VOTE open for at least 72 hours: [ ] +1 Graduate Apache Tajo from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Tajo from the Incubator because Here is my enthusiastic +1 for Tajo's graduation! Cheers, Chris [1] http://s.apache.org/sM ---resolution WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to low latency queries, and extract, transform and load (ETL) operations for the Hadoop ecosystem. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Tajo Project be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Tajo Project be and hereby is responsible for the creation and maintenance of software related to low latency queries, and extract, transform and load (ETL) operations for the Hadoop ecosystem; and be it further RESOLVED, that the office of Vice President, Apache Tajo, be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Tajo Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Tajo Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Tajo Project: Alex Karasulu akaras...@apache.org Eli Reisman ereis...@apache.org Henry Saputra hsapu...@apache.org Hyunsik Choi hyun...@apache.org Jakob Glen Homan jgho...@apache.org Chris Mattmann mattm...@apache.org Owen O'Malley omal...@apache.org JaeHwa Jung blrun...@apache.org Jinho Kim jh...@apache.org Jihoon Son jihoon...@apache.org Keuntae Park sir...@apache.org Roshan Sumbaly rsumb...@apache.org Sangwook Kim sw...@apache.org Yi Liu y...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hyunsik Choi be appointed to the office of Vice President, Apache Tajo, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Tajo Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Tajo podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Tajo podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Edward J. Yoon (@eddieyoon) Chief Executive Officer DataSayer, Inc. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: general Digest of: get.43956
Thanks for links! On Wed, Feb 5, 2014 at 12:49 AM, Billie Rinaldi bil...@apache.org wrote: On Mon, 3 Feb 2014 10:55, Edward J. Yoon edwardy...@apache.org wrote: Hi, Hoya looks nice. 5. Help migrate more distributed applications into YARN clusters - such as Apache HAMA. BTW, this means that HAMA can be deployed on YARN cluster using HOYA without implement separate YARN application? Yes. You would still have to write a Hoya provider for Hama, but this should be significantly easier than writing a Yarn app from scratch. Steve has written some documentation on the types of apps that can be deployed with Hoya [1]. If you'd like to see example provider code, take a look at the accumulo and hbase providers [2]. Billie [1]: https://github.com/hortonworks/hoya/blob/master/src/site/markdown/app_needs.md [2]: https://github.com/hortonworks/hoya/tree/master/hoya-core/src/main/java/org/apache/hoya/providers On Wed, Jan 22, 2014 at 6:42 PM, Steve Loughran ste...@hortonworks.com wrote: thanks Jakob - we haven't had a vote yet though, still discussing the proposal On 22 January 2014 06:57, Jakob Homan jgho...@gmail.com wrote: HOYA looks like a useful bit of code,which if squinted at appropriately, might, sorta be able to be implemented with another useful bit of code already in the incubator. But could just as well be independent. Let's let HOYA in and see where the communities that develop around it and Twill want to go. Samza would certainly be interested in evaluating it as it matures. +1 (binding) on the proposal. On Tue, Jan 21, 2014 at 2:05 PM, Chris Riccomini criccomini@gmail.comwrote: Hey Guys, I'd like to +1 non-binding Hoya (or whatever you want to call it). It's going to be really useful for the YARN ecosystem to have a project like this out there, and it makes a lot of sense to put it in Apache. Hopefully we can move past the naming stuff, and get the project in. Cheers, Chris On Mon, Jan 20, 2014 at 12:32 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: I just can speak for the Hama-to-Yarn use case (with my newbie hat on) and it seems Hoya may be really helpful as the entry point to address it as it provides a set of simple and useful tools. For the sake of the names I think Hoya would be good (while Hyena would not). Just my 0.02 cents, Tommaso 2014/1/17 Steve Loughran ste...@hortonworks.com On 16 January 2014 12:41, Tommaso Teofili tommaso.teof...@gmail.com wrote: Hi all, @Steve I'm curious to know if also Apache Hama may leverage Hoya to be deployed on YARN. If you are going to make a 100% commit to running in YARN -which, if you aren't ready yet, Hama should be able to do in some point in the future- then I'd say go for it! and then point you at Twill to get you started. If all you are trying to do is deploy the BSP daemons in a YARN cluster, and they don't need any persistent localfs storage, then Hoya should work. You already use ZK for the binding mechanism, don't you? If yes, that'd hopefully bring some more people involved from Hama as well. That'd be great! -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- Best Regards, Edward J. Yoon @eddieyoon -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hoya Proposal
Hi, Hoya looks nice. 5. Help migrate more distributed applications into YARN clusters - such as Apache HAMA. BTW, this means that HAMA can be deployed on YARN cluster using HOYA without implement separate YARN application? On Wed, Jan 22, 2014 at 6:42 PM, Steve Loughran ste...@hortonworks.com wrote: thanks Jakob - we haven't had a vote yet though, still discussing the proposal On 22 January 2014 06:57, Jakob Homan jgho...@gmail.com wrote: HOYA looks like a useful bit of code,which if squinted at appropriately, might, sorta be able to be implemented with another useful bit of code already in the incubator. But could just as well be independent. Let's let HOYA in and see where the communities that develop around it and Twill want to go. Samza would certainly be interested in evaluating it as it matures. +1 (binding) on the proposal. On Tue, Jan 21, 2014 at 2:05 PM, Chris Riccomini criccomini@gmail.comwrote: Hey Guys, I'd like to +1 non-binding Hoya (or whatever you want to call it). It's going to be really useful for the YARN ecosystem to have a project like this out there, and it makes a lot of sense to put it in Apache. Hopefully we can move past the naming stuff, and get the project in. Cheers, Chris On Mon, Jan 20, 2014 at 12:32 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: I just can speak for the Hama-to-Yarn use case (with my newbie hat on) and it seems Hoya may be really helpful as the entry point to address it as it provides a set of simple and useful tools. For the sake of the names I think Hoya would be good (while Hyena would not). Just my 0.02 cents, Tommaso 2014/1/17 Steve Loughran ste...@hortonworks.com On 16 January 2014 12:41, Tommaso Teofili tommaso.teof...@gmail.com wrote: Hi all, @Steve I'm curious to know if also Apache Hama may leverage Hoya to be deployed on YARN. If you are going to make a 100% commit to running in YARN -which, if you aren't ready yet, Hama should be able to do in some point in the future- then I'd say go for it! and then point you at Twill to get you started. If all you are trying to do is deploy the BSP daemons in a YARN cluster, and they don't need any persistent localfs storage, then Hoya should work. You already use ZK for the binding mechanism, don't you? If yes, that'd hopefully bring some more people involved from Hama as well. That'd be great! -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Twill for Incubation
+1 (non-binding) On Fri, Nov 8, 2013 at 7:37 AM, Alejandro Abdelnur t...@cloudera.com wrote: +1 On Thu, Nov 7, 2013 at 2:19 PM, Roman Shaposhnik r...@apache.org wrote: On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann a...@apache.org wrote: The discussion about the Weave proposal has calmed. As the outcome of the discussion, we have chosen a new name for the project, Twill. I would like to call a vote for Twill to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/TwillProposal Let's keep this vote open for three business days, closing the voting on Tuesday 11/12. [ ] +1 Accept Twill into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Twill because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache MRQL 0.9.0 incubating (RC5)
Hi all, we need one more IPMC vote. On Wed, Oct 23, 2013 at 12:01 AM, Alan D. Cabrera l...@toolazydogs.com wrote: On Oct 14, 2013, at 5:37 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: [ ] +1 Release this package as Apache MRQL 0.9.0-incubating [ ] -1 Do not release this package because ... +1 Thanks for being so patient! Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache MRQL 0.9.0 incubating
-1. The PGP signatures are good, but the .md5 and .sha1 checksums do not include '*filename', so I get: $ md5sum -c mrql-bin-dist-0.9.0-incubating.tar.gz.md5 md5sum: mrql-bin-dist-0.9.0-incubating.tar.gz.md5: no properly formatted MD5 checksum lines found You'll need to manually create .md5 .sha1 for bin and src packages. And then, please upload binary and source packages to your private Apache account or https://dist.apache.org/repos/dist/dev/incubator/mrql/. Please attach both nexus repo and dist url links. On Tue, Sep 24, 2013 at 9:44 PM, Leonidas Fegaras fega...@cse.uta.edu wrote: Hello, This is a call for a vote on Apache MRQL 0.9.0 incubating. MRQL is a query processing and optimization system for large-scale, distributed data analysis, built on top of Apache Hadoop, Hama, and Spark. This is our first release. A vote was held on the MRQL developer mailing list and it passed with three +1 votes (plus one late vote), and zero -1 or 0 votes (see the vote thread [1] and result thread [2]), and now requires a vote on general@incubator.apache.org. The vote will be open for 72 hours (it will close on Friday 27/Sep/2013 at 1pm GMT) and passes if a majority of at least three +1 IPMC votes are cast. [ ] +1 Release this package as Apache MRQL 0.9.0-incubating [ ] -1 Do not release this package because... A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemrql-055/ You are voting only for the source distribution. The source tar ball is available at: https://repository.apache.org/content/repositories/orgapachemrql-055/org/apache/mrql/mrql-src-dist/0.9.0-incubating/ The release candidate consists of the following source distribution archives: - mrql-src-dist-0.9.0-incubating.[zip|tar.gz] SHA1 of TGZ: 4b5c6c2df32881b77633303435cb0c99856105cd SHA1 of ZIP: edae1009a5ef7a7613f4da4d2d46e1c9339cb70f You can compile the sources using 'mvn package'. In addition, the following supplementary binary distributions are provided for user convenience at: https://repository.apache.org/content/repositories/orgapachemrql-055/org/apache/mrql/mrql-bin-dist/0.9.0-incubating/ The binary distribution archives are: - mrql-bin-dist-0.9.0-incubating.[zip|tar.gz] SHA1 of TGZ: 27a1c569a0da333a22da260b07356673b81f539c SHA1 of ZIP: 6afdeb2640e6b3a31a97e44a0b5e585e6ade62ac The release candidate has been signed through the key 798764F1 in: http://www.apache.org/dist/incubator/mrql/KEYS http://keyserver.kjsl.org:11371/pks/lookup?op=getsearch=0xB7737C07798764F1 The release candidate is based on the sources tagged with MRQL-0.9.0-incubating-RC1: https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=tag;h=a7f69742a21393f98d951a8bc5822ae218ffda60 RAT output: http://people.apache.org/~fegaras/dist/MRQL-0.9.0-incubating-RC1/rat.txt Suitable name search: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-32 Note: The NOTICE includes the 3rd party copyright notices for JLine and CUP because the JLine and the CUP runtime libraries are bundled in the jar files in the MRQL binary distribution (files lib/*.jar). This was required because the MRQL jar files must contain all the dependencies in order to run on Hadoop and Hama. To learn more about Apache MRQL, please visit: http://wiki.apache.org/mrql/ Thanks, Leonidas Fegaras [1] http://markmail.org/message/nhyjdxlmas5vlg5x [2] http://markmail.org/message/5zsmncpimbdgfyn7 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Graduate Apache Curator as an Apache Top Level Project
+1! (non-binding) On Mon, Sep 2, 2013 at 11:41 PM, Daniel Shahaf danie...@apache.org wrote: On Mon, Sep 02, 2013 at 10:28:10AM -0400, Suresh Marru wrote: We don't need to worry for this vote, but in general relying on voter's statement is not a good idea. +1! (binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
Whirr, Apache ACE, Apache Karaf, and Apache Camel, and options exist to use Apache Maven as a build tool with the jclouds API. jclouds includes support for the Apache CloudStack API and is used as a compatibility test tool for its EC2 interface. jclouds can also be used to test Apache Deltacloud EC2 portability. === An Excessive Fascination with the Apache Brand === jclouds recognizes the fortitude of the Apache brand, but the motivation for becoming an Apache project is to strengthen and expand the jclouds community and its user base. While the jclouds community has seen steady growth over the past several years, association with the ASF is expected to expedite this pattern of growth. Development is expected to continue on jclouds under the Apache license whether or not it is supported by the ASF. == Documentation == The [[http://www.jclouds.org/|jclouds]] project documentation is publicly available at the following sites: * http://jclouds.org: installation guide, user guides, development resources, news, resources to get started * https://github.com/jclouds/jclouds: current source, source code issues log * https://github.com/jclouds/jclouds.github.com: static content for jclouds.org, documentation issues log * https://twitter.com/jclouds: jclouds on Twitter * https://groups.google.com/forum/?fromgroups#!forum/jclouds-dev: the jclouds development forum on Google Groups * https://groups.google.com/forum/?fromgroups#!forum/jclouds: the jclouds community forum on Google Groups == Initial Source == The initial source is located on GitHub in the following repositories: * git://github.com/jclouds/jclouds.git * git://github.com/jclouds/jclouds-labs.git * git://github.com/jclouds/jclouds.github.com.git * git://github.com/jclouds/jclouds-chef.git * git://github.com/jclouds/jclouds-cli.git * git://github.com/jclouds/jclouds-karaf.git * git://github.com/jclouds/jclouds-examples.git == Source and Intellectual Property Submission Plan == jclouds's initial source is licensed under the Apache License, Version 2.0. https://github.com/jclouds/jclouds/blob/master/resources/LICENSE.txt == External Dependencies == This is a listing of Maven coordinates for all of the external dependencies jclouds uses. All of the dependencies are in Sonatype and their licenses should be accessible. * aopalliance:aopalliance:jar:1.0:compile * com.google.code.gson:gson:jar:2.2.2:compile * com.google.guava:guava:jar:14.0.1:compile * com.google.inject.extensions:guice-assistedinject:jar:3.0:compile * com.google.inject:guice:jar:3.0:compile * javax.annotation:jsr250-api:jar:1.0:compile * javax.inject:javax.inject:jar:1:compile * javax.ws.rs:jsr311-api:jar:1.1.1:compile * org.99soft.guice:rocoto:jar:6.2:compile == Cryptography == jclouds contains no cryptographic algorithms, but it does provide the ability for people to plug in various cryptographic libraries. == Required Resources == === Mailing lists === * jclouds-dev: for development discussions * jclouds-user: for community discussions * jclouds-private: for PPMC discussions * jclouds-commits: for code changes === Apache git repository === The jclouds team is experienced in git and requests the following allocation on the Apache git server: git://git.apache.org/incubator-jclouds.git === Issue Tracking === jclouds currently uses GitHub for issue tracking. The intent is to request an allocation for Jira upon acceptance into the Incubator. Proposed project name: jclouds == Initial Committers == * Ignasi Barrera, ignasi dot barrera at gmail dot com * Andrew Bayer, abayer at apache dot org * Ioannis Canellos, iocanel at gmail dot com * Adrian Cole, adrianc at netflix dot com * Andrew Gaul, gaul at maginatics dot com * Andrew Phillips, aphillips at qrmedia dot com * Matt Stephenson, mattstep at mattstep dot net * Everett Toews, everett dot toews at rackspace dot com * Becca Wood, silkysun at silkysun dot net == Affiliations == * Ignasi Barrera, Abiquo * Andrew Bayer, Cloudera * Ioannis Canellos, Red Hat * Adrian Cole, Netflix * Andrew Gaul, Maginatics * Matt Stephenson, Google * Everett Toews, Rackspace == Sponsors == === Champion === * Brian McCallister, Apache Software Foundation === Mentors === * Brian McCallister, Apache Software Foundation * Tom White, Apache Software Foundation * Henning Schmiedehausen, Apache Software Foundation * David Nalley, Apache Software Foundation * Jean-Baptiste Onofré, Apache Software Foundation * Mohammad Nour El-Din, Apache Software Foundation * Olivier Lamy, Apache Software Foundation * Tomaz Muraus, Apache Software Foundation * Suresh Marru, Apache Software Foundation * Carlos Sanchez, Apache Software Foundation === Sponsoring Entity === The jclouds contributors and community request sponsorship from the Incubator. -- Best Regards, Edward J. Yoon
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
Thanks Ant. Could you please also create commits@ list for wiki/source commit mails? The submit button of the web form doesn't change from Disabled. On Thu, Mar 21, 2013 at 5:59 PM, ant elder ant.el...@gmail.com wrote: Please find that the MRQL mailing lists have been created and are ready to be used for further discussion: d...@mrql.incubator.apache.org u...@mrql.incubator.apache.org priv...@mrql.incubator.apache.org Would everyone named on the proposal please go subscribe to them, and happy MRQL'ing. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Accept MRQL into the Incubator
The required action has been taken, so let me close this thread again. I apologize again for my mistake. The Sponsors are changed as following: == Champion == * Alex Karasulu akarasulu AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org * Mohammad Nour mnour AT apache DOT org * Alan Cabrera adc AT apache DOT org The following IPMCers voted in favor: * Mohammed Nour El-Din * Alex Karasulu * Tommaso Teofili * Chris Mattmann * Christian Grobmeier * Niall Pemberton Thanks. On Sat, Mar 16, 2013 at 10:37 PM, Alex Karasulu akaras...@apache.org wrote: Looks like we can call this finally closed and approved. Edward I think we can carry forward now. On Sat, Mar 16, 2013 at 10:23 AM, Christian Grobmeier grobme...@gmail.comwrote: True. I'm totally down with your reasoning. But don't you think it might be a formality we need to comply with, even if it does not make sense at this stage? There has been a vote, which passed with enough binding votes, no one has -1'd, and no one has retracted their vote. Lets wait till Monday and if the majority vote still passes just carry on with the additional mentors. I hope no one does -1, theres several experienced mentors now so nothing really to be gained from forcing some new vote. ...ant As already mentioned I am also +1 to this proposal now, -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, -- Alex -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
could you please close the Create MRQL tasks in the Infra Jira until the situation has been cleared up. Whenever this all has been sorted out you can reopen the issues. Sure. Since this might not be fixed soon, proposal can be changed (especially corporation volunteers). And, thank you for your suggestion, but I'm already in initial committers list. To IPMC, I would request you to focus more on reviewing Proposal in the future. The opportunity of MRQL should not be faded by my mistake. On Fri, Mar 15, 2013 at 4:13 PM, Christian Grobmeier grobme...@gmail.com wrote: Hi Eddie, On Fri, Mar 15, 2013 at 8:02 AM, Ted Dunning ted.dunn...@gmail.com wrote: No. This doesn't work. That sentence is followed by another: Where the Champion is not a Member of the Foundation (i.e. is an Officer only), the Champion shall be a member of the PMC of the Sponsor. The Sponsor here is the Incubator. The PMC of the Sponsor is the IPMC. You aren't an IPMC member. Therefore, since you are not a Member and you aren't a member of the PMC of the Sponsor, you can't be the champion. could you please close the Create MRQL tasks in the Infra Jira until the situation has been cleared up. Whenever this all has been sorted out you can reopen the issues. On another note: There were now multiple issues with this podling. Can I make a suggestion? What, if you would not join as a Mentor/Champion but as an initial committer. As you said yourself you do not know all the rules but you are willing to learn. Joining this podling would be a great chance to learn all the rules, which are mandatory to know when you want to mentor a podling. If that is ok, I furthermore suggest you write to general@ that you are going to add your name to the initial committers list. I guess nobody will object. Then there is a need for a champion; please ask on general@ in another mail for somebody who has the interest. When it comes to mentors, most people say a podling should start with 3. There are a few podlings with 2 mentors. I guess it could work out. Whenever you have the champion, please ask him to create a new acceptance vote for MRQL. I guess this one would be ok since Alex and Mo already +1, but I also feel it would be a good idea to make it proper. My 2 cents - other IPMC members might see things different. Cheers Christian On Thu, Mar 14, 2013 at 9:43 PM, Edward J. Yoon edwardy...@apache.orgwrote: As you have previously pointed out Champion and Mentors are required to be IPMC members [1], [2]. So sorry you cannot be counted as a mentor/champion for MRQL. Regarding Champion, Am I not a Officer of ASF? - A candidate project shall be sponsored by an Officer or Member of the Foundation. -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Joining IPMC member
Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Joining IPMC member
Yes, I think I'm not familiar with handling issues like personnel, and somewhat emotional person. However, I want to helping people who want to contribute to ASF or collaborate with ASF projects in the future. On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey mar...@rectangular.com wrote: Edward, are you not familiar with our custom of handling personnel matters on private lists? It has not always been that way, but do you understand why virtually all ASF projects adhere to that convention now? Marvin Humphrey On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Joining IPMC member
understand why virtually all ASF projects adhere to that convention now? P.S., It's been 6 years since I uploaded my first patch on HBase. I still don't know many things but I'm continuously learning from you guys ;-) On Thu, Mar 14, 2013 at 4:07 PM, Edward J. Yoon edwardy...@apache.org wrote: Yes, I think I'm not familiar with handling issues like personnel, and somewhat emotional person. However, I want to helping people who want to contribute to ASF or collaborate with ASF projects in the future. On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey mar...@rectangular.com wrote: Edward, are you not familiar with our custom of handling personnel matters on private lists? It has not always been that way, but do you understand why virtually all ASF projects adhere to that convention now? Marvin Humphrey On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
Maybe 3 including myself? or If we need to recruit one more Mentor and re-open the vote with properly updated proposal, Please let us know. I apologize that I made a mistake here. I was confused with this comment[1]. 1. http://markmail.org/message/k6s56f5wlxgqhq3k On Fri, Mar 15, 2013 at 10:06 AM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher dave2w...@comcast.net wrote: Are the five binding votes from IPMC members? It is not 5. For the record, there were 4 binding IPMC votes in favor. Mohammed Nour El-Din Alex Karasulu Tommaso Teofili Chris Mattmann Also, should proposals with only 1 valid Mentor be acceptable? In addition to Alex Karasulu, Mohammed Nour El-Din had volunteered, but seems to have been left off the version of the proposal which was VOTEd on. So unless Mohammed has withdrawn, MRQL has 2 Mentors. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
OKay I see. As you have previously pointed out Champion and Mentors are required to be IPMC members [1], [2]. So sorry you cannot be counted as a mentor/champion for MRQL. Regarding Champion, Am I not a Officer of ASF? - A candidate project shall be sponsored by an Officer or Member of the Foundation. On Fri, Mar 15, 2013 at 1:29 PM, Suresh Marru sma...@apache.org wrote: On Mar 14, 2013, at 9:25 PM, Edward J. Yoon edwardy...@apache.org wrote: Maybe 3 including myself? Hi Edward, As you have previously pointed out Champion and Mentors are required to be IPMC members [1], [2]. So sorry you cannot be counted as a mentor/champion for MRQL. Since you have asked to be added to IPMC [3], I assume you realize you are not part of IPMC. Casting a binding vote on EasyAnt graduation [3] is not right. Please avoid creating such confusions. Suresh [1] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor [2] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion [3] - http://markmail.org/message/ldoyqm3o5eifyzrl [4] - http://markmail.org/message/dxqqa2cf6cpvoeyp or If we need to recruit one more Mentor and re-open the vote with properly updated proposal, Please let us know. I apologize that I made a mistake here. I was confused with this comment[1]. 1. http://markmail.org/message/k6s56f5wlxgqhq3k On Fri, Mar 15, 2013 at 10:06 AM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher dave2w...@comcast.net wrote: Are the five binding votes from IPMC members? It is not 5. For the record, there were 4 binding IPMC votes in favor. Mohammed Nour El-Din Alex Karasulu Tommaso Teofili Chris Mattmann Also, should proposals with only 1 valid Mentor be acceptable? In addition to Alex Karasulu, Mohammed Nour El-Din had volunteered, but seems to have been left off the version of the proposal which was VOTEd on. So unless Mohammed has withdrawn, MRQL has 2 Mentors. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Joining IPMC member
The reason of opening here is that I see mails like Request to join IPMC[1]. Moreover I already sent a mail to private@ at Feb 27. 1. http://mail-archives.apache.org/mod_mbox/incubator-general/201202.mbox/%3c87945f79-c905-4cdf-af5b-d7a9b54f3...@gmail.com%3E On Fri, Mar 15, 2013 at 1:25 AM, Suresh Marru sma...@apache.org wrote: On Mar 14, 2013, at 3:26 AM, Edward J. Yoon edwardy...@apache.org wrote: understand why virtually all ASF projects adhere to that convention now? P.S., It's been 6 years since I uploaded my first patch on HBase. I still don't know many things but I'm continuously learning from you guys ;-) Hi Edward, I do not think any one is questioning your credibility as a committer, or pmc member. I think Marvin hit it right and straight forward way. At ASF one of the few things (and primarily the only thing) like adding to a PMC is handled on private lists. Given that you have been contributing since 6 years you are certainly expected to know it. It is not healthy to side track the issue with your contributions or citing emotional reasons. Suresh On Thu, Mar 14, 2013 at 4:07 PM, Edward J. Yoon edwardy...@apache.org wrote: Yes, I think I'm not familiar with handling issues like personnel, and somewhat emotional person. However, I want to helping people who want to contribute to ASF or collaborate with ASF projects in the future. On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey mar...@rectangular.com wrote: Edward, are you not familiar with our custom of handling personnel matters on private lists? It has not always been that way, but do you understand why virtually all ASF projects adhere to that convention now? Marvin Humphrey On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Please publish the incubator website, when did changes
status page) would also publish the website right after. Otherwise the Thanks I see. To publish the website, do I only need to commit to production like below? Log: mrql added, changes to ripple. Added: websites/production/incubator/content/ - copied from r854238, websites/staging/incubator/trunk/content/ On Wed, Mar 13, 2013 at 3:41 PM, Christian Grobmeier grobme...@gmail.com wrote: Hi folks, from time to time I publish the website. Usually I check the diff first, and it happens that I see changes which I didn't include. I am then required to make a quick cross check and see if they are ok. It would be better if the person who pushed a change (most often the status page) would also publish the website right after. Otherwise the next publisher will never knew if publication is desired or not. Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Please publish the incubator website, when did changes
Nice. Thanks! On Wed, Mar 13, 2013 at 5:33 PM, Christian Grobmeier grobme...@gmail.com wrote: On Wed, Mar 13, 2013 at 7:53 AM, Edward J. Yoon edwardy...@apache.org wrote: status page) would also publish the website right after. Otherwise the Thanks I see. To publish the website, do I only need to commit to production like below? Even easier. Its document here: http://incubator.apache.org/guides/website.html When you have committed the incubator website as you did it recently, then you just need to go to this place: https://cms.apache.org/incubator/publish (see: generating the top level website) Fill out the form, check the diff and hit submit button. The CMS will take care of all the rest from there. You changes should be visible pretty quickly. Cheers Christian Log: mrql added, changes to ripple. Added: websites/production/incubator/content/ - copied from r854238, websites/staging/incubator/trunk/content/ On Wed, Mar 13, 2013 at 3:41 PM, Christian Grobmeier grobme...@gmail.com wrote: Hi folks, from time to time I publish the website. Usually I check the diff first, and it happens that I see changes which I didn't include. I am then required to make a quick cross check and see if they are ok. It would be better if the person who pushed a change (most often the status page) would also publish the website right after. Otherwise the next publisher will never knew if publication is desired or not. Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon -- http://www.grobmeier.de https://www.timeandbill.de -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Accept MRQL into the Incubator
optimization techniques, and new distributed back-ends, thus sustaining enough research interest. Another risk is that, when graduate students who write code graduate, they may leave their work undocumented and unfinished. We will strive to gain enough momentum to recruit additional committers from industry in order to eliminate these risks. == Inexperience with Open Source == The initial developer has been involved with various projects whose source code has been released under open source license, but he has no prior experience on contributing to open-source projects. With the guidance from other more experienced committers and participants, we expect that the meritocracy rules will have a positive influence on this project. == Homogeneous Developers == The initial committer comes from academia. However, given the interest we have seen in the project, we expect the diversity to improve in the near future. == Reliance on Salaried Developers == Currently, the MRQL code was developed on the committer's volunteer time. In the future, UTA graduate students who will do some of the coding may be supported by UTA and funding agencies, such as NSF. == Relationships with Other Apache Products == MRQL has some overlapping functionality with Hive and Tajo, which are Data Warehouse systems for Hadoop, and with Drill, which is an interactive data analysis system that can process nested data. MRQL has a more powerful data model, in which any form of nested data, such as XML and JSON, can be defined as a user-defined datatype. More importantly, complex data analysis tasks, such as PageRank, k-means clustering, and matrix multiplication and factorization, can be expressed as short SQL-like queries, while the MRQL system is able to evaluate these queries efficiently. Furthermore, the MRQL system can run these queries in BSP mode, in addition to MapReduce mode, thus achieving low latency and speed, which are also Drill's goals. Nevertheless, we will welcome and encourage any help from these projects and we will be eager to make contributions to these projects too. == An Excessive Fascination with the Apache Brand == The Apache brand is likely to help us find contributors and reach out to the open-source community. Nevertheless, since MRQL depends on Apache projects (Hadoop and Hama), it makes sense to have our software available as part of this ecosystem. = Documentation = Information about MRQL can be found at http://lambda.uta.edu/mrql/ = Initial Source = The initial MRQL code has been released as part of a research project developed at the University of Texas at Arlington under the Apache 2.0 license for the past two years. The source code is currently hosted on GitHub at: https://github.com/fegaras/mrql MRQL’s release artifact would consist of a single tarball of packaging and test code. = External Dependencies = The MRQL source code is already licensed under the Apache License, Version 2.0. MRQL uses JLine which is distributed under the BSD license. = Cryptography = Not applicable. = Required Resources = == Mailing Lists == * mrql-private * mrql-dev * mrql-user == Subversion Directory == * Git is the preferred source control system: git://git.apache.org/mrql == Issue Tracking == * A JIRA issue tracker, MRQL == Wiki == * Moinmoin wiki, http://wiki.apache.org/mrql = Initial Committers = * Leonidas Fegaras fegaras AT cse DOT uta DOT edu * Upa Gupta upa.gupta AT mavs DOT uta DOT edu * Edward J. Yoon edwardyoon AT apache DOT org * Maqsood Alam maqsoodalam AT hotmail DOT com * John Hope john.hope AT oracle DOT com * Mark Wall mark.wall AT oracle DOT com * Kuassi Mensah kuassi.mensah AT oracle DOT com * Ambreesh Khanna ambreesh.khanna AT oracle DOT com * Karthik Kambatla kasha AT cloudera DOT com = Affiliations = * Leonidas Fegaras (University of Texas at Arlington) * Upa Gupta (University of Texas at Arlington) * Edward J. Yoon (Oracle corp) * Maqsood Alam (Oracle corp) * John Hope (Oracle corp) * Mark Wall (Oracle corp) * Kuassi Mensah (Oracle corp) * Ambreesh Khanna (Oracle corp) * Karthik Kambatla (Cloudera) = Sponsors = == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org * Edward J. Yoon edwardyoon AT apache DOT org == Sponsoring Entity == Incubator PMC -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] MRQL for the Apache Incubator
I think it's time to call for vote. On Mon, Mar 4, 2013 at 9:25 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: Nice proposal indeed, I'd say having 3 mentors is usually better to avoid release headaches. Regards, Tommaso 2013/3/4 Edward J. Yoon edwardy...@apache.org Sure I can. :) Of course, we'll welcome more mentors from incubator IPMC if there're volunteers. On Mon, Mar 4, 2013 at 7:34 PM, Alex Karasulu akaras...@apache.org wrote: On Mon, Mar 4, 2013 at 12:31 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sat, Mar 2, 2013 at 7:12 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org ... Is Edward going to stay on as a mentor as well? Two (active) mentors is the bare minimum IMO. I suspect so but let's hear from Edward himself. Best Regards, -- Alex -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept MRQL into the Incubator
product-driven. It happens very often in academic research, when a project becomes outdated and doesn't produce publishable results, to be abandoned in favor of new cutting-edge projects. We do not believe that this will be the case for MRQL for the years to come, because it can be adapted to support new query languages, new optimization techniques, and new distributed back-ends, thus sustaining enough research interest. Another risk is that, when graduate students who write code graduate, they may leave their work undocumented and unfinished. We will strive to gain enough momentum to recruit additional committers from industry in order to eliminate these risks. == Inexperience with Open Source == The initial developer has been involved with various projects whose source code has been released under open source license, but he has no prior experience on contributing to open-source projects. With the guidance from other more experienced committers and participants, we expect that the meritocracy rules will have a positive influence on this project. == Homogeneous Developers == The initial committer comes from academia. However, given the interest we have seen in the project, we expect the diversity to improve in the near future. == Reliance on Salaried Developers == Currently, the MRQL code was developed on the committer's volunteer time. In the future, UTA graduate students who will do some of the coding may be supported by UTA and funding agencies, such as NSF. == Relationships with Other Apache Products == MRQL has some overlapping functionality with Hive and Tajo, which are Data Warehouse systems for Hadoop, and with Drill, which is an interactive data analysis system that can process nested data. MRQL has a more powerful data model, in which any form of nested data, such as XML and JSON, can be defined as a user-defined datatype. More importantly, complex data analysis tasks, such as PageRank, k-means clustering, and matrix multiplication and factorization, can be expressed as short SQL-like queries, while the MRQL system is able to evaluate these queries efficiently. Furthermore, the MRQL system can run these queries in BSP mode, in addition to MapReduce mode, thus achieving low latency and speed, which are also Drill's goals. Nevertheless, we will welcome and encourage any help from these projects and we will be eager to make contributions to these projects too. == An Excessive Fascination with the Apache Brand == The Apache brand is likely to help us find contributors and reach out to the open-source community. Nevertheless, since MRQL depends on Apache projects (Hadoop and Hama), it makes sense to have our software available as part of this ecosystem. = Documentation = Information about MRQL can be found at http://lambda.uta.edu/mrql/ = Initial Source = The initial MRQL code has been released as part of a research project developed at the University of Texas at Arlington under the Apache 2.0 license for the past two years. The source code is currently hosted on GitHub at: https://github.com/fegaras/**mrql https://github.com/fegaras/mrqlMRQL’s release artifact would consist of a single tarball of packaging and test code. = External Dependencies = The MRQL source code is already licensed under the Apache License, Version 2.0. MRQL uses JLine which is distributed under the BSD license. = Cryptography = Not applicable. = Required Resources = == Mailing Lists == * mrql-private * mrql-dev * mrql-user == Subversion Directory == * Git is the preferred source control system: git://git.apache.org/mrql == Issue Tracking == * A JIRA issue tracker, MRQL == Wiki == * Moinmoin wiki, http://wiki.apache.org/mrql = Initial Committers = * Leonidas Fegaras fegaras AT cse DOT uta DOT edu * Upa Gupta upa.gupta AT mavs DOT uta DOT edu * Edward J. Yoon edwardyoon AT apache DOT org * Maqsood Alam maqsoodalam AT hotmail DOT com * John Hope john.hope AT oracle DOT com * Mark Wall mark.wall AT oracle DOT com * Kuassi Mensah kuassi.mensah AT oracle DOT com * Ambreesh Khanna ambreesh.khanna AT oracle DOT com * Karthik Kambatla kasha AT cloudera DOT com = Affiliations = * Leonidas Fegaras (University of Texas at Arlington) * Upa Gupta (University of Texas at Arlington) * Edward J. Yoon (Oracle corp) * Maqsood Alam (Oracle corp) * John Hope (Oracle corp) * Mark Wall (Oracle corp) * Kuassi Mensah (Oracle corp) * Ambreesh Khanna (Oracle corp) * Karthik Kambatla (Cloudera) = Sponsors = == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org * Edward J. Yoon edwardyoon AT apache DOT org == Sponsoring Entity == Incubator PMC -- Best Regards, -- Alex -- Best Regards, Edward J. Yoon
Re: [PROPOSAL] MRQL for the Apache Incubator
Sure I can. :) Of course, we'll welcome more mentors from incubator IPMC if there're volunteers. On Mon, Mar 4, 2013 at 7:34 PM, Alex Karasulu akaras...@apache.org wrote: On Mon, Mar 4, 2013 at 12:31 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sat, Mar 2, 2013 at 7:12 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org ... Is Edward going to stay on as a mentor as well? Two (active) mentors is the bare minimum IMO. I suspect so but let's hear from Edward himself. Best Regards, -- Alex -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
MRQL (miracle) is looking for mentors and more volunteers
Hello all, MRQL (miracle)[1] is looking for mentors and more volunteers. We hope you will plan to participate and give us your feedback if you have any interest in this project. Thanks. 1. http://wiki.apache.org/incubator/MRQLProposal -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Bigtop podling from Apache Incubator
+1 Sent from my iPhone On 2012. 9. 13., at 오전 3:00, Avik Dey aviks.em...@gmail.com wrote: +1 ( Good work guys! ) Best, Avik On Wed, Sep 12, 2012 at 10:47 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Super +1. Great work! (binding - especially on the great work part!) :) Cheers, Chris On Sep 12, 2012, at 9:08 AM, Roman Shaposhnik wrote: This is a call for vote to graduate Bigtop podling from Apache Incubator The Apache Bigtop project entered incubator in June of 2011. Since then we have grown the community in users and contributors, and we've made significant improvements to the project. Following the Apache guidelines we have made four releases, we are preparing a 5th major and 6th maintenance releases, and we've added two new committers. The current set of committers and PPMC members are from different organizations and have demonstrated interest in growing the community further. We have learned the basis to manage the different aspects of an Apache project. The community of Bigtop is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Bigtop community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Bigtop podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Bigtop podling [ ] -1 Reject graduation of Bigtop podling from Apache Incubator This vote will remain open for at least 72 hours from now (till 15 Sep 2012, NOON PST). Please find the proposed board resolution below. [1] http://s.apache.org/SGm [2] http://s.apache.org/LOA Thanks, Roman Shaposhnik X. Establish the Apache Bigtop Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a system for integration, packaging, deployment and validation of a big data management software distribution based on Apache Hadoop for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Bigtop Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Bigtop Project be and hereby is responsible for the creation and maintenance of software related to a system for open-source software related to a system for integration, packaging, deployment and validation of a big data management software distribution based on Apache Hadoop; and be it further RESOLVED, that the office of Vice President, Apache Bigtop be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Bigtop Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Bigtop Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Bigtop Project: * Alan Gatesga...@apache.org * Patrick Hunt ph...@apache.org * Steve Loughranste...@apache.org * Tom White tomwh...@apache.org * Alejandro Abdelnurt...@apache.org * Andrew Bayer aba...@apache.org * Konstantin Boudnikc...@apache.org * Stephen Chu s...@apache.org * Bruno Mahébm...@apache.org * Peter Linnell plinn...@apache.org * James Pagejamesp...@apache.org * Patrick Taylor Ramsey p...@apache.org * Roman Shaposhnik r...@apache.org * Michael Stack st...@apache.org * Andrei Savu as...@apache.org * Edward J. Yoonedwardy...@apache.org * Andre Arcilla arci...@apache.org * Eli Collins e...@apache.org * Travis Crawford traviscrawf...@apache.org * John Sichij...@apache.org * Owen O'Malley omal...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Roman Shaposhnik be appointed to the office of Vice President, Apache Bigtop, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Bigtop PMC be and hereby is tasked
Re: [DISCUSS] Crunch to join the Apache Incubator
+1 Sent from my iPad On May 27, 2012, at 6:51 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Personally I've never fully understood the practice of allowing just about anyone to sign up as an initial committer of a podling. Putting your name on a list does not make you a part of a community, participating and contributing does. Recognizing such merit with committership is an important part of the social glue that binds our communities together. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Crunch into the Apache Incubator
+1 On Thu, May 24, 2012 at 7:16 AM, Patrick Hunt ph...@apache.org wrote: +1 Patrick On Wed, May 23, 2012 at 2:49 PM, Alan D. Cabrera l...@toolazydogs.com wrote: +1 Regards, Alan On May 23, 2012, at 11:45 AM, Josh Wills wrote: I would like to call a vote for accepting Apache Crunch for incubation in the Apache Incubator. The full proposal is available below. We ask the Incubator PMC to sponsor it, with phunt as Champion, and phunt, tomwhite, and acmurthy volunteering to be Mentors. Please cast your vote: [ ] +1, bring Crunch into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Crunch into Incubator, because... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. http://wiki.apache.org/incubator/CrunchProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Graduation of Hama as a TLP
The approval of Hama graduation passes with the following votes: +1 Jukka Zitting ** +1 Tommaso Teofili ** +1 Steve Loughran ** +1 Edward J. Yoon * +1 Thomas Jungblut * +1 Suraj Menon * +1 ChiaHung Lin * +1 Eric Charles +1 Praveen Spripati Thanks! On Fri, May 4, 2012 at 12:46 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: I think the vote can be closed. Cheers, Tommaso 2012/4/28 Steve Loughran steve.lough...@gmail.com [X ] +1 Hama graduation Binding. -Steve - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Hama as a TLP
PS. You may want to revise the wording of the resolution, as distributed computing framework based on Bulk Synchronous Parallel doesn't sound like good language to me (though English isn't my native language). A better alternative could be distributed computing framework based on the Bulk Synchronous Parallel model. yes, it sounds better :-) Thank you very much! On Sat, Apr 28, 2012 at 11:34 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: [x] +1 Hama graduation 2012/4/28 Jukka Zitting jukka.zitt...@gmail.com Hi, On Wed, Apr 25, 2012 at 8:03 AM, Edward J. Yoon edwardy...@apache.org wrote: The community graduation vote was held and passed with 6 positive (4 binding) votes, no negative votes[1]. Now I would like to ask the IPMC to approve the graduation. Please VOTE on the below resolution for promoting Hama to an Apache TLP and graduating from the Incubator. [x] +1 Hama graduation PS. You may want to revise the wording of the resolution, as distributed computing framework based on Bulk Synchronous Parallel doesn't sound like good language to me (though English isn't my native language). A better alternative could be distributed computing framework based on the Bulk Synchronous Parallel model. yes, it sounds better :-) BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Hama as a TLP
Ping? 나의 iPhone에서 보냄 2012. 4. 25. 오후 3:03 Edward J. Yoon edwardy...@apache.org 작성: Hi IPMCers and Incubator community, The Hama podling joined the incubator in May 2008. Since then, our community has been steadily growing, we have made 3 releases, added 5 new committers and 3 new PPMC members. Diversity of the organizations or countries contributing to our project is also great. Thanks to ASF incubator, we have learned to self-govern and grow our community using accepted Apache practices. The community graduation vote was held and passed with 6 positive (4 binding) votes, no negative votes[1]. Now I would like to ask the IPMC to approve the graduation. Please VOTE on the below resolution for promoting Hama to an Apache TLP and graduating from the Incubator. [ ] +1 Hama graduation [ ] -1 Hama is not ready to graduate, because Voting will be open for 72 hours. Thanks. 1. http://markmail.org/thread/zuqkk47xgyxs2b6p 2. http://markmail.org/thread/vk4vedwtcts4pgmy ## Resolution to create a TLP from graduating Incubator podling X. Establish the Apache Hama Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a distributed computing framework based on Bulk Synchronous Parallel for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Hama Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Hama Project be and hereby is responsible for the creation and maintenance of software related to a distributed computing framework based on Bulk Synchronous Parallel; and be it further RESOLVED, that the office of Vice President, Apache Hama be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Hama Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Hama Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Hama Project: * ChiaHung Lin chl...@apache.org * Thomas Jungblut tjungb...@apache.org * Edward J. Yoonedwardy...@apache.org * Suraj Menon surajsme...@apache.org * Tommaso Teofili tomm...@apache.org * Steve Loughranste...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward J. Yoon be appointed to the office of Vice President, Apache Hama, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Hama PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Hama Project; and be it further RESOLVED, that the Apache Hama Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Hama podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Hama podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Graduation of Hama as a TLP
Hi IPMCers and Incubator community, The Hama podling joined the incubator in May 2008. Since then, our community has been steadily growing, we have made 3 releases, added 5 new committers and 3 new PPMC members. Diversity of the organizations or countries contributing to our project is also great. Thanks to ASF incubator, we have learned to self-govern and grow our community using accepted Apache practices. The community graduation vote was held and passed with 6 positive (4 binding) votes, no negative votes[1]. Now I would like to ask the IPMC to approve the graduation. Please VOTE on the below resolution for promoting Hama to an Apache TLP and graduating from the Incubator. [ ] +1 Hama graduation [ ] -1 Hama is not ready to graduate, because Voting will be open for 72 hours. Thanks. 1. http://markmail.org/thread/zuqkk47xgyxs2b6p 2. http://markmail.org/thread/vk4vedwtcts4pgmy ## Resolution to create a TLP from graduating Incubator podling X. Establish the Apache Hama Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a distributed computing framework based on Bulk Synchronous Parallel for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Hama Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Hama Project be and hereby is responsible for the creation and maintenance of software related to a distributed computing framework based on Bulk Synchronous Parallel; and be it further RESOLVED, that the office of Vice President, Apache Hama be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Hama Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Hama Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Hama Project: * ChiaHung Lin chl...@apache.org * Thomas Jungblut tjungb...@apache.org * Edward J. Yoonedwardy...@apache.org * Suraj Menon surajsme...@apache.org * Tommaso Teofili tomm...@apache.org * Steve Loughranste...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward J. Yoon be appointed to the office of Vice President, Apache Hama, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Hama PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Hama Project; and be it further RESOLVED, that the Apache Hama Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Hama podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Hama podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Resolved] (INCUBATOR-123) Update Hama status file
[ https://issues.apache.org/jira/browse/INCUBATOR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward J. Yoon resolved INCUBATOR-123. -- Resolution: Fixed Updated Update Hama status file --- Key: INCUBATOR-123 URL: https://issues.apache.org/jira/browse/INCUBATOR-123 Project: Incubator Issue Type: Improvement Components: site Affects Versions: 2012.3 Reporter: Edward J. Yoon Labels: patch Fix For: 2012.4 Update Hama status file. http://incubator.apache.org/guides/website.html#Edit+your+project+status+report http://incubator.apache.org/guides/graduation.html#notes-status -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] CloudStack for Apache Incubator
makes use of encryption functions available via Java and the underlying OS. We expect that the CloudStack will have to follow the export control procedures described at http://www.apache.org/dev/crypto.html. When the CloudStack was previously registered with BIS the open source version qualified for the TSU exception. The CloudStack uses https to communicate to XenServer and vCenter. ssh and scp are used between the Management Server and hypervisor hosts as well. The CloudStack stores an MD5 hash of user password data. The CloudStack uses MySQL encryption to store some data in an encrypted fashion. The CloudStack stores a pair of API public/secret keypairs for users. This is done using javax.crypto.KeyGenerator with HMAC-SHA-1. The CloudStack does not specify key lengths explicitly. It uses SSH, SCP and lets them negotiate encryption. The CloudStack provides a public HTTP-based API to provision and deprovision VPN users. The CloudStack has internal Java-based abstractions for managing VPN users. This Java software makes private API calls to another system, which will then provision the VPN user in the VPN software on that other system. The actual set up of the VPN session is done using L2TP/IPSec. As mentioned earlier the CloudStack includes software to build and later deploy Debian-based virtual machines. These VMs are stripped down versions of Debian that include encryption sufficient for ssh/scp, https, and IPSec VPN to work. The CloudStack does not include the source for these VMs. The maximum encrypted throughput of the VPN has not been determined. Required Resources Mailing Lists We request mailing lists to match the mailing lists currently in use, plus the recommended private list. These are: cloudstack-private: for confidential PPMC discussion cloudstack-dev: for development discussions cloudstack-user: for administrator and discussions Subversion Directory The CloudStack has used git for approximately two years. We understand that there is a prototype git server available. We request an allocation on this git server. We believe this will be less disruptive to the committers than a change to SVN. We request /repos/asf/incubator/cloudstack. Issue Tracking We would like an allocation for Jira. CloudStack uses bugzilla today, but we have been planning a move to Jira for some time. We request that the project name be CloudStack. Other Resources The CloudStack Project includes several websites. Donation of these websites was discussed in the IP submission plan. We would like to engage in discussion on the logistics of this. Initial Committers In the past few months several new developers have joined the Citrix CloudStack team. We are recommending that only the developers with several months of experience with CloudStack join as initial committers. The Project will then follow the meritocratic process to enable the newer team members to become committers. We believe this will be a good exercise for us as we transition to an Apache development model in the Project. The list of initial committers follows. At this time none of the initial committers has a CLA on file with ASF. Abhinandan Prateek, abhinandan.prateek.at.citrix.com Alena Prokharchyk, alena.prokharchyk.at.citrix.com Alex Huang,alex.huang.at.citrix.com Anthony Xu, xuefei.xu.at.citrix.com Brian Federle, brian.federle.at.citrix.com Chiradeep Vittal, chiradeep.vittal.at.citrix.com David Nalley, david.nalley.at.citrix.com Edison Su, edison.su.at.citrix.com Frank Zhang, frank.zhang.at.citrix.com Janardhana Reddy, janardhana.reddy.at.citrix.com Jessica Tomechak, jessica.tomechak.at.citrix.com Jessica Wang, jessica.wang.at.citrix.com Kelven Yang, kelven.yang.at.citrix.com Kevin Kluge, kevin.kluge.at.citrix.com Kishan Kavala, kisha.kavala.at.citrix.com Murali Reddy, murali.reddy.at.citrix.com Nitin Mehta, nitin.mehta.at.citrix.com Prachi Damle, prachi.damle.at.citrix.com Sam Robertson, sam.robertson.at.citrix.com Sheng Yang, sheng.yang.at.citrix.com Sonny Chhen, sonny.chhen.at.citrix.com Will Chan, will.chan.at.citrix.com Affiliations The initial committers are all affiliated with Citrix Systems. Sponsors Champion Jim Jagielski Nominated Mentors Jim Jagielski, Daniel Kulp, Alex Karasulu, Olivier Lamy, Brett Porter, Mohammad Nour, Matt Hogstrom Sponsoring Entity We request that the Incubator sponsor this effort. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon
Re: svn commit: r1291363 - /incubator/public/trunk/site-author/projects/isis.xml
Just minor issue, I can't find site-author folder. It seems, should be changed to The sources for the status pages are in content/projects/*.xml in website.html. On Tue, Feb 21, 2012 at 9:45 PM, Mark Struberg strub...@yahoo.de wrote: hi! there is a build.sh script in trunk which you need to call. And then you simply check what has been changed and commit the stuff in site-publish. LieGrue, strub - Original Message - From: Dan Haywood d...@haywood-associates.co.uk To: sebb seb...@gmail.com; general@incubator.apache.org Cc: Sent: Tuesday, February 21, 2012 9:16 AM Subject: Re: svn commit: r1291363 - /incubator/public/trunk/site-author/projects/isis.xml Forgive my ignorance... is there any guidance on how to do that regeneration that you could point me to...? Dan On 21 February 2012 03:58, sebb seb...@gmail.com wrote: On 20 February 2012 16:52, danhayw...@apache.org wrote: Author: danhaywood Date: Mon Feb 20 16:52:18 2012 New Revision: 1291363 URL: http://svn.apache.org/viewvc?rev=1291363view=rev Log: Updating Isis project summary after 0.2.0-incubating release Modified: incubator/public/trunk/site-author/projects/isis.xml Next time please regenerate the site and commit the updated html version of the file. Modified: incubator/public/trunk/site-author/projects/isis.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/projects/isis.xml?rev=1291363r1=1291362r2=1291363view=diff == --- incubator/public/trunk/site-author/projects/isis.xml [utf-8] (original) +++ incubator/public/trunk/site-author/projects/isis.xml [utf-8] Mon Feb 20 16:52:18 2012 @@ -26,9 +26,9 @@ titleNews/title ul - li2010-09-07 Isis has been accepted to enter incubation/li - + li2012-02-20 Released version 0.2.0-incubating/li li2011-07-14 Released version 0.1.2-incubating/li + li2010-09-07 Isis has been accepted to enter incubation/li /ul /section @@ -274,20 +274,20 @@ ul li - a href=http://wiki.apache.org/incubator/October2010#Isis October - 2010/a + a + href=http://wiki.apache.org/incubator/December2011#Isis December + 2011/a /li li a - href=http://wiki.apache.org/incubator/November2010#Isis November - 2010/a + href=http://wiki.apache.org/incubator/September2011#Isis September + 2011/a /li li - a - href=http://wiki.apache.org/incubator/December2010#Isis December - 2010/a + a href=http://wiki.apache.org/incubator/June2011#Isis;June + 2011/a /li li @@ -296,20 +296,20 @@ /li li - a href=http://wiki.apache.org/incubator/June2011#Isis;June - 2011/a + a + href=http://wiki.apache.org/incubator/December2010#Isis December + 2010/a /li li a - href=http://wiki.apache.org/incubator/September2011#Isis September - 2011/a + href=http://wiki.apache.org/incubator/November2010#Isis November + 2010/a /li li - a - href=http://wiki.apache.org/incubator/December2011#Isis December - 2011/a + a href=http://wiki.apache.org/incubator/October2010#Isis October + 2010/a /li /ul /section - To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org For additional commands, e-mail: cvs-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-122) Replace all site-author to content in content/guides/website.xml
Replace all site-author to content in content/guides/website.xml Key: INCUBATOR-122 URL: https://issues.apache.org/jira/browse/INCUBATOR-122 Project: Incubator Issue Type: Improvement Components: site Reporter: Edward J. Yoon I don't know the background why site-author direcotry renamed to content[1] but shouldn't we change also the text in website.xml? 1. http://markmail.org/thread/xehg3nd4xw525kjw -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-123) Update Hama status file
Update Hama status file --- Key: INCUBATOR-123 URL: https://issues.apache.org/jira/browse/INCUBATOR-123 Project: Incubator Issue Type: Improvement Components: site Affects Versions: 2012.3 Reporter: Edward J. Yoon Fix For: 2012.4 Update Hama status file. http://incubator.apache.org/guides/website.html#Edit+your+project+status+report http://incubator.apache.org/guides/graduation.html#notes-status -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Release Apache Hama 0.4-incubating RC7
This vote has now passed with +3 (binding) from Tommaso Teofili, Steve loughran, Ant Alder. There were no +0 or -1 votes and additional votes cast on this voting thread. I'll try to push out the artifacts. Thank you! On Mon, Mar 5, 2012 at 5:50 PM, ant elder ant.el...@gmail.com wrote: Looks ok to me, +1 ...ant On Sun, Mar 4, 2012 at 11:18 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi all, This RC7 has passed the Hama PMC vote as follows (*, ** marks an PMC, IPMC vote) : +1 Thomas Jungblut * +1 Edward J. Yoon * +1 Tommaso Teofili ** +1 ChiaHung Lin * +1 Steve Loughlan ** http://markmail.org/thread/zxn5jfziafgh5vpc We still need one more IPMCer vote. Thanks. On Thu, Mar 1, 2012 at 1:42 PM, Edward J. Yoon edwardy...@apache.org wrote: We need IPMCer's votes! Sent from my iPad On Feb 29, 2012, at 6:12 PM, Thomas Jungblut thomas.jungb...@googlemail.com wrote: Signatures: - GPG signatures matches (asc) - md5 sums ok - sha1 sums ok Build: build is fine with maven, testcases pass (tar and zip) Examples: Tested all examples on local/pseudodistributed and distributed mode Whirr: started 2 EC2 instances with whirr and ran SSSP and Pagerank. The textToSeq utils also work as expected. Rat check also reveals that everything is ok. +1 (binding). Am 28. Februar 2012 13:42 schrieb Chia-Hung Lin cli...@googlemail.com: +1 mvn apache-rat:check ok sha1sum ok md5sum ok local build/ test passes executing on 4 vms works ok. On 28 February 2012 09:50, Edward J. Yoon edwardy...@apache.org wrote: Hi all, I'd like to ask your approval to release the Hama RC7 as Apache Hama 0.4.0-incubating. Signing KEYS: http://incubator.apache.org/hama/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC7/ SVN Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/ Added all 3rd party license texts into LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/LICENSE.txt Disclaimer: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/DISCLAIMER.txt New website: http://people.apache.org/~edwardyoon/site/ % mvn apache-rat:check is OK. The all builds, single mode, and distributed mode, web UI are all OK. The asc, md5, sha1 signatures are all OK. I'm +1. If there's a problem, Please let me know so that I can recreate RC8. [ ] +1 approve [ ] -1 disapprove (because why) Thanks. -- Best Regards, Edward J. Yoon @eddieyoon -- Thomas Jungblut Berlin thomas.jungb...@gmail.com -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Hama 0.4-incubating Released!
Hi all, The Hama team is pleased to announce the release of Apache Hama 0.4-incubating under the Apache Incubator. Hama is a pure BSP(Bulk Synchronous Parallel) computing framework on top of HDFS (Hadoop Distributed File System) for massive scientific computations such as matrix, graph and network algorithms. This release includes: * Stabilized Barrier Synchronization * Multiple tasks per node * Input/Output Formatter * Message Combiners * Improved examples * and its Benchmark test results Thanks to the Hama and Apache Incubating community for helping grow the project! -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Hama 0.4-incubating RC7
Hi all, This RC7 has passed the Hama PMC vote as follows (*, ** marks an PMC, IPMC vote) : +1 Thomas Jungblut * +1 Edward J. Yoon * +1 Tommaso Teofili ** +1 ChiaHung Lin * +1 Steve Loughlan ** http://markmail.org/thread/zxn5jfziafgh5vpc We still need one more IPMCer vote. Thanks. On Thu, Mar 1, 2012 at 1:42 PM, Edward J. Yoon edwardy...@apache.org wrote: We need IPMCer's votes! Sent from my iPad On Feb 29, 2012, at 6:12 PM, Thomas Jungblut thomas.jungb...@googlemail.com wrote: Signatures: - GPG signatures matches (asc) - md5 sums ok - sha1 sums ok Build: build is fine with maven, testcases pass (tar and zip) Examples: Tested all examples on local/pseudodistributed and distributed mode Whirr: started 2 EC2 instances with whirr and ran SSSP and Pagerank. The textToSeq utils also work as expected. Rat check also reveals that everything is ok. +1 (binding). Am 28. Februar 2012 13:42 schrieb Chia-Hung Lin cli...@googlemail.com: +1 mvn apache-rat:check ok sha1sum ok md5sum ok local build/ test passes executing on 4 vms works ok. On 28 February 2012 09:50, Edward J. Yoon edwardy...@apache.org wrote: Hi all, I'd like to ask your approval to release the Hama RC7 as Apache Hama 0.4.0-incubating. Signing KEYS: http://incubator.apache.org/hama/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC7/ SVN Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/ Added all 3rd party license texts into LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/LICENSE.txt Disclaimer: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/DISCLAIMER.txt New website: http://people.apache.org/~edwardyoon/site/ % mvn apache-rat:check is OK. The all builds, single mode, and distributed mode, web UI are all OK. The asc, md5, sha1 signatures are all OK. I'm +1. If there's a problem, Please let me know so that I can recreate RC8. [ ] +1 approve [ ] -1 disapprove (because why) Thanks. -- Best Regards, Edward J. Yoon @eddieyoon -- Thomas Jungblut Berlin thomas.jungb...@gmail.com -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hama status (Was: [Incubator Wiki] Update of March2012 by thomasjungblut)
Hi, Well, I think, Hama is ready to discuss about graduate incubation. According to pulse.apache.org, the number of Hama user/dev subscribers is growing and in the top 3 of all incubator projects. Contributions from new people are also increased. December report. What have you done since then to grow the community, and are you happy with the results so far? We prepared releasing of our new stable release and currently being voted on here. Please vote if you have a time. How do you plan to address this issue going forward? Would extra help from the Incubator or ComDev be useful? As we described in Wiki, we'll looking forward to participate in GSOC and invite new committers. Thanks. On Fri, Mar 2, 2012 at 8:56 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, Thanks for the early report, Hama! On Mon, Feb 27, 2012 at 4:57 PM, Apache Wiki wikidi...@apache.org wrote: + == Top 2 or 3 things to resolve prior to graduation == + + * Grow the community size. Community size was the only remaining issue mentioned also in your December report. What have you done since then to grow the community, and are you happy with the results so far? How do you plan to address this issue going forward? Would extra help from the Incubator or ComDev be useful? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hama status (Was: [Incubator Wiki] Update of March2012 by thomasjungblut)
Hi Team, I've added one more issue that should must be fixed before discuss about graduate incubation. + * Making a ready-to-use release it was only a few months ago that Barrier Sync and all examples worked smoothly[1]. 1. http://wiki.apache.org/hama/Benchmarks Thanks. On Fri, Mar 2, 2012 at 10:15 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Fri, Mar 2, 2012 at 1:52 PM, Edward J. Yoon edwardy...@apache.org wrote: Well, I think, Hama is ready to discuss about graduate incubation. According to pulse.apache.org, the number of Hama user/dev subscribers is growing and in the top 3 of all incubator projects. Contributions from new people are also increased. Sounds great, thanks! It would be good if you could add this info to the report, so that we have a better record of progress. BR, Jukka Zitting -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hama status (Was: [Incubator Wiki] Update of March2012 by thomasjungblut)
Oh, thank you very much for your note! On Fri, Mar 2, 2012 at 11:23 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Fri, Mar 2, 2012 at 2:55 PM, Edward J. Yoon edwardy...@apache.org wrote: I've added one more issue that should must be fixed before discuss about graduate incubation. + * Making a ready-to-use release Note that technical quality is not a graduation requirement [1]. So instead of the extra technical detail you added to the report, I was more interested in the note about the contributions by Apurv and Suraj. Also, especially the first paragraph of your earlier message would be a great addition to the report. [1] http://incubator.apache.org/guides/graduation.html#checklist BR, Jukka Zitting -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Hama 0.4-incubating RC7
The gap is too big between our progress and old website information. If there's no problem, I'd like to update our website first before finishing the release process. On Thu, Mar 1, 2012 at 1:42 PM, Edward J. Yoon edwardy...@apache.org wrote: We need IPMCer's votes! Sent from my iPad On Feb 29, 2012, at 6:12 PM, Thomas Jungblut thomas.jungb...@googlemail.com wrote: Signatures: - GPG signatures matches (asc) - md5 sums ok - sha1 sums ok Build: build is fine with maven, testcases pass (tar and zip) Examples: Tested all examples on local/pseudodistributed and distributed mode Whirr: started 2 EC2 instances with whirr and ran SSSP and Pagerank. The textToSeq utils also work as expected. Rat check also reveals that everything is ok. +1 (binding). Am 28. Februar 2012 13:42 schrieb Chia-Hung Lin cli...@googlemail.com: +1 mvn apache-rat:check ok sha1sum ok md5sum ok local build/ test passes executing on 4 vms works ok. On 28 February 2012 09:50, Edward J. Yoon edwardy...@apache.org wrote: Hi all, I'd like to ask your approval to release the Hama RC7 as Apache Hama 0.4.0-incubating. Signing KEYS: http://incubator.apache.org/hama/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC7/ SVN Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/ Added all 3rd party license texts into LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/LICENSE.txt Disclaimer: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/DISCLAIMER.txt New website: http://people.apache.org/~edwardyoon/site/ % mvn apache-rat:check is OK. The all builds, single mode, and distributed mode, web UI are all OK. The asc, md5, sha1 signatures are all OK. I'm +1. If there's a problem, Please let me know so that I can recreate RC8. [ ] +1 approve [ ] -1 disapprove (because why) Thanks. -- Best Regards, Edward J. Yoon @eddieyoon -- Thomas Jungblut Berlin thomas.jungb...@gmail.com -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Hama 0.4-incubating RC7
We need IPMCer's votes! Sent from my iPad On Feb 29, 2012, at 6:12 PM, Thomas Jungblut thomas.jungb...@googlemail.com wrote: Signatures: - GPG signatures matches (asc) - md5 sums ok - sha1 sums ok Build: build is fine with maven, testcases pass (tar and zip) Examples: Tested all examples on local/pseudodistributed and distributed mode Whirr: started 2 EC2 instances with whirr and ran SSSP and Pagerank. The textToSeq utils also work as expected. Rat check also reveals that everything is ok. +1 (binding). Am 28. Februar 2012 13:42 schrieb Chia-Hung Lin cli...@googlemail.com: +1 mvn apache-rat:check ok sha1sum ok md5sum ok local build/ test passes executing on 4 vms works ok. On 28 February 2012 09:50, Edward J. Yoon edwardy...@apache.org wrote: Hi all, I'd like to ask your approval to release the Hama RC7 as Apache Hama 0.4.0-incubating. Signing KEYS: http://incubator.apache.org/hama/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC7/ SVN Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/ Added all 3rd party license texts into LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/LICENSE.txt Disclaimer: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/DISCLAIMER.txt New website: http://people.apache.org/~edwardyoon/site/ % mvn apache-rat:check is OK. The all builds, single mode, and distributed mode, web UI are all OK. The asc, md5, sha1 signatures are all OK. I'm +1. If there's a problem, Please let me know so that I can recreate RC8. [ ] +1 approve [ ] -1 disapprove (because why) Thanks. -- Best Regards, Edward J. Yoon @eddieyoon -- Thomas Jungblut Berlin thomas.jungb...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[CLOSED][VOTE] Release Apache Hama 0.4-incubating RC6
I'm open new vote with RC7. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Hama 0.4-incubating RC7
Hi all, I'd like to ask your approval to release the Hama RC7 as Apache Hama 0.4.0-incubating. Signing KEYS: http://incubator.apache.org/hama/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC7/ SVN Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/ Added all 3rd party license texts into LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/LICENSE.txt Disclaimer: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC7/DISCLAIMER.txt New website: http://people.apache.org/~edwardyoon/site/ % mvn apache-rat:check is OK. The all builds, single mode, and distributed mode, web UI are all OK. The asc, md5, sha1 signatures are all OK. I'm +1. If there's a problem, Please let me know so that I can recreate RC8. [ ] +1 approve [ ] -1 disapprove (because why) Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
