Re: [PROPOSAL] New blockchain project: Cava

[Charith Elvitigala]

+1

On Wed, 6 Feb 2019 at 13:04, Furkan KAMACI  wrote:

> Hi,
>
> I have Blockchain development experience with my Blockchain startup and
> would like to be added as an initial committer for this proposal.
>
> Kind Regards,
> Furkan KAMACI
>
> On Wed, Feb 6, 2019 at 9:45 AM Jean-Baptiste Onofré 
> wrote:
>
> > Hi Antoine,
> >
> > I would be happy to help (as mentor, or as committer, or both, up to you
> > ;)).
> >
> > Regards
> > JB
> >
> > On 05/02/2019 23:42, Antoine Toulme wrote:
> > > Hi all,
> > >
> > > We’d like to start a conversation around a new proposal for a set of
> > Java-based blockchain project.
> > >
> > > I have written a proposal available here, and reproduced below:
> > https://wiki.apache.org/incubator/CavaProposal <
> > https://wiki.apache.org/incubator/CavaProposal>
> > >
> > > At this time, we have a champion, Jim Jagielski (thanks Jim), and would
> > like to recruit additional developers and mentors.
> > >
> > > We have deliberately left room on the project charter to engage openly
> > with the community. That said, we would start the project with code
> coming
> > from ConsenSys, and we will recruit developers from there and elsewhere
> > actively.
> > >
> > > The goal of this thread is engage with the community and gather
> interest
> > for participation in the project. Please let us know what you think!
> > >
> > > Cheers,
> > >
> > > Antoine Toulme
> > >
> > > == Abstract ==
> > > Cava is a set of libraries and other tools to aid development of
> > blockchain and other decentralized software in Java and other JVM
> languages.
> > >
> > > Please note: Cava is a contraction of "ConsenSys Java". The community
> > should consider an alternate name.
> > >
> > > = Proposal =
> > >
> > > Cava is a set of libraries and other tools to aid development of
> > blockchain and other decentralized software in Java and other JVM
> languages.
> > > It includes a low-level bytes library, serialization and
> deserialization
> > codecs (e.g. RLP), various cryptography functions and primatives, and
> lots
> > of other helpful utilities.
> > > Cava is developed for JDK 1.8 or higher, and depends on various other
> > FOSS libraries.
> > >
> > > === Background ===
> > >
> > > Cava was built as an open source project from the grounds up to
> > accelerate the maturation of the blockchain ecosystem, particularly in
> > relation with enterprise products predominantly built in Java.
> > > Cava is used by several products today: Orion, Pantheon, and Artemis
> > from Pegasys.
> > >
> > > Cava libraries are also used in various experiments regarding
> > scalability, such as Canto.
> > >
> > > Several other community members would want to leverage Cava and would
> > benefit from working directly on the project outside of the influence of
> > the original corporate sponsor, ConsenSys.
> > >
> > > === Rationale ===
> > >
> > > Cava is organized as set of libraries that form the basis of most
> > blockchain, distributed ledgers or cryptography work.
> > >
> > > Most of the work built for Cava was meant for Ethereum, but can be
> > reused across other blockchain technologies.
> > >
> > > There is a need for blockchain implementors to use well trusted,
> > production-ready software to bootstrap their efforts.
> > >
> > > === Initial Goals ===
> > >
> > > The goal is to form a community of developers and adopters who will be
> > able to collaborate openly around blockchain technologies and mature
> > frameworks
> > > to reduce risk when implementing blockain-related projects.
> > >
> > > === Current Status ===
> > >
> > > The project is well established and counts 2 active committers. Some
> > contributions were made from the community.
> > >
> > > The project has made several releases, distributed through Maven
> > Central, with GPG signatures and proper Maven metadata published.
> > >
> > > '''Meritocracy:'''
> > >
> > > Active discussions on github issues and PRs has helped identify new
> > possible commiters.
> > >
> > > Our main goal, moving to Apache is to promote our project as a
> > meritocracy under the guideline of the Apache Way to help foster a
> > community around our efforts.
> > >
> > >  * '''Community:'''
> > >
> > > Blockchain protocol developers organize well in communities, and some
> > lively discussions take place over Twitter, Gitter, Telegram.
> > >
> > > We would like to create a community for dedicated Java developers to
> > contribute to the blockchain space.
> > >
> > > We currently have a little activity through the channels mentioned
> > above, but no channel dedicated specifically to Cava is seeing a lot of
> > traction.
> > >
> > >  * '''Core Developers:'''
> > >
> > > Cava was built by two developers with a long experience in open source
> > work. Both lead separate open source projects.
> > > One of the developers is the PMC Chair for Apache Buildr and a
> committer
> > for Apache ODE.
> > >
> > >  * '''Alignment:'''
> > >
> > > We believe there isn't a blockchain TLP for Java at 

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Charith Elvitigala]

