raiden00pl commented on PR #13494: URL: https://github.com/apache/nuttx/pull/13494#issuecomment-2357751169
> https://github.com/apache/nuttx/pull/13509#issuecomment-2357587237 Quick note from me: too much text. Reading the actual change in gitdiff takes much less time than going through the report. One the one hand, the report provides valuable information, but on the other hand, the wall of text is simply discouraging to read. Maybe a better solution would be to move some of the text to the documentation and attach links in reports ? Another problem I see is that PRs are not equal. Changes that affect the entire OS and all users are not equal let's say to a cosmetic change in code style. When it takes longer to complete the PR content than to make the actual change in code, it can discourage user from contributing. We have to keep in mind that people are ... lazy, and nothing can be done about it. I don't know how reliably the PR impact can be estimated automatically without human interaction. The greater the impact, the greater the requirements for the PR description should be. Maybe PR labels would be useful for this ? Currently they are practically not used. There are github bots that can help automate this process. -- 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]
