Mobileread
Submitting bug reports
#1  kguil 07-06-2016, 06:19 PM
Hello everyone.

I've been receiving bug reports or queries about possible bugs scattered throughout many different threads making it very difficulty for me to keep track of them and replying in context. This is especially the case when they are posted as replies to threads having an unrelated topic to the report.

It would really help me a lot if you submit reports directly by email (Settings > About > Info). In many cases, I would need to follow up with you by email anyway.

Thanks for helping.
Reply 

#2  quiris 07-08-2016, 01:16 PM
What about maintaining bug reports on https://github.com/kguil similar to: https://github.com/kguil/Marvin-Roadmap/issues ?
Reply 

#3  kguil 07-08-2016, 02:25 PM
I'd rather not introduce yet another place to track in my workflow.
Reply 

#4  JKenP 07-08-2016, 03:01 PM
What you are asking is to use the device with an annoying keyboard for those of us not hooked on SMS. The easier it is to submit problems the better the problem solving. The more transparent that is the better the moral.
Reply 

#5  Faterson 07-08-2016, 05:16 PM
I hope you're not saying GitHub is dead, Kris. GitHub is the professional place to track bug reports and feature requests. MobileRead forums are an unholy mess, compared to GitHub.
Reply 

#6  ShellShock 07-09-2016, 04:08 AM
Quote Faterson
I hope you're not saying GitHub is dead, Kris. GitHub is the professional place to track bug reports and feature requests. MobileRead forums are an unholy mess, compared to GitHub.
He didn't say anything about GitHUb being dead, nor did he suggest using MobileRead forums. Clearly Kris wants people to email him.

I am not sure about GitHub. You said it yourself, it is the professional place to track bugs. This may put off the more casual user, whereas they may find the MR forums, or using email from Marvin itself, an easier and more friendly way of raising bugs.
Reply 

#7  Faterson 07-09-2016, 04:37 PM
And your point is...? My point is that whatever is done, GitHub should be kept alive as the (or at least a, for all I care) place to track Marvin bug reports and feature requests. No need to set up a new GitHub for Marvin 3, in my opinion; the current listing is perfectly fine, I believe – it simply needs to be updated to reflect the most recent Marvin 3 developments. But many Marvin deficiencies are (unfortunately) shared among all existing Marvin versions, and that is why I believe it's not necessary to set up a separate GitHub for Marvin 3.

PS: If the hordes of MobileRead trolls stay away from GitHub, so much the better! GitHub, as a professional tool, thanks to its clear organization, makes it obvious which users are truly trying to help improve Marvin, and which users simply have nothing better to do than to attack fellow Marvin users. Here, in chaotic MobileRead forums, that crucial difference is obfuscated, which suits the trolls, of course.
Reply 

Today's Posts | Search this Thread | Login | Register