Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name

[Vinayakumar B]

+1 (binding)

-Vinay


On Sat, 11 May 2024 at 5:48 PM, Suyan  wrote:

> -0 binding from suyanhanx
>
> Sincerely,
> Suyan
>
> tison  于2024年5月8日周三 08:32写道：
> >
> > Hi,
> >
> > Following the discussion thread [1], I'd start a vote on the following
> > proposals:
> >
> > 1. Establish a consensus to allow and finally converge podling's GitHub
> repo to
> > have a name without the incubator- prefix.
> > 2. Allow existing ongoing podlings to ask the INFRA to drop their
> > incubator- prefix by now, not MUST during the graduation.
> > 3. Update the docs on incubator.apache.org everywhere if the description
> > can conflict with this consensus.
> > 4. Update the docs on incubator.apache.org to guide how to describe
> > podling's incubating status on the GitHub repo (namely, including
> > "incubating" in the repo description and README, point to the DISCLAIMER
> > content).
> >
> > [1] https://lists.apache.org/thread/kxvdkrf8g8yr6hww1n08r21xdy67y4ok
> >
> > +1 allow podling's GitHub repo to have a name without the incubator-
> > prefix, and other items above
> > +0 do not care strongly
> > -1 disagree the proposals above, because ...
> >
> > Please vote with your ASF ID followed by (binding) if you are a member of
> > the Incubator PMC or (not binding) if not.
> >
> > Vote will be open for at least 72 hours.
> >
> > Best,
> > tison.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept EventMesh into Apache Incubator

[Vinayakumar B]

+1 ( binding)

-Vinay

On Fri, 12 Feb 2021 at 2:21 AM, Dave Fisher  wrote:

