Re: Impala commit policy

“No explicit commit policy” means that only committers can commit. It is each committer’s discretion whether they ask for others to review the change before they commit it, whether they check in code that doesn’t build, whether they run the test suite before committing. This policy is the bare

Re: Impala commit policy

at 6:42 PM, Roman Shaposhnik wrote: > > On Wed, Dec 2, 2015 at 4:24 PM, Julian Hyde wrote: >> “No explicit commit policy” means that only committers can commit. >> It is each committer’s discretion whether they ask for others to review >> the change before they commit it,

Re: [VOTE] Accept Metron into Apache Incubator

+1 (binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

December reports - Eagle and Concerted are running late

I am the mentor of two new projects - Eagle and Concerted. It seems that neither has filed a report yet. Concerted received a reminder and has a template report generated in https://wiki.apache.org/incubator/December2015 ; Eagle did not receive a

Re: December reports - Eagle and Concerted are running late

On Fri, Dec 4, 2015 at 3:18 PM, Henry Saputra wrote: > I am seeing Eagle is in group 2: http://incubator.apache.org/report-groups.txt And I see that it was you who put it in group 2, in r1711145 to podlings.xml. :) But think they should be monthly at this point. December will be their first repo

Re: apache-website-template git commit: Add LICENSE and NOTICE files

I’ve been making some changes to the template and submitting them as github pull requests. (I made 5 pull requests a couple of weeks ago, which weren’t noticed, and Luciano subsequently made very some similar changes. Frustrating.) I don’t want to clutter this list with dev traffic, but there’s

Re: apache-website-template git commit: Add LICENSE and NOTICE files

sues. > > Thanks. > > On Friday, December 4, 2015, Julian Hyde wrote: > >> I’ve been making some changes to the template and submitting them as >> github pull requests. (I made 5 pull requests a couple of weeks ago, which >> weren’t noticed, and Luciano subsequent

Re: December reports - Eagle and Concerted are running late

gt; Thanks Julian for catching the error. > > - Henry > > On Fri, Dec 4, 2015 at 3:45 PM, Julian Hyde wrote: >> On Fri, Dec 4, 2015 at 3:18 PM, Henry Saputra >> wrote: >>> I am seeing Eagle is in group 2: >>> http://incubator.apache.org/report-groups

Re: DRAFT report December 2015 -- please review

Marvin, Thanks for this. I don’t recall whether your preview “DRAFT report … please review” messages have contained detailed commentary. As someone who writes reports and also signs off podlings’ reports in the mentor role, it is very helpful to hear what you consider to be useful content. Jul

Re: interested in joining the IPMC

After Marvin's message I was curious enough to look up the policy. It is documented, and it is indeed as Marvin says: http://incubator.apache.org/guides/participation.html#pmcer I would encourage people to post links when responding to policy questions. It is not necessary, but it helps counter t

Re: [VOTE] Apache Slider (incubating) release 0.90.2-incubating

> On Jan 6, 2016, at 7:16 AM, Steve Loughran wrote: > >> On 5 Jan 2016, at 11:55, Daniel Gruno wrote: >> >> See http://compliance.rocks/result.html?1152a2a9 for a list of minor >> nits (missing some license headers in a bunch of python scripts). >> > nice script +1 > I think some other proj

Re: Concerted may be in need of help

(Removing dev@concerted from the To: list.) Good grief. No one is suggesting there should be "steady activity requirement". I and other Concerted mentors just have a hunch that the project isn't doing well, and thought it would be better to bring our concerns to this list earlier rather than later

Re: [VOTE] Accept the iota project into the Apache Incubator

+1 (binding) Julian > On Jan 19, 2016, at 10:43 PM, Jean-Baptiste Onofré wrote: > > +1 (binding) > > Regards > JB > > On 01/19/2016 01:25 PM, Hadrian Zbarcea wrote: >> I want to encourage more IPMC members to cast a vote, in case this >> thread went unnoticed. >> >> Cheers, >> Hadrian >> >>

Re: [VOTE] Accept Beam into the Apache Incubator

+1 (binding) > On Jan 28, 2016, at 10:42 AM, Mayank Bansal wrote: > > +1 (non-binding) > > Thanks, > Mayank > > On Thu, Jan 28, 2016 at 10:23 AM, Seetharam Venkatesh < > venkat...@innerzeal.com> wrote: > >> +1 (binding). >> >> Thanks! >> >> On Thu, Jan 28, 2016 at 10:19 AM Ted Dunning >> w

Re: Confusion over NOTICE vs LICENSE files

I can see how a TLP would not be receptive to someone nit-picking their LICENSE/NOTICE files. Asking for patches, as Marvin suggests, is one approach that might work. Another approach is for someone with expertise in licensing to approach a TLP and offer to take them through a licensing review.

Re: [VOTE] Accept Science Data Analytics Platform (SDAP) into Apache Incubator WAS Re: [DISCUSS] Accept Science Data Analytics Platform (SDAP) into Apache Incubator

+1 good luck > On Oct 17, 2017, at 2:14 PM, Tom Barber wrote: > > +1 > > Happy to help out if the vote passes. > > On Tue, Oct 17, 2017 at 10:07 PM, Madhawa Kasun Gunasekara < > madhaw...@gmail.com> wrote: > >> Here is my +1 >> >> Thanks, >> Madhawa >> >> Madhawa >> >> On Tue, Oct 17, 201

Re: Crail project looking for mentors

If you’re still looking for mentors, I volunteer. Julian > On Oct 18, 2017, at 8:38 PM, patrick stuedi wrote: > > Hi Von Gosling, > > That's great, we will be more than happy to learn from your > experience. Great work with RocketMQ btw.. > > -Patrick > > On Thu, Oct 19, 2017 at 3:58 AM, Von

Re: [VOTE] Accept Crail into the Apache Incubator

+1 binding Julian On Thu, Oct 26, 2017 at 10:30 AM, Kacie Karo wrote: > One > > kacie karo > >> On Oct 26, 2560 BE, at 11:25 AM, Clebert Suconic >> wrote: >> >> apache > > - > To unsubscribe, e-mail: general-unsubscr...@incub

Re: Crail project looking for mentors

ome aboard! Let me add you to our slack channel as > well (crail.slack.com). > > -Patrick > > On Tue, Oct 24, 2017 at 7:31 AM, Raphael Bircher > wrote: >> Hi Julian >> >> Thanks a load... you save the day! >> >> Regards Raphael >> >>

Re: Crail project looking for mentors

move on now and >> start preparing the mailing lists etc.. >> >> -Patrick >> >> >> On Mon, Nov 27, 2017 at 8:45 PM, Julian Hyde wrote: >>> The vote to accept Crail into the incubator passed almost a month ago >> [1], and I am one of the mentors. I

Re: Crail project looking for mentors

Great. Please reply to this message when you have a name. I need someone to nag. :) > On Nov 28, 2017, at 10:15 AM, Luciano Resende wrote: > > On Tue, Nov 28, 2017 at 8:07 PM, Julian Hyde <mailto:jh...@apache.org>> wrote: > >> OK, good to hear. >> >>

Incubator status report - Crail

Crail is a new podling, and I am one of its mentors. It was not listed in the template for this month’s report[1] (we are looking into why) so we wrote it in. There is no shepherd assigned. Julian [1] https://wiki.apache.org/incubator/December2017

Giving karma

As a mentor of the Crail podling (and an ASF member) I want to give one of the PPMC permission to edit their status file, http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/crail.xml . How d

Re: Giving karma

7; group can edit the SVN files. > > On Thu, Dec 14, 2017 at 1:43 PM Julian Hyde wrote: > >> As a mentor of the Crail podling (and an ASF member) I want to give one of >> the PPMC permission to edit their status file, >> http://svn.apache.org/repos/asf/incubator/

Re: [DRAFT] Incubator PMC Board Report - January 2018

ts: >> [ ](annotator) Jim Jagielski >> Comments: >> >> IPMC/Shepherd notes: >> >> >> >> >> BatchEE >> >> BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a >> set of useful exten

Re: question about including website source in release

I agree that standard practice is to not include the site. However, in Calcite we do include the web site (or rather, the markdown files from which the site is generated) since the web site is also our documentation. So, your choice. Our site includes Jekyll template code under MIT license and s

Re: [DISCUSS] Druid incubation proposal

t; Druid who have expressed interest in being involved in Apache incubation. > Affiliations are listed where relevant. We may seek to add other committers > during incubation; for example, we would want to add any current Druid > committers who express an interest after incubation begins. > > * Charles Allen (char...@allen-net.com) (Snap) > * David Lim (david.clarence@gmail.com) (Imply) > * Eric Tschetter (ched...@apache.org) (Splunk) > * Fangjin Yang (f...@imply.io) (Imply) > * Gian Merlino (g...@apache.org) (Imply) > * Himanshu Gupta (g.himan...@gmail.com) (Oath) > * Jihoon Son (jihoon...@apache.org) (Imply) > * Jonathan Wei (jon@imply.io) (Imply) > * Maxime Beauchemin (maximebeauche...@gmail.com) (Lyft) > * Mohamed Slim Bouguerra (slim.bougue...@gmail.com) (Hortonworks) > * Nishant Bangarwa (nish...@apache.org) (Hortonworks) > * Parag Jain (paragjai...@gmail.com) (Oath) > * Roman Leventov (leventov...@gmail.com) (Metamarkets) > * Xavier Léauté (xav...@leaute.com) (Confluent) > > == Sponsors == > > * Champion: Julian Hyde > * Nominated mentors: Julian Hyde, P. Taylor Goetz, Jun Rao > * Sponsoring entity: Apache Incubator

Re: [DISCUSS] Druid incubation proposal

th Druid currently all have one of the >> following Category A or B licenses: ASL, BSD, CDDL, EPL, MIT, MPL; with one >> exception: the optional Druid MySQL metadata store extension depends on >> MySQL Connector/J, which is GPL licensed. Druid currently packages this as >> a

[VOTE] Accept Druid into the Apache Incubator

(Imply) * Jonathan Wei (jon@imply.io) (Imply) * Maxime Beauchemin (maximebeauche...@gmail.com) (Lyft) * Mohamed Slim Bouguerra (slim.bougue...@gmail.com) (Hortonworks) * Nishant Bangarwa (nish...@apache.org) (Hortonworks) * Parag Jain (paragjai...@gmail.com) (Oath) * Roman Leventov (leventov...@gmail.c

[RESULT] [VOTE] Accept Druid into the Apache Incubator

* Julian Hyde * P. Taylor Goetz * Ryan Blue * Steve Blackmon * Suneel Marthi * Ted Dunning * Tom Barber * Willem Jiang Non-binding +1: * Amol Kekre * Anu Engineer * Arpit Agarwal * Ashish * Atul K. Gupta * Bhupesh Chawda * Bolke de Bruin * Chinmay Kolhatkar * Hao Chen * Hugo Lauro * Jordan

Re: Druid 0.12.0 release (pre incubation)

As a mentor of Druid, sounds good to me. It’s good to keep on releasing regularly - the community relies on it. Please mention this in the board report (due in about a week). When will the next release be, and will you be able to make that under the incubator process? Julian > On Mar 2, 2018

Podling setup

I’m a mentor of a new podling, Druid. I would like to help them get set up, e.g. create mailing lists, create git repos. I tried to use https://selfserve.apache.org/ for these, but it only allows officers (i.e. PMC chairs). How is this supposed to work? Is the po

Re: Podling setup

> On Mar 8, 2018, at 4:51 AM, Mark Thomas wrote: > > On 07/03/18 23:24, Julian Hyde wrote: >> I’m a mentor of a new podling, Druid. I would like to help them get set up, >> e.g. create mailing lists, create git repos. I tried to use >> https://s

Re: Podling setup

s wrote: > > On 09/03/18 07:47, Julian Hyde wrote: >> >> >>> On Mar 8, 2018, at 4:51 AM, Mark Thomas wrote: >>> >>> On 07/03/18 23:24, Julian Hyde wrote: >>>> I’m a mentor of a new podling, Druid. I would like to help them get set >

Re: [VOTE] Accept Pinot into Apache Incubator

+1 (binding) Ironic that Druid — a similar project — has just entered incubation too. But of course that is not a conflict. Both are great projects. Good luck! Julian > On Mar 9, 2018, at 7:37 PM, Carl Steinbach wrote: > > +1 (binding) > > On Fri, Mar 9, 2018, 7:29 PM kishore g wrote: > >

Re: Self Serve & IPMC Members

It was I who originally raised this issue. I didn’t expect much to be done. I was very pleasantly surprised. Thank you to John Ament, Mark Thomas, Greg Stein and Chris Lambertus (and maybe others I am unaware of) for each picking up the baton and driving this issue to a solution. Julian > On

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

The guidance at https://www.apache.org/dev/release-signing.html#basic-facts is inconsistent with https://www.apache.org/dev/release-distribution#sigs-and-sums . The former

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

Yes, https://www.apache.org/dev/release-signing.html#basic-facts <https://www.apache.org/dev/release-signing.html#basic-facts> now makes sense. Thanks for updating it, sebb. > On Mar 14, 2018, at 6:15 PM, sebb wrote: > > On 14 March 2018 at 19:11, Julian Hyde wrote: >>

[DISCUSS] Absent mentors

The incubator has an ongoing problem with lack of mentor engagement. Mentors are a crucial component of the incubation process. Incubation is the time when projects learn the Apache Way, and they cannot learn in a vacuum. I’d like to discuss possible solutions to this problem. I’d like to hear f

Re: The role of a mentor

Has anyone here taught someone how to fish? (Or how to make cookies, or ski?) Mostly you just stand off, watching what they do. If you see them about to screw up in a big way, step in. Occasionally, offer them hints for how they might do what they’re doing a little bit better. (Not too often, be

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

I (as a Druid mentor) suggested the placeholder page, for the exact reasons Greg describes. Short term, I promise, and better than a 404. Julian > On Apr 13, 2018, at 20:15, Greg Stein wrote: > > One step at a time. If they want to throw a single page up *today* rather > than wait six weeks t

Re: Default webpages for new podlings

A template paragraph of simple HTML seems ideal, and it’s reasonable to expect podlings to create it by the time of their first board report. A full branding-compliant web site is a more complex undertaking, and we the IPMC should not try to hurry that process. The podling's interests are aligne

Re: Default webpages for new podlings

Luciano created a Jekyll prototype a year or so ago. Let’s dust that off. Julian > On Apr 15, 2018, at 19:30, Ted Dunning wrote: > >> On Sun, Apr 15, 2018 at 12:37 PM, Dave Fisher wrote: >> >> Hi - >> >> I think that a brand compliant initial podling page would not be hard to >> create usin

Re: Default webpages for new podlings

Just to clarify, in case people are not familiar with Jekyll. It is a code generator that a developer runs in their sandbox, and it generates the site. The developer then checks in the site to git or svn. So, the developer has complete control over the HTML that is checked in. They can manually

Re: Review mailing list membership?

I’m one of your (druid codling’s) mentors and, yes, I moderate the druid lists. I tried a week or so ago to list the members of druid’s lists and struck out. In twenty minutes, I couldn’t find the solutions listed below: whimsy and dev-l...@druid.apache.org . (

Re: [VOTE] Apache Crail 1.0-incubating (RC2)

Forwarding my vote from the PPMC vote: +1 (binding) Julian > On May 7, 2018, at 7:49 AM, Jonas Pfefferle wrote: > > Please vote to approve the source release of Apache Crail 1.0-incubating > (RC2). > > The podling dev vote thread: > https://www.mail-archive.com/dev@crail.apache.org/msg00241

Re: [VOTE] Apache Crail 1.0-incubating (RC2)

IPMC members, This vote has been open 72 hours and has two votes so far (Luciano and I are mentors). I’d really appreciate it if someone else could download and vote. This is Crail’s first release in the incubator but in my opinion they’re in pretty good shape. Julian > On May 7, 2018, at

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

In other words, there are several ways to prove that a binary release is WRONG but (to Greg’s point) there is no way to prove it RIGHT. As a mentor, I strongly advise against podlings making binary releases, especially for the first release. It’s difficult enough to get L&N correct for source r

Re: [VOTE] Apache Crail 1.0-incubating (RC2)

I agree about the missing DISCLAIMER file and the missing disclaimer in README.md. -1 until those are fixed. Regarding directories, I disagree. Common practice is to have everything (including NOTICE, README and DISCLAIMER) in a directory that is named after the release. If you do otherwise, yo

Re: [VOTE] Apache Crail 1.0-incubating (RC2)

, at 11:42 AM, John D. Ament wrote: > > > Julian, > > On 2018/05/10 18:40:12, Julian Hyde <mailto:jh...@apache.org>> wrote: >> I agree about the missing DISCLAIMER file and the missing disclaimer in >> README.md. -1 until those are fixed. >> >> Reg

Re: [VOTE] Apache Crail 1.0-incubating (RC2)

ent. If so, you can >> just pull out the distribution logic from the parent pom's repo ( >> https://github.com/apache/maven-apache-parent/blob/master/pom.xml#L336-L417 >> ) and merge that into the Crail pom. >> >> John >> >> On 2018/05/10 19:10:29,

Re: [VOTE] Apache Crail 1.0-incubating (RC3)

Forwarding my vote from the PPMC vote: +1 (binding) Julian > On May 22, 2018, at 12:29 AM, Jonas Pfefferle wrote: > > Forgot to add: > > Release artifacts have been signed with the following key: > https://people.apache.org/keys/committer/pepperjo.asc > > Thanks, > Jonas > > On Tue, 22 May

Re: [VOTE] Apache Crail 1.0-incubating (RC3)

Willem, You didn’t cast a vote on the release. I don’t think test failures is a blocker because README.md tells people to skip tests. IPMC, We still need one more +1, please. Julian > On May 23, 2018, at 12:23 AM, Jonas Pfefferle wrote: > > Hi, > > At the moment there is no way to run th

Re: Looking for Champion

Note that there is an existing database product called Palo - an open source OLAP engine by German company Jedox[1]. There there is a high likelihood that Palo would have to change its name during incubation, if accepted. Julian [1] https://en.wikipedia.org/wiki/Palo_(OLAP_database)

Re: Apache account creation issues

I have submitted an account request. Sorry the original request got ignored by the Druid mentors, including myself. Just in case, please check your spam folder: I emailed you yesterday that I had submitted an account request, apparently before you sent this email, and it’s possible that other m

Re: Poddlings length of time in the incubator

Regarding Quickstep. I am a mentor. (One mentor resigned earlier this year, but the other mentor, Roman, is sufficiently engaged.) I am concerned that Quickstep is not going to graduate. They are functioning well as an academic project, as evidenced by papers at top conferences[1], but all of thei

Re: Dealing with Unresponsive Mentors

There was a long thread about absent mentors a few months ago[1]. The consensus on the thread seemed to be to introduce some metrics. I was and am skeptical of that approach because it requires constant attention from the IPMC. The solution I advocated in that thread is to encourage podlings to

Re: [DISCUSS] Absent mentors

There is a strong presumption here that a mentor is fulfilling their duty if and only if they sign the reports. I’m skeptical. I can think of cases where an engaged mentor does not sign reports (because someone else has done it), and vice versa where a disengaged mentor shows up once a quarter

Re: [DISCUSS] Absent mentors

I hear what you’re saying. As a metric it’s better than nothing, but let’s not assume it is telling us everything. I believe that asking all mentors to sign off is a change in policy or at least in practice. (Neither the “Mentors’ guide”[1] nor the “Guide to being a mentor”[2] talks about signi

Re: [DISCUSS] Absent mentors

Thanks for doing this, Justin. It must have taken quite a while. You've convinced me that missing sign-off is a reasonable proxy for mentor disengagement. Just curious: As you were reviewing lists looking for mentor activity, did you learn anything about patterns of mentor behavior? Are there any

Re: Email to be sent to inactive mentors

Perhaps add some recognition in the text of the email that there may be activity that we are unaware of? (Unlikely, but it seems rude to presume.) I strongly support your efforts to hold mentors accountable. Thanks for doing it, Justin! Julian On Sat, Sep 8, 2018 at 5:53 PM Justin Mclean wrote:

Re: Incubator release checklist

Releases are invariably created from a particular commit from the source control system (usually a git commit these days). I think it’s important to check that the contents of the source tarball match the contents of the source control system at that commit. (To do this, I unpack the tar file in

Re: Email to be sent to inactive mentors

By that argument there’s no point speaking at ApacheCon. Because it doesn’t happen on a mailing list. So let’s not be so strict. Clearly there are many ways that a mentor can assist. Some of them are not measurable (such as having a phone call). But I think any measurable activity should count

How to review so-called "binary releases"?

It has been said many times that Apache does not do binary releases, only source releases. But users like binary releases (or pre-built binary artifacts, if you prefer), and therefore podlings like to create them. So, is there any guidance for how to review a release that contains source and bi

Re: How to review so-called "binary releases"?

t;> >>> When reviewing binary archives we need to make sure that the license file >>> is updated with the shiped dependencies licenses appropriately and that >>> they are all compatible with the Apache License (notice file might also >>> need to be updated).

Re: How to review so-called "binary releases"?

that LICENSE policy that Justin linked to applies to > convenience binaries creates confusion about reviewing binaries. > > My 2 cents, > -Alex > > On 10/25/18, 6:39 PM, "Greg Stein" wrote: > >On Thu, Oct 25, 2018 at 12:25 PM Julian Hyde wrote: >

Re: [VOTE] Release of Apache Crail-1.1-incubating [rc3]

Forwarding my vote from the PPMC vote: +1 (binding) I checked the source artifacts but not the binary artifacts. Therefore I agree with Justin that the source artifacts can be included in the release but not the binary artifacts. Julian On Sun, Nov 4, 2018 at 1:04 AM Justin Mclean wrote: > > Hi

Re: licenses and copyrights of dependencies

What Alex is saying makes sense. Whether you like it or not, you are creating a derived work (or something - I am not a lawyer), and that needs its own L&N. > On Nov 7, 2018, at 9:03 AM, Alex Harui wrote: > > IIRC, we use the food allergy analogy for these situations. AIUI, the goal > is f

Re: [VOTE] Accept burp into the Apache Incubator

Dave, You’ll want to cancel this vote. The subject line is an unfortunate victim of auto-correct. Julian > On Nov 8, 2018, at 11:06 AM, Dave Fisher wrote: > > Hi - > > This is a VOTE to accept the brpc Project into the Apache Incubator. > > It will last for at least 72 hours and will pass

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

+1 (binding) > On Nov 8, 2018, at 11:29 AM, Dave Fisher wrote: > > +1 (binding) > > Regards, > Dave > >> On Nov 8, 2018, at 11:25 AM, Dave Fisher wrote: >> >> Hi - >> >> This is a VOTE to accept the brpc Project into the Apache Incubator. >> >> It will last for at least 72 hours and will p

Re: [VOTE] Accept the Iceberg project for incubation

+1 (binding) Julian > On Nov 13, 2018, at 9:28 AM, Arthur Wiedmer wrote: > > +1 > > (Non-binding) > > Best, > Arthur > > On Tue, Nov 13, 2018, 09:24 Hugo Louro >> +1 (non-binding) >> >>> On Nov 13, 2018, at 9:19 AM, Owen O'Malley >> wrote: >>> >>> +1 (binding) >>> On Tue, Nov 13,

Re: How to review so-called "binary releases"?

The question with which I started this discussion has not been answered. Given that a collection of artifacts is up for a vote, and those artifacts are a mixture of source and binary artifacts, what is a reviewer to do: 1. Vote -1. The release contains binaries. 2. Perform some cursory checks on

Re: How to review so-called "binary releases"?

+1 to everything Mark Thomas said. On Wed, Nov 14, 2018 at 3:08 AM Mark Thomas wrote: > > On 13/11/2018 20:49, Roman Shaposhnik wrote: > > Personally, given the amount of binary releases that are distributed off of > > our very own infrastructure (and I'm not even counting our namespace > > on thi

[VOTE] Retire Crail

-1 [ ] Do not retire Crail from the Incubator Here is my vote: +1 [x] Retire Crail from the Incubator Julian Hyde (Member IPMC, Crail mentor) [1] https://incubator.apache.org/projects/crail.html [2] https://lists.apache.org/list?d...@crail.apache.org [3] https://lists.apache.org/thread

[RESULT] [VOTE] Retire Crail

With five binding +1 votes and no 0 or -1 votes, the vote passes. Thanks to all who voted. I'll work with other mentors to carry out the post-retirement steps. Julian On 2022/06/06 19:48:20 Julian Hyde wrote: > After years of declining activity[1][2], and following discussions on >

Re: Short process intro for exec's?

When I was mentoring the Hop podling a couple of years ago, I gave the following talk to educate the initial committers about the process. But it is probably suitable for executives: https://www.slideshare.net/julianhyde/what-to-expect-when-youre-incubating

Re: Short process intro for exec's?

es look great BTW, exactly what I can use as my starting point > internally. > > On 6/17/22, 3:15 PM, "Julian Hyde" wrote: > >When I was mentoring the Hop podling a couple of years ago, I gave the > following talk to educate the initial committers about the proc

Crail retirement is complete

As you know, the Crail podling retired as of 2022-06-20 [1]. I am pleased to report completion of the steps to clean up [2][3]. I note that Crail's retirement is mentioned in the draft Board report for July [4]. Julian [1] https://incubator.apache.org/projects/index.html#crail [2] https://issue

Re: Short process intro for exec's?

Rich, Thanks for revising this presentation and sharing back. I hope others will find it useful. Julian > On Jul 23, 2022, at 8:58 AM, Salz, Rich wrote: > > Thanks Julian. > > Here is the current draft intended to be a stand-alone introduction to Apache > and Incubation. Hope others find i

Re: [VOTE] Accept StreamPark into the Apache Incubator

A few people on this thread are voting -1 with the rationale that StreamPark is similar to existing projects. This is not a valid reason. Apache does not try to ensure that projects don't overlap. The 'community over code' mantra holds true: Apache does not pick technologies, it builds communities

Re: [DISCUSS] Incubating Proposal for Datark

HW-Chao, Your message is unreadable. Can you please resend without the HTML markup? Julian > On Sep 23, 2022, at 7:12 AM, HW-Chao Wang <576749...@qq.com.INVALID> wrote: > >     This is an interesting project, +1 on the proposal.  >     On 2022/09/23 13:06:00 Yu Li wrote: > Thanks all for the

Re: [Discuss] Baremaps Proposal

To our knowledge, none of the dependencies currently used in our main > >> branch are a matter of concern (BSD, MIT, Apache). > >> > >> == Cryptography == > >> There is no cryptography required in Apache Baremaps at present time. > >> > >> = Requ

Re: [Discuss] Baremaps Proposal

I’m happy to have this meeting if and when Baremaps starts incubation. But first let’s make the case to the IPMC that Baremaps should be in the Incubator, and get the vote passed. Julian > On Sep 28, 2022, at 12:45 AM, Bertil Chapuis wrote: > > >>> When I mentor a project (as I have volunte

Re: [VOTE] Accept Baremaps into the Apache Incubator

+1 (binding) Julian On Thu, Oct 6, 2022 at 8:10 AM Josh Fischer wrote: > > +1 (non-binding) > > On Thu, Oct 6, 2022 at 7:54 AM Bertrand Delacretaz > wrote: > > > Bertrand Delacretaz wrote: > > > ...I'm calling a vote to accept Baremap into the > > > Apache incubator. > > >... > > > > +1, brin

Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members.

> If we now exercise our means to object [to] a nomination after it’s executed, > we have this odd unpleasant situation of the person knowing what happened. While this is a legitimate concern, as far as I know the Board and the IPMC have not once exercised the right of veto, for hundreds if not th

Re: [DISCUSS] What to do with long incubating projects?

One idea is to schedule a review after the project has been in the incubator longer than the median time (say after 2 years). Deep-dive into what is going right and wrong, identify things that can be fixed, and set targets. And schedule another review a year later. Or schedule a vote to retire. On

Re: [MENTORS] Projects > 1000 days in Incubation

> SDAP - discussing steps to graduation (making a release) Last week I joined SDAP as a mentor. I am encouraging them to reassess what's left before graduation. As Justin says, the main thing is to make a release. There's a lot of stuff that they *think* they need to do (e.g. setting up CI) that t

Removed 'incubator.' from project status template

FYI, I removed 'incubator' from the project status template [1]. In Baremaps we concluded that we wanted the shorter URL and email addresses that would survive into graduation. And I figured that the next podling would want to do the same. If there are objections I can back it out. Julian [1] h

SDAP 1.0.0-rc2

Incubator PMC members, Can I get some help inspecting a release candidate? SDAP has been in incubation for several years, has only one remaining active mentor (myself!) and has just produced a release candidate good enough for me to vote +1. In due course this RC will appear in a vote on this li

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

I am a mentor of SDAP. Forwarding my vote from the PPMC thread [1]: +1 (binding) Julian [1] https://lists.apache.org/thread/vh9472q76kzndcs55pmpjmld8snzn1ny On Thu, Dec 22, 2022 at 7:19 PM Riley Kuttruff wrote: > Hello everyone, > > This is a call for a vote to release Apache SDAP (incubat

SDAP release vote

Could some IPMC members please vote on the SDAP 1.0.0-rc2 release thread? [1] The vote has been open for a week and there's only one vote so far (from me). (The podling has been in incubation for some time, and all of its original mentors have drifted away. I joined as a mentor in November because

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

Good catch. But could you (and others) continue the process of reviewing and voting on the release. It is established that an official ASF release must not contain gradle-wrapper.jar [1], but in my opinion this is a problem that could be solved in the next incubating release. If a few IPMC members

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

Thank you to Calvin, John, Justin, Larry for reviewing/voting. You raised some good points. SDAP is discussing on its dev@ list and I will argue there that they should address most or all in a new RC. A couple of responses to specific remarks. > On 2023/01/03 04:48:23 Justin Mclean wrote: > >

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc3

Forwarding my vote from the dev@sdap thread: +1 (binding) To repeat what I said for RC2, I am the sole active mentor for SDAP, and we appreciate the time and attention of IPMC members doing due diligence on this release. In RC3, SDAP have taken pains to address the issues noted in RC2. The v

Re: [QUESTION] are binary distributions/releases required?

It’s useful to clarify the terminology. There’s no such thing as a “binary release”. Release policy [1] says: > Every ASF release MUST contain one or more source packages > All releases are in the form of the source materials needed to make changes > to the software being released. > > As a conve

Re: [VOTE] Release Apache SDAP (incubating) 1.1.0-rc0

(I am a mentor of SDAP but was too late to vote in the thread on dev@sdap.) +1 (binding) Checked signatures/hashes, compared with git, checked NOTICE, LICENSE.txt, DISCLAIMER-WIP; built Collection Manager and Granule Infester using Docker, following the instructions in README. Notes: * You sho

Re: Little "upsie" at the Wayang podling

As others have said, there’s no way to retract a release when it’s gone to Maven Central. (Many of us have noticed show-stopping bugs just after the release.) The only remedy is to make a superseding release. I don’t support adding a step where an IPMC member presses the release button. Mistak

Re: Feedback requested - How to deal with retired podling resources

In regard to assets, I see no particular reason to treat retired podlings differently from graduated podlings. Keep the foo.apache.org hostname; retain the repository (read-only); keep the website (tagged with a notice ’This podling has retired. It may be contacted at …

Re: [VOTE] Release Apache Baremaps 0.7.2-rc2 (incubating)

-1 (binding) I had voted +1 on the dev list but I am changing my vote in light of the header issues that Calvin discovered. A typical java file in Baremaps has this header: /* * License

Re: [VOTE] Release Apache Baremaps 0.7.2-rc3 (incubating)

+1 (binding) Downloaded, checked signatures, README, LICENSE, NOTICE, DISCLAIMER-WIP; compared src-tar contents with git; built using OpenJDK 17/Maven 3.8.1 on Ubuntu/amd64; ran RAT. Checked that file headers are now correct. Julian > On Oct 3, 2023, at 11:48 AM, Leo wrote: > > +1 (binding)

<    1   2   3   4   >