Dev

dev@lists.roundcube.net

2 participants
4318 discussions

Progress report on Trac and a few questions...
by B. Johannessen 11 Oct '05

11 Oct '05

Time for a progress report on the Trac installation. After many, *many* hours, I've finally reached an agreement with Python. The agreement basically boils down to this; Python will put up with being installed in /usr/local/python (instead of in /usr or /usr/local), and I will put up with having to hack every Python "extension" in the known universe to get it to work. In practice this means everything will take about 10 times as long, at least in the beginning. The only reason I haven't taken both Trac and Python out back and shot then both in the neck, is that certain people whose opinion i respect claims Python is actually an excellent idea. But, at the end of the day (or more precisely at the end of two days), I've succeeded. Trac and Python, and their combined cluster of dependencies finally fell into place. We now have a working Trac installation! This means it's time for me to start asking some questions. The ticket tracking system has a few settings we need to agree upon before we start using it. I'll present the issues in question, along with my suggested answers, and let you all battle it out for a few days before we make a final decision. I'll give Thomas final say, and assume he speaks on behalf of the current active developers. * Type: When you create a ticket, you also select a ticket type. The default list of available types include the following: 'defect', 'enhancement' and 'task'. My suggestion is that we substitute these 3 with the following 2: 'Bug' and 'Feature Request'. My motivation for both reducing and renaming is simplicity. When a first-time Trac user submits her first ticket, lets make sure it's as simple and self explanatory as can be. * Priority: A ticket is assigned a priority. The default Trac installation is set up with a total of 5 priorities; 'blocker', 'critical', 'major', 'minor' and 'trivial'. I suggest we reduce and rename to: 'High', 'Medium' and 'Low', for the reasons listed above. * Component: As far as I can tell, the RoundCube project only has one component so far. I suggest we name this 'RoundCube Core'. * Milestone: At what milestone is this bug fix or feature supposed to be available. To keep things simple in the beginning I suggest we define the following milestones: '0.1-beta', '0.1-final', '0.2-alpha' and '0.2-beta'. More milestones will of course be added later. If we agree to start with this list, I'll need a guesstimate from Thomas on when they'll be released. * Version: The version of RoundCube that this ticket pertains to. I see no point in adding any older versions to the system, so I think this list should initially include only 'v0.1-20051007'. The important thing to remember about the above lists is that non of this will be carved in stone. We'll surely make additions and alterations as we go. The goal here is just to make sure we start with some sane defaults. Then there's the question of the design. The current design looks fantastic, but doesn't lend itself easily to some of the thinks we'll be publishing. My suggestion is to just go live with the default design of Trac, a slightly modified design on the mailing list archive, and the main RoundCube site just like it looks today. Then, once everything is up and running I'll ask for some design help on the mailing list. Last, but not least; the question of CVS to SVN migration. It's a lot easier for me just to fetch the latest source from SourceForge CVS and import this into Subversion. If we want to import all the history as well, someone with a bit more CVS-foo then me will have to help me get my hands on a repository tar-ball. This is once again a decision for the developers. Is it acceptable to leave all the old history in SourceForge CVS? At the end of the day, I'll leave this decision to Thomas. I think that's about it for tonight. Bob

3 2

Re: Progress report on Trac and a few questions...
by Praneet Kandula 11 Oct '05

11 Oct '05

