From:
Justin Simoni
Subject:
Re: Change in Subscription Confirmation Process - RFC
In-Reply-To:
Re: Change in Subscription Confirmation Process - RFC
Date:
Fri Feb 10 20:11:02 2012
On Nov 16, 2007, at 6:31 PM, Rob Taylor wrote: > Thanks for giving us a voice in the development process. Can't wait > to start kicking the tires
The more voices, the better. The program is going to get a big boost in popularity and is also going to be used in ways it hasn't before in a really really short time. I'm going to need a whole lot of feedback real soon
I'll try to get a release out as soon as I can't find anything show stopping.
Right now, I'm still wrangling with dragons. Which is stressful.
|
<< Previous: Re: Change in Subscription Confirmation Process - RFC |
| Archive Index | |
Next: Re: Change in Subscription Confirmation Process - RFC >> |
This mailing list is to discuss the nerdy programming development of Dada Mail -
If you are just looking for support Dada Mail, consult the message boards at:
http://dadamailproject.com/support/boards
To post to this list, send a message to:
dadadev@dadamailproject.com
All subscribers of this list may post to the list itself.
Some on topic... topics include:
At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.
Please, please please familiarize yourself with the documentation at:
http://dadamailproject.com/support/documentation/
Since no one wants to answer the same question twice.
Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.
NOTE - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.