[wp-hackers] Putting the P in WordPress

[Harry Metcalfe]

Agreed. If a sensibly designed survey says people don't care or think 
it's good I'll totally stfu.

Harry


On 06/07/10 16:13, Gavin Pearce wrote:
>> Ask the question, get the answer, act on it, and problem solved.
>
> Fully agree. In that order.
>
> Not: act on it, ignore the problem, pretend it goes away and send
> arrogant answers to people who disagree.
>
> Which is what has become the case here.
>
> G
>
>
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com
> [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Mitch
> Canter
> Sent: 06 July 2010 15:52
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] Putting the P in WordPress
>
> The core argument here is whether or not people would be OK with their
> blogging software having the ability to edit content (even if it's
> just changing the spelling) without their permission.  Why not ask the
> community?  A poll, a blog post, anything could be done where you
> simply ask the question:
>
> Would you mind if WordPress put code in your software that would
> autocorrect the spelling of the word WordPress?
>
> Explain why (branding reasons, continuity) and have someone draft the
> cons (principle of editing content, etc) and ask the people.
> WordPress is all about the community, this list isn't a good sample of
> that community (because we're all much more technically savvy than a
> lot of the users).
>
> Ask the question, get the answer, act on it, and problem solved.
>
> ~Mitch
>
> On Tue, Jul 6, 2010 at 9:42 AM, Gavin Pearce<Gavin.Pearce at 3seven9.com>
> wrote:
>>> I'm really not trying to be difficult! I just think this filter is a
>> terrible idea.
>> +1 :)
>>
>> _Ryan McCue
>>> If you're on this list, you should at least be able to do that.
>>
>> Yes I know! And various people have offered a patch to fix this bug,
> but
>> Matt/Core Team reckon it isn't open to discussion. That's what people
>> are getting so worked up about here ...
>>
>> The function is broke. It needs a fix commiting to core code. Like I
>> said before - end of topic as far as I'm concerned.
>>
>> _ mccormicky
>>> Isn't that true? So how can it change filenames? Anyway why are you
>> using uppercase for filenames? This is stupid!
>>
>> Don't know where to begin on this ....
>>
>> Firstly this filter does affect URI paths, it affects all/any content
>> put into the "editable" content area.
>>
>> Secondly, with the filter, it would now look for a file called
>> "filename-WordPress.jpg" - making it capitalised whereas before it
>> wouldn't have been (so the filter is actually causing the capitals
> when
>> you just said you hated capitals).
>>
>> Thirdly, on a Linux box there is many good reasons why to use case in
>> file-names, not least readability when you have several hundred files
> in
>> a folder.
>>
>> Finally, what bit is stupid?
>>
>> Gav
>>
>>
>> -----Original Message-----
>> From: wp-hackers-bounces at lists.automattic.com
>> [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Harry
>> Metcalfe
>> Sent: 06 July 2010 15:33
>> To: wp-hackers at lists.automattic.com
>> Subject: Re: [wp-hackers] Putting the P in WordPress
>>
>> I wrote a patch weeks ago to take it out. I'm really not trying to be
>> difficult! I just think this filter is a terrible idea. And it's a
>> little sad to witness the total lack of interest from the core team.
>> This isn't how it's supposed to work, IMO.
>>
>>
>>
>> On 06/07/10 15:17, Ryan McCue wrote:
>>> Matt Mullenweg wrote:
>>>> If someone made a better version of the function and benchmarked it
>>>> next to the current or some of our other formatting functions in
> some
>>>> real-world situations, that would be useful too, and add to the
>>>> discussion rather than the noise. I'd love to see wp-hackers return
>> to
>>>> more, well, hacking.
>>>>
>>>
>>> I'm staying out of the discussion apart for this reason. I'm not on
>> this
>>> list because I want to hear people bikeshedding irrelevant stuff like
>>> this, I'm here because I want to participate in discussions about
>>> hacking WordPress.
>>>
>>> Also, if the functionality is really that broken (affecting URLs,
>> etc),
>>> write a patch and fix it yourselves. If you're on this list, you
>> should
>>> at least be able to do that.
>>>
>>
>> --
>> Harry Metcalfe
>> Tel: 07790 559 876
>> Web: http://thedextrousweb.com
>> Twitter: @harrym, @dextrousweb
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
>

-- 
Harry Metcalfe
Tel: 07790 559 876
Web: http://thedextrousweb.com
Twitter: @harrym, @dextrousweb