Re: Incubator PMC members not subscribed to private list
Hi, I can see a couple of people have signed up and a couple of inactive IPMC members have asked to be removed. However we still have a large number of IPMC members are still not subscribed to the private list. A possible idea. Do we want to consider the drastic step of removing all IPMC from the PMC who are not signed up to the private mailing list? They could re-instated themselves by subscribing to the private list. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Podling reporting timeline for February
Hi, Also last month we had a number of podlings who used their own formatting and didn’t stick to the required formatting. Whimsy and other tool expect the report to formatted in a certain way so please make sure that you try to: • Keep all lines under 76 characters long. • All content under the ### headings should be indented by two spaces. Do not use tabs. • Please don't change the text in the headings or add new ones. • Include a space after a bullet point or full stop on a numbered list. • Use [X] (X and no spaces) to sign off reports. (as is mentioned at the top of teh page) For long URLs it’s best to the us ether URL shortener https://s.apache.org. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Podling reporting timeline for February
Hi - > On Jan 15, 2020, at 5:45 PM, Justin Mclean wrote: > > HI, > >> I would recommend breaking up the pages so that every project edits its own >> page >> and doesn't risk modifying or (deleting! ) any of the other projects! > > Most project do edit or collate their reports on their own wiki page or on > their mailing list and then transfer the final report to that page. Having > each podling report on a seperate page would be more work for the IPMC, but > there might be a way to automate it. It’s all revisioned so it's easy enough > to revert a mistake. > > BTW the report should cover the full month of January. Also, the report should be discussed within the podling on either the dev@ or private@ mailing lists. Your Mentors (like me) might have guidance. No one person on the PPMC is in charge. We don’t want Benevolent Dictators so let’s avoid behaviors that could be viewed that way. 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: [MENTORS] Podling reporting timeline for February
HI, > I would recommend breaking up the pages so that every project edits its own > page > and doesn't risk modifying or (deleting! ) any of the other projects! Most project do edit or collate their reports on their own wiki page or on their mailing list and then transfer the final report to that page. Having each podling report on a seperate page would be more work for the IPMC, but there might be a way to automate it. It’s all revisioned so it's easy enough to revert a mistake. BTW the report should cover the full month of January. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Podling reporting timeline for February
Hi, > I am having difficulty editing the document. When I open the editor I only > see the first 200 lines. I’m not 100% sure what you mean by that and it looks OK to me. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Podling reporting timeline for February
Fixed, I had to revert. Nonetheless, my gentle feedback is that this way of creating your report is quite fragile and risky. I accidentally almost deleted most of the report (of all the projects) due to mistyping a few keystrokes!! I would recommend breaking up the pages so that every project edits its own page and doesn't risk modifying or (deleting! ) any of the other projects! Cheers, Lee. On Wed, Jan 15, 2020 at 5:17 PM leerho wrote: > Justin, > I am having difficulty editing the document. When I open the editor I > only see the first 200 lines. > > Lee. > > On Wed, Jan 15, 2020 at 4:23 PM Justin Mclean > wrote: > >> Hi, >> >> Draft report can be found: >> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020 >> >> Dates Due: >> Wed February 05 - Podling reports due by end of day >> Sun February 09 - Shepherd reviews due by end of day >> Sun February 09 - Summary due by end of day >> Tue February 11 - Mentor signoff due by end of day >> Wed February 12 - Report submitted to Board >> Wed February 19 - Board meeting >> >> Podlings expected to report: >> Annotator* >> DataSketches >> DolphinScheduler >> Doris >> ECharts >> Heron >> Milagro* >> Myriad* >> NuttX >> PageSpeed >> Pinot >> Ratis >> S2Graph >> SDAP >> StreamPipes >> Tamaya >> Taverna* >> Toree >> Training >> TubeMQ >> Tuweni >> >> It’s likely that YuniKorn will be added to that list. >> >> Thanks, >> Justin >> >> * Did not report last month so need to report this month >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: Font size on incubator site too small?
Done - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Podling reporting timeline for February
Justin, I am having difficulty editing the document. When I open the editor I only see the first 200 lines. Lee. On Wed, Jan 15, 2020 at 4:23 PM Justin Mclean wrote: > Hi, > > Draft report can be found: > https://cwiki.apache.org/confluence/display/INCUBATOR/February2020 > > Dates Due: > Wed February 05 - Podling reports due by end of day > Sun February 09 - Shepherd reviews due by end of day > Sun February 09 - Summary due by end of day > Tue February 11 - Mentor signoff due by end of day > Wed February 12 - Report submitted to Board > Wed February 19 - Board meeting > > Podlings expected to report: > Annotator* > DataSketches > DolphinScheduler > Doris > ECharts > Heron > Milagro* > Myriad* > NuttX > PageSpeed > Pinot > Ratis > S2Graph > SDAP > StreamPipes > Tamaya > Taverna* > Toree > Training > TubeMQ > Tuweni > > It’s likely that YuniKorn will be added to that list. > > Thanks, > Justin > > * Did not report last month so need to report this month > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[MENTORS] Podling reporting timeline for February
Hi, Draft report can be found: https://cwiki.apache.org/confluence/display/INCUBATOR/February2020 Dates Due: Wed February 05 - Podling reports due by end of day Sun February 09 - Shepherd reviews due by end of day Sun February 09 - Summary due by end of day Tue February 11 - Mentor signoff due by end of day Wed February 12 - Report submitted to Board Wed February 19 - Board meeting Podlings expected to report: Annotator* DataSketches DolphinScheduler Doris ECharts Heron Milagro* Myriad* NuttX PageSpeed Pinot Ratis S2Graph SDAP StreamPipes Tamaya Taverna* Toree Training TubeMQ Tuweni It’s likely that YuniKorn will be added to that list. Thanks, Justin * Did not report last month so need to report this month - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: New Proposal Help
On 2020/01/11 17:19:26, Dave Meikle wrote: > Hi Eya, > > A good way if you don't have someone you know in the ASF to ask to be your > champion is to draft a high level project proposal / share details about > the project(s) you are proposing to incubate [1]. > > Often there are potential mentors or champions who have a natural synergy > with your project who volunteer when they know more. > > Is there a quick summary you can share with us? > > Thanks, > Dave > > [1] > http://mail-archives.apache.org/mod_mbox/incubator-general/201806.mbox/%3CD7402AF3.6893%25lide%40baidu.com%3E > > On Fri, 10 Jan 2020 at 22:49, Eya Badal Abdisho > wrote: > > > Hello there, > > > > This is Eya Badal, I would appreciate your time if you can guide me on some > > steps. I am trying to create a proposal and I found out that I need to have > > a champion and two mentors. I was wondering how should I find those people > > and ask them to my mentors and champion? > > > > I tried to send a thread in general@incubator to seek some information but > > I had no luck so I would greatly appreciate it if you can help me. > > > > In addition, I created an account on cwiki and I want to request to > > edit/write permission to create m proposal over there. > > > > I would appreciate any help on this matter. > > > > I look forward to hearing from you soon. > > > > Best Regards, > > > > -- > > > > Bitnine Global, Inc. - We create value for our clients by connecting the > > world's data. > > > > > > *Eya Badal Abdisho* > > > > Technical Engineer > > > > E-mail : eya.abdi...@bitnine.net > > > > Mobile : +1 408-966-3301 > > > > 3945 Freedom Cir., Suite 260, > > Santa Clara, CA 95054 > > > > www.bitnine.net > > > Hello Dave, Thank you so much for your reply. I really appreciate your time. As you recommended we are drafting a high-level project proposal to share here. Meantime as you requested please following find a quick summary of the AgensGraph Extension project: """We propose the AgensGraph Extension to the Apache foundation. AgensGraph Extension is to provide an extension for PostgreSQL to give the users the ability to leverage graph database on top of the existing relational database with minimal effort. The basic principle of the project is to create single storage that can handle both relational and graph model data so that the users can use the standard ANSI SQL along with openCypher (http://www.opencypher.org), the Graph query language. """ Please let me know if you have any questions or need additional information. I look forward to hearing more recommendations from you. Best regards, Eya - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Superset (Incubating) version 0.35.2 Released
Hello Community, The Apache Superset (incubating) team is pleased to announce that Superset 0.35.2 has just been released. Apache Superset (incubating) is a modern, enterprise-ready business intelligence web application The official source release: https://www.apache.org/dist/incubator/superset/0.35.2 The Pypi package: https://pypi.org/project/apache-superset/ If you have any usage questions, or have problems when upgrading or find any problems about enhancements included in this release, please don't hesitate to let us know by sending feedback to d...@superset.apache.org . = *Disclaimer* Apache Superset is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Release Apache Superset (incubating) version 0.35.2
Thanks to everyone that participated. The vote to release Apache Superset (incubating) version 0.35.2 is now closed. The vote PASSED with 3 binding +1, 0 non binding +1 and 0 -1 votes: Binding votes: - Alan - Paul - Justin We will work to complete the release process. Thanks, The Apache Superset (Incubating) Team On Thu, Jan 9, 2020 at 9:14 PM Ville Brofeldt wrote: > Hello IPMC, > > > The Apache Superset (incubating) community has voted on and approved a > proposal to > > release Apache Superset (incubating) version 0.35.2. > > The voting thread can be found here: > https://lists.apache.org/thread.html/rf8b1cbe6c880d408583448e5a96e08b90da1258c7cdaf4658836%40%3Cdev.superset.apache.org%3E > > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > Apache Superset (incubating) is a modern, enterprise-ready business > intelligence web application. > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.2rc2/ > > > Git tag for the release: > > https://github.com/apache/incubator-superset/tree/0.35.2rc2 > > > The Change Log for the release: > > https://github.com/apache/incubator-superset/blob/0.35.2rc2/CHANGELOG.md > > > public keys are available at: > > > https://www.apache.org/dist/incubator/superset/KEYS > > > The vote will be open for at least 72 hours or until the necessary number > > of votes are reached. > > > Please vote accordingly: > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > Thanks, > > The Apache Superset (Incubating) Team >
Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1
Hi, > Most of the author tags are leftover from the initial software grant from > CertiVox and have no IP consequences. All good changing my vote to +1 (binding). For future releases I’d leave the ones that where in there before the donation and just remove the ones added since. > Please can you provide details of your environment I’m on macOS Majave, I have both python 2.7 and python 3 installed. It was the only test that failed. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1
Hi Justin, Many thanks for testing our release out and for your feedback. Comments inline below. Would the fixes proposed below for a subsequent release be sufficient for you to change your vote or should we implement them now and revote? Regards. John > -Original Message- > From: Justin Mclean > Sent: 15 January 2020 02:04 > To: general@incubator.apache.org > Subject: Re: [VOTE] Release Apache Milagro (incubating) Crypto-C V2.0.1 > > Hi, > > Currently I’m -1 on this release due to the author tags, which may imply it > contains 3rd party code, whose licenses not listed in LICENSE. There's > probably an explanation for why they are there and if given I’ll change my > vote. Most of the author tags are leftover from the initial software grant from CertiVox and have no IP consequences. However, we'll remove ALL author tags in the next release. > > I checked: > - incubating in name > - signatures and disclaimer exist > - LICENSE is incorrect as it contains "Copyright 2019 The Apache Software > Foundation” in the appendix. We'll fix in the next release. > - NOTICE has incorrect year Also to be fixed in the next release. > - A couple of files are missing ASF headers [1][2][3][4] (assuming they are > files > created at the ASF) Also to be fixed in the next release. > - can compile from source > > The code contains a large number of author tags, author tags are usually > frowned on at the ASF. Some are from current committers and others are > not. What this in the original code when donated or have they been added > later? Is any of this code 3rd party code with an incorrect ASF header? > > I also had one test fail test_python_mpin_install_BLS381 Please can you provide details of your environment - particularly the OS/version and also what version of Python you're running? We thought this might be due to Python 2.7 (the README incorrectly states that 2.7 is supported - also to be resolved in the next release), however I can't replicate the issue using Python 2.7 on Ubuntu 18, so it may be some other issue. > > Thanks, > Justin > > 1. incubator-milagro-crypto-c- > 2.0.1/cmake/determine_word_size/check_16.c > 2. incubator-milagro-crypto-c- > 2.0.1/cmake/determine_word_size/check_32.c > 3. incubator-milagro-crypto-c- > 2.0.1/cmake/determine_word_size/check_64.c\ > 4. incubator-milagro-crypto-c-2.0.1/scripts/buildMulti.sh > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org smime.p7s Description: S/MIME cryptographic signature
[VOTE] Release Apache Livy 0.7.0 (incubating) based on RC4
The Livy PPMC has voted to release Livy 0.7.0 RC4 as the next Livy release. Livy enables programmatic, fault-tolerant, multi-tenant submission of Spark jobs from web/mobile apps (no Spark client needed). So, multiple users can interact with your Spark cluster concurrently and reliably. Vote thread: https://lists.apache.org/thread.html/r171f4a079f2c27c9039aaee1083ab6adb3ba516234a69bfb2d9c60fd%40%3Cdev.livy.apache.org%3E Result thread: https://lists.apache.org/thread.html/rc5524835a62dec8b94b2a827dcb32ba8bdfa5a8576bd438d1835026e%40%3Cdev.livy.apache.org%3E The RC is based on tag v0.7.0-incubating-rc4: https://github.com/apache/incubator-livy/commit/664503355d8bae763989ebac087122e306239d54 The release files can be found here: https://dist.apache.org/repos/dist/dev/incubator/livy/0.7.0-incubating-rc4/ The staged maven artifacts can be found here: https://repository.apache.org/content/repositories/orgapachelivy-1013 The list of resolved JIRAs in this release can be found here: https://issues.apache.org/jira/projects/LIVY/versions/12345179 Please help to vote. Thanks!
