o-nikolas commented on PR #1423:
URL: https://github.com/apache/airflow-site/pull/1423#issuecomment-3955161317

   Yeah, I hear that. I think you could have some simple heuristics that would 
help a lot. Like the project must have existed for some number of days (7, 20, 
30 something like this). And then maybe have any 2 of the following: X number 
of stars, X number of issues (open/closed), x number of PRs (open/closed), X 
number of previous releases, etc.
   
   I think just a small handful of simple rules like this will help quite a 
bit. Adding new projects/tools that have existed for only a small number of 
days (or hours even after publishing) really leaves us vulnerable for a bait 
and switch like you described happening in the past. People use AI to blast 
together some project, get it linked here, then swap it for whatever they like.
   
   But again, it was just a spare thought. Happy to stand down given the load 
you think it would put on PMC otherwise! And as always appreciate the 
engagement @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