Attended a QCon back in...2017 I think it was? I voluntarily created a presentation for my team because it was truly an eyeopener as to how truly Jurassic the tech at my company was and I wanted to see what, if anything, we could adopt to spring forward to at least the Paleolithic. As of late 2020 we're still living before the Dawn of Man, but I think my team at least as progressed from the Jurassic to the Cretaceous. We're an investment bank - we're about as mobile and nimble as the Death Star experiencing engine trouble.
I did it volunteeringly. Describe the venue, how many people, setup (e.g. how many parallel tracks), what went well, types on attendees and sponsors. Was it very commercial or community driven? Then a list of presentations I visited and 3-5 bullet points unless a presentation was extra interesting. With an audience of 20 people I can't remember ever receiving a follow-up question so I wouldn't overthink the format, style or level of detail of such a report.
Yes but emphasize how what you've learned may benefit your organisation
I don't have to but I usually do and share with the team, is a good opportunity to evangelize what you liked and exercise leadership.
Yes, if you want to go to any more conferences. Need to show the value or potential value of the conference, and of you attending.
Usually, yeah. Might as well share the knowledge.
No. This question might be better as a poll
voluntarily during a group meeting, in other places nobody cared
No, all the non-developers like dev mgrs, product mgrs, tpms, marketing people that get a free ride to the "developer" conferences and spend a week getting kickbacks from vendors do not "create a report." So I would never. What is this grade school? If other devs want to learn they can watch the videos.
Seriously, all the other non developer people in the company that they send to a conference are going to be getting drunk, getting free meals, not paying for anything. I assume the OP is a developer, because no other profession they do this shit about writing a book report with. It is insulting, but just add it to the list of insults that developers have to endure in the workplace.