Re: [VOTE] Accept XTable into the ASF Incubator
+1 (binding) Regards, Ismaël On Sun, Dec 17, 2023 at 6:03 AM Ayush Saxena wrote: > +1(Binding) > > -Ayush > > > On 17-Dec-2023, at 10:23 AM, Hitesh Shah wrote: > > > > +1 (binding) > > > > — Hitesh > > > >> On Fri, Dec 15, 2023 at 20:17 Jesus Camacho Rodriguez < > jcama...@apache.org> > >> wrote: > >> > >> Hi All, > >> > >> Following the discussion in the incubator mailing list [1], I am > starting > >> this official vote for the XTable project. > >> > >> Here is the proposal - > >> https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal > >> > >> Please cast your vote: > >> > >> [ ] +1, bring XTable into the Incubator > >> [ ] +0, I don't care either way > >> [ ] -1, do not bring XTable into the Incubator, because... > >> > >> This majority vote is open for at least 96 hours (due to the weekend). > >> > >> Only votes from Incubator PMC members are binding, but other votes are > >> welcome! > >> > >> Thanks, > >> Jesús > >> > >> [1] https://lists.apache.org/thread/rx9z8ffrf37qjhpkf1vp5rqg5lhht7jm > >> > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] OneTable proposal
Thanks for the info PJ, done ! On Thu, Dec 7, 2023 at 11:29 PM PJ Fanning wrote: > Hi Ismaël, > Could you make a request to join the Incubator PMC? ASF members will > be accepted into the PMC. It's just that podling mentors need to be > part of the PMC. > Requests are made to the priv...@incubator.apache.org list. > > Regards, > PJ > > On Thu, 7 Dec 2023 at 23:20, Ismaël Mejía wrote: > > > > Hello Jesus, > > > > I am interested on both contributing to this project as a committer, and > as > > an ASF member I want to volunteer to mentor the project during > incubation. > > I am a committer and part of the PMC of both Apache Beam and Apache Avro > so > > I am close to this space so glad to help where I can. > > > > Regards, > > Ismaël > > > > > > On Mon, Dec 4, 2023 at 10:24 PM Jesus Camacho Rodriguez < > jcama...@apache.org> > > wrote: > > > > > Hi All, > > > > > > I would like to propose a new project to the ASF incubator - OneTable. > > > > > > OneTable[1] is an omni-directional converter for table formats that > > > facilitates interoperability across data processing systems and query > > > engines. Currently, OneTable supports widely adopted open-source table > > > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > > > > > Here is the proposal - > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal > > > > > > I would be the Champion of the project. I will mentor and help the > project > > > through the incubator with Hitesh Shah [hit...@apache.org], Stamatis > > > Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré [ > > > jbono...@apache.org]. > > > > > > We are looking forward to your feedback! > > > > > > Thanks, > > > Jesús > > > > > > [1] https://github.com/onetable-io/onetable > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] OneTable proposal
Hello Jesus, I am interested on both contributing to this project as a committer, and as an ASF member I want to volunteer to mentor the project during incubation. I am a committer and part of the PMC of both Apache Beam and Apache Avro so I am close to this space so glad to help where I can. Regards, Ismaël On Mon, Dec 4, 2023 at 10:24 PM Jesus Camacho Rodriguez wrote: > Hi All, > > I would like to propose a new project to the ASF incubator - OneTable. > > OneTable[1] is an omni-directional converter for table formats that > facilitates interoperability across data processing systems and query > engines. Currently, OneTable supports widely adopted open-source table > formats such as Apache Hudi, Apache Iceberg, and Delta Lake. > > Here is the proposal - > https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal > > I would be the Champion of the project. I will mentor and help the project > through the incubator with Hitesh Shah [hit...@apache.org], Stamatis > Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré [ > jbono...@apache.org]. > > We are looking forward to your feedback! > > Thanks, > Jesús > > [1] https://github.com/onetable-io/onetable >
Re: [IP CLEARANCE] Apache Avro - Rust Library donation `avro-rs`
There were no -1 votes, therefore this IP clearance vote passes by lazy consensus. Thank you! On Fri, May 28, 2021 at 11:41 AM Ismaël Mejía wrote: > > Hi Incubator PMC, > > The Apache Avro PMC has voted to accept the donation of "avro-rs", which > is a Rust language implementation of Apache Avro [1]. > > Please vote to accept this contribution. > > This is a lazy consensus majority vote, per the IP clearance process [2], > open for at least 72 hours. > > Thanks, > > Ismaël Mejía > > Apache Avro PMC > > [1] https://incubator.apache.org/ip-clearance/avro-rust-library.html > [2] http://incubator.apache.org/ip-clearance/ > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP CLEARANCE] Apache Avro - Rust Library donation `avro-rs`
Hi Incubator PMC, The Apache Avro PMC has voted to accept the donation of "avro-rs", which is a Rust language implementation of Apache Avro [1]. Please vote to accept this contribution. This is a lazy consensus majority vote, per the IP clearance process [2], open for at least 72 hours. Thanks, Ismaël Mejía Apache Avro PMC [1] https://incubator.apache.org/ip-clearance/avro-rust-library.html [2] http://incubator.apache.org/ip-clearance/
Re: [VOTE] Graduate Apache Airflow to TLP
+1 (non-binding) Great to see this project becoming a TLP ! On Thu, Dec 6, 2018 at 7:35 PM Arthur Wiedmer wrote: > > +1 (non-binding) > > On Wed, Dec 5, 2018, 15:38 Jakob Homan > > Hello- > > > > The Airflow podling community has VOTEd[0] to graduate, following a > > very successful DISCUSS[1]. Accordingly I'm bringing the resolution > > up for an IPMC VOTE. > > > > The podling result was: > > Overall: 21 x +1 votes, 0 x -1 votes > > > > Binding +1 x 11: Kaxil, Tao, Bolke, Fokko, Maxime, Arthur, Hitesh, > > Chris, Sid, Ash, Jakob. > > Non-binding +1 x 10: Daniel, Shah, Stefan, Kevin, Marc, Sunil, > > Adityan, Deng, Neelesh, Sai > > > > Since entering the Incubator in 2016, the Airflow community has: > >* successfully produced 7 releases > >* added 9 new committers/PPMC members > >* built a diverse group of committers from multiple different employers > >* had more than 3,300 JIRA tickets opened > >* completed the project maturity model with positive responses[2] > > > > Here's my binding +1. The VOTE will run for at least 72 hours. > > > > Thanks, > > Jakob > > > > [0] > > https://mail-archives.apache.org/mod_mbox/airflow-dev/201812.mbox/%3c115b1380-619d-41d7-a30e-9c041cd4d...@gmail.com%3E > > [1] > > https://lists.apache.org/thread.html/%3c0a763b0b-7d0d-4353-979a-ac6769eb0...@gmail.com%3E > > [2] > > https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation > > > > > > > > Establish the Apache Airflow 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 workflow automation and scheduling > > that can be used to author and manage data pipelines. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee (PMC), to be known as the "Apache Airflow Project", > > be and hereby is established pursuant to Bylaws of the > > Foundation; and be it further > > > > RESOLVED, that the Apache Airflow Project be and hereby is > > responsible for the creation and maintenance of software > > related to workflow automation and scheduling that can be > > used to author and manage data pipelines; and be it further > > > > RESOLVED, that the office of "Vice President, Apache Airflow" 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 Airflow Project, and to have primary responsibility > > for management of the projects within the scope of > > responsibility of the Apache Airflow 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 Airflow Project: > > > > * Alex Guziel > > * Alex Van Boxel > > * Arthur Wiedmer > > * Ash Berlin-Taylor > > * Bolke de Bruin > > * Chris Riccomini > > * Dan Davydov > > * Fokko Driesprong > > * Hitesh Shah > > * Jakob Homan > > * Jeremiah Lowin > > * Joy Gao > > * Kaxil Naik > > * Maxime Beauchemin > > * Siddharth Anand > > * Sumit Maheshwari > > * Tao Feng > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Bolke de Bruin > > be appointed to the office of Vice President, Apache Airflow, 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 Airflow 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 Airflow Project; and be it further > > > > RESOLVED, that the Apache Airflow Project be and hereby > > is tasked with the migration and rationalization of the Apache > > Incubator Airflow podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator Airflow 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 > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Auto-cleaning up Stale PRs
While I agree that autoclosing PRs can be unwelcoming. I don't see clearly the argument of INFRA in the ticket. > The policy of no-write-access for bots is a requirement by the foundation > legal team. We cannot allow write access to repos without an ICLA. Labeling and closing the PR in github does not imply write-access from the bot into the 'real' gitbox repository, so I don't see how this can be an issue, or are we in a gray area (in case bot automation of metadata can have legal issues which I doubt since this is not part of the source distribution). As a precedent we had Probot/Stale enabled for Apache Beam so I suppose that this should be possible for Airflow too. https://issues.apache.org/jira/browse/INFRA-16589 On Thu, Sep 13, 2018 at 5:55 PM Sid Anand wrote: > > Apache Airflow has, at any point, >200 PRs open. During the slower summer > months, we've been merging 100-200 PRs a month. We have been growing the > community -- we have <600 contributors, ~200 companies using it, and 20+ > committers. A person is promoted to "Committer" in recognition for work > he/she has done without an expectation of future work in maintaining the > code base. Hence, minting new committers doesn't always translate into > greater bench strength where merging PRs is concerned. That said, we are > actively adding new committers. The last 4-5 committers we added have been > super active maintainers, so the coverage on PRs and questions has been > getting better. > > There are many causes of Cold-case PRs: > >1. Submitter is not actively responding > 1. One example is that we requested tests and they were never written > 2. Discussion ensued on the PR and the submitter did not accept the > community's feedback >2. Committers didn't get to it in a timely manner and after a while the >engagement fell > > We are in a better position now to handle (2) -- this was not the case a > year ago. We're at least able to keep up with our in-flow of PRs > week-to-week, but are still having challenges with the > previously-established backlog. But, (1) is also a contributor to stale PRs. > > We do have a lot of stale PRs to manually handle -- I spent all of Summer > 2017 pinging submitters of old PRs and I find myself in the same position > now. > > Probot/stale is a useful tool. It has legitimate use-cases. A policy > reflects the health/mentality/approaches of the community. A tool like this > enforces the policy. Let's not overlook adoption of what would be a very > useful tool to the community due to a meta conversation about policy. I > think everyone on this list cares about growing a healthy and vibrant > community. We also care about being efficient with our spare time. This > tools can help us manage both. > > Also, I am not suggesting that we close JIRA, just stale PRs. JIRAs need to > be kept open so we don't lose visibility of bugs/features/etc... This tool > doesn't handle JIRA closing anyway. > > -s > > On Thu, Sep 13, 2018 at 1:37 AM Mark Thomas wrote: > > > On 12/09/18 19:16, Sid Anand wrote: > > > A stale PR is defined by a policy -- for example, 60 days without any > > > movement on the PR. > > > > Automatically closing such issues is not going to do anything to aid > > community building and is likely to actively damage such efforts. > > > > > Stale PRs would be bad experiences in general for community members, but > > > after no movement for 60 days, this is just about cleaning up PRs that > > are > > > not getting feedback from the committers or PR submitters. > > > > That is the wrong solution the problem. > > > > If reporters of issues are not responding to questions and there is > > genuinely nothing the community can do to progress the issue without > > their input then closing the issue is fair enough. But that should very > > much be the exception rather than the rule. In projects I am involved in > > I probably do that a handful of times a year. However, even in a good > > chunk of those cases, the main reason for the lack of response from the > > OP is that the community did not respond to the original report for an > > excessively long time. > > > > If the committers are not responding to issues in a timely manner then > > the solution is to start looking for more committers. > > > > Reporting an issue is often the first interaction someone new to the > > community has with the project. It should be treated as an opportunity > > to attract new members to the community and to grow the project. > > > > Mark > > > > > > > > > > -s > > > > > > On Wed, Sep 12, 2018 at 10:58 AM Dave Fisher > > wrote: > > > > > >> Hi - > > >> > > >> I was pointing out a potential community problem which is what we are > > >> about here in the Incubator. > > >> > > >> On Sep 12, 2018, at 10:27 AM, Sid Anand wrote: > > >> > > >> A stale PR has not activity for some length of time. > > >> https://github.com/probot/stale > > >> > > >> The policy file example shown on that link it pretty easy to
Re: [VOTE] Livy to enter Apache Incubator
ation = >> >> Documentation can be found on the Livy website http://livy.io/ >> >> The Livy web site is version controlled on the ‘gh-pages’ branch of the >> above repository. >> Additional documentation is provided on the github wiki: >> https://github.com/cloudera/livy/wiki >> APis are documented within the source code as JavaDoc style documentation >> comments. >> >> = Initial Source = >> >> The initial source code for Livy is hosted at >> https://github.com/cloudera/livy >> >> = Source and Intellectual Property submission plan = >> >> The Livy codebase and web site is currently hosted on GitHub and will be >> transitioned to the ASF repositories during incubation. Livy is already >> licensed under the Apache 2.0 license. Cloudera has collected ICLAs and >> CCLAs from all committers. There are, however, some contributions recently >> from authors that have not signed the CCLA and ICLA. If necessary for a >> successful SGA, we’ll seek the necessary documentation or replace the >> contributions. >> >> The “Livy” name is not a registered trademark. We will need to do a >> trademark search and make sure it is available for the Apache Foundation >> prior to graduation. >> >> Cloudera currently owns the domain name: http://livy.io/. Once all the >> documentation has moved over to ASF infrastructure, the main landing page >> will become livy.incubator.apache.org and the old domain will just act as >> a >> redirect. >> >> = External Dependencies = >> >> The list below covers the non-Apache dependencies of the project and their >> licenses. >> >> * Jetty: Apache 2.0 >> * Dropwizard Metrics: Apache 2.0 >> * FasterXML Jackson: Apache 2.0 >> * Netty: Apache 2.0 >> * Scala: BSD >> * Py4J: BSD >> * Scalatra: BSD >> >> Build/test-only dependencies: >> >> * Mockito: MIT >> * JUnit: Eclipse >> >> = Required Resources = >> >> == Mailing Lists == >> >> * priv...@livy.incubator.apache.org (PPMC) >> * d...@livy.incubator.apache.org (dev mailing list) >> * u...@livy.incubator.apache.org (User questions) >> * comm...@livy.incubator.apache.org (subscribers shouldn’t be able to >> post) >> * iss...@livy.incubator.apache.org (subscribers shouldn’t be able to >> post) >> >> == Git Repository == >> >> git://git.apache.org/incubator-livy >> >> == Issue Tracking == >> >> We would like to import our current JIRA project into the ASF JIRA, such >> that our historical commit message and code comments continue to reference >> the appropriate bug numbers. >> >> = Initial Committers = >> >> * Marcelo Vanzin (van...@cloudera.com) >> * Alex Man (alex@alexman.space) >> * Jeff Zhang (zjf...@gmail.com) >> * Saisai Shao (ss...@hortonworks.com) >> * Kostas Sakellis (kos...@cloudera.com) >> >> = Affiliations = >> >> The initial set of committers includes people employed by Cloudera and >> Hortonworks as well as one currently independent contributor. >> >> = Additional Interested Contributors = >> >> Those interested in getting involved with the project as we enter >> incubation >> are encouraged to list themselves here. >> >> * Ismaël Mejía (ieme...@apache.org) >> >> = Sponsors = >> >> == Champion == >> >> Sean Busbey (bus...@apache.org) >> >> == Nominated Mentors == >> >> * Bikas Saha (bi...@apache.org) >> * Brock Noland (br...@phdata.io) >> * Luciano Resende (lrese...@apache.org) >> >> == Sponsoring Entity == >> >> We ask that the Incubator PMC sponsor this proposal. >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
