emmaviolet

3 ms·

1. 1.▲
   by emmaviolet 8mo ago

   Yep, totally get this. We're going to try and provide some quick solves first for the most affected maintainers, and then go back and make sure we can also help with the kind of nuance you describe.
2. 2.▲
   by emmaviolet 8mo ago

   Totally get this. One thing we'd love to do is help make contribution patterns (not just guidelines) more visible to contributors, to help you get a better read of what's expected. Would that help? If so, where would you expect it
3. 3.▲
   by emmaviolet 8mo ago

   Great, we're on it
4. 4.▲
   by emmaviolet 8mo ago

   That makes a lot of sense, and we've been considering some of those options too so good to know we're on the right track there. On trying to figure out whether a PR was vibe-coded: in some cases it's obvious, but in many case
5. 5.▲
   by emmaviolet 8mo ago

   GitHub PM here. From what we've seen, you're right about the motivation; I've also seen plenty of job ads where "significant contribution to open source" is something that's called out explicitly as a valid sub
6. 6.▲
   by emmaviolet 8mo ago

   GitHub PM here working on how we can make this problem feel better for maintainers. Really appreciate how tiring this can be, especially when even low volume is sustained for many months. Would love your thoughts on some of the things we&#x