> +1 (binding)
>
> All The Best,
> Dave
>
> > On Jan 31, 2021, at 10:43 PM, Eason Chen 
> wrote:
> >
> > Hi,
> >
> > After the discussion of EventMesh proposal (discussion thread is
> here[1]),
> > I would like to call a VOTE to accept it into the Apache Incubator.
> >
> > Please cast your vote:
> >
> >  [ ] +1, bring EventMesh into Incubator
> >  [ ] +0, I don't care either way
> >  [ ] -1, do not bring EventMesh into Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the
> Incubator
> > PMC are binding.
> >
> > The project's proposal is available at [2].
> >
> > [1]
> >
> https://lists.apache.org/thread.html/rcb4bc1e5b4994d377aba4191737ff7c1f7e375fb9044cfbebe236e95%40%3Cgeneral.incubator.apache.org%3E
> > [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
-Vinay

Re: [VOTE] Graduate Apache Ratis as TLP Project

[Vinayakumar B]

+1 (binding)

-Thanks

On Sun, 31 Jan 2021 at 2:18 AM, Rui Wang  wrote:

> +1 (non binding)
>
>
> Thanks,
> Rui Wang
>
> On Sat, Jan 30, 2021 at 10:54 AM Xiaoyu Yao 
> wrote:
>
> > +1 (binding)
> >
> > Thanks Uma for driving this effort.
> >
> > Regards,
> > Xiaoyu
> >
> > On Fri, Jan 29, 2021 at 12:35 PM Uma gangumalla 
> > wrote:
> >
> > > Here is my vote
> > >
> > > +1 (binding)
> > >
> > > Regards,
> > > Uma
> > >
> > > On Fri, Jan 29, 2021 at 12:32 PM Uma gangumalla 
> > > wrote:
> > >
> > > > Dear Incubator Community,
> > > >
> > > >  We have discussed Apache Ratis Podling graduation in the incubator
> > > > general DISCUSS thread[1] and We did not see any objections to
> proceed
> > > for
> > > > voting. Here is the official vote for graduating Apache Ratis project
> > as
> > > > TLP.
> > > >
> > > > Please provide your in the following options:
> > > > [ ] +1 - Recommend graduation of Apache Ratis as a TLP
> > > > [ ]  0 - I don't feel strongly about it, but don't object
> > > > [ ] -1 - Do not recommend graduation of Apache Ratis because...
> > > >
> > > > The VOTE will open for at least 72 hours.
> > > >
> > > > Just to summarize again:
> > > > Apache Ratis project is a very active project and the community has
> > grown
> > > > well by following the Apache way in the process. It produced several
> > > > releases by having diverse people as release managers. I and the
> > > community
> > > > strongly believe that it's ready for graduation.
> > > >
> > > > The Apache Ratis project has been an Apache incubator project for
> > nearly
> > > 3
> > > > year. Since then the community has grown and followed Apache Way.
> Some
> > > > highlights include:
> > > > * 7 releases given ( including 1.0.0 and 0.0.1 alpha ) by having
> > > > different people as release managers
> > > > * 50 contributors ( from report)
> > > > * 28 committers
> > > > * More than 1161 Jiras created, 905 resolved or closed
> > > > * > 293 pull requests in github
> > > > * One of the biggest positives for this community is that most of the
> > > > members in this community have a lot of experience in other Apache
> > > projects
> > > > already.
> > > >
> > > > Some additional note about the resolution below:
> > > > The current PPMC will be transitioned to the PMC. We have invited
> some
> > of
> > > > the mentors in the current PPMC who like to stay involved.
> > > > We are also adding Siddharth and Jie Wang into PMC as we believe they
> > are
> > > > committed to the project and a good addition to PMC.
> > > >
> > > > We have already voted for Ratis TLP in the Ratis Podling community.
> > > Please
> > > > find the voting threads for reference. Ratis PPMC DISCUSS thread:
> [2],
> > > > Ratis PPMC Vote: [3] and Ratis Community: [4]
> > > >
> > > > To make easy for you to review, here is the *resolution text*[5]
> > copied:
> > > >
> > >
> >
> ==
> > > > Establish the Apache Ratis 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 java implementation for RAFT consensus protocol.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache Ratis Project", be and hereby is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache Ratis Project be and hereby is responsible
> > for
> > > > the creation and maintenance of software related to A java
> > > > implementation for RAFT consensus protocol; and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache Ratis" 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 Ratis
> > > > Project, and to have primary responsibility for management of the
> > > > projects within the scope of responsibility of the Apache Ratis
> > 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 Ratis
> Project:
> > > >
> > > >  * Anu Engineer  [Hadoop, Ozone PMC,
> > > > Incubator Committer]
> > > >  * Arpit Agarwal [ ASF Member, Hadoop,
> Ozone,
> > > > Incubator PMC]
> > > >  * Enis Soztutar [ASF Member, Hadoop,
> HBase,
> > > > Incubator PMC and also PMC in curator, gora, phoenix]
> > > >  * Hanisha Koneru[Hadoop, Ozone
> PMC,
> > > > Incubator Committer]
> > > >  * Jie Wang  [Incubator, Ozone
> > > > Committer]
> > > >  * Jing Zhao [Hadoop PMC, Incubator
> > > > Committer]
> > > >  * Jitendra 

Re: [VOTE] Apache Tuweni 1.2.0 release

[Vinayakumar B]

Carrying my +1 from podling's vote to here.

-Vinay


On Mon, Oct 12, 2020 at 11:46 AM Antoine Toulme  wrote:

> Thanks, anyone with time to vote on this release?
>
> Cheers,
>
> Antoine
>
> > On Oct 9, 2020, at 5:09 AM, Michael Wall  wrote:
> >
> > Antoine,
> >
> > I'll take a look this weekend.
> >
> > Mike
> >
> > On Fri, Oct 9, 2020 at 2:12 AM Antoine Toulme 
> wrote:
> >>
> >> Any chance we may get more votes from the incubator? Please advise.
> >>
> >> Cheers,
> >>
> >> Antoine
> >>
> >>> On Sep 30, 2020, at 23:58, Furkan KAMACI 
> wrote:
> >>>
> >>> Hi,
> >>>
> >>> +1 from me (binding, carrying over my vote).
> >>>
> >>> I checked:
> >>>
> >>> - Incubating in name
> >>> - DISCLAIMER exists
> >>> - LICENSE and NOTICE are fine
> >>> - No unexpected binary files
> >>> - Checked PGP signatures
> >>> - Checked checksums
> >>> - Code compiles
> >>>
> >>> Kind Regards,
> >>> Furkan KAMACI
> >>>
> >>>> On Wed, Sep 30, 2020 at 9:34 AM Antoine Toulme 
> wrote:
> >>>>
> >>>> Hi all,
> >>>>
> >>>> We're voting on the source distributions available here:
> >>>>
> https://dist.apache.org/repos/dist/dev/incubator/tuweni/1.2.0-incubating/
> >>>> <
> https://dist.apache.org/repos/dist/dev/incubator/tuweni/1.2.0-incubating/
> >>>>>
> >>>> The release tag is present here:
> >>>>
> https://github.com/apache/incubator-tuweni/releases/tag/v1.2.0-incubating
> >>>> <
> https://github.com/apache/incubator-tuweni/releases/tag/v1.2.0-incubating
> >>>>>
> >>>>
> >>>> This release includes the following changes:
> >>>> New:
> >>>> * Ethash hashing support
> >>>> * EVMC support
> >>>> * Simplify distribution down to one binary and source artifacts
> >>>> * Added doc build
> >>>> Changes:
> >>>> * Refactor discv5, testing it with an eth2 client
> >>>> * Simplified and streamlined LES to match ETH devp2p subprotocols
> >>>> Bug fixes:
> >>>> * Fixes #141 - Generated Maven pom.xml have incorrect information
> >>>> * Fix SecureScuttlebutt setup.
> >>>> Misc:
> >>>> * Added codecov and tests adding coverage
> >>>>
> >>>> Here is the release thread on the d...@tuweni.apache.org  >>>> d...@tuweni.apache.org> list:
> >>>>
> >>>>
> https://lists.apache.org/thread.html/re9128953304e3bdc3a80012e623b63e0d122b5aa261410f24c7041bf%40%3Cdev.tuweni.apache.org%3E
> >>>> <
> >>>>
> https://lists.apache.org/thread.html/re9128953304e3bdc3a80012e623b63e0d122b5aa261410f24c7041bf@%3Cdev.tuweni.apache.org%3E
> >>>>>
> >>>>
> >>>> The release vote has passed with the following votes (
> >>>>
> https://lists.apache.org/thread.html/r47854c9fe57147b12f9158504c9310650a9abfae0c8daf35347d1f03%40%3Cdev.tuweni.apache.org%3E
> >>>> <
> >>>>
> https://lists.apache.org/thread.html/r47854c9fe57147b12f9158504c9310650a9abfae0c8daf35347d1f03@%3Cdev.tuweni.apache.org%3E
> >>>>> )
> >>>> 3 +1:
> >>>> Antoine Toulme
> >>>> Furkan Kamaci
> >>>> Vinayakumar B
> >>>> 0 +0
> >>>> 0 -1
> >>>>
> >>>> The release vote is open at least until 10/3 12pm PST time.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Antoine
> >>>>
> >>>>
> >>
> >>
> >> -
> >> 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] Hop proposal

