[SM-ANNOUNCE] Request for Official Development Servers

[Paul J. T. <cap...@sq...>]

To the SquirrelMail Project Team:

   Do you want to make thousands of dollars a day with
   little or no effort! Well, I did and so can you!

Just kidding, I wanted to make this sound like the SPAM that fills
my email box every day. Urgh. Anyways, PLEASE keep reading as I
actually had something interesting to say.

With our recent rash of "dang, that doesn't work on YOUR imap
server" bugs, it has come to my attention that we need better
testing facilities.

So, in light of this concept, I would like to establish a collection
of servers that we can use as "Official Development Servers". These
would be machines which had a variety of SquirrelMail configs for
testing code as we work on it in CVS.

Accounts on these machines would be managed by SquirrelMail
leadership and handed out strictly for SquirrelMail development
purposes.

However, of course, we need these machines before we can start
handing out accounts to them. So, this email is a request to the
SquirrelMail Project Team as a whole to see who might have machines
that we might be able to use for such purposes. Here are the way I
would like the rules to be able to stand for the machine:

  1. Of course, as stated above, access would be handed out
     for SquirrelMail development efforts alone. Therefore,
     not a great amount of traffic should be generated on them.

  2. When possible, I would like these machines to be dedicated
     SquirrelMail development boxes. If this is not possible, we
     would of course be willing to settle for sharing something.
     However, considering the low usage requirements, I would be
     willing to bet there are enough hosts out there for this.

  3. I would like for account management to be handled by the
     SquirrelMail leadership team (me and others). This leadership
     team is managed by me, so if you feel you can trust me, then
     you can trust the leadership team. The purpose of this "rule"
     is so that we do not have to go through the process of asking
     for accounts to be created whenever the are needed, etc. This
     would presumably infer us having root access to the box.

  4. All shell access to the box will be accomplished either
     through the local terminal (not likely ever for most boxes)
     or through SSH.

  5. It will be assumed that the machine need not be backed up,
     or recoverable in any means in the case of a crash. This
     simply means that we don't need anything fancy. We will not
     be storing irrecoverable data on it, or at least developers
     will know that anything stored on it is possible to be lost
     if something bad happens.

Those are our basic needs, as I can think of it. If anyone feels
they can help us out in these ways, please contact me at the contact
information listed below. In the past, I have recieved a couple of
emails from people volunteering boxes. If you get this message,
please speak up again to me now. Otherwise, I will be finding your
message in my archive and contacting you personally, just in case
this message does not find it's way into your email account.

Here are some profiles of boxes that we need.

  * UW IMAP Server (required)
  * Courier IMAP Server (required)
  * Cyrus IMAP Server (required)
  * Exchange IMAP Server (required)
  * Other variety of setups (as available)

If all else fails, I have a box that can be used for one of these
categories (except Exchange, of course, as I don't OWN it). However,
that box is behind a cable modem connection that may go down from
time to time and is technically NOT supposed to be used for hosting
things, so I would prefer not to use it for such things.

Thanks for your patience, people. I hope that you are enjoying
SquirrelMail 1.2. I am enjoying it, as am I enjoying being a dad for
the second time.

Here's to hoping the best for SquirrelMail 1.2, 1.3, 2.0 and beyond!

-- 
Paul Joseph Thompson
cap...@sq...
AIM/Yahoo/MSN IM: Captain Bunzo
ICQ Number: 38801719

(Sorry to the people on both the announce and devel list who may
have got this message twice.)