March towards 1.2.0

Team,

As we march towards our 1.2.0 release, there are new services that are
now available to our community. However there are some things that need
input from those that are involved in the project. Below are a few
things that i have in my que to work on, and i would like peoples input.

Site Certificate:

The new build system is online and uses SSL for administrative work. I
have put a temp cert on the machine, but was looking at putting a cert
that is signed by an authority that is in a majority of the browsers. I
have some options.
	a. Godaddy.com will give an open source project a 1 year certificate
for free. They say no strings attached, so that sounds promising. The
only problem that i see is we would need to renew the cert every year.
But not bad for free.
	b. Sign the cert ourselves and use that. The issue with this is that it
will be an annoyance to users with a prompt about the authenticity of
the cert. But we can make it last allot longer.
	c. Purchase a cert. The disadvantage of this should be obvious. But
this is an option.

We are also planing to migrate to Trac, and there may be parts of that
service that we would want to put behind ssl. So doing a wildcard Cert
may be something that we would want to do.

That is all i have discovered for Certificate signing and usage. If
anyone has anything more to add or other services that are available
please let me know.

If i don't hear back from anyone i will just decide on something myself.

Thanks


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/