Matt and I coordinated off-list today and got our presentation proposals submitted to ApacheCon. Assuming they're all accepted, Log4j will have four presentations representing it. Go us!
Nick On Jan 31, 2014, at 11:25 PM, Nick Williams wrote: > Matt, sorry for the delay. I've had a bad cold today. Ick. Anyway, my > proposals are below. I haven't submitted them yet. Haven't seen your > proposals yet--can you get them to me ASAP? If you decide you're > uncomfortable committing to two presentations, I'm prepared to also take on > "Extending Log4j 2: Writing Custom Appenders, Filters, and Layouts" and leave > you to deal with just the first/intro one. I've been using the following > guidelines from the ApacheCon website: > >> • Choose a submission type (Presentation, Panel, BoFs, Tutorial) >> • Choose the category for your proposal (Developer, Operations, >> Business/Legal, Wildcard) >> • Provide a biography, including your previous speaking experience (900 >> characters maximum). >> • Provide us with an abstract about what you will be presenting at the >> event (900 characters maximum). >> • Describe who the audience is and what you expect them to gain from >> your presentation (900 characters maximum). >> • Tell us how the content of your presentation will help better the >> Apache and open source ecosystem. (900 characters maximum). >> • Select the experience level (Beginner, Intermediate, Advanced, Any). >> • List any technical requirements that you have for your presentation >> over and above the standard projector, screen and wireless Internet. > > ------- > Title: Log4j 2 in Web Applications: A Deeper Look at Effective Java EE Logging > Experience: Intermediate > > Abstract: The newly-released Log4j 2 includes much greater support than > previous versions for Java EE web applications and proper initialization and > deinitialization of the framework with the application lifecycle. The Servlet > and JSP specifications have changed significantly in the 12 years since Log4j > 1.2 first released. Some of those changes make logging easier, and some of > them make it harder. In this presentation you will learn about properly > configuring Log4j in a web application, what to do when the container is > using Log4j, how to log within your JSPs using the Log4j tag library, and > what to do when handling requests asynchronously. > > Audience Gain: The audience will gain a better understanding of the lifecycle > and class loader hierarchy of Java EE web applications and how they affect > the lifecycle and configuration of Log4j. They'll take a look at some of the > different ways to initialize and configure Log4j and learn when each approach > is appropriate and--more importantly--when it's not. They'll explore some of > the pitfalls of asynchronous request handling and learn about the important > tools that Log4j provides to help and the steps they must take to keep > logging working. Finally, they'll see that logging in JSPs is easy, too, and > doesn't require a single line of Java code. > > Benefit: This is one in a series of hopefully four different presentations on > Log4j lead by the Apache Logging community. These presentations will benefit > the community by providing exposure for the new version of Log4j, explaining > its benefits and strengths over other frameworks, and encouraging Log4j users > to improve the framework and contribute those improvements back to the > community. I am submitting two presentations and Matt Sicker is submitting > the other two. For the most part their order doesn't matter, but Matt's "An > Intro to Log4j 2.0: A New Generation of Apache Logging" should happen earlier > on the schedule than the other three. > ------- > > ------- > Title: Logging to Relational and NoSQL Databases with Log4j 2 > Experience: Intermediate > > Abstract: The newly-released Log4j 2 contains a number of different appenders > to help you deliver log events to the storage device you desire. Among those > are the JDBCAppender, JPAAppender, and NoSQLAppender, allowing you to store > your log events in essentially any database you can imagine. While very > powerful, configuring these appenders requires more knowledge and care than > configuring standard file appenders with the PatternLayout. In this > presentation you will learn more about these appenders, how to properly > configure and use them, and how to easily support your specific NoSQL > database of choice. > > Audience Gain: The audience will gain a better understanding of how these > three database appenders work. Configuring these appenders involves carefully > mapping log event properties to columns and creating appropriate database > tables and columns to match. Audience members will learn about these nuances > and explore the various options, as well as how to achieve the best > performance possible. Finally, only a few NoSQL databases are supported > initially, but creating support for new NoSQL databases is easy. The audience > will learn how to do this and also be encouraged to contribute their > creations back to the Log4j 2 source code. > > Benefit: This is one in a series of hopefully four different presentations on > Log4j lead by the Apache Logging community. These presentations will benefit > the community by providing exposure for the new version of Log4j, explaining > its benefits and strengths over other frameworks, and encouraging Log4j users > to improve the framework and contribute those improvements back to the > community. I am submitting two presentations and Matt Sicker is submitting > the other two. For the most part their order doesn't matter, but Matt's "An > Intro to Log4j 2.0: A New Generation of Apache Logging" should happen earlier > on the schedule than the other three. > ------- > > Nick > > On Jan 31, 2014, at 7:49 AM, Matt Sicker wrote: > >> Yeah that would work. Nashville huh? My co-worker is from there too, neat. >> >> In regard to the async and such, I think that'd be a great idea. One of the >> selling points of log4j over logback is performance, right? >> >> Matt Sicker >> >> On Jan 31, 2014, at 0:52, Nick Williams <nicho...@nicholaswilliams.net> >> wrote: >> >>> >>> On Jan 30, 2014, at 9:25 PM, Matt Sicker wrote: >>> >>>> On 30 January 2014 18:01, Nick Williams <nicho...@nicholaswilliams.net> >>>> wrote: >>>> Matt, >>>> >>>> Do you want to share a hotel room? I know it would certainly help my >>>> finances to split one, and depending on whether you get employer support, >>>> it should probably help yours as well. I'm planning on being there all >>>> five days (staying in the hotel Sunday night through Thursday night)—you? >>>> >>>> Sharing a hotel room sounds like a good idea. I'm not sure on which days >>>> I'll be there, but it would most likely be almost if not the same ones. >>> >>> Okay. I'm registering and booking my travel tomorrow (Friday, which I guess >>> is actually today now). Should I book the hotel, too, and then you can just >>> pay me for your part depending on how many nights we split it? That >>> arrangement. works fine for me. >>> >>> By the way, I'm in central time, which is why the website say >>> America/Chicago. I'm actually in Nashville, though. >>> >>>> >>>> I was planning on putting together several CFPs. Originally I was thinking >>>> about these four: >>>> >>>> - An Intro to Log4j 2.0: A New Generation of Apache Logging >>>> - Log4j 2 in Web Applications: A Deeper Look at Effective Java EE Logging >>>> - Logging to Relational and NoSQL Databases with Log4j 2 >>>> - Extending Log4j 2: Writing Custom Appenders, Filters, and Layouts >>>> >>>> I really like those ideas. You've effectively modularized all the ideas I >>>> had for CFPs. I'd be interested in doing any of those, but I have the >>>> least experience with the myriad Java EE technologies out of those four. >>> >>> Why don't you write up a CFP for the first and fourth ones? Be sure to >>> include the performance studies mentioned on the website and information >>> about the Levels and their extensibility, the logger interfaces, etc. in >>> the first one. I'll write up the CFPs for the second and third one. Before >>> we submit them, let's trade them with each other for review, proofreading, >>> and comments. How about we plan on exchanging them about 6 p.m. CST Friday >>> evening and then submitting them by 10 p.m. CST Friday evening. Sound good? >>> >>> Look forward to working with you on representing Log4j at ApacheCon. >>> >>> Nick >>> >>>> >>>> Before you write up your CFPs, lets coordinate and come to a consensus on >>>> which of us is doing which CFP. Having two people there covering Log4j >>>> would be great! >>>> >>>> I've only drafted out a couple ideas so far, but they match up with one as >>>> your first one, and the other a union of the remaining. >>>> Nick >>>> >>>> On Jan 30, 2014, at 8:42 AM, Matt Sicker wrote: >>>> >>>>> I know I'm not a committer (yet), but I would be interested in doing a >>>>> talk on logging. I'll see if I can get employer support as well. Is >>>>> anyone else interested in putting together a CFP or two? I'd like to >>>>> cover the neat new features in log4j, why we're more awesome than SLF4J, >>>>> how to use logging effectively (e.g., using aspects to inject trace >>>>> logging, using informative log messages, effective usage of the API, when >>>>> to use different levels, using markers, complex logging configurations, >>>>> etc), how to help make log4j compatible with other logging APIs not >>>>> already implemented, creating additional components (I.e., appenders, >>>>> filters, layouts, etc.), and many other ideas. Obviously that's too much >>>>> to cover in one talk, but it's a good place to start examining what >>>>> topics to cover and at what levels of expertise. >>>>> >>>>> Matt Sicker >>>>> >>>>>> On Jan 28, 2014, at 11:29, Nick Williams <nicho...@nicholaswilliams.net> >>>>>> wrote: >>>>>> >>>>>> Guys, let's show up for Apache Logging! They're hurting for CFP's right >>>>>> now. Rich Bowen at ApacheCon assures me that if money is an issue >>>>>> getting committers to come and lead talks, the Travel Assistance >>>>>> Committee will do everything it can to help you get there. Email them at >>>>>> t...@apache.org. >>>>>> >>>>>> I'm definitely going and I'll submit a CFP as well. I'm open to >>>>>> suggestions. Let's try to get 3-5 good Apache Logging talks in from >>>>>> different people! If we can get two PMC members to come, we can even >>>>>> have a summit, which would be great exposure! We need to coordinate so >>>>>> that we're covering different topics and not stepping on each other. >>>>>> >>>>>> I NEED A ROOMMATE AND YOU DO, TOO! Hotel is the biggest expense for >>>>>> this--more than flights and committer registration combined. I'm looking >>>>>> for someone who wants to go and is willing to share a hotel room and >>>>>> split the cost. If we can get 4 Logging guys there, we can use just 2 >>>>>> hotel rooms and save a bunch of money. I plan on flying in Sunday night >>>>>> and checking out of the hotel Friday morning--that's five nights. If >>>>>> someone can only share the hotel for 3 nights, we can split the price >>>>>> accordingly. >>>>>> >>>>>> Inline below I have included the answers I got to some questions I asked >>>>>> Rich. >>>>>> >>>>>> I hope some of you will come to ApacheCon with me! It'll be a great >>>>>> opportunity to publicize Log4j 2.0 GA! >>>>>> >>>>>> Nick >>>>>> >>>>>>> On Jan 27, 2014, at 6:21 AM, Nick Williams wrote: >>>>>>> >>>>>>> - What exactly is a project summit? >>>>>> >>>>>> Rich: Some projects are taking the opportunity to have a "summit" of one >>>>>> kind or another, to do sprints on features, or to discuss the direction >>>>>> of the project, or to do bug triage, or whatever. A project summit is >>>>>> whatever you want to make it, if two or more members of the PMC are >>>>>> together in a room to make it happen. >>>>>> >>>>>>> - What exactly is a tutorial and how is it different from a talk on the >>>>>>> normal days? >>>>>> >>>>>> Rich: A talk is 50 minutes. A tutorial is 3 hours. That's the main >>>>>> difference. A tutorial is usually more indepth, with hands-on elements - >>>>>> more of a training class than an overview. >>>>>> >>>>>>> I noticed the fee is normally $799 (until Friday, then $1099), but it's >>>>>>> $275 for "committers." That means that anyone who's a committer on any >>>>>>> Apache project whatsoever /only/ pays $275 to attend the entire >>>>>>> conference, right? >>>>>> >>>>>> Rich: That's correct. >>>>>> >>>>>>> >>>>>>> The registration page says there is an additional fee for tutorials on >>>>>>> April 10th: "$399 for ½ day tutorials ($299 for students) and $749 for >>>>>>> full day tutorials (students and attendees)." What it doesn't say is: >>>>>>> 1) Is there an additional fee for tutorials on April 10th for >>>>>>> /committers/? >>>>>> >>>>>> Rich: Yes, tutorials have a fee for everyone. >>>>>> >>>>>>> 2) Is there an additional fee for tutorials on April 11th for anyone >>>>>>> (it only mentions April 10th, but the schedule shows tutorials on April >>>>>>> 11th as well)? >>>>>> >>>>>> Rich: We'll get that fixed. >>>>>> >>>>>>> 3) Is there an additional fee for project summits on April 10th or 11th? >>>>>> >>>>>> Rich: Project summits are usually open to anyone interested in the >>>>>> project, and no extra fee is charged. >>>>>> >>>>>>> It says they will have 5-9 tracks going on this year. I assume that >>>>>>> means 5-9 conference rooms (based on the # of CFPs submitted), which >>>>>>> means 5-9 simultaneous talks can occur. >>>>>> >>>>>> Rich: That is correct. >>>>>> >>>>>>> It sounds like there is potentially time to have multiple talks on >>>>>>> Apache Logging. Though I am new-ish, I'd love to present on behalf of >>>>>>> Apache Logging. Do we want to have multiple talks? >>>>>>> >>>>>>> Nick >>>>>>> >>>>>>>> On Jan 26, 2014, at 9:29 PM, Ralph Goers wrote: >>>>>>>> >>>>>>>> I would like to attend but I’m not sure I can. >>>>>>>> >>>>>>>> Ralph >>>>>>>> >>>>>>>>> On Jan 25, 2014, at 11:11 AM, Christian Grobmeier >>>>>>>>> <grobme...@gmail.com> wrote: >>>>>>>>> >>>>>>>>> Hi folks, >>>>>>>>> >>>>>>>>> I would like to remind you ApacheCon is happening in April 2014. >>>>>>>>> If you would like to submit your talk, now is the chance. >>>>>>>>> >>>>>>>>> I think it would be great to have somebody presenting our Logging >>>>>>>>> frameworks. >>>>>>>>> I will not be there unfortunately. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Christian >>>>>>>>> >>>>>>>>> --- >>>>>>>>> http://www.grobmeier.de >>>>>>>>> The Zen Programmer: http://bit.ly/12lC6DL >>>>>>>>> @grobmeier >>>>>>>>> GPG: 0xA5CC90DB >>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >>>>>>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >>>>>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >>>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >>>> >>>> >>>> >>>> >>>> -- >>>> Matt Sicker <boa...@gmail.com> >>> > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