[Vinayakumar B]

+1 (binding)

-Vinay


On Thu, Sep 17, 2020 at 1:34 PM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Don’t hesitate to ping me if you need help.
>
> Regards
> JB
>
> > Le 16 sept. 2020 à 15:28, Matt Casters
>  a écrit :
> >
> > Hi Apache,
> >
> > I'd like to call a vote on accepting Hop into the Apache Incubator.
> > Please see the discussion thread [1].
> >
> > Please see the full proposal:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/HopProposal
> > Please cast your vote
> >
> >[ ] +1 Accept Hop into the Incubator
> >[ ] +0 Indifferent to the acceptance of Hop
> >[ ] -1 Do not accept Hop because …
> >
> > The vote will be open at least for 72 hours.
> >
> > Incubator PMC member votes are binding. Everyone else is welcomed to vote
> > too
> > (mark them as non-binding if you can)!
> >
> > Thanks in advance for your time.
> >
> > Regards,
> > Matt
> >
> > [1]
> >
> http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-Hop-proposal-td68232.html
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept YuniKorn into Apache Incubator

[Vinayakumar B]

+1 (binding)

-Vinay


On Mon, Jan 13, 2020 at 8:24 AM Junjie Chen 
wrote:

> +1 (non-binding), good luck!
>
> On Mon, Jan 13, 2020 at 10:28 AM Yiheng Wang  wrote:
>
> > +1 ( non-binding)
> >
> > On Sat, Jan 11, 2020 at 1:47 AM Vinod Kumar Vavilapalli <
> > vino...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > I'd like to call a vote on accepting YuniKorn into the Apache
> Incubator.
> > >
> > > Please see the discussion thread [1].
> > >
> > > Please see the full proposal:
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/YuniKornProposal
> > >
> > > Please cast your vote
> > >
> > > [ ] +1 Accept YuniKorn into the Incubator
> > > [ ] +0 Indifferent to the acceptance of YuniKorn
> > > [ ] -1 Do not accept YuniKorn because …
> > >
> > > The vote will be open at least for 72 hours.
> > >
> > > Incubator PMC member votes are binding. Everyone else is welcomed to
> vote
> > > too (mark them as non-binding if you can)!
> > >
> > > Thanks
> > > +Vinod
> > >
> > > [1] [DISCUSS] YuniKorn Proposal
> > >
> >
> https://lists.apache.org/thread.html/59a3fc019119352f06e75a2bae5c25cd1b652282d7a59b85ed2188cf%40%3Cgeneral.incubator.apache.org%3E
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>
>
> --
> Best Regards
>

Re: Podling use of StackOverflow

[Vinayakumar B]

Agree with james.

Most of us search for an answer in Google.. which eventually take us to
stackoverflow.

Apache Mailing list answers are very rare in Google results.

Stackoverflow like portal could become next podling for incubator.

-Vinay

On Fri, 5 Apr 2019, 7:05 pm James Bognar,  wrote:

