I just checked the repo, there aren't any open PRs from you Craig [1]
or I am checking the wrong place maybe, though I don't have the c-bit
on comdev, but would have definitely tried to review. I tried to check
what policy is followed with comdev but couldn't find any reference to
that. If there is
I recently sent a PR for the site and nothing happened. No one reviewed. No one
commented.
Just one data point but... Is there a process for review of PRs?
Craig
On 2023/08/17 03:50:04 Rich Bowen wrote:
> It seems to me that the recent requests for comdev membership are symptoms
> of broken pr
> "Bulk" voting is something I have heard before. Certainly can be a
solution
*if* the packages don't depend on each other. Otherwise I cannot see how it
helps with the cases I shared earlier. That is, `log4j-core` needs to be
released first so that `log4j-bom` can be updated and released. Put anot
Thanks for sharing insights from the Airflow land, much appreciated.
"Bulk" voting is something I have heard before. Certainly can be a solution
*if* the packages don't depend on each other. Otherwise I cannot see how it
helps with the cases I shared earlier. That is, `log4j-core` needs to be
rele
This is a bit of a grey area, so I would love to hear the opinion of others.
From my perspective a vote is only needed when doing a release of the source
code, all the other things fall under the “convenience binaries/artifacts"
So things like docker images/BOM/packaging based on the source code
Yeah,
thanks for bringing this up … this is actually something I brought up in the
last board meeting.
I also think it’s not ok to release stuff like parent poms with lazy consensus
and was currently following up with ASF Legal on that matter.
Just because some projects might be doing it, doesn
I would love to hear about it, but I believe releasing any software is an
"act of Foundation" and requires 3 explicit PMC members to say "+1" in
order for it to have legal repercussions.
So I am not so sure if releasing "software" of any kind that can be "ASF
software" should be done without votin
I am aware that certain projects follow this [LAZY][VOTE] convention. But I
am not able to read our release policy in such a way to allow that. What I
would appreciate is that somebody pointing me to a certain part of the
policy and explaining the legal room for this [LAZY][VOTE] act.
For the reco