+1

On Mon, 12 Nov 2018, 06:03 Tan,Zhongyi,  wrote:

> +1 (no binding)
>
> 在 2018/11/11 上午5:29， "Justin Mclean"  写入:
>
> >Hi,
> >
> >+1 (binding)
> >
> >Thanks,
> >Justin
> >
> >-
> >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>

Re: [VOTE] Accept Doris into the Apache Incubator

[Charith Elvitigala]

+1

On Fri, 6 Jul 2018 at 06:21, Tan,Zhongyi  wrote:

> +1 （no binding）
>
> 发件人: Dave Fisher mailto:dave2w...@comcast.net>>
> 答复: mailto:general@incubator.apache.org>>
> 日期: 2018年7月6日 星期五 上午3:22
> 至: mailto:general@incubator.apache.org>>
> 主题: [VOTE] Accept Doris into the Apache Incubator
>
> Hi All,
>
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for
> which only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/DorisProposal
>
> Best regards,
> Dave
>
> = Apache Doris =
>
> == Abstract ==
>
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis.
>
> == Proposal ==
>
> We propose to contribute the Doris codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation,
> and aim to build an open community around Doris’s continued development in
> the ‘Apache Way’.
>
> === Overview of Doris ===
>
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> (BE).
>
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to guarantee
> fault-tolerance, and load balancing.
>
> **Backend daemon** stores the data and executes the query fragments. Many
> backend daemons could also be deployed to provide scalability and
> fault-tolerance.
>
> A typical Doris cluster generally composes of several frontend daemons and
> dozens to hundreds of backend daemons.
>
> Users can use MySQL client tools to connect any frontend daemon to submit
> SQL query. Frontend receives the query and compiles it into query plans
> executable by the Backend. Then Frontend sends the query plan fragments to
> Backend. Backend will build a query execution DAG. Data is fetched and
> pipelined into the DAG. The final result response is sent to client via
> Frontend. The distribution of query fragment execution takes minimizing
> data movement and maximizing scan locality as the main goal.
>
> == Background ==
>
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single tool,
> users were forced to build hybrid architectures that stitch multiple tools
> together, but we believe that they shouldn’t need to accept such inherent
> complexity. A storage system built to provide great performance across a
> broad range of workloads provides a more elegant solution to the problems
> that hybrid architectures aim to solve. Doris is the solution.
>
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also provides
> near real-time mini-batch data loading. Doris also provides high
> availability, reliability, fault tolerance, and scalability.
>
> == Rationale ==
>
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
>
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of users’
> and systems’ requirements, including near real-time data ingestion and
> query ability, as well as high availability, reliability, fault tolerance,
> and scalability for large data and query volumes.
>
> Impala is a modern, open-source MPP SQL engine architected from the ground
> up for the Hadoop data processing environment. At present, by virtue of its
> superior performance and rich functionality， Impala has been comparable to
> many commercial MPP database query engine. Mesa can satisfy the needs of
> many of our storage requirements, however Mesa itself does not provide a
> SQL query engine; Impala is a very good MPP SQL query engine, but the lack
> of a perfect distributed storage engine. So in the end we chose the
> combination of these two technologies.
>
> Learning from Mesa’s data model, we developed a distributed storage
> engine. Unlike Mesa, this storage engine does not rely on any distributed
> file system. Then we deeply 