> My $.02.
>
> Apache is sorely in need of a portal similar to StackOverflow.  I,
> like many other software developers, primarily use Google for finding
> answers.  90% of the time those answers are going to be found on
> StackOverflow.  Answers on mailing lists are not going to show up in
> Google results, and as an external user I'm not going to go out of my
> way to figure out how to find and search for them.  If I can't find it
> on Google, then for all practical purposes it doesn't exist.
>
> I don't know if this will ever change.  Using mailing lists for
> everything is one of the top Apache-Way principles.
>
> I'll buy a beer for anyone who sets up an Apache-specific
> StackOverflow clone for all of us to use.
>
> On Thu, Apr 4, 2019 at 9:21 PM Ted Dunning  wrote:
> >
> > I sometimes used cut and paste in such cases. And if questions are
> > reflected into the dev or user, the duplications are apparent.
> >
> > On Thu, Apr 4, 2019, 11:03 AM Julian Hyde  wrote:
> >
> > > It can be frustrating when someone posts a question to both the user
> list
> > > and to StackOverflow. It means that the community has to answer the
> > > question in two places.
> > >
> > > But like many problems, that is an opportunity. Answering StackOverflow
> > > questions is a great way for people to contribute without writing
> code. If
> > > you take the view that everyone reading or writing StackOverflow is
> part of
> > > the community — and I do — then StackOverflow is an excellent way to
> grow
> > > community.
> > >
> > > Julian
> > >
> > >
> > >
> > >
> > > > On Apr 4, 2019, at 10:33 AM, Ted Dunning 
> wrote:
> > > >
> > > > Just subscribe to appropriate tags on stack overflow and direct
> > > > notifications to the dev list.
> > > >
> > > > Then encourage the community to answer on stack overflow.
> > > >
> > > >
> > > > On Wed, Apr 3, 2019 at 6:32 PM Dave Fisher 
> > > wrote:
> > > >
> > > >> I think a user@ mailing list is better for the project’s
> sustainability
> > > >> and Apache.
> > > >>
> > > >> I have examples related to POI where there is substantial
> StackOverflow
> > > >> support happening.
> > > >>
> > > >> 12 years ago I became a POI committer for answering user questions.
> > > >>
> > > >> Recently we asked an active StackOverflow answer if he was
> interested in
> > > >> being a committer and StackOverflow was his community.
> > > >>
> > > >> Apache records are always better than stuff at another company.
> Gmane
> > > and
> > > >> markmail email links have rotted away.
> > > >>
> > > >> I would encourage a user list for the visibility for the PMC in
> > > >> understanding what’s happening along with a more coherent community!
> > > >>
> > > >> Regards,
> > > >> Dave
> > > >>
> > > >> Sent from my iPhone
> > > >>
> > > >>> On Apr 3, 2019, at 6:02 PM, Alan Gates 
> wrote:
> > > >>>
> > > >>> The superset podling is working out their processes around FAQs and
> > > >>> answering user questions.  One thing that they have suggested is
> that
> > > >> they
> > > >>> encourage people to use StackOverflow for questions and answers
> given
> > > the
> > > >>> ease of searching old questions, etc.  You can see the mail thread
> at
> > > >>>
> > > >>
> > >
> https://lists.apache.org/thread.html/1cd1c1e7d02d712ec4e1a13a50cb6016318be5e55ca023b10087cb61@%3Cdev.superset.apache.org%3E
> > > >>>
> > > >>> Personally I think encouraging podlings to use tools they and
> everyone
> > > >> are
> > > >>> comfortable with and that meet our criteria of being open to all
> is a
> > > >> good
> > > >>> thing, but I wanted to check if there was official policy on this
> > > before
> > > >>> they proceed with it.
> > > >>>
> > > >>> Alan.
> > > >>
> > > >>
> > > >>
> -
> > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > > >>
> > > >>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Apache TVM into the incubator

[Vinayakumar B]

+1 (binding)

-Vinay

On Mon, 4 Mar 2019, 11:47 am 吴晟 Sheng Wu,  wrote:

> +1 binding
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "Mohammad Asif Siddiqui";
> Date:  Mon, Mar 4, 2019 02:13 PM
> To:  "general";
>
> Subject:  Re: [VOTE] Accept Apache TVM into the incubator
>
>
>
> +1 (binding)
>
> Regards
> Asif
>
> On 2019/02/28 04:44:13, Markus Weimer  wrote:
> > Hi everyone,
> >
> > we've discussed the proposal for the TVM project in [1]. The proposal
> itself can
> > be found on the wiki [2].
> >
> > According to the Incubator rules[3] I'd like to call a vote to accept
> the new
> > TVM project as a podling in the Apache Incubator.
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone
> > is welcome to vote, only Incubator PMC member votes are binding. It
> would be
> > helpful (but not required) if you could add a comment stating whether
> your vote
> > is binding or non-binding.
> >
> > This vote will run for at least 72 hours (but I expect to keep it open
> for
> > longer). Please VOTE as follows:
> >
> > [ ] +1 Accept TVM into the Apache Incubator
> > [ ] +0 Abstain
> > [ ] -1 Do not accept TVM into the Apache Incubator because ...
> >
> > Thank you for everyone who decided to join in in the past discussions!
> >
> > Markus
> >
> > [1]:
> https://lists.apache.org/thread.html/e2b1fe9ca76422ec80b146a6b120091f2419e2f1c27d57080f39cf6f@%3Cgeneral.incubator.apache.org%3E
> >
> > [2]: https://wiki.apache.org/incubator/TVMProposal
> >
> > [3]: https://incubator.apache.org/guides/proposal.html#the_vote
> >
> > -
> > 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 Cava into the Apache Incubator

