Hi all,

First, excuse us for the problems some of you experienced a few hours
ago with OpenWengo's subversion repository - we were having some
problems with a change in the config.

The changes in the config that we were making are great, though... as of
now, there is an access to Subversion through HTTPS:
https://dev.openwengo.com/svn/openwengo

It's an unsigned certificate, but this should suffice for secure
password exchange.

The second good news is that unauthentified read-only access is now
allowed to the repository in both HTTP and HTTPS. You can forget the
guest password at last (see the URL above)!

Over the next few weeks, we will transition away from the http access
altogether, and use https only. For the moment, both will remain active,
and we will update all scripts and wiki pages that refer to the HTTP
repository (help is most welcome for this very exciting task).

We will also need to document how people with existing repositories can
migrate to https easily. I don't think svn switch will work, since the
protocol string means Subversion considers that it's a different repository.

Cheers,
Dave.

-- 
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
_______________________________________________
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to