Re: [VOTE] Accept ECharts for Apache Incubation

[Charith Elvitigala]

+1

On 13 January 2018 at 16:03, Romain Manni-Bucau 
wrote:

> +1
>
> Le 13 janv. 2018 09:17, "Pierre Smits"  a écrit :
>
> > +1
> >
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > V.P. Apache Trafodion
> >
> > On Sat, Jan 13, 2018 at 9:12 AM, Sergio Fernández 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > On Jan 12, 2018 14:13, "Kevin A. McGrail"  wrote:
> > >
> > > > Hi All,
> > > >
> > > > I would like to start a VOTE & I vote +1 to bring the ECharts project
> > in
> > > > as an Apache incubator podling.
> > > >
> > > > The ASF voting rules are described:
> > > >
> > > > https://www.apache.org/foundation/voting.html
> > > >
> > > > A vote for accepting a new Apache Incubator podling is a majority
> vote
> > > for
> > > > which only Incubator PMC member votes are binding.
> > > >
> > > > This vote will run for at least 72 hours. Please VOTE as follows
> > > > [ ] +1 Accept ECharts into the Apache Incubator
> > > > [ ] +0 Abstain.
> > > > [ ] -1 Do not accept ECharts into the Apache Incubator because ...
> > > >
> > > > The proposal is listed below, but you can also access it on the wiki:
> > > > https://wiki.apache.org/incubator/EChartsProposal
> > > >
> > > > Regards,
> > > > KAM
> > > >
> > > >
> > > > ECharts Proposal
> > > >
> > > > Abstract
> > > >
> > > > ECharts is a charting and data visualization library written in
> > > JavaScript.
> > > >
> > > > Proposal
> > > >
> > > > ECharts provides a powerful, interactive charting and data
> > visualization
> > > > library and framework for web browser, mobile App and backend usage.
> > > >
> > > > Background
> > > >
> > > > A primary goal of data visualization is to communicate information
> > > clearly
> > > > and efficiently via statistical graphics, plots and other graphics.
> > > >
> > > > Numerical data may be presented in dots, lines, or bars, to visually
> > > > communicate a quantitative message. Effective visualization helps
> users
> > > to
> > > > analyze data .It makes complex data more readable, understandable.[1]
> > > >
> > > > Now data visualization concerns mainly about presentation and
> > propagation
> > > > in web, ECharts uses JavaScript as its basic programing language. It
> > > brings
> > > > great compatibility across multiple platforms, not only in web
> > browsers,
> > > > but also in mobile Apps via embedded web engine or in backend
> > environment
> > > > via the techniques of headless browser.
> > > >
> > > > Rationale
> > > >
> > > > ECharts encapsulates the underlying data transformation, control
> flow,
> > > > visual encoding and rendering, receiving the visualization
> requirements
> > > > with declarative language, and produces interactive charts and
> > > components.
> > > > We will highlight the features below to illustrate the power that
> > ECharts
> > > > already has, and our concerns and our visions:
> > > >
> > > > User Diversity:
> > > >
> > > > ECharts expects that its users are not only web developers, but also
> > > > people with lesser programing skills. So ECharts enables users to
> > > describe
> > > > data and settings with declarative language, which lowers the barrier
> > but
> > > > without losing the power, and benefit to transfer and store.
> > > >
> > > > Configurable Interactions:
> > > >
> > > > ECharts has provided plenty of interactions and aims at providing
> more.
> > > > Both human interactions and the interactions with upper program are
> > > > supported and can be configurable.
> > > >
> > > > Large Data:
> > > >
> > > > Although the browser environment and JavaScript bring some
> performance
> > > > limits in visualizing large data or performing animations, ECharts
> have
> > > > been adopting various optimization techniques to rise the upper limit
> > of
> > > > the amount of data that it can process, and keep improving the
> fluency
> > of
> > > > interactions and animations.
> > > >
> > > > Cross-Platform:
> > > >
> > > > The underlying render engine of ECharts can be switched between
> > > > HTMLCanvas, SVG, or VML, which provides good compatibility and brings
> > > > opportunities to optimize performance according to different platform
> > and
> > > > usage scenarios. Besides, ECharts can also works in backend
> environment
> > > via
> > > > headless techniques.
> > > >
> > > > ECharts can be created using headless browsers to pregenerate reports
> > on
> > > > more powerful machines for better performance on resource-limited
> > devices
> > > >
> > > > Extension and Customization:
> > > >
> > > > ECharts provides extension mechanisms to make new types of chart and
> > > > components, adopt other layout algorithms, or even adopt other render
> > > > techniques. Various developers have contributed different types of
> > > > extensions based on ECharts.[2]
> > > >
> > > > Current Status
> > > >
> > > > ECharts has been an open source project on GitHub[3] since 2013.
> > > 

