On 03/21/2013 01:42 PM, Bernhard Posselt wrote:
The thing youre describing is actually not a problem, we ask people to
provide logs etc on github and if we dont have enough information or
cant reproduce it over a longer period we close the issue anyways.
Asking for bugs on the mailing lists kinda spams my inbox and keeps me
from fixing problems.
If I am confident enough that I have discovered a bug, then I file a bug
report on github. But I am not always sure, if that is a bug, so yes, it
makes sense to discuss it here and get feedback from other users.
It happened to me already that I filed a bug on github, and as it turned
out the problem was that the cache in my browser was not cleared, and I
had javascript functions from the pre-upgrade version after an upgrade.
I felt silly to use the time of a developer unnecessarily. (Although I
learned from the experience).
Yours: Laszlo
On 03/21/2013 01:36 PM, Diederik de Haas wrote:
On Thursday 21 March 2013 11:44:54 Frank Karlitschek wrote:
The next thing we need is to really understand what exactly is
triggering
the problem in your setup.
So if you want to help us then please provide us with detailed
information
how your server setup looks like, which software your use, OS,DB,
client/server, ...
Can you please provide us step by step description what you can do to
trigger this problem staring for a vanilla ownCloud server. I don't
think
currently developers knows where this problem is.
I completely agree with this.
Which is why I find it rather strange that lately a lot of times the
(only)
response someone is getting to a question they ask on this ML is:
"Please file an issue on github"
When the cause of the issue is known, the way to trigger it is known
and a way
to reproduce it is known ... then it would be really useful if an
issue was filed
describing the problem and the steps to reproduce it.
But when someone describes a problem and/or strange thing they see on
their OC
server and concludes that with "Is someone else seeing this?" then you
can be
pretty sure he/she doesn't have the above mentioned information ready
to file a
proper bug report.
Instead he/she is trying to figure out what's causing the issue by
asking the
community/ML whether someone else is experiencing that as well so they
can
compare 'notes' (OS, DB used, config, browser, etc) and then determine
the cause
of the issue and hopefully steps to reproduce it reliably.
But when someone describes such a 'strange thing' and get 'buzzed off'
by a reply
like "Please file an issue on github", then there will probably be
only losers.
1. Developers because they get 'useless' bug reports and the list of
open issues
just keeps rising and rising ...
2. Users because their 'useless' bug report isn't getting a reaction,
let alone
a fix and the 'solution' to their ML-question is "Please file an issue
on github"
so no use in trying again, either asking the ML or filing an issue on
github....
That way everybody looses.
My 0.02
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
