[webteam] welcome

[Sander Devrieze]

2007/7/9, Peter Saint-Andre <stpeter at jabber.org>:
<snip>
> For server admins and developers, there is a lot of information at the
> relevant project pages for ejabberd, Openfire, Loudmouth, Net::XMPP, and
> so on. No need to duplicate that. We can be a "clearinghouse" for links
> to those projects.

Agreed, and the same for clients. We don't need to duplicate their
documentation, we just should help Jabber projects to create
documentation by sharing knowledge of how the different projects
create their documentation.

> For managers and business people, case studies and lists of companies
> that use Jabber technologies would be very helpful (oh great, Sun and
> Apple and Google and Joost and Twitter all use this? I guess I'm safe to
> choose it, too).

We can create a list of case studies and allow Jabber projects to put
them on their website and to share other case studies with the rest of
the community using this community website we'll create. Projects then
can pick the case studies that they find the most valid for their
target group, so that these users don't get overloaded by too much not
relevant case studies. The list of companies can be used for Jabber
projects to write press releases.

> For end users, we can provide much more than they are getting anywhere
> else right now.

Client projects should do this, they just need to be helped to do this.

<snip>
> > Do we have a leader?
>
> I think that's me. So if you guys want me to be ultimately responsible,
> that's fine with me.

We don't need a leader B-) We only need someone to fix infrequent big
fights between contributors. The content on ejabberd.jabber.ru and
coccinella.im is made without a real leader; we just contribute stuff
and sometimes comment on eachother's contributions. AFAIR we never
needed some dedicated leader for this; the one that creates content is
the defacto leader.

<snip>

> > Internationalization is where the previous efforts to setup an end user
> > site stranded. It's very hard to create a site that allows multiple
> > languages, especially if you want to keep all those languages reasonably
> > up to date and if you don't want to require a 100% translation of all
> > content. Last time I looked (approx a year ago?) some efforts to
> > facilitate this were on the way but nothing mature enough yet. No idea
> > what the current status on this front is.
>
> I think this is hard for the reasons you mention. Maybe it's better to
> keep separate sites for now.

I don't think this was the main problem. I guess the problem was:
* it's a too ambitious project that requires too much effort
* people have different ideas for who is the end user

--> That's why I believe we should target the Jabber contributor
community instead, much easier and we all have the same goal: a
broader adoption of Jabber technologies. So, there will be no
conflicts that block the project because people have different goals.

> > I still think that the thing that the Jabber world lacks most is a very
> > good/strong end user site where people can just 'get started' with
> > Jabber. Jabber is still something just for geeks except for Google Talk.
> > It's almost impossible for Aunt Tilly to get started and the 'open,
> > distributed' arguments are probably not going to be enough to win her
> > over :) But that's a different discussion :D Main thing is that we
> > create a visually appealing site where it's trivial for people to figure
> > out what Jabber is and how to get started. All this is a few minutes
> > with a minimal amount of reading.
>
> Agreed.

Agreed, but I think this is the work for the different Jabber client
projects themselves. See e.g. http://coccinella.im/ ;-)

-- 
Mvg, Sander Devrieze.