Re: [VOTE] Accept ServiceComb into the Apache Incubator

[Charith Elvitigala]

+1（binding)

On 14 November 2017 at 20:50, Liang Chen  wrote:

> +1
>
> Regards
> Liang
>
> 2017-11-14 16:05 GMT+08:00 Timothy Chen :
>
> > +1 as well.
> >
> > Tim
> >
> > On Mon, Nov 13, 2017 at 10:45 PM, Jean-Baptiste Onofré 
> > wrote:
> > > +1 (binding), of course ;)
> > >
> > > I'm looking forward the donation and happy to be part of and work on
> this
> > > project !
> > >
> > > Regards
> > > JB
> > >
> > >
> > > On 11/14/2017 07:15 AM, Willem Jiang wrote:
> > >>
> > >> Hi All,
> > >>
> > >> I would like to start a VOTE to bring the ServiceComb project in as an
> > >> Apache incubator podling.
> > >>
> > >> The ASF voting rules are described:
> > >>
> > >> https://www.apache.org/foundation/voting.html
> > >>
> > >> A vote for accepting a new Apache Incubator podling is a majority vote
> > for
> > >> which only Incubator PMC member votes are binding.
> > >>
> > >> This vote will run for at least 72 hours. Please VOTE as follows
> > >> [] +1 Accept ServiceComb into the Apache Incubator
> > >> [] +0 Abstain.
> > >> [] -1 Do not accept ServiceComb into the Apache Incubator because ...
> > >>
> > >> The proposal is listed below, but you can also access it on the wiki:
> > >>
> > >> https://wiki.apache.org/incubator/ServiceCombProposal
> > >>
> > >> Best regards,
> > >>
> > >> Willem Jiang
> > >>
> > >> = ServiceComb Proposal =
> > >>
> > >> == Abstract ==
> > >>
> > >> ServiceComb is a microservice framework that provides a set of tools
> and
> > >> components to make development and deployment of cloud applications
> > >> easier.
> > >> It provides functionalities such as service contract enforcement,
> > service
> > >> registration, service discovery, load balance, service reliability
> > >> (latency
> > >> and fault tolerance, flow control and graceful degradation, handler
> > chain
> > >> tracing), eventual data consistency and so forth.
> > >>
> > >> == Proposal ==
> > >>
> > >> The goal of this proposal is to bring the existing ServiceComb
> codebase
> > >> and
> > >> existing developers into the Apache Software Foundation (ASF) in order
> > to
> > >> build a vibrant, diverse and self-governed open source community
> around
> > >> the
> > >> technology.
> > >> So far the major contributors to the project have been affiliated with
> > >> Huawei and Huawei is planning to continue market and sell the Cloud
> > >> Service
> > >> Engine leveraging the ServiceComb framework.
> > >> ServiceComb is currently a registered trademark owned by Huawei, and
> > >> Huawei
> > >> is happy to donate this trademark to Apache.
> > >>
> > >> Huawei is submitting this proposal to donate the Service source code
> and
> > >> associated artifacts (documentation, web site content, wiki, etc.) to
> > the
> > >> Apache Software Foundation Incubator under the Apache License, Version
> > 2.0
> > >> and is asking Incubator PMC to establish an open source community.
> These
> > >> artifacts are currently available on GitHub at
> > >> https://github.com/ServiceComb/ and include:
> > >>   * Java Chassis: a multi-protocol (RPC & Restful) microservice
> > framework
> > >> which adopts contract-first design
> > >>   * Service Center: a service registry that enforces service contract
> > upon
> > >> service registration and discovery
> > >>   * Saga: a distributed coordinator to achieve eventual data
> consistency
> > >> based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem
> > >>   * ServiceComb.github.io:  the website repo of ServiceComb.
> > >>   * The other projects will be moved to another place if ServiceComb
> is
> > >> accepted by Apache as an incubator project.
> > >>
> > >> == Background ==
> > >>
> > >> Microservices is a variant of the service-oriented architecture (SOA)
> > >> architectural style that structures an application as a collection of
> > >> loosely coupled services. ServiceComb is an open source microservice
> > >> framework initiated as part of Huawei CSE projects (Cloud Service
> > Engine)
> > >> which was developed in 2015. It is a part of ServiceStage of Huawei
> > Public
> > >> Cloud which is one-stop PaaS platform for enterprises and developers.
> > >> Besides ServiceStage, it’s  also used in the Huawei Core Network IOT
> > >> Platform and Huawei consumer cloud. The number of  companies using
> > >> ServiceComb to develop their enterprise applications, they are
> > >> chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com,
> and
> > >> the
> > >> number is over 5 and counting.
> > >>
> > >> == Rationale ==
> > >>
> > >> ServiceComb has been developed as a total, open source solution for
> > >> developing cloud native applications. So far ServiceComb has existed
> as
> > a
> > >> GitHub project with committers mostly working for Huawei. We feel that
> > >> moving it to a neutral organization like Apache, with its strong
> > >> governance
> > >> model, is expected to help get more contributions from various
> > >> 

