[webteam] vendor lock-in, what the .... is it?

[Robert Martinez]

Sander Devrieze wrote:
> 2007/9/22, Robert Martinez <mail at mray.de>:
>   
>> Hal Rottenberg wrote:
>>     
>>> Can someone justify the existence of this field?  I don't think it's necessary.
>>>
>>>
>>>       
>> The vendor lock-in field marks projects that allow users only to use it
>> with only certain accounts.
>> google talk would be the most prominent here.
>>     
>
> Then you should choose something else than vendor lock-in: I also
> would call vendor lock-in all undocumented extensions to XMPP. I also
> would call all documented extensions without any interest and help of
> the software project to get them standardized in the future, vendor
> lock-in.
>
>   
This is about a client software listn not a documentation or extension 
judgement.
And if the -> jabber <- client does not actually work if you don't have 
the "right account" it is something very special.
The vendor lock-in field is thought to warn users (there is a small lock 
icon behind the name).
Every user expects that jabber is open after all!

I raised the question how to call this field in the chatroom once.
The feedback was a bit ambiguous imo.
I drew the conclusion that it might not be the best name (mainly because 
it has a negative touch), but decided to go with it because in this list 
it *is* negative in our context.

But you're welcome to make suggestions for a replacement name :)

Because the process of submitting software should be clear.