[webteam] web saccount creation

[Robert Martinez]

Adam Nemeth schrieb:
> On 8/1/07, Robert Martinez <mail at mray.de> wrote:
>
>   
>> I have drafted some mockups for a possible 3-step-wizard.
>> Can someone please confirm how realistic this idea is?
>> If it turns out we have to solve this completely differently we might
>> need new mockups.
>>
>> There is also a new version of the front page and  a client node mockup:
>>
>> http://wiki.jabber.org/index.php/Jabber.org_relaunch
>>
>>     
> Definitely not bad :) (ok, great... ;)
>
> Here are my points though what would need to be changed
>
> 1) While it's OK that GTalk, LJTalk and a few others are the most
> popular, we should put there some list for not-just-jabber services,
> for the sake of correctness and a quick scroll-up (like a html
> <select> with a height of 10 rows or such), or at least some link.
>   
Did I get you right:
You just want to have big logos for "jabber services ONLY" and a textual 
list of providers that offer a jabber account ALONG with many other things?
I'm sure the list needs to be completed, changed and re-ordered and so 
on... it is just a mockup fpr now.
I think you get the idea what it should look like in the final page ;)
> 2) I think that the country of residence does not matter that much for
> a lot of users, however, general opinion, number of users (like:
> there's definitely more life on conference.jabber.ru than our MUC
> server :) could count much more...
>   
The fields that are actually used to filter in the wizard are 
placeholders, too.
We can have a discussion about what exactly will have to be filtered.
I strongly recommend that we use a SIMPLE version of our database 
filtering with reasonable presets.
The wizard should be hassle free with few options and a quick result.
Browsing the database the NON-wizard way should be completely 
"customizable" with an endless option to filter by any possible criteria.
> 3) Client nodes would also need some "social processing tools" (it's a
> research buzzword: rating, commenting, tagging, implicated measures
> like numbers of download, trust network, etc; shows the relevance,
> popularity of the client for example)
>
>   
This is true. Stuff like reviews or rating may be of interest.
Once we have that features I'll look into updating the  nodestyle.
Besides: My mocup isn't really compelte here either, the bottom is 
missing (XEPs, code language etc...)
 - This is just a rough idea so I can start theming with the consens of 
everybody else.
> 4) Generally, filtering interface should be improved, although kept
> simple - this will be a serious task. I mean, I'd need a (theoretical)
> jabber client which handles avatars, voice, and video on OS X, and I
> want it to select this out AJAX-style (realtime filtered list).
>
> (I can help with the JS part)
>   
Help is appreciated since I don't consider myself a coder, and we 
certainly need to tweak MUCH stuff to teach drupal how to behave ;)
> 5) We should filter out the features which does count; probably we
> should also note incompatibilities (Gizmo can't talk with Neos MT,
> since the first is SIP, the other is H.323 on voice etc)
>   
This will be covered by our XEP matrix.
Both clients would have a VoIP Feature, but Gizmo would be missing some 
XEPs.
We could then filter all VoIP-compatible clients Neos by XEP.
Maybe we run into problems that way and we will have to come up with 
another solution?
I think this kind of incompatibility is a challange, but we need to make 
it transparent WHY something does not work like an ordinary user would 
expect it. (also file transfer etc)
This is pretty advanced stuff and we should consider it NOW, even if we 
need to focus on the most basic things at the moment.
> The last point will need a lot of work; I think we don't have
> resources for a marketing research (what people DO need), but we'll
> have to refine this iteratively (could those stats be public?:)
>
> Anyway, it's a good start, congratulations! :)
>   
Thanks!