Docs/create community files#315
Merged
brarcher merged 3 commits intolibcheck:masterfrom Nov 4, 2020
Merged
Conversation
I created a GitHub issue template specifically for bug reports to help streamline the process of pinning down, replicating, verifying, and fixing user-reported issues.
The config.yml at the root of the .github/ISSUE_TEMPLATE directory controls the issue templates configuration for the project directory. Eventually, it would be nice to not have to accept blank issues, since having an issue template for each kind of issue helps speed up the process by allowing us to define the necessary information we need up front. While we create the issue templates, however, I'm leaving blank issues enabled. I also added the user mailing list address from the website in case someone prefers to seek the wisdom therein.
brarcher
reviewed
Nov 2, 2020
| blank_issues_enabled: true | ||
| contact_links: | ||
| - name: Check Library Users Mailing List | ||
| url: check-users@sourceforge.net |
Contributor
There was a problem hiding this comment.
Should we direct users to post questions on GitHub rather that the mailing list?
Sometimes users include attachments with their questions (like screenshots). if they are too big an admin of the mailing list needs to approve it. It would be easier if the questions (and their attachments) were handled by GitHub. It may be easier to discover similar questions if they are all on GitHub as well.
Collaborator
Author
There was a problem hiding this comment.
Yea, I agree; I saw the configuration file allowed for including the development mailing list and I thought it might look nice and official, but I think including it might be counterproductive. I didn't know about the mailing list attachment size limit, either.
As discussed in the pull request (libcheck#315), the user mailing list has been removed to prevent the bifurcation of the user base. It is preferable to have all user questions, feature requests, and bug reports filed here via the GitHub issues feature. Discussion: libcheck#315 (comment)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I created an
ISSUE_TEMPLATEdirectory in the.githubproject directory to allow us to pre-populate bug-report related issues and speed up the turnaround time by being able to skip the information request phase, letting us get right into the verification, diagnosis, fix, and test phases.