Brett, wondering if the the problem we had with the forum (trouble receiving .... and what can I do) is still necessary?
In addition I think it would be wise to add another link to the bugtracker and a short 1,2,3 on how to submit bugs, requests and patches. I find that there are some good suggestions and fixes being logged in the forum, but not admitted to trac.
Suggestion version 1. "Be aware that the development team has an official bugtracker in place where bugs, fixes, requests and patches can be logged an monitored.
Before you log an issue we ask you to:
- use the community to confirm the bug, test the patch or confirm the future request
- test patches in the common browsers before uploading - and keeping in mind that the solution needs to work not only for you but all RC users
- Upload the item to the bugtracker with a clear description and log of tests performed + in case of a bug the steps to reproduce
"
Seansan
List info: http://lists.roundcube.net/dev/
Before you log an issue we ask you to:
- use the community to confirm the bug, test the patch or confirm
the future request
Could you clarify this procedure ?
( testing a patch is pretty clear, but the other parts are not clear
for me ).
Charles Dostale System Admin - Silver Oaks Communications http://www.silveroaks.com/ 824 17th Street, Moline IL 61265
List info: http://lists.roundcube.net/dev/
On Feb 5, 2008 4:45 PM, chasd chasd@silveroaks.com wrote:
Before you log an issue we ask you to:
- use the community to confirm the bug, test the patch or confirm
the future request
Could you clarify this procedure ? ( testing a patch is pretty clear, but the other parts are not clear for me ).
I may! ;-)
I think what we are after is this:
User reports: "Email causes loop"
What we would like is:
X amount of people test and say, "Correct, I can reproduce this behavior." and maybe upload a bunch of emails to testing.roundcube.net in the process and let us know about it.
I know we don't always have the fastest turn-around on bugs and tickets but generally what we also lack is more feedback. Someone opens an issues and is never to be seen again. And when it works for us, we close with WORKSFORME. Which doesn't rule out that the error is still stuck somewhere in RoundCube.
Till _______________________________________________ List info: http://lists.roundcube.net/dev/
User reports: "Email causes loop"
One issue is that some of the reports may be on the users mail list,
some may be on the forums. I don't know of a way to get those two
( and others I don't know about ) reconciled. If two users on the
mail list report a bug, and two users on the forums report the same
bug, it is the same as if _only_ two users report the bug and not
four. Obviously Trac is where that should be consolidated, but at
what point is a bug "confirmed" by the community ?. Four users run
into the bug ? Three ? Five ?
What we would like is:
X amount of people test and say, "Correct, I can reproduce this behavior." and maybe upload a bunch of emails to testing.roundcube.net in the process and let us know about it.
OK, I've used RC for over a year and never knew about that site. Of course, I haven't had a need.
I know we don't always have the fastest turn-around on bugs and tickets but generally what we also lack is more feedback.
Yes, I think what feedback you have is too diffuse ( spread out ).
Someone opens an issues and is never to be seen again.
I call those drive-by bug reports. The user has an issue, fires off
an e-mail to some list, and thinks that is enough. They may even
unsubscribe from the mail list at that point because of "too many
messages." I know of one acquaintance of mine that joined a list to
report a bug ( not RC ), and then set his spam filter to block all
the traffic from the list. Didn't even bother to unsubscribe. Those
types of reports we can't help, even if it is an actual bug. I would
hope that if the bug is serious enough, someone else will run into
it, and they will have what it takes to champion it to Trac and
provide enough information for the bug to be verified and possible
fixed.
Open source software is based on community, which means ( at least to
me ) the end users must take an active role in reporting and
following through on bugs. Most users are used to commercial
software, where it not only is not expected for the end user to
provide feedback, but it is actively discouraged in many cases.
So IMHO any messages reporting bugs on the Users list or on the
forums should be funneled to
http://trac.roundcube.net/wiki/Howto_ReportIssues
so bug reporting is consistent for the developers.
And when it works for us, we close with WORKSFORME. Which doesn't rule out that the error is still stuck somewhere in RoundCube.
In order to "reward" those who spend their time to provide decent
feedback, is there any feedback from the developer(s) when a bug has
been verified ?
OK, what about RFE's though ? They can't be "confirmed" in any way. Popularity is not always a good indicator of priority either.
Would viable RFE's get included on
http://trac.roundcube.net/roadmap
or
http://www.roundcube.net/about
under planned features ?
How will those RFE's not determined to be viable be handled or
notified ?
I assume all RFEs should have a Trac ticket.
Charles Dostale System Admin - Silver Oaks Communications http://www.silveroaks.com/ 824 17th Street, Moline IL 61265
List info: http://lists.roundcube.net/dev/
-
chasd -
Seansan -
till