[drupal-devel] what do you call a rose?

[Bèr Kessels]

No one in this thread has problems with #4. I think everyone will love 
improvements that make the overall feeling for Drupal better. 

The dispute, however remains. And let me try to re-explain this by the (never 
ending) taxo vs catogory issue:
- If a user inserts a post on a drupal site he/she will never see the word 
node or taxonomy or category. He/she sees 'Site Classification' Or 'Choose 
City' or whatever the **admin** chose for that taxonomy tree.
- If an administrator gets a Drupal site to administrate, and he/she wants to 
add content classifications, or a city per post, he/she SHOULD search 
drupal.org, or mail the support ML, and recieve the very nice posts about how 
to use taxonomy. ICW with some introductionary texts about taxonomies. 
- If a site administrator is too lazy to do that, or too new to all this, 
he/she is simply not up to Drupal. Hhe/she should then print the handbook and 
read some articles about managing a site. 
- But if a site administrator sees 'categories', chances are very big that he 
or she will never think of the possibility to add cities in there! Nor that 
he/she will read in the handbooks that this is a very good example use of 
taxonomy. 

We want to get all this as easy as possible, really, but making complex 
features simple by ONLY naming them easy, is not the solution. Making them 
easy, as a whole, is not easy, but that, acc to many people in the thread, is 
the real solution. So that we really make things simple. Not only make then 
appear simple. But that is hard. really hard.

Bèr 'Lets make things better' Kessels :)

On Monday 03 October 2005 18:52, Kobus Myburgh wrote:
> Okay, let me get this straight. What reasons may there be to create an
> excellent piece of software like Drupal?
>
> 1. Personal fame (and maybe a resume) of the developers.
> 2. Financial gain.
> 3. A sense of personal victory.
> 4. The desire to create something special for the world.
> 5. Investing of time something that you use and have considerable control
> over its development, as opposed to an out-of-the-box commercial system
> which is often a pain in the backside.
>
> Okay - that's just a few of the most important reasons why you would
> develop Drupal.
>
> Now...
>
> Let's go through these items:
>
> 1. Sure - everyone knows who Gerhard is.
> 2. Maybe - I don't know if you charge your clients, or even if you have
> any. Probably. 3. Yes - but this depends on your nature. Are you a person
> who challenge the status quo? Yes. Okay. 4. Hmmm... - it will not be
> special to the world if you would make it difficult for them to use it. 5.
> Yes - this would probably be one of your main reasons if Drupal was yours.
>
> Where am I going with this? Simple:
>
> You may not want to focus on item #4, or feel inclined that if the world
> will not fit in, they must move out, but, in reality, if everyone felt the
> way you do, where would Drupal be today?
>
> Regards,
>
> Kobus
>
> >>> killesreiter at physik.uni-freiburg.de 10/3/2005 6:42 PM >>>
>
> On Mon, 3 Oct 2005, Kobus Myburgh wrote:
> > Your point is taken, however, who is going to do the education? You? Me?
> > Other members of the team? Sure, we can make a best effort, but will we
> > reach them all, due to the dynamic nature of Drupal's user base?
>
> The people are supposed to educate themselves by means of the docs we got
> to provide. If they are too lazy to read it is their problem if they stay
> dumb and cannot use excellent software.
>
> Cheers,
> 	Gerhard