|
I am not understanding the early LUG contact and notification issue either. I know both Don and I did start contacting the hosting LUGS in and about the next city as the prior conference was cranking do. Getting several LUGS on conference calls to ask questions on topic and speaker date and evening of Special "Speaker of choice" on site LUG session. As well as discussions on LUG Booth , Expo and other freebies. I admit Chicago was a bit different. As it got nearer a family member was very ill and I could not attend. Our COMMON BoD LUG Liaison covered in my stead.
Since , I past the LUG Chair position on, I am not as close to the Orlando planning, but I have been involved with a few direct FLA. LUG communications as well as other informational calls.I have never seen a member LUG refused a meeting room in the evening beyond the Special LUG session if space was available, if they asked. The LUG committee, has always been open to member requests. IF there is a feeling a pre conference communication addition should be made to ask the hosting LUGs if they want an additional evening meeting room, then please make the request
In all the years I have been part of the LUG Committee, I have only been refuse two requests, and I fully understand why. It does not mean I agree with it but ... Hey when was it your life allowed you to get everything you wanted?
Glenn At 07:47 PM 8/10/2005, Don wrote:
OK....I'm going to raise an exception and concern here.In RECENT TIMES (since I started the LUG Committee and later!), I've yet to see COMMON conference management yet NOT be willing to make evening meeting room space available AT CONFERENCE to accomodate a LUG meeting, during conference, on conference real estate. Now, my budget hasn't let me goto all of the most recent conferences, but I know that all I was involved with as chair and as far as I know, all that Glenn was involved with as chair, and with ALOT of help from Maria, et al, went well with the LUG (where there was still a LUG) being able to hold a evening meeting at the conference, during the conference. And since COMMON posts their schedule a few years in advance, I've yet to see an affiliated LUG not be able to work with or around the COMMON posted schedule to alls mutual benefit. (OK, you can breath now).So, Paul, I don't get your point as frankly, I've not seen any problems with LUG meetings or benefits, in recent history, being an issues... What am I not seeing here? There's plenty other issues you and I agree on, but this one I just don't see...what am I missing here?(I'm waiting for Barsa to respond that I found yet another thing about COMMON I liked...Come on Al, make my day...:) :) :)Don in DC ------------------------------------------------------------------- On Wed, 10 Aug 2005, pnelson@xxxxxxxxxx wrote:The elephant doesn't really care about what's underneath when it puts its foot down. COMMON has been just as guilty of this as SSA, JDE, etc. COMMON is getting better, but you can bet that they don't check a LUG's meeting calendar before they schedule a conference. -- Paul Nelson Arbor Solutions, Inc. 708-670-6978 Cell pnelson@xxxxxxxxxx Glenn Ericson <Glenn-Ericson@xxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/10/2005 09:00 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, interlug@xxxxxxxxxxxx cc Subject Re: SSA steps on COMMON - might this be a broader trend for LUGs? Paul and others Do you think this same (protectionism) train of thought applies to other Local and Regional User Group events/meetings? Everyones feedback is invited, on line or privately Glenn At 09:47 AM 8/10/2005,Paul Nelson wrote:More like they're doing it intentionally, in order to have theircustomersnot be exposed to alternatives. -- Paul Nelson Arbor Solutions, Inc. 708-670-6978 Cell pnelson@xxxxxxxxxx Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/09/2005 08:43 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc midrange-l-bounces@xxxxxxxxxxxx, Bev_Russell@xxxxxxxxxx, interlug-bounces@xxxxxxxxxxxx, midrange-l@xxxxxxxxxxxx Subject Re: SSA steps on COMMON The only conclusion that I can draw is they they (SSA) are very stupid. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com pnelson@xxxxxxxxx m Sent by: To midrange-l-bounce midrange-l@xxxxxxxxxxxx, s@xxxxxxxxxxxx interlug-bounces@xxxxxxxxxxxx cc Bev_Russell@xxxxxxxxxx 08/09/2005 06:05 Subject PM SSA steps on COMMON Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> http://www.ssaglobal.com/gcf2005/index.aspx -- Paul Nelson Arbor Solutions, Inc. 708-670-6978 Cell pnelson@xxxxxxxxxx -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailinglistTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.