Dev February 2008

dev@lists.roundcube.net

63 participants
78 discussions

Re: [RCD] @Brett - forum suggestion
by till 06 Feb '08

06 Feb '08

On Feb 5, 2008 6:01 PM, chasd <chasd(a)silveroaks.com> wrote: > > 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 ? 1+ can be confirmed. As long as someone can upload an email to reproduce this, it's confirmed by a single person. The difficulty lies within those reports "RoundCube doesn't work in Firefox", then a dozen people say, "works for me" or "yeah, same problem". ;-) It doesn't take much to confirm a bug, it's just about the reproduction. As long as that is given, we can always fix it. > > 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. Believe me, I am glad. For others in need (this is linked from the trac homepage): http://trac.roundcube.net/wiki/Howto_ReportIssues I also frequently pass around this link on IRC and on the mailinglists. > > 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. I'd welcome drive-by patches. ;-) > 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> Yes, please. But only to a certain extend. We also get the "I can't send email"-stuff which in 99.99999% of all cases is config related. But I guess there are various things how we can improve that etc.. > 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 ? I try to confirm them too. I am trying to check Trac's timeline every day and work through issues. It obviously doesn't work always like that, but generally that's what I try. And when I say, "I", I really mean "we". I know are doing the same. > > > 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. Could have a trac ticket, I suppose. There is nothing wrong with it. But currently it doesn't always work like that. Cheers, Till _______________________________________________ List info: http://lists.roundcube.net/dev/

3 3

Critical Bug empty's Inbox
by Stefan Novak 06 Feb '08

06 Feb '08

Hello! There is a critical Bug in Roundcube that empty's the users mailbox when emptying the trash folder... http://trac.roundcube.net/ticket/1484449 <http://trac.roundcube.net/ticket/1484449> "empty kills mailbox" http://roundcubeforum.net/forum/index.php?topic=2195.new;topicseen#new Empty Trash empties INBOX <http://roundcubeforum.net/forum/index.php?PHPSESSID=ee05103c553298635a1 503839337a382&topic=2195.msg8706#msg8706> We also figured out that this always happen's when the user clicks on the button empty trash and at the same time the automatic refresh of the inbox is happen, the inbox is also empty. Maybe it's the same Problem described in: http://trac.roundcube.net/ticket/1484678 Method session_start with custom session handlers is not thread-safe I hope we can discuss some solutions, because we can't fix this issue by ourselves... thx Stefan _______________________________________________ List info: http://lists.roundcube.net/dev/

5 4

@Brett - forum suggestion
by Seansan 06 Feb '08

06 Feb '08

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: 1. use the community to confirm the bug, test the patch or confirm the future request 2. 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 3. 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/

3 3

GoPHP5 Status
by chasd 04 Feb '08

04 Feb '08

Let me first say I am happy with the progress of RoundCube and all the work the developers are doing. However, as part of my plans to migrate our servers to PHP5, I was wondering if there was any information about the status of the migration of RoundCube to PHP5. I remember that the devel-vnext branch was the target for this work, but I might be mistaken. Do the devs want to get out of RC stage to a 0.1 release before concentrating on GoPHP5 ? Should any patches be against devel-vnext instead of trunk ? Should there be instructions on <http://trac.roundcube.net/wiki/ Dev_SVN> on how to check out and use devel-vnext ? Is anyone using devel-vnext without major problems, known major issues not resent in trunk ? Am I asking too many questions ? Charles Dostale System Admin - Silver Oaks Communications http://www.silveroaks.com/ 824 17th Street, Moline IL 61265 _______________________________________________ List info: http://lists.roundcube.net/dev/

7 12

Discussing need of update script / alternative way of testing latest trunk
by Seansan 03 Feb '08

03 Feb '08

On item: Can we add a simple update scripte for developers - update to latest SVN / http://trac.roundcube.net/ticket/1484742 Seen the comments on this ticket. Would like to add some thought on it. I understand that the core developers have SVN installed and can work with tortoise fine. But I think a lot of others out there don't use these two programs, or sometimes don't have the ability to access and/or install SVN on the ISP server - or don't have a local installation. On the other hand: when bugs are fixed there is often a statement that one should update to latest SVN to test. I have the idea that the issue logger often thinks it is to much of a hassle to reinstall (and even find out how and where to download the latest SVN - then copy config, chmod log directory and continue). The users that log the bugs are not developers and sometimes technology adverse. Another way would be to have a a tester and developer only version available that always runs the latest SVN. Seansan _______________________________________________ List info: http://lists.roundcube.net/dev/

1 0

@ Adam - trac improvements
by Seansan 03 Feb '08

03 Feb '08

Adam, can you have a look at the ticket below. I think there are some good trac improvements that are suggested and will improve the way RC evolves (and adds clarity and speed of return). http://trac.roundcube.net/ticket/1484641 Seansan _______________________________________________ List info: http://lists.roundcube.net/dev/

1 0

OpenID
by Anton Lindstrom 03 Feb '08

03 Feb '08

I was reading about Yahoo's implementation of Open ID and was wondering if it is possible to integrate OpenID in Roundcube in some sort of way. It would be really cool and useful. _______________________________________________ List info: http://lists.roundcube.net/dev/

3 3

#1484710
by Robin Elfrink 02 Feb '08

02 Feb '08

Hi, Anybody please verify my patch for #1484710. Works on my end, but I'm quite sure I saw something over the head [1]. Robin [1] Literal translation of a dutch expression, let's see how many people understand :) _______________________________________________ List info: http://lists.roundcube.net/dev/

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Dev February 2008