Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

Hi All, It seems that the Call For Papers has a new date for submissions Call for Papers Closes March 11, 2016 Regards Ravi Sharma On Sun, Mar 6, 2016 at 5:48 PM, arslist wrote: > ** > > I have submitted my problem trying to get to where we can vote, I am >

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered? URL error fixed below

Thanks for that correction! I just got an email that the deadline is extended to March 11, so you have a little more time to submit something! From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of arslist Sent: Monday, March 07, 2016 5:52 AM To:

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered? URL error fixed below

I head back from support, apparently the problem is that if you click on the URL we were given, the final ] is not part of it I should have noticed that it was black on my screen not blue... The following works https://communities.bmc.com/community/engage/content?filterID=contentstatus[

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

I have submitted my problem trying to get to where we can vote, I am wondering if anyone else is getting this? When I try to get there, logged in with my Communities ID, I get: "The area of BMC Communities is visible to registered logged in users. If you are logged in when you receive this

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

Everyone, I would strongly encourage you to use the Communities Forum for Engage for submitting the "I would like to see but I am not the presenter" type topics. That gives visibility to the ideas to everyone. It gives a chance to vote if interested. It may give you new ideas of things to

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

Some of the topics were submitted as Ideas on the Engage forum - you can vote on those

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

Where would we get to see a list of ideas that are submitted? Would that be an internal list for BMC to review or will that list be published for feedback or ratings on ideas that are submitted? Personally I feel the later is a better idea than having those ideas filtered by BMC internally.

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

Yeah - What he said! We've had people comment in the past that there weren't enough topics for the more technically knowledgeable of you; or not enough topics on things that interest you. So please do flood us with topics of interest! Of course, "no guarantees" and all that. But would be great

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

Everyone, I just want to step in here in support of Daniel's suggestion and to encourage you all to submit ideas. If you have a topic you are passionate about and have expertise in that others would like to know, please submit a talk. You get a free pass to the conference if your talk is

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

A few topics I'd love to see are: 1) How to best secure Smart IT and My IT. 2) How to best set up Smart IT and My IT to scale in a production environment. 3) How to build integrations with My IT. 4) What is AppZone and how can it be used. 5) How to add custom

Re: Engage 2016 Call for Papers - due March 7 - a discussion suggestion .... technical topics to be covered?

let us assume that if we indicate some highly technical development related topics quickly, that someone who knows that area would submit it if we showed interest, or that BMC would fill in what we can't. Possibly one might be how to read the new java logs for the core and quickly know what