[jdev] [Fwd: [Interop] online testing environment]

[Peter Saint-Andre]

FYI.

To discuss, join the interop list:

http://mail.jabber.org/mailman/listinfo/interop

/psa


-------- Original Message --------
Subject: [Interop] online testing environment
Date: Fri, 19 Jan 2007 14:19:01 -0700
From: Peter Saint-Andre <stpeter at jabber.org>
Reply-To: XMPP Interop <interop at xmpp.org>
To: interop at xmpp.org

At the 1st XMPP interop event last July, we talked about building an
online environment for ongoing testing of XMPP-based software. I think
it's time to start making that a reality, especially since I mention it
at http://www.xmpp.org/xsf/roadmap.shtml :-)

Here's what I think the next steps are:

1. Define an agreement that members of the online testing system will
sign and adhere to. This will involve things like non-disclosure of bugs
found, use of the system only for protocol compliance testing (not for
scalability testing or whatever), etc. I will work up a draft of this soon.

2. Define who may join. I see this being limited to developers (or QA
testers) of XMPP-based software. No marketing people. No customers. Etc.

3. Define how it will work. I see two aspects:

a. Server instances will be hosted by the relevant project or company
and the XSF will simply point DNS at the IPs provided. So let's say that
the ejabberd team participates -- at the XSF we will point something
like ejabberd.interop.xmpp.org at an IP address that the ejabberd team
tells us about, and the ejabberd team will run that server on their own
hardware. Nothing will be hosted at the XSF infrastructure unless that's
absolutely necessary.

b. Client developers (and for that matter server developers) will
register at a website like https://interop.xmpp.org/ (no, that doesn't
exist yet). They will choose a preferred username to be set up at each
server instance. That way a given developer on, say, the Psi project
will be able to log in as psidev at ejabberd.interop.xmpp.org and so on.
We'll need to figure out some algorithm for password creation.

4. Make it secure. All connections (c2s and s2s) will be protected via
TLS. To make that easier, the XSF will issue certificates (both domain
and, in the future, end-user) through its intermediate certification
authority. Only authorized users (registered as above) will be allowed
to use the system. No in-band registration. Etc.

Anything else?

Peter

-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml


-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20070119/d23338d2/attachment-0002.bin>