Awesome work, Bob! I agree with all of your Trac settings except one. I suggest that you have more than one setting for the components, that would initially include: - Webmail - Address Book - Skins - Other (settings, etc.) We can expand to include more as we need (plugins, notes, etc.). What do you think? On 10/11/05, B. Johannessen <bob(a)db.org> wrote: > Time for a progress report on the Trac installation. After many, *many* > hours, I've finally reached an agreement with Python. The agreement > basically boils down to this; Python will put up with being installed in > /usr/local/python (instead of in /usr or /usr/local), and I will put up > with having to hack every Python "extension" in the known universe to > get it to work. In practice this means everything will take about 10 > times as long, at least in the beginning. The only reason I haven't > taken both Trac and Python out back and shot then both in the neck, is > that certain people whose opinion i respect claims Python is actually an > excellent idea. > > But, at the end of the day (or more precisely at the end of two days), > I've succeeded. Trac and Python, and their combined cluster of > dependencies finally fell into place. We now have a working Trac > installation! > > This means it's time for me to start asking some questions. The ticket > tracking system has a few settings we need to agree upon before we start > using it. I'll present the issues in question, along with my suggested > answers, and let you all battle it out for a few days before we make a > final decision. I'll give Thomas final say, and assume he speaks on > behalf of the current active developers. > > * Type: > When you create a ticket, you also select a ticket type. The default > list of available types include the following: 'defect', 'enhancement' > and 'task'. My suggestion is that we substitute these 3 with the > following 2: 'Bug' and 'Feature Request'. My motivation for both > reducing and renaming is simplicity. When a first-time Trac user submits > her first ticket, lets make sure it's as simple and self explanatory as > can be. > > * Priority: > A ticket is assigned a priority. The default Trac installation is set up > with a total of 5 priorities; 'blocker', 'critical', 'major', 'minor' > and 'trivial'. I suggest we reduce and rename to: 'High', 'Medium' and > 'Low', for the reasons listed above. > > * Component: > As far as I can tell, the RoundCube project only has one component so > far. I suggest we name this 'RoundCube Core'. > > * Milestone: > At what milestone is this bug fix or feature supposed to be available. > To keep things simple in the beginning I suggest we define the following > milestones: '0.1-beta', '0.1-final', '0.2-alpha' and '0.2-beta'. More > milestones will of course be added later. If we agree to start with this > list, I'll need a guesstimate from Thomas on when they'll be released. > > * Version: > The version of RoundCube that this ticket pertains to. I see no point in > adding any older versions to the system, so I think this list should > initially include only 'v0.1-20051007'. > > The important thing to remember about the above lists is that non of > this will be carved in stone. We'll surely make additions and > alterations as we go. The goal here is just to make sure we start with > some sane defaults. > > Then there's the question of the design. The current design looks > fantastic, but doesn't lend itself easily to some of the thinks we'll be > publishing. My suggestion is to just go live with the default design of > Trac, a slightly modified design on the mailing list archive, and the > main RoundCube site just like it looks today. Then, once everything is > up and running I'll ask for some design help on the mailing list. > > Last, but not least; the question of CVS to SVN migration. It's a lot > easier for me just to fetch the latest source from SourceForge CVS and > import this into Subversion. If we want to import all the history as > well, someone with a bit more CVS-foo then me will have to help me get > my hands on a repository tar-ball. This is once again a decision for the > developers. Is it acceptable to leave all the old history in SourceForge > CVS? At the end of the day, I'll leave this decision to Thomas. > > I think that's about it for tonight. > > > Bob > > >

2 1

Pear errors
by Jeffrey Lee 11 Oct '05

11 Oct '05

I installed the available version of round cube mail and get some errors: Warning: preg_match: internal pcre_fullinfo() error -3 in /usr/share/ pear/DB.php on line 762 Warning: preg_match: internal pcre_fullinfo() error -3 in /usr/share/ pear/DB.php on line 789 Warning: preg_match: internal pcre_fullinfo() error -3 in /usr/share/ pear/DB.php on line 762 Warning: preg_match: internal pcre_fullinfo() error -3 in /usr/share/ pear/DB.php on line 789 Warning: preg_match: internal pcre_fullinfo() error -3 in /usr/share/ pear/DB.php on line 631 Warning: preg_match: internal pcre_fullinfo() error -3 in /usr/share/ pear/DB.php on line 631 Warning: preg_match: internal pcre_fullinfo() error -3 in /usr/share/ pear/DB.php on line 631 I am using php 5 apache 2 and mysql 4.1.14 Any ideas why I get these errors? - Jeff

1 0

Roadmap ?
by Hervé Piedvache 11 Oct '05

11 Oct '05

Hi, Just a smal question .. but is there a public roadmap of the development planning ?? And is there also task attribution for next roundcube evolutions ? I just ask this to not do something on the code already done by other people ... Thanks, -- Hervé Piedvache Elma Ingénierie Informatique 3 rue d'Uzès F-75002 - Paris - France Pho. 33-144949901 Fax. 33-144882747

2 1

Folder Listing CSS Styling
by Ross Poulton 11 Oct '05

11 Oct '05

