When a websurfer goes to drupal.COM they get this error:
"Unable to connect to database server"
It looks like an incomplete install....
Not Professional.... THIS is a MARKETING Issue!
It would be more professional to have a redirect
set up with the registrar.
Even though I KNOW that it is drupal.ORG....
My fingers still haven't got the message on most days.
-Bob O
Comments
Comment #1
aruns4 commentedhttp://tech-arun.blogspot.com
i agree with you. i hope dries would have registered long back to keep his trademark safe. the official druapl.org contents may also would have hosted in that domain to show its not empty. but since they dint link it with MySql you see that error message.
Comment #2
damien tournoud commentedComment #3
dwwYes, this is a little annoying. However, this has been rehashed many times before:
http://drupal.org/node/86768
http://drupal.org/search/node/drupal.com
I'm tempted to mark this issue duplicate, but we probably should do something and there's no issue open in either the webmasters or infra issue queue about this. Seems like Dries decided to use acquia.com as his commercial drupal domain, so I'm not sure what the plans are for drupal.com itself. Until he comes up with a plan, it'd probably be nice to have a redirect in place.
Moving this to the infra queue, since this is really an infra question. However, nothing can happen here until Dries replies...
Cheers,
-Derek
Comment #4
dwwAlternative to a redirect would be a single page that says "Drupal.org is over there, acquia.com is over there, etc".
Comment #5
Amazon commentedI think the fundamental principled approach around the Drupal trademark, and Drupal web properties is to protect them on behalf of the community and ensure they are open and fair to everyone. So pointing to one company, wouldn't be consistent with that principle. But that's just a personal opinion.
I had floated the idea that drupal.com could become a revenue generating commercial market place for show casing Drupal businesses and offerings. But the Drupal.org redesign is my current priority.
Kieran
Comment #6
dwwAgreed. I only pointed out the landing page approach since technically Dries owns it and he'd be free to do with it as he pleases. I think a redirect to d.o would make more sense, but it's not my decision. There are all sorts of things that drupal.com *could* be someday. But, right now, it's just a DB error message, and that's sort of lame. ;) It'd take 2 minutes to make it just redirect to d.o, as an interim measure while things like the d.o redesign are underway.
Comment #7
keesje commentedIt seems like this issue is being addressed, drupal.com has a pretty site of it's own now, although work seems to be in progress.
So, fixed?