You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maka.apache.org by Lei Yuhan <le...@outlook.com> on 2026/08/19 18:22:37 UTC
[DISCUSS] Add .asf.yaml for repository configuration
Hi all,
Now that the codebase lives at apache/maka, the repository still has no .asf.yaml. Every GitHub setting is whatever the migration left behind, and no GitHub activity reaches our mailing lists. I would like to add one.
Draft PR: https://github.com/apache/maka/pull/3262
The proposed file covers repository metadata (description, topics), merge policy (squash only, delete branch on merge), Dependabot alerts, branch protection on main, and notification routing.
Two points I would like consensus on rather than plain review:
Branch protection on main. main currently has no protection at all; anyone with write access can push to it directly. I propose requiring one approving review and dismissing stale reviews on new commits. This ends the self-merge path the project used before incubation, including for small or mechanical changes.
Notification routing. We have dev@ and commits@ only. I propose routing commits, issues, pull requests, and job results to commits@, keeping dev@ for discussion. The alternative is routing pull requests to dev@ for higher visibility, at the cost of noise on the discussion list.
One thing I left out for now: required status checks. On main today the CI jobs are gated behind a path-filter job and report as "skipped" when a change does not touch their surface, and GitHub treats a skipped required context as unmet, so listing them would block every pull request. The change proposed in the "[DISCUSS] Reduce pull request CI runner usage" thread (PR #3261) collapses those jobs into a single always-running "CI / test" gate. Once that lands, requiring that one context here is a one-line follow-up, and I would fold it in before merging this if #3261 goes first. The two changes are otherwise independent.
If there are no objections, I will merge in 72 hours (lazy consensus).
Thanks,
Yuhan Lei (astrohan, @Astro-Han on GitHub)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
Re: [DISCUSS] Add .asf.yaml for repository configuration
Posted by M4n5ter <wy...@apache.org>.
Thanks, Yuhan.
I support the updated proposal: require one independent approval and a
passing `test` check on `main`, with stale approvals dismissed after new
commits. One approval is the right count for our current reviewer pool;
requiring two would impose too much coordination overhead.
I understand that this ends the existing no-review fast path and requires
human review for Dependabot PRs as well. I’m prepared to share that review
load.
Before merging, please update both CONTRIBUTING files so the fast-path
language and the references to the ASF development list match the policy
being enforced.
With those documentation updates, I have no objection to proceeding after
the lazy-consensus window.
Best,
Yongtao Wang
On Thu, Aug 20, 2026 at 8:54 AM Lei Yuhan <le...@outlook.com> wrote:
> Hi all,
>
> Two corrections to my original message. Both change the proposal.
>
> 1. I wrote that no GitHub activity reaches our mailing lists. That is
> wrong. commits@ has received 97 messages in the last month by Infra
> default; I had
> only checked dev@. The notifications block is now removed from the PR.
> 2. I wrote that required status checks could not be configured yet. Also
> wrong. A job skipped by an `if:` condition reports success, unlike a
> workflow
> skipped by a path filter, and ci.yml's `test` job already runs under `if:
> always()`. The PR now requires the `test` context. Without it, branch
> protection would have required a human approval but no passing CI.
>
> The PR is updated. The 72-hour window still stands, and the question is
> unchanged: branch protection on main.
>
> Yuhan Lei (astrohan, @Astro-Han on GitHub)
>
>
> > 2026年8月20日 02:22,Lei Yuhan <le...@outlook.com> 写道:
> >
> > Hi all,
> >
> > Now that the codebase lives at apache/maka, the repository still has no
> .asf.yaml. Every GitHub setting is whatever the migration left behind, and
> no GitHub activity reaches our mailing lists. I would like to add one.
> >
> > Draft PR: https://github.com/apache/maka/pull/3262
> >
> > The proposed file covers repository metadata (description, topics),
> merge policy (squash only, delete branch on merge), Dependabot alerts,
> branch protection on main, and notification routing.
> >
> > Two points I would like consensus on rather than plain review:
> >
> > Branch protection on main. main currently has no protection at all;
> anyone with write access can push to it directly. I propose requiring one
> approving review and dismissing stale reviews on new commits. This ends the
> self-merge path the project used before incubation, including for small or
> mechanical changes.
> >
> > Notification routing. We have dev@ and commits@ only. I propose routing
> commits, issues, pull requests, and job results to commits@, keeping dev@
> for discussion. The alternative is routing pull requests to dev@ for
> higher visibility, at the cost of noise on the discussion list.
> >
> > One thing I left out for now: required status checks. On main today the
> CI jobs are gated behind a path-filter job and report as "skipped" when a
> change does not touch their surface, and GitHub treats a skipped required
> context as unmet, so listing them would block every pull request. The
> change proposed in the "[DISCUSS] Reduce pull request CI runner usage"
> thread (PR #3261) collapses those jobs into a single always-running "CI /
> test" gate. Once that lands, requiring that one context here is a one-line
> follow-up, and I would fold it in before merging this if #3261 goes first.
> The two changes are otherwise independent.
> >
> > If there are no objections, I will merge in 72 hours (lazy consensus).
> >
> > Thanks,
> > Yuhan Lei (astrohan, @Astro-Han on GitHub)
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
> > For additional commands, e-mail: dev-help@maka.apache.org
> >
>
>
Re: [DISCUSS] Add .asf.yaml for repository configuration
Posted by Lei Yuhan <le...@outlook.com>.
Hi all,
Two corrections to my original message. Both change the proposal.
1. I wrote that no GitHub activity reaches our mailing lists. That is wrong. commits@ has received 97 messages in the last month by Infra default; I had
only checked dev@. The notifications block is now removed from the PR.
2. I wrote that required status checks could not be configured yet. Also wrong. A job skipped by an `if:` condition reports success, unlike a workflow
skipped by a path filter, and ci.yml's `test` job already runs under `if: always()`. The PR now requires the `test` context. Without it, branch protection would have required a human approval but no passing CI.
The PR is updated. The 72-hour window still stands, and the question is unchanged: branch protection on main.
Yuhan Lei (astrohan, @Astro-Han on GitHub)
> 2026年8月20日 02:22,Lei Yuhan <le...@outlook.com> 写道:
>
> Hi all,
>
> Now that the codebase lives at apache/maka, the repository still has no .asf.yaml. Every GitHub setting is whatever the migration left behind, and no GitHub activity reaches our mailing lists. I would like to add one.
>
> Draft PR: https://github.com/apache/maka/pull/3262
>
> The proposed file covers repository metadata (description, topics), merge policy (squash only, delete branch on merge), Dependabot alerts, branch protection on main, and notification routing.
>
> Two points I would like consensus on rather than plain review:
>
> Branch protection on main. main currently has no protection at all; anyone with write access can push to it directly. I propose requiring one approving review and dismissing stale reviews on new commits. This ends the self-merge path the project used before incubation, including for small or mechanical changes.
>
> Notification routing. We have dev@ and commits@ only. I propose routing commits, issues, pull requests, and job results to commits@, keeping dev@ for discussion. The alternative is routing pull requests to dev@ for higher visibility, at the cost of noise on the discussion list.
>
> One thing I left out for now: required status checks. On main today the CI jobs are gated behind a path-filter job and report as "skipped" when a change does not touch their surface, and GitHub treats a skipped required context as unmet, so listing them would block every pull request. The change proposed in the "[DISCUSS] Reduce pull request CI runner usage" thread (PR #3261) collapses those jobs into a single always-running "CI / test" gate. Once that lands, requiring that one context here is a one-line follow-up, and I would fold it in before merging this if #3261 goes first. The two changes are otherwise independent.
>
> If there are no objections, I will merge in 72 hours (lazy consensus).
>
> Thanks,
> Yuhan Lei (astrohan, @Astro-Han on GitHub)
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
> For additional commands, e-mail: dev-help@maka.apache.org
>