Bug reporting - Issue tracker

[amis92]

There was a suggestion to enable people from outside GitHub to report bugs, in addition to fixes.

Before the idea leaves my mind, I'll post it here: maybe integrate it with BattleScribe, to report bugs, and optionally include failing roster? That could be great if executable.

For example index.xml/bsi would include URL for bug-reporting service on BSData, so that when working on some roster, BattleScribe could remember where from this file was downloaded, and report issue within it's GUI.

Besides BScribe, the website could also offer something like uploading roster together with report. I think roster contains enough information to connect with appropriate catalogue revision, right?

I just don't really know where these files (rosters) should be held, because obviously the reports themselves are going to be sent as Issues to GitHub. I guess there is no way to attach files to them.

[dattanchu]

I thought our original idea was to have bug reporters report directly to
the github repository that hosts individual catalogues. The catalogue
owners can then act on them accordingly. This shields BSData from potential
IP issue. There is a small annoyance that user would need to log into
Github, but they have openid with G+ so it shouldn't be too bad.

On Wed, Feb 12, 2014 at 11:17 AM, Amadeusz Sadowski <
notifications@github.com> wrote:

There was a suggestion to enable people from outside GitHub to report
bugs, in addition to fixes.

Before the idea leaves my mind, I'll post it here: maybe integrate it with
BattleScribe, to report bugs, and optionally include failing roster? That
could be great if executable.

For example index.xml/bsi would include URL for bug-reporting service on
BSData, so that when working on some roster, BattleScribe could remember
where from this file was downloaded, and report issue within it's GUI.

Besides BScribe, the website could also offer something like uploading
roster together with report. I think roster contains enough information to
connect with appropriate catalogue revision, right?

I just don't really know where these files (rosters) should be held,
because obviously the reports themselves are going to be sent as Issues to
GitHub. I guess there is no way to attach files to them.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10
.

[Jonskichov]

@amis92 While I love the idea, I'd rather not put in a connection between the app and the site...