Hey, Roshan! I appreciate getting your comments, since you're the "primary source". :)
The good news is that the new Drupal trademark policy draft falls in your favor, as it promises to apply some consistency to the use of the term. Further, entities currently using it (including me!) will have to request permission anew. So at least you're going to be on a level playing field there.
As for why Gloscon hasn't been listed at http://drupal.org/drupal-services... that's a very good question. Obviously I'm not privy to the details, but here's what I think's going on.
I think some misunderstanding ruffled feathers on both sides, and now there's bad blood. Further, that page is probably updated by someone who's overworked and underpaid -- by which I mean UNpaid. :) So updates to the page probably aren't a priority. In other words, it might not be personal.
If I were in your shoes, I'd make some more private inquiries before (as we say in the U.S.) airing your dirty laundry in public. If you don't get satisfaction after several weeks, make your own blog post that details the attempts you've made to be listed there, and the results. Be fair, understanding, honest, and polite (as I assume you have been so far :) ). Acknowledge your own errors, and make it clear that Gloscon is in this for the long run. That means both that you'll be there to continue to support Drupal -- but also that the issue won't go away. :)
Ultimately you might have to agree to disagree. Make a plan to do that well, too.
Hey, Roshan! I appreciate getting your comments, since you're the "primary source". :)
The good news is that the new Drupal trademark policy draft falls in your favor, as it promises to apply some consistency to the use of the term. Further, entities currently using it (including me!) will have to request permission anew. So at least you're going to be on a level playing field there.
As for why Gloscon hasn't been listed at http://drupal.org/drupal-services... that's a very good question. Obviously I'm not privy to the details, but here's what I think's going on.
I think some misunderstanding ruffled feathers on both sides, and now there's bad blood. Further, that page is probably updated by someone who's overworked and underpaid -- by which I mean UNpaid. :) So updates to the page probably aren't a priority. In other words, it might not be personal.
If I were in your shoes, I'd make some more private inquiries before (as we say in the U.S.) airing your dirty laundry in public. If you don't get satisfaction after several weeks, make your own blog post that details the attempts you've made to be listed there, and the results. Be fair, understanding, honest, and polite (as I assume you have been so far :) ). Acknowledge your own errors, and make it clear that Gloscon is in this for the long run. That means both that you'll be there to continue to support Drupal -- but also that the issue won't go away. :)
Ultimately you might have to agree to disagree. Make a plan to do that well, too.
Good luck!