[NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] Hello Apache projects, I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on github as well as the standard ASF commit access via gitbox.apache.org. ## Why this move? ## The move comes as a result of retiring the git-wip service, as the hardware it runs on is longing for retirement. In lieu of this, we have decided to consolidate the two services (git-wip and gitbox), to ease the management of our repository systems and future-proof the underlying hardware. The move is fully automated, and ideally, nothing will change in your workflow other than added features and access to GitHub. ## Timeframe for relocation ## Initially, we are asking that projects voluntarily request to move their repositories to gitbox, hence this email. The voluntary timeframe is between now and January 9th 2019, during which projects are free to either move over to gitbox or stay put on git-wip. After this phase, we will be requiring the remaining projects to move within one month, after which we will move the remaining projects over. To have your project moved in this initial phase, you will need: - Consensus in the project (documented via the mailing list) - File a JIRA ticket with INFRA to voluntarily move your project repos over to gitbox (as stated, this is highly automated and will take between a minute and an hour, depending on the size and number of your repositories) To sum up the preliminary timeline; - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) relocation - January 9th -> February 6th: Mandated (coordinated) relocation - February 7th: All remaining repositories are mass migrated. This timeline may change to accommodate various scenarios. ## Using GitHub with ASF repositories ## When your project has moved, you are free to use either the ASF repository system (gitbox.apache.org) OR GitHub for your development and code pushes. To be able to use GitHub, please follow the primer at: https://reference.apache.org/committer/github We appreciate your understanding of this issue, and hope that your project can coordinate voluntarily moving your repositories in a timely manner. All settings, such as commit mail targets, issue linking, PR notification schemes etc will automatically be migrated to gitbox as well. With regards, Daniel on behalf of ASF Infra. PS:For inquiries, please reply to us...@infra.apache.org, not your project's dev list :-). - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IPMC Board report - missing podling reports for DLab, Marvin-AI and Pinot
Hi Justin, DLab prepared a report and posted it to the dev@ list, but unfortunately we mentors failed to get it posted to the wiki. I’ve since posted it. I’ll work with the podling to get them access to the wiki. -Taylor > On Dec 6, 2018, at 5:29 PM, Justin Mclean wrote: > > Hi, > > 3 podlings have failed to report on time and will be asked to report next > month. They are Dlab, Marvin-AI and Pinot. > > If the mentors of these projects would be so kind to make the following > happen it would be appreciated: > a) That the PPMC is encouraged to discuss the report (preferable on-list) > ahead of the deadline. > b) That all the PPMC members are signed up to the dev and private lists and > so see the report reminders or email about late reports. > c) That the PPMC is aware that it is their responsibility to create and > submit the report. > d) Someone responds to the report reminders so it's known it’s been worked on. > e) That the next report now due in a month is submitted before the deadline. > > A good indication of mentor inactivity is not submitting reports in on time, > and while missing one is not a big deal but if several in a row are missed it > a good indication that the podling probably needs new mentors. Podlings if > you mentors are not helping you (and I’ve not looked to see if they are) > please bring this up on the the general@ incubator list and we’ll try to help. > > Thanks, > Justin > - > To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org > For additional commands, e-mail: dev-h...@dlab.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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: IPMC Board report - missing podling reports for DLab, Marvin-AI and Pinot
Hi, > DLab prepared a report and posted it to the dev@ list, but unfortunately we > mentors failed to get it posted to the wiki. Do you know why this is the case? Reminder were sent to the dev list and this list. Are the mentors signed up to the dev list or this list? Are the mentors active? Does the project need new mentors? > I’ve since posted it. I’ll work with the podling to get them access to the > wiki. Thanks for that. However I had already reflowed the report (lines need to be a maximum of 76 character and no double blank lines) and now will need to do so again. late reports cause extra work. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IPMC Board report - missing podling reports for DLab, Marvin-AI and Pinot
Sent from my iPhone > On Dec 7, 2018, at 12:15 PM, Justin Mclean wrote: > > Hi, > >> DLab prepared a report and posted it to the dev@ list, but unfortunately we >> mentors failed to get it posted to the wiki. > > Do you know why this is the case? Reminder were sent to the dev list and this > list. Are the mentors signed up to the dev list or this list? Are the mentors > active? Does the project need new mentors? > >> I’ve since posted it. I’ll work with the podling to get them access to the >> wiki. > > Thanks for that. However I had already reflowed the report (lines need to be > a maximum of 76 character and no double blank lines) and now will need to do > so again. late reports cause extra work. Since Mentor signoff is due next Tuesday then you may need to reflow at that time. Regards, Dave > > 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
Re: IPMC Board report - missing podling reports for DLab, Marvin-AI and Pinot
> On Dec 7, 2018, at 3:15 PM, Justin Mclean wrote: > > Do you know why this is the case? I forgot, and until today didn’t have access to the machine with all my Apache credentials. > Reminder were sent to the dev list and this list. Are the mentors signed up > to the dev list or this list? Are the mentors active? Does the project need > new mentors? 2/3 mentors are active. 3/3 are signed up for both lists. I don’t feel the project needs additional mentors, but am open to adding a mentor if there’s interest. My apologies for the inconvenience. -Taylor
Re: IPMC Board report - missing podling reports for DLab, Marvin-AI and Pinot
Hi, >> Reminder were sent to the dev list and this list. Are the mentors signed up >> to the dev list or this list? Are the mentors active? Does the project need >> new mentors? > > 2/3 mentors are active. 3/3 are signed up for both lists. I don’t feel the > project needs additional mentors, but am open to adding a mentor if there’s > interest. Thanks for checking that all sounds fine to me and nothing more needs to be done. Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Airflow to TLP
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] Apache Gobblin 0.14.0 release RC0
Hi, +1 (binding) I checked: - incubating in name - signatures and hashes good - DISCLAIMER exists - LICENSE and NOTICE correct - As source files have ASF headers - No unexpected binary files - Can compile from source Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Airflow to TLP
Hi +1 Regards Liang -- Sent from: http://apache-incubator-general.996316.n3.nabble.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator exit interview
Hi, I was just wondering if it would be a good idea to ask projects a few questions of committers/PPMC members once they leave the incubator to gauge how we are doing and find out where there is room for improvement? It would be simple to try as a proof of concept on a couple of graduating projects to see to we get any valuable feedback that we don’t normally get on this list or in the podling reports. Some suggested questions off the top of my head: Thinking about the project that you have just graduated as part of: - I am a X committer X PMC member X mentor X none of those X rather not say - How many times have you gone through the incubation process: X one X two X three X more than three - Have you felt supported by the incubator? If not what could be improved? - Have you felt supported by the your mentors? If not what could be improved? - Did you run into any issues with any part of the incubating process? If so what? - Was is clear what you needed to do to graduate? - What, if anything, could be done to make the graduation process smoother? - Is the time taken to graduate X too short? X just right? X too long? - Do you have a good understanding of the Apache Way? If not what areas are you unclear on? - Anything else you want to add or comment on? Probably best if answers were anonymous. Anyone have any ideas for other questions or improvement to the above? I’d like to keep it under a dozen questions. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Airflow to TLP
+1 (non-binding) Regards Brahma Reddy On Sat, Dec 8, 2018 at 10:58 AM, Liang Chen wrote: > Hi > > +1 > > Regards > Liang > > > > -- > Sent from: http://apache-incubator-general.996316.n3.nabble.com/ > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- --Brahma Reddy Battula
Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC4]
Hi, +1 (binding) but there's a number of things to fix for the next release. I checked: - incubating in name - DISCLAIMER exists - LICENSE and notice need more work (see below) - All ASF source files have ASF like headers (but not quite the correct text - see below) - No unexpected binary files LICENSE needs to list any licenses of bundled software it includes, currently it lists none. NOTICE should not list license information and is only reserved for certain things.(e.g relocated copyrights, content from other ASF notices files). Please speak to your mentors on how to assemble these files, [1] if it wasn’t your first release I would probably vote -1 on this. I would expect LICENSE to mention: - jquery-1.11.0.min.js - jquery-ui-1.9.2.js - underscore-1.2.2.js - jquery.dataTables-1.8.2.js - these 3 files [4][5][6] - these 2 files [7][8] - this file [9] I also a little concerned by this file [2] as it mentions thing that should not be in a source releases. (i.e. CDDL and EPL licensed things). Should this file [3] have an ASF header given it looks like public domain? either way it also should be in LICENSE. With headers I can see 4000+ instances of this: “The ASF licenses this file to you under the Apache License, Version 2.0 (the License”);" And 80 odd of: "The ASF licenses this file to You under the Apache License, Version 2.0 the “License”);” Neither of which isn’t quite right, ie You vs you and the missing bracket and missing quote. Probably a search replace went off-piste? The correct header has: "The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); “ I also note that a “mvn -DskipTests=true compile” will fail, but I was able to compile. Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html 2. apache-druid-0.13.0-incubating-src/examples/quickstart/tutorial/hadoop/docker/LICENSE 3. apache-druid-0.13.0-incubating-src/processing/src/main/java/org/apache/druid/query/groupby/epinephelinae/Groupers.java 4. apache-druid-0.13.0-incubating-src/extendedset/src/main/java/org/apache/druid/extendedset/intset/AbstractIntSet.java 5. apache-druid-0.13.0-incubating-src/extendedset/src/main/java/org/apache/druid/extendedset/intset/ConciseSet.java 6. apache-druid-0.13.0-incubating-src/extendedset/src/main/java/org/apache/druid/extendedset/intset/IntSet.java 7. apache-druid-0.13.0-incubating-src/extendedset/src/main/java/org/apache/druid/extendedset/intset/ConciseSetUtils.java 8. apache-druid-0.13.0-incubating-src/extendedset/src/main/java/org/apache/druid/extendedset/utilities/IntList.java 9. apache-druid-0.13.0-incubating-src/server/src/main/resources/static/old-console/css/demo_table.css - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Gobblin 0.14.0 release RC0
+1 (binding) I checked: - LICENSE, NOTICE, DISCLAIMER are there - ASF headers - build Thanks, Regards JB On 05/12/2018 00:12, Abhishek Tiwari wrote: > The Apache Gobblin community has voted on and approved the release of > Apache Gobblin 0.14.0 (incubating): > https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02386.html > > Results: > 3 binding +1 votes > No 0 votes > No -1 votes > > I'd like to call a vote in general to approve the release. > > The source release candidate RC0 can be downloaded here: > https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin-incubating-0.14.0-rc0/ > > > The artifacts (i.e. JARs) corresponding to this release candidate can be > found here: > https://repository.apache.org/content/repositories/orgapachegobblin-1008/ > > This has been signed with PGP key 234E3FE3, corresponding to > a...@apache.org, which is included in the repository's KEYS file. This > key can be found on keyservers, such as: > http://pgp.mit.edu/pks/lookup?op=get&search=0x234E3FE3 > > It is also listed here: > https://people.apache.org/keys/committer/abti.asc > > The release candidate has been tagged with release-0.14.0-rc0 > I've also created a branch 0.14.0 > > For reference, here is a list of all closed JIRAs tagged with 0.14.0: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GOBBLIN%20AND%20fixVersion%20%3D%200.14.0%20AND%20status%20in%20(Closed%2C%20Resolved)%20ORDER%20BY%20updatedDate%20DESC%2C%20createdDate%20DESC%2C%20status%20DESC%2C%20priority%20DESC > > > For a summary of the changes in this release, please see: > https://github.com/apache/incubator-gobblin/blob/0.14.0/CHANGELOG.md > > Please review and vote. The vote will be open for atleast 72 hours (ends on > Friday, December 7, 2018 at 3:30 pm PT). > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks, > Abhishek, on behalf of the Apache Gobblin (incubating) PPMC > -- 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