[Vinayakumar B]

+1

-Vinay



On Fri, 22 Feb 2019, 7:22 am Huxing Zhang,  wrote:

> +1 (non-binding)
>
> On Thu, Feb 21, 2019 at 3:50 AM Antoine Toulme 
> wrote:
> >
> > Hi everyone,
> >
> > we've discussed the proposal for the Cava project in [1] and [2]. The
> > proposal itself can be found on the wiki[3].
> >
> > We discussed how to go about finding a suitable name for the project in
> [2].
> > I will kick off a vote to pick a name based on the proposals made there.
> >
> > According to the Incubator rules[4] I'd like to call a vote to accept the
> > new "Cava" project as a podling in the Apache Incubator.
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote.
> > Everyone is welcome to vote, only Incubator PMC member votes are binding.
> > It would be helpful (but not required) if you could add a comment stating
> > whether your vote is binding or non-binding.
> >
> > This vote will run for at least 72 hours (but I expect to keep it open
> for
> > longer). Please VOTE as follows:
> >
> > [ ] +1 Accept Cava into the Apache Incubator
> > [ ] +0 Abstain
> > [ ] -1 Do not accept Cava into the Apache Incubator because ...
> >
> > Thank you for everyone who decided to join in in the past discussions!
> > Antoine
> >
> > [1]:
> https://lists.apache.org/thread.html/5a7f6a218b11a1cac61fbd53f4c995fd7716f8ad3751cf9f171ebd57@%3Cgeneral.incubator.apache.org%3E
> > [2]:
> https://lists.apache.org/thread.html/8d8014f53f140a3ccdd517c3c303de1d45cc04afdaee5961ac43e7fc@%3Cgeneral.incubator.apache.org%3E
> > [3]: https://wiki.apache.org/incubator/CavaProposal?action=recall=14
> > [4]: https://incubator.apache.org/guides/proposal.html#the_vote
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> --
> Best Regards！
> Huxing
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Binary jars in the source release which are only for testing

[Vinayakumar B]

Hi,

For testing purpose.. why cant provide bin artifacts in a separate
convenience binary package as its being done in many other projects.. why
it should be part of source package.?

For the easy detection.. bin artifacts can have same version number as
source.

Again.. Official voting is on source package as per policy.

-Vinay

On Sun, 24 Feb 2019, 12:44 pm Willem Jiang,  wrote:

> Hi Ted,
>
> You made a good point,  I think my solution could be building the jars
> from source and then using it for testing.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Feb 24, 2019 at 10:02 AM Ted Dunning 
> wrote:
> >
> > Willem,
> >
> > This issue of embedded binaries for testing purposes has come up before.
> > Examples include network intercepts for testing malware detection or
> class
> > files for a byte code manipulator. The network files can't easily be
> > recreated since they were observed in the wild and the class files might
> > have been produced by a specific (possibly broken) compiler version that
> > isn't widely available.
> >
> > The key question is whether these binaries are derived from some source
> > that could be compiled instead of distributing the binary objects.
> Failing
> > that, can the provenance and justification for the binary object be
> > described?
> >
> >
> >
> >
> > On Sat, Feb 23, 2019 at 6:49 PM Willem Jiang 
> wrote:
> >
> > > Hi
> > >
> > > Thanks Justin for the clarification.  I guess the policy imply the
> > > source materials cannot have any binary.
> > > But what if the binary is only for testing, which cannot be part of
> > > the released software.
> > > From my point of view, we don't need to modify the source materials
> > > testing binary to do the software release as it is not a part of the
> > > binary release of the software.
> > >
> > > Any thoughts?
> > >
> > > Regards,
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Sat, Feb 23, 2019 at 2:41 PM Justin Mclean <
> jus...@classsoftware.com>
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > > [1]http://www.apache.org/legal/release-policy.html#what
> > > >
> > > > It’s explained in that link there i.e.  "The Apache Software
> Foundation
> > > produces open source software. All releases are in the form of the
> source
> > > materials needed to make changes to the software being released”.
> > > >
> > > > Thanks,
> > > > Justin
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Training into the Apache Incubator

[Vinayakumar B]

+1 (binding)

-Vinay


On Wed, Feb 13, 2019 at 4:58 PM Hans-Peter Zorn  wrote:

