You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by "milamberspace (via GitHub)" <gi...@apache.org> on 2026/07/11 08:03:00 UTC

[I] setup: derive adopter config from existing sources (.asf.yaml, repo metadata) instead of duplicating [magpie]

milamberspace opened a new issue, #815:
URL: https://github.com/apache/magpie/issues/815

   ## Problem
   
   When adopting Magpie, several `.apache-magpie-overrides/` values duplicate information that already lives elsewhere in the adopter repo and can drift out of date. Feedback from an adopter (Apache JMeter): a PMC member flagged that the per-project config forces maintainers to hand-copy data that changes often — *"stale context is worse than no context"* — and asked that Magpie source it from `.asf.yaml` rather than making everyone duplicate it.
   
   For an ASF project a lot of the adopter config is already available:
   
   - **`.asf.yaml`** — repo description, homepage, labels, `notifications:` (→ dev / commits / PR mailing lists), branch protection.
   - **GitHub repo metadata** (`gh repo view`) — default branch, description, topics.
   - **CI check names** — these are *not* in `.asf.yaml`; they come from `.github/workflows/` (often generated, e.g. a `matrix.*` script), so a hand-maintained check-name map is the most stale-prone surface of all.
   
   ## Proposal
   
   In the adopt / config flow, prefer deriving from existing sources over asking the adopter to duplicate:
   
   1. **Auto-source the stable fields** — repo, default branch, mailing lists (from `.asf.yaml notifications:`), labels — from `.asf.yaml` + repo metadata, and only fall back to prompting when a value is absent.
   2. **Don't require a per-check-name CI map.** Given CI job names are volatile (and often generated), default the CI-check → doc mapping to a single generic pointer unless the adopter explicitly wants finer buckets (still overridable).
   3. Optionally, re-derive on `/magpie-setup upgrade` and surface drift when a sourced value changed, instead of silently keeping a stale copy.
   
   This keeps the committed override surface minimal and removes the maintenance burden the adopter raised.
   
   ## Context
   
   - Adopter discussion: `milamberspace/jmeter#1` (JMeter adoption PR) — as an interim, the JMeter CI-check map was collapsed to a single generic pointer locally (*stale > no context*).
   - Related prior upstream fix from the same adoption: apache/magpie#786.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] setup: derive adopter config from existing sources (.asf.yaml, repo metadata) instead of duplicating [magpie]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #815:
URL: https://github.com/apache/magpie/issues/815#issuecomment-4953024651

   Sure - feel free. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] setup: derive adopter config from existing sources (.asf.yaml, repo metadata) instead of duplicating [magpie]

Posted by "justinmclean (via GitHub)" <gi...@apache.org>.
justinmclean closed issue #815: setup: derive adopter config from existing sources (.asf.yaml, repo metadata) instead of duplicating
URL: https://github.com/apache/magpie/issues/815


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] setup: derive adopter config from existing sources (.asf.yaml, repo metadata) instead of duplicating [magpie]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #815:
URL: https://github.com/apache/magpie/issues/815#issuecomment-4945982900

   Good points - this might be ASF-specific adoption path (we have to remember that Magpie is "organisation agnostic - but it does have organization-specific variants). 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] setup: derive adopter config from existing sources (.asf.yaml, repo metadata) instead of duplicating [magpie]

Posted by "justinmclean (via GitHub)" <gi...@apache.org>.
justinmclean commented on issue #815:
URL: https://github.com/apache/magpie/issues/815#issuecomment-5087845153

   completed


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] setup: derive adopter config from existing sources (.asf.yaml, repo metadata) instead of duplicating [magpie]

Posted by "onlyarnav (via GitHub)" <gi...@apache.org>.
onlyarnav commented on issue #815:
URL: https://github.com/apache/magpie/issues/815#issuecomment-4952821988

   Do this issue still need work? I can work on this if required. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org