Say you have a bug report or feature request to make to a package. How can you use information on GitHub to manage your expectations (will there be a quick fix) and actions (should you go ahead and fork the repository)? In this post, we shall go over sources of information and explain how they can be used. In the end, there is no magical recipe, except perhaps graciousness, as software is made by humans. 😉
This is a companion discussion topic for the original entry at https://ropensci.org/blog/2022/07/01/evaluating-github-activity-for-contributors/