[DISCUSS] Removing emeritus and activity requirements
http://www.apache.org/foundation/records/minutes/2013/board_minutes_2013_06_19.txt notes: "removal of a member of a PMC, except due to their death or resignation, can be requested of the Board of Directors by the PMC chairman or by formal decision of the PMC, but requires a decision by the Board of Directors" Note that our bylaws say a number of things about "active" PMC members or committers and "emeritus" status: https://impala.apache.org/bylaws.html The even include automatic removal for people who don't contribute for a while. This was all created when we copied Hadoop's bylaws. I propose we remove the distinction between active and inactive, remove the notion of emeritus status (which the ASF's official tools do not support anyway), and note that removing PMC members required ASF board approval. My view is that we should welcome contributions from community members, including ones who have been inactive for a while. If this discussion goes well, I'll propose a bylaws diff and a vote on it.
Re: Wrong Jira id in commit (IMPALA-7147 vs IMPALA-7417)
I would do this, it's quite courteous for future devs. "Our current idea is to change IMPALA-7417 to be a duplicate of IMPALA-7147, and create a new Jira with IMPALA-7417's original contents." On Mon, Sep 3, 2018 at 12:12 PM, Csaba Ringhofer wrote: > Hi folks! > > We have just discovered (thanks Laszlo), that one of my changes was pushed > with wrong Jira id in the commit message (it fixed IMPALA-7147, but I wrote > it as IMPALA-7417, which didn't exist at that time). > > Luckily there is no commit pushed for IMPALA-7417 yet (it is on review, > and happens to be my commit too). Our current idea is to change IMPALA-7417 > to be a duplicate of IMPALA-7147, and create a new Jira with IMPALA-7417's > original contents. > > Does someone have an idea about the best action in this case? My concern > is that the wrong Jira id can trick some tools and steal some time from > people. >
Wrong Jira id in commit (IMPALA-7147 vs IMPALA-7417)
Hi folks! We have just discovered (thanks Laszlo), that one of my changes was pushed with wrong Jira id in the commit message (it fixed IMPALA-7147, but I wrote it as IMPALA-7417, which didn't exist at that time). Luckily there is no commit pushed for IMPALA-7417 yet (it is on review, and happens to be my commit too). Our current idea is to change IMPALA-7417 to be a duplicate of IMPALA-7147, and create a new Jira with IMPALA-7417's original contents. Does someone have an idea about the best action in this case? My concern is that the wrong Jira id can trick some tools and steal some time from people.