> +1 (non-binding)
>
> Looking forward to work on this!
> Thanks,
> Hans-Peter
>
> > Am 13.02.2019 um 08:57 schrieb Lars Francke :
> >
> > Hi everyone,
> >
> > we've discussed the proposal for the Training project in [1] and [2]. The
> > proposal itself can be found on the wiki[3].
> >
> > According to the Incubator rules[4] I'd like to call a vote to accept the
> > new "Training" project as a podling in the Apache Incubator.
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote.
> > Everyone is welcome to vote, only Incubator PMC member votes are binding.
> > It would be helpful (but not required) if you could add a comment stating
> > whether your vote is binding or non-binding.
> >
> > This vote will run for at least 72 hours (but I expect to keep it open
> for
> > longer). Please VOTE as follows:
> >
> > [ ] +1 Accept Training into the Apache Incubator
> > [ ] +0 Abstain
> > [ ] -1 Do not accept Training into the Apache Incubator because ...
> >
> > Thank you for everyone who decided to join in in the past discussions!
> > Lars
> >
> > [1] <
> >
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> >>
> >
> > [2] <
> >
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> >>
> >
> > [3] 
> >
> > [4] <
> >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc2

[Vinayakumar B]

Hi Sheng Zha,

Check example from Hadoop's documentation.
https://raw.githubusercontent.com/apache/hadoop/trunk/hadoop-common-project/hadoop-common/src/site/markdown/filesystem/filesystem.md

In Hadoop's documentation all markdown files have header and none of them
are excluded from RAT check.
-Vinay


On Wed, Feb 13, 2019 at 9:34 AM Sheng Zha  wrote:

