[wp-hackers] Putting the P in WordPress

[Gavin Pearce]

> A problem here, is that anyone thinks 20 people in an email conversation is
> a 'vast majority'. It quite simply is not. So the vast majority *of
> WordPress users* have no opinion on this.

Not really a fair sample here - 20 people who have strong technical background of Wordpress - one just need flick through TRAC or various forums to see of non-technical users reporting the same issue. It shouldn't matter how many people say it's a bug - if just one person reports a bug, (bug purposely used instead of feature) that's enough reason to look into fixing it. This does break things for some non-technical users. I consider the fact it breaks things to be the end of discussion on whether it causes issues or not - it needs looking into one way or another.

> Again, "many users" is simply not true in the grand scale of things, and
> WordPress *is* on a grand scale.

20 users reporting the same issue is "many" users in comparison to many of the WordPress bug reports.

> As has already been pointed out, there is a plugin to turn it off, so no-one
> has to edit source thanks to the wonderful thing that is WordPress and it's
> auto plugin installation. It is no harder than installing any other plugin,
> several of which turn off other filters that are active by default (about
> which I see no protracted debates).

Core code should only be code that really matters - filters like this should be "installed" by a plugin, not "deactivated" by a plugin.

> As has been pointed out on this thread, WordPress is a trademark, and as
> such *must* be actively protected, otherwise the trademark status will be
> lost.

As also pointed on this thread - that's complete rubbish. If enough people start writing MicroSoft, that doesn't "loose" Microsoft's right to the trademark. The only time this would be any issue in the slightest, is when trying to protect an "unregistered" trademark. 

End users writing Wordpress, Wordress, wOrDpReSs, WORDPRESS etc doesn't affect the trademark in any way whatsoever. (slightly different if WordPress foundation started doing it).

(http://www.uspto.gov/trademarks/law/index.jsp | http://www.ipo.gov.uk/types/tm.htm)

Gav


-----Original Message-----
From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Mike Little
Sent: 06 July 2010 10:53
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] Putting the P in WordPress

On 6 July 2010 10:32, Gavin Pearce <Gavin.Pearce at 3seven9.com> wrote:

>
> 1) The vast majority of people seem to be in favor for it being removed
> (REF# TRAC, this thread, forums).
>

A problem here, is that anyone thinks 20 people in an email conversation is
a 'vast majority'. It quite simply is not. So the vast majority *of
WordPress users* have no opinion on this.



> 2) It *does* break things for many users (some of them are non-technical
>

Again, "many users" is simply not true in the grand scale of things, and
WordPress *is* on a grand scale.



> so they won't be editing source) - fact.
>

As has already been pointed out, there is a plugin to turn it off, so no-one
has to edit source thanks to the wonderful thing that is WordPress and it's
auto plugin installation. It is no harder than installing any other plugin,
several of which turn off other filters that are active by default (about
which I see no protracted debates).



>
> At the end of the day who CARES if WordPress is Wordpress, Wordress,
> wordPress or anything else -


As has been pointed out on this thread, WordPress is a trademark, and as
such *must* be actively protected, otherwise the trademark status will be
lost.


Mike
-- 
Mike Little
http://zed1.com/
_______________________________________________
wp-hackers mailing list
wp-hackers at lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-hackers