Since upgrading to the latest public release, I've had some funnyness in my folder listing. I've added the following block in skins/default/mail.css to make the message list easier to read (I'm using FireFox 1.0.7, courier imapd, apache, debian linux). Firstly I modified the '#mailboxlist li.selected a' block, to change the color from '#FFF' to '#000'. This makes the listing black. Under this block I then added: #mailboxlist li.selected ul li a { color: #000; font-weight: normal; } This removes the boldness from subfolders of the current folder. Also, all folders are listed in black which is infinitely easier to read than when they were white. I'm finding the CSS for the folder list very odd in the new version - it's all cascaded (which is great) but the colors are a bit messed up (it looks completely different in Firefox & IE for me, both look screwed up though). Is anybody currently looking into this, or even experiencing similar problems? If not I'll try to clean it up over the next few days. Ross www.rossp.org

3 5

Re: Courier Problems
by Kennedy, Richard (Aventure Media) 11 Oct '05

11 Oct '05

Unfortunately its still timing out on sending mail, looking at the server logs, its going through. When clicking the send icon on new mail its just going to -> Page cannot be found after about 20 seconds. Changed all of the configs, and even tried changing it to SMTP instead of via mail() At 23:13 11/10/2005 +1000, Ross Poulton wrote: >Richard, > >I'm using Courier here, I believe version 3.0.8 on debian Linux. >Double-clicking messages (new & old) opens them no problems. > >With regards to your first problem - is your $rcmail_config['trash_mbox'] >set correctly for your server? On my Courier setup it has to be set to >'INBOX.Trash' and it works a treat. > >Ross > >Kennedy, Richard (Aventure Media) wrote: > >>So far, these are the problems we have found with RoundCube/Courier. >> >>- Delete messages is not working, they remove instantly, but when you >>login/go back to that folder, they are still there. >>- Cannot open messages until the dirty fix is used, messages will remain >>unread due to fix >>- Sending email seems to be causing a problem also, it times out, but on >>occasions appears to send >> >>We could also use a few alt tags on the icons as a side note, even I'm >>clicking logout on occasion instead of the delete icon :p >> >>Anyone have any idea of a release date for a fix or just a code change to >>resolve these? >> >>Richard >>

1 1

Problem with charsets.
by grayd_work 11 Oct '05

11 Oct '05

Hi! It's cool, that someone has made attempt to create open-source candy-look webmail client. Since all other open webmail clients ugly enough on a look. But, unfortunately, I have found, that in roundcube there are serious problems with charsets. Below I have put two files: one (charset-correct.jpg) shows, as the text looks before sending, and the second (charset-sent.jpg) as it looks after. The text is written in cyrillic charset windows-cp1251. Thanks for attention!

2 1

Quick word of thanks
by Erryn Pollock 11 Oct '05

11 Oct '05

First, I wanted to thank the developers for this web client. We love it here. Second, are we meant to put RFEs here or into the SourceForge system? I've seen several in the list in just the few days I've been on here. Third, is there a mailing list archive somewhere? Finally...thanks again, this thing is great. I'll be pestering you guys for enhancements. (I sent a couple of emails offering my assistance, but got no response, but I probably screwed that up somewhere.)

2 2

from address domain other than the domain of the imap server and auth integration
by justin 11 Oct '05

11 Oct '05

howdy, new to this list and this software, but i like what i see :-) we are evaluating roundcube for integration into a larger application. (after a week of hacking squirrelmail, i'm glad a decision was made to try roundcube...) a few of questions: my mail server is volta.babel.com.au, but i want my email domain to be babel.com.au. is it possible to set the from address domain to something other than the $rcmail_config['default_host']? i couldn't see an option for this. also, we want to integrate the authentication and error handling of roundcube into our application wide mechanisms. i've just hacked index.php so that a logged-in user has their inbox loaded without having to log in to roundcube. i'm wondering if making the authentication configurable, such that this can be done via some config options/plugins is desirable for roundcube? i'm happy to work on working up some patches if there's interest in this. pgp and s/mime: where is it at? we're going to need this, we've done it before and will do it ourselves again if needs be, but it would be better to work with something/somebody rather than just do it ourselves. comments? cheers justin

1 0

Courier Problems
by Kennedy, Richard (Aventure Media) 11 Oct '05

11 Oct '05

So far, these are the problems we have found with RoundCube/Courier. - Delete messages is not working, they remove instantly, but when you login/go back to that folder, they are still there. - Cannot open messages until the dirty fix is used, messages will remain unread due to fix - Sending email seems to be causing a problem also, it times out, but on occasions appears to send We could also use a few alt tags on the icons as a side note, even I'm clicking logout on occasion instead of the delete icon :p Anyone have any idea of a release date for a fix or just a code change to resolve these? Richard

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Dev