> Also, I looked to the TLP Apache Spark for an example on license header on
> markdown, and I found none [1].
>
> Is your comment on markdown file a suggestion or a requirement? Some
> clarification would be much appreciated.
>
> -sz
>
> [1]
> https://github.com/apache/spark/search?q=Licensed+to+the+Apache+Software+Foundation_q=Licensed+to+the+Apache+Software+Foundation
>
>
> On 2019/02/13 03:49:49, Sheng Zha  wrote:
> > Hi Luciano,
> >
> > Thank you for the helpful feedback. As a PPMC member of Apache MXNet,
> I'd like to resolve this issue once for all. One thing that we can benefit
> from your help is narrowing down what file types are acceptable to be in
> whitelist.
> >
> > I started a pull-request for this purpose [1] (and thread [2]). Given
> that RAT check is a popular method at Apache, I'd appreciate you and other
> people who are willing to help to comment on it. If others find it useful,
> I'm happy to bring back the result to the list once we have clarity.
> >
> > -sz
> >
> > [1] https://github.com/apache/incubator-mxnet/pull/14142
> > [2]
> https://lists.apache.org/thread.html/7edb466510963e1c9f2c7b3bf35b7c6a8b0dac83bfa520113b34cea3@%3Ccommits.mxnet.apache.org%3E
> >
> > On 2019/02/12 04:51:01, Luciano Resende  wrote:
> > > On Mon, Feb 11, 2019 at 3:55 PM Hen  wrote:
> > > >
> > > > Did you mean:
> > > >
> > > > "The rat-exclude configuration on the project _must_ be less
> permissive."
> > > >
> > > > ?
> > > >
> > >
> > > What I was trying to say is that, even though MXNet has configured and
> > > is using rat, the rat-exclude then is very broad, where it excludes
> > > like (*.xml which leave pom.xml out for example, or docker/*) this
> > > causes a lot of files that can ahd must have apache license headers to
> > > not be checked.
> > >
> > > > (your text suggests it's an option, whereas your vote says it's
> required)
> > > >
> > >
> > > https://www.apache.org/legal/src-headers.html
> > >
> > > > On Sun, Feb 10, 2019 at 8:08 PM Luciano Resende <
> luckbr1...@gmail.com>
> > > > wrote:
> > > >
> > > > > I ran RAT, and while I understand that a lot of the failures are
> > > > > coming from the 3rdparty directory, some of those are from files
> that
> > > > > should have the ASF license header such as pom files, docker files,
> > > > > project documentation (yes, MD files do accept apache license
> > > > > headers),  Maybe the rat-exclude configuration on the project
> should
> > > > > be less permissive.
> > > > >
> > > > > Based on this I am -1 (binding)
> > > > >
> > > > > On Wed, Feb 6, 2019 at 1:59 PM Steffen Rochel <
> steffenroc...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > Dear community,
> > > > > >
> > > > > > This is a call for releasing Apache MXNet (incubating) 1.4.0,
> release
> > > > > > candidate 2
> > > > > >
> > > > > > Apache MXNet (incubating) community has voted and approved the
> release.
> > > > > >
> > > > > > Vote thread:
> > > > > >
> > > > > >
> > > > >
> https://lists.apache.org/thread.html/4b445460d36d098be1c1e60e29869cf243e2bc37bd2b84ca7b1daab3@%3Cdev.mxnet.apache.org%3E
> > > > > >
> > > > > >
> > > > > > Result thread:
> > > > > >
> > > > > >
> > > > >
> https://lists.apache.org/thread.html/60e3272326cf93100370fa5b01a54a4b2f18f95462553b5a1acfd456@%3Cdev.mxnet.apache.org%3E
> > > > > >
> > > > > > The community raised the following issues which are not
> considered as
> > > > > > release stopper:
> > > > > >
> > > > > > 1. NOTICE year is wrong (2018): Not considered a stopping issue
> as
> > > > > release
> > > > > > was started in 2018.
> > > > > > 2. TVM NOTICE missing - TVM NOTICE file was added post the
> commit ID used
> > > > > > in MXNet v1.4.0.rc2 release, not considered a stopping issue
> > > > > > 3. build with make passes, but build with cmake failed in
> > > > > > 3rdparty/dmlc-core/test/unittest
> > > > > > 4. Recent MKLDNN upgrade prevents us from offering binary
> distribution
> > > > > for
> > > > > > earlier versions before OSX 10.13.
> > > > > >
> > > > > >
> > > > > > The source tarball, including signatures, digests, etc. can be
> found at:
> > > > > >
> > > > > >
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc2/
> > > > > >
> > > > > > The tag to be voted upon:
> > > > > > https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc2
> > > > > >
> > > > > > The release hash is e999a46
> > > > > > <
> > > > >
> https://github.com/apache/incubator-mxnet/commit/e999a46a8ca1383e78a9178dc65fa91e6e656c26
> > > > > >
> > > > > > :
> > > > > >
> > > > > >
> > > > >
> https://github.com/apache/incubator-mxnet/commit/e999a46a8ca1383e78a9178dc65fa91e6e656c26
> > > > > >
> 

Re: [PROPOSAL] New blockchain project: Cava

[Vinayakumar B]

+1,

Interesting proposal.

I would be happy to be part of the project in any way possible..
(Contributor/Reviewer/Mentor/Committer)

-Vinay

On Wed, 6 Feb 2019, 6:32 pm Pierre Smits  Hi Antoine,
>
> Thank you for bringing this proposal to the Apache Incubator. So I gladly
> give my +1.
>
> Having a background in accounting and being one of the Apache OFBiz
> contributors I am very interested in blockchain technology, while being
> very interested in applying its functionalities in an ERP setting like
> Apache OFBiz is.
>
> While the Apache Trafodion project was in incubation I was very much
> involved in helping (mentoring) that project towards graduation, which it
> has successively done. I would like to help out as one of the mentors, and
> as a contributor/committer (of the other kind).
>
> Best regards,
>
> Pierre Smits
>
> *Apache Trafodion , Vice President & PMC
> Chair*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> *Apache OFBiz , contributor (without privileges)
> since 2008*
> Apache Steve , committer
>
>
> On Tue, Feb 5, 2019 at 11:42 PM 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 

Re: [VOTE] Accept Hudi into the Apache Incubator

[Vinayakumar B]

+1

- Vinay

On Tue, 15 Jan 2019, 10:56 am Hongtao Gao  +1
>
> Hongtao Gao
>
>
> Thomas Weise  于 2019年1月14日周一 上午6:34写道：
>
> > Hi all,
> >
> > Following the discussion of the Hudi proposal in [1], this is a vote
> > on accepting Hudi into the Apache Incubator,
> > per the ASF policy [2] and voting rules [3].
> >
> > A vote for accepting a new Apache Incubator podling is a
> > majority vote. Everyone is welcome to vote, only
> > Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as
> > follows:
> >
> > [ ] +1 Accept Hudi into the Apache Incubator
> > [ ] +0 Abstain
> > [ ] -1 Do not accept Hudi into the Apache Incubator because ...
> >
> > The proposal is included below, but you can also access it on
> > the wiki [4].
> >
> > Thanks for reviewing and voting,
> > Thomas
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/12e2bdaa095d68dae6f8731e473d3d43885783177d1b7e3ff2f65b6d@%3Cgeneral.incubator.apache.org%3E
> >
> > [2]
> >
> >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> >
> > [3] http://www.apache.org/foundation/voting.html
> >
> > [4] https://wiki.apache.org/incubator/HudiProposal
> >
> >
> >
> > = Hudi Proposal =
> >
> > == Abstract ==
> >
> > Hudi is a big-data storage library, that provides atomic upserts and
> > incremental data streams.
> >
> > Hudi manages data stored in Apache Hadoop and other API compatible
> > distributed file systems/cloud stores.
> >
> > == Proposal ==
> >
> > Hudi provides the ability to atomically upsert datasets with new values
> in
> > near-real time, making data available quickly to existing query engines
> > like Apache Hive, Apache Spark, & Presto. Additionally, Hudi provides a
> > sequence of changes to a dataset from a given point-in-time to enable
> > incremental data pipelines that yield greater efficiency & latency than
> > their typical batch counterparts. By carefully managing number of files &
> > sizes, Hudi greatly aids both query engines (e.g: always providing
> > well-sized files) and underlying storage (e.g: HDFS NameNode memory
> > consumption).
> >
> > Hudi is largely implemented as an Apache Spark library that reads/writes
> > data from/to Hadoop compatible filesystem. SQL queries on Hudi datasets
> are
> > supported via specialized Apache Hadoop input formats, that understand
> > Hudi’s storage layout. Currently, Hudi manages datasets using a
> combination
> > of Apache Parquet & Apache Avro file/serialization formats.
> >
> > == Background ==
> >
> > Apache Hadoop distributed filesystem (HDFS) & other compatible cloud
> > storage systems (e.g: Amazon S3, Google Cloud, Microsoft Azure) serve as
> > longer term analytical storage for thousands of organizations. Typical
> > analytical datasets are built by reading data from a source (e.g:
> upstream
> > databases, messaging buses, or other datasets), transforming the data,
> > writing results back to storage, & making it available for analytical
> > queries--all of this typically accomplished in batch jobs which operate
> in
> > a bulk fashion on partitions of datasets. Such a style of processing
> > typically incurs large delays in making data available to queries as well
> > as lot of complexity in carefully partitioning datasets to guarantee
> > latency SLAs.
> >
> > The need for fresher/faster analytics has increased enormously in the
> past
> > few years, as evidenced by the popularity of Stream processing systems
> like
> > Apache Spark, Apache Flink, and messaging systems like Apache Kafka. By
> > using updateable state store to incrementally compute & instantly reflect
> > new results to queries and using a “tailable” messaging bus to publish
> > these results to other downstream jobs, such systems employ a different
> > approach to building analytical dataset. Even though this approach yields
> > low latency, the amount of data managed in such real-time data-marts is
> > typically limited in comparison to the aforementioned longer term storage
> > options. As a result, the overall data architecture has become more
> complex
> > with more moving parts and specialized systems, leading to duplication of
> > data and a strain on usability.
> >
> > Hudi takes a hybrid approach. Instead of moving vast amounts of batch
> data
> > to streaming systems, we simply add the streaming primitives (upserts &
> > incremental consumption) onto existing batch processing technologies. We
> > believe that by adding some missing blocks to an existing Hadoop stack,
> we
> > are able to a provide similar capabilities right on top of Hadoop at a
> > reduced cost and with an increased efficiency, greatly simplifying the
> > overall architecture in the process.
> >
> > Hudi was originally developed at Uber (original name “Hoodie”) to address
> > such broad inefficiencies in ingest & ETL & ML pipelines across Uber’s
> data
> > ecosystem that required the upsert & incremental consumption primitives
> > supported by Hudi.
> 

Re: Draft email to member list to try and recruit some new mentors

[Vinayakumar B]

Hi,
I am not a member. PMC of Hadoop.
Still I would like to help here if any possible.

Please do let me know.

-Vinay

On Sat, 3 Nov 2018, 4:32 am Justin Mclean  HI,
>
> Update of draft email below, if there no further feedback I’ll send this
> out is a few days.
>
> --
> Hi,
>
> The incubator PMC needs you!
>
> We have a number of existing podlings [1] and several new podlings
> starting up at the IPMC than need mentors.
>
> As an ASF member all you need to do to become part of the incubator PMC
> is to ask. [2]
>
> Some reasons you may want to become a mentor:
> - Share your experience and knowledge.
> - Learn more about the Apache Way and how different projects operate
> within that.
> - Be actively involved to helping a project become a top level project.
> - Help build a community around a project
> - Polish you skills on reviewing releases.
>
> And, lets be honest, it looks good on a resume :-)
>
> So what is expected of you? Basically this:
> - Subscribe to the projects mailing lists.
> - Scan lists looking for anomalies or possible issues.
> - Encourage PPMC members to look for new committers and grow their
> community.
> - Answer questions on incubator or ASF process and policy or direct them
> to the correct place.
> - Keep the project's roster up-to date.
> - Review/vote on proposed releases.
> - Review/approve podling board reports.
> - Help on podling setup and podling exit (hopefully graduation).
>
> Mostly you just need to be aware of what is going on and for a smoothly
> running PPMC there is little work. You can find full ist of
> responsibilities here. [3] If you would like to be a mentor please get in
> touch.
>
> Thanks,
> Justin
> (V.P. Incubator)
>
> 1. Airflow, Annotator, Crail, Daffodil, Edgent, Hivemail, Milagro, Myriad,
> ODF toolkit, Omid, Openwhisk, Pony mail, Quickstep, Rya, S2Graph, Samoa,
> Sdap, Senssoft, Spot, Tamaya, Tephra, Unomi, Warble and Weex
> 2. https://incubator.apache.org/guides/pmc.html#joining_the_ipmc
> 3.
> https://incubator.apache.org/policy/roles_and_responsibilities.html#responsibilities_toward_podling_community
> —
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept ServiceComb into the Apache Incubator

[Vinayakumar B]

+1, Non-binding

-vinay

On 14 Nov 2017 21:44, "Charith Elvitigala"  wrote:

+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