<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'>From your manager's comment, I think that you can give the type of talk we want. Talk<br>to Mike Burton about when to give a presentation.<br><br>----- Original Message -----<br>From: "Mike Bean" <beandaemon@gmail.com><br>To: "CLUE talk" <clue-talk@cluedenver.org><br>Sent: Wednesday, December 1, 2010 9:12:49 AM<br>Subject: Re: [clue-talk] possible VMware presentation<br><br><br>Let's park the idea for the moment. I don't have a good way to reach<br>Mike Burton, but it still sounds like this is a sore spot, point of some<br>discussion, and I think I can speak with some confidence to the effect<br>that we (VMware) don't particularly want to go where we're not invited.<br><br>To illustrate, here's the last quote I got from my manager on the<br>subject<br><br>"No problem. I would say that I've seen the presentations from the SEs<br>and they are semi technical, not sales pitches. More like feature sets<br>and how products and features work. The LUG needs to clarify what they<br>want. But it's up to them to take the next step as we're likely able to<br>provide whatever they want, assuming that isn't something silly like<br>kernel architecture for example."<br><br>Mike Bean<br><br>(Mike Burton, on the off chance you see this, please let me know<br>beandaemon@gmail.com; we might be able to take some of the discussion<br>off the mailing list. Quit spamming people quite so much = )<br><br>On Tue, 2010-11-30 at 20:43 -0700, David L. Willson wrote:<br>> Mike Burton is the speaker coordinator. If you can't get a hold of<br>> him, Dennis Perkins is club president. December is already booked. I<br>> don't know what's booked for January, February, etc...<br>> <br>> David L. Willson<br>> Trainer, Engineer, Enthusiast<br>> RHCE MCT MCSE Network+ A+ Linux+ LPIC-1 NovellCLA UbuntuCP<br>> tel://720.333.LANS<br>> Freedom is better when you earn it. Learn Linux.<br>> <br>> ----- "Mike Bean" <beandaemon@gmail.com> wrote: <br>> > At the risk of throwing fuel on the fire, my manager did get back to<br>> me today. He said the sales guys are "willing to participate in the<br>> LUG, depending on the details", and he asked me for a specific<br>> point/person of contact they could contact to discuss it. So, is<br>> there a specific person/means they should contact??<br>> > <br>> > In terms of the debate, as to what's appropriate, and what isn't, I<br>> can only speak on my own behalf, but I would think they're likely not<br>> going to do it out of the generosity of their hearts. Even if they<br>> don't give the full-on sales pitch, they'll likely just see it as an<br>> excuse to network among like minded people, which, as long as I'm<br>> being honest, is one of my many reasons I went to my first CLUE<br>> meeting a while ago, so I can't really point a finger at that. (no<br>> moral highground).<br>> > <br>> > I would just advocate a principal of honesty, that we describe the<br>> group, and let them decide what kind of presentation they want to<br>> give. (perhaps nudge them towards matters technical.) Once that<br>> decision is made, make that information public. On Day X, VMware<br>> reps will be hearing doing X presentation. If people aren't<br>> interested, or would be uncomfortable, (shrug), they don't have to<br>> come.<br>> > <br>> > For my part, I can only offer to do what I can to help both sides of<br>> the aisle. If there are ESX/ESXi questions they can't answer, that I<br>> can, I promise not to remain shy.<br>> > <br>> > _______________________________________________ clue-talk mailing<br>> list clue-talk@cluedenver.org<br>> http://cluedenver.org/mailman/listinfo/clue-talk<br>> _______________________________________________<br>> clue-talk mailing list<br>> clue-talk@cluedenver.org<br>> http://cluedenver.org/mailman/listinfo/clue-talk<br><br><br>_______________________________________________<br>clue-talk mailing list<br>clue-talk@cluedenver.org<br>http://cluedenver.org/mailman/listinfo/clue-talk<br></div></body></html>