choo121600 commented on PR #228:
URL: https://github.com/apache/airflow-steward/pull/228#issuecomment-4526558013

   I want to share an honest reservation about this skill, while also 
acknowledging upfront that I’m not sure my concern is necessarily the right 
conclusion.
   
   I tested the skill on my own GitHub handle (choo121600) as the simplest 
possible subject. The fetch and render work as intended, the output is 
well-structured, the disclaimers are present, and the maintainer-time savings 
this PR aims for do feel real to me. Those positives are clear.
   
   What I’m less sure about is the experience of using it.
   
   The skill makes it very easy to see which areas align with typical PMC 
expectations and which areas appear lacking. As I was testing it, I found 
myself naturally thinking, “Should I try to fill in those gaps?”
   
   What felt slightly uncomfortable to me was how quickly and naturally that 
progression happened. Measurable things became goals much faster than I 
expected, and it made me wonder whether contributors might gradually optimize 
for what is visible in the table rather than for the many kinds of valuable but 
less visible contributions that communities also depend on.
   
   Of course, self-application is not the intended use case here. (<nominator> 
is the expected caller, not <candidate>.)
   
   But if this becomes one of Magpie’s default support skills, I wonder whether 
regardless of intent it could become the path of least resistance inside the 
project, and whether that might gradually shift contributor attention toward 
the things that are easiest to quantify.
   
   I genuinely don’t know the answer myself, but I think it’s a question worth 
wrestling with.
   Maybe this is something we could discuss together once we have a mailing 
list in place.
   cc @potiuk 


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to