Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Issue template for Synapse #2413

Merged
merged 5 commits into from
Aug 21, 2017
Merged

Issue template for Synapse #2413

merged 5 commits into from
Aug 21, 2017

Conversation

lampholder
Copy link
Member

Encouraging users to try #matrix:matrix.org for support queries in preference to filing a bug.

A new issue template proposed to try and steer people towards #matrix:matrix.org for support queries relating to running their own homeserver.
Oops capital L.
Removed the sentence encouraging people not to file a bug - if people are in doubt we'd rather they filed a bug than gave up entirely.
@lampholder lampholder requested a review from ara4n August 14, 2017 13:41
- that reproduce the bug
- using hyphens as bullet points

Describe how what happens differs from what you expected.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Include some text to ask for log snippets. It's hard to troubleshoot issues without stacktraces or any indication as to what is going on. Similar to the "please screenshot it" in Riot.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I stopped short of asking for logs since we've got no secure way to receive them (other than via Riot itself), but we could ask for 'relevant log snippets' if the user is able to provide them.

Ideally we'd also expose the rageshake server to receive logs securely, but that will need time to develop :)


- **Homeserver**: was this issue identified on matrix.org or another homeserver?
- **Platform**: tell us about the environment in which your homeserver is operating
- distro, hardware, if it's running in a vm/container, etc.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add the version of the running instance (if known).
And maybe the install method (via package manager/ via git clone/ ...)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed; thanks.

Responding to review comments.
Added instructions for checking server version.
@richvdh
Copy link
Member

richvdh commented Aug 17, 2017

honestly I think this errs to much towards an implication that we might actually bother to look at things reported here, but ymmv.

@lampholder
Copy link
Member Author

Well, the whole idea is to reduce the signal/noise ratio, so perhaps we even will actually look at some of these things :P

@lampholder lampholder merged commit 20b3660 into master Aug 21, 2017
richvdh added a commit that referenced this pull request Sep 5, 2017
PR #2413 added an issue template, but just adding files to the project
directory upsets the packaging scripts: we need to explicitly include or
exclude them.

Move the template into a .github directory to make that easy, and to de-clutter
the root a bit.
richvdh added a commit that referenced this pull request Sep 5, 2017
PR #2413 added an issue template, but just adding files to the project
directory upsets the packaging scripts: we need to explicitly include or
exclude them.

Move the template into a .github directory to make that easy, and to de-clutter
the root a bit.
@hawkowl hawkowl deleted the toml-issue-template branch September 20, 2018 13:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants