[JDEV] Best way to drive Jabber adoption?

[Steven Brown]

> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> Justin Karneges
> Sent: Friday, June 13, 2003 8:59 PM
> To: jdev at jabber.org
> Subject: Re: [JDEV] Best way to drive Jabber adoption?

> However, we still
> need that "single place where people can go" to back it up.  We need a
> reliable free server devoted to end-users, with an easy client
> that uses that
> server by default.

IMO, that's the wrong direction.  What you need is to make it out-of-the-box
_zero-configuration_ support existing user groups, and make sure all the
distributors have that version.  E.g., a rpm install that uses the system's
user list and passwords via pam by default (so it'll do UNIX passwords,
LDAP, etc.) or whatever pam equiv. Windows uses, and easily support Apache
user/password groups (as many user communities are web auth. based).
Organizations want to just drop Jabber service into their existing setup.
Making it so trivial that most people just enable it by default when
installing a server will get rid of the 'what server do I use' issue, and
eliminate the hassle of creating an account to boot.  That's the way Jabber
is designed to be used, one server per community.  It'd happen by itself if
it wasn't extra work.  Remove the extra work. :)