Re: [VOTE] MXNet to enter the Incubator

[Charith Elvitigala]

+1 (binding)

Regards,

On 21 January 2017 at 18:22, Jean-Baptiste Onofré  wrote:

> +1 (binding)
>
> Good luck !
>
> Regards
> JB
>
>
> On 01/17/2017 05:20 AM, Henri Yandell wrote:
>
>> Hi Incubator folk,
>>
>>I would like to call a vote for accepting "MXNet" for incubation in the
>> Apache Incubator.
>>
>> The full proposal is available at this wiki link:
>>
>> https://wiki.apache.org/incubator/MXNetProposal?action=recall=19
>>
>> I will reply to this email with a copy of the proposal.
>>
>> MXNet already has a broad community, which I think is clear from the
>> interest from many contributors in being a part of the project at Apache.
>> There are four mentors signed up, along with 2 or 3 other Apache
>> committers
>> looking to be involved in the project.
>>
>> Please cast your vote:
>>
>>   [ ] +1, bring MXNet into the Incubator
>>   [ ] -1, MXNet should not enter the Incubator, because...
>>
>>  The vote will be open for at least 72 hours, and only votes from the
>> Incubator PMC are binding.
>>
>> As the proposer, I consider my vote already cast in favour (and binding as
>> I'm a PMC member).
>>
>> Thanks all,
>>
>> Hen
>>
>>
> --
> 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
>
>

Charitha Elvitigala
Linkdin : https://www.linkedin.com/in/charitha-elvitigala-42a5081a/

Re: [VOTE] Accept OpenWhisk into the Apache Incubator

[Charith Elvitigala]

+1

On 17 November 2016 at 21:08, Felix Meschberger  wrote:

> +1
>
> Regards
> Felix
>
> > Am 17.11.2016 um 07:22 schrieb Sam Ruby :
> >
> > Now that the discussion thread on the OpenWhisk Proposal has died
> > down, please take a moment to vote on accepting OpenWhisk 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 OpenWhisk into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept OpenWhisk into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >   https://wiki.apache.org/incubator/OpenWhiskProposal
> >
> > - Sam Ruby
> >
> > = OpenWhisk Proposal =
> >
> > OpenWhisk is an open source, distributed Serverless computing platform
> > able to execute application logic (Actions) in response to events
> > (Triggers) from external sources (Feeds) or HTTP requests governed by
> > conditional logic (Rules). It provides a programming environment
> > supported by a REST API-based Command Line Interface (CLI) along with
> > tooling to support packaging and catalog services.
> >
> > Champion: Sam Ruby, IBM
> >
> > Mentors:
> > * Felix Meschberger, Adobe
> > * Isabel Drost-Fromm, Elasticsearch GmbH
> > * Sergio Fernández, Redlink GmbH
> >
> > == Background ==
> >
> > Serverless computing is the evolutionary next stage in Cloud computing
> > carrying further the abstraction offered to software developers using
> > Container-based operating system virtualization. The Serverless
> > paradigm enables programmers to just “write” functional code and not
> > worry about having to configure any aspect of a server needed for
> > execution. Such Serverless functions are single purpose and stateless
> > that respond to event-driven data sources and can be scaled on-demand.
> >
> > The OpenWhisk project offers a truly open, highly scalable, performant
> > distributed Serverless platform leveraging other open technologies
> > along with a robust programming model, catalog of service and event
> > provider integrations and developer tooling.
> > Specifically, every architectural component service of the OpenWhisk
> > platform (e.g., Controller, Invokers, Messaging, Router, Catalog, API
> > Gateway, etc.) all is designed to be run and scaled as a Docker
> > container. In addition, OpenWhisk uniquely leverages aspects of Docker
> > engine to manage, load balance and scale supported OpenWhisk runtime
> > environments (e.g., JavaScript, Python, Swift, Java, etc.), that run
> > Serverless functional code within Invoker compute instances, using
> > Docker containers.
> >
> > OpenWhisk's containerized design tenants not only allows it to be
> > hosted in various IaaS, PaaS Clouds platforms that support Docker
> > containers, but also achieves the high expectation of the Serverless
> > computing experience by masking all aspects of traditional resource
> > specification and configuration from the end user simplifying and
> > accelerating Cloud application development.
> > In order to enable HTTP requests as a source of events, and thus the
> > creation of Serverless microservices that expose REST APIs, OpenWhisk
> > includes an API Gateway that performs tasks like security, request
> > routing, throttling, and logging.
> >
> > == Rationale ==
> >
> > Serverless computing is in the very early stages of the technology
> > adoption curve and has great promise in enabling new paradigms in
> > event-driven application development, but current implementation
> > efforts are fractured as most are tied to specific Cloud platforms and
> > services. Having an open implementation of a Serverless platform, such
> > as OpenWhisk, available and governed by an open community like Apache
> > could accelerate growth of this technology, as well as encourage
> > dialog and interoperability.
> >
> > Having the ASF accept and incubate OpenWhisk would provide a clear
> > signal to developers interested in Serverless and its future that they
> > are welcome to participate and contribute in its development, growth
> > and governance.
> >
> > In addition, there are numerous projects already at the ASF that would
> > provide a natural fit to the API-centric, event-driven programming
> > model that OpenWhisk sees as integral to a Serverless future. In fact,
> > any project that includes a service that can produce or consume
> > actionable events could become an integration point with
> > OpenWhisk-enabled functions. Apache projects that 

Re: [VOTE] Accept NetBeans into the Apache Incubator

[Charith Elvitigala]

+1

On 28 September 2016 at 16:58, Stian Soiland-Reyes  wrote:

> +1 (non-binding)
>
> Great committer list! Don't worry if you don't get all the ICLAs signed
> right away :-)
>
> On 27 Sep 2016 9:30 p.m., "Ate Douma"  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
> > NetBeans.
> >
> > Alignment: The application framework is the basis of a range of
> mission
> > critical scientific software at large organizations in defense,
>