Open Source Comes to Campus/Newcomer Tasks/Issue Tracker Cleaning: Difference between revisions

In each of these cases, you'll want to leave a comment on the issue.

==== Not Enough Information ====

An ideal bug report has a lot of information. That includes:

* Steps to take to reproduce the problem, including any input (this can be files, text, or instructions such as "click the leftmost button"

* What they expected to happen

* What actually happened, including the text of any unexpected output such as error messages

* Software and operating system versions

If you are having trouble carrying out the steps to reproduce a bug, you should ask a mentor or member of the community whether they can supply the missing information. For instance, perhaps the bug reporter references a part of the project you can't find. It may be, though, that the reporter did not provide enough information for anyone to attempt to reproduce the bug.

In this case, you can help everyone out by identifying the missing information and leaving a comment asking the reporter to provide that information. For instance, you might write:

<blockquote>I'm trying to reproduce this bug, but it's not clear to me what you did leading up to the problem. Which input type seems to cause the problem?</blockquote>

or

<blockquote>Thanks for reporting this bug! Can you tell us which version of the project you found the bug in, and which operating system and version number you're using?</blockquote>