Back in 2012, I first experienced Uber. While I assume everyone knows what Uber is, just in case you don’t, it is a ride service that heavily leverages modern technology to disrupt the livery/taxi industry.
When I first used Uber in 2012, it was limited to “black cars”, vehicles like Town Cars on the higher end of the scale, and the price reflected it. Now they have a number of different options, such as UberX (similar to a taxi), UberPool (more of a ride share version of UberX), UberSushi, UberMusic, etc. (okay, I made the last two up).
I had a rather positive experience with Uber back in 2012, but I rarely had the chance to use it much after that. Later, when I started reading about some “evil” things they were doing, I wasn’t inclined to call on them when I needed a ride, and their Android app seems to need an awful lot of permissions in order to work correctly, so I wouldn’t install it.
I am currently spending a few days in San Francisco, and when I landed at SFO I decided to take a taxi instead of BART. I like BART, but I was running late and also had a fairly large suitcase with me, so I opted for the convenience of a cab.
It was a bad experience.
When I approached the cab stand, I was assigned the next cab in line. This was car 226 from “Veteran’s Cab Company” and it was a very tired Toyota Prius. The driver seemed more interested in listening to music on his phone and texting than getting me to my hotel.
He repeatedly ignored my requests that he not text and drive, and as I was watching for the best routes on Google Maps, he also ignored my requests to take me on the faster route. Outside of putting my life in danger, he probably cost me an extra $10 and an extra 15 minutes.
I did survive the trip, and I checked into the hotel, dropped my bags and headed back out because I was meeting a friend and we were going to take BART to the East Bay.
Although her house was only a 10-15 minute walk from BART, she was in heels and decided that we would catch a ride with Uber. This was UberX. The driver was waiting for us in an immaculate Prius and promptly took us to the house. As I ended up staying there past the time that BART stopped running, they called me another UberX ride to take me back to the hotel. This was also in a Prius, clean, and the driver was very friendly and safe.
It is hard to express the stark contrast between the experience of a normal taxi versus Uber.
I was in town for the EFF’s 25th anniversary party. While I walked to the “minicon” they held during the day, I decided to take Uber to the evening party. I dusted off my Uber account, updated the credit card, and called for a ride.
Within three minutes Ye showed up in a nice Toyota Camry. The route to the DNA Lounge was already in his phone, adjusted to avoid traffic, and the trip was quick and pleasant. As everything is paid for via the app, I had nothing to do but enjoy the ride.
I can see why people could get used to this.
For the ride back, I used Uber again. This time Allam picked me up in a Honda CR-V. Again, he arrived within three minutes. I was his first customer for the night and we hit it off to the point where I didn’t want the ride to end (he was originally from the West Bank of Israel and we talked a lot about the Middle East, which I’ve enjoyed visiting).
When I go to the airport tomorrow to head to CLS and OSCON, I plan to take UberX, or I might try UberPool.
While I still have concerns about some of Uber’s policies, and I probably need to check out Lyft (a competing service), we are talking about an experience that is orders of magnitude better than the old status quo. I’ll be hard pressed to take a taxi again.
As I was spending this morning trying to get organized, I thought it would help me to post some of the OpenNMS events coming up over the next few months.
The O’Reilly Open Source Conference, being held the week of 20 July in Portland, OR, USA, is probably the last great commercial open source conference. I’ll be there on the Expo floor and would love to chat with folks about OpenNMS and open source. We are also sponsoring a free concert with MC Frontalot and the Doubleclicks at Dante’s on Thursday night the 23rd:
We are holding our formal week-long OpenNMS training course the week of 10 August at OpenNMS HQ in Pittsboro, NC. This is the best way to get up to speed with OpenNMS, plus you get to meet a lot of the people who make it happen.
September: Users Conference
This year’s users conference is shaping up to be the best yet. It will be held from 28 September to 1 October at the University of Applied Science in Fulda, Germany, which is just outside of Frankfurt.
Sponsored by the independent OpenNMS Foundation, The Call for Papers is still open. Also this year we’ll have the gang from the Bad Voltage podcast doing a live show for your entertainment.
October: All Things Open
From 18-20 October, the All Things Open conference returns to America’s Open City: Raleigh, NC (home of Red Hat). This is a great time and OpenNMS will be a sponsor this year.
So, after this year’s Dev-Jam, several people followed us back to Pittsboro. Markus von Rüden, Ronny, Christian and Dustin all came to visit, as did Antonio. It was an extra week to get even more work done and a chance for us to socialize.
On Thursday Ben suggested we visit a really nice Japanese restaurant called Dashi in Durham. While downstairs serves noodles, upstairs is a bar with small plates. We rented the place out for a few hours.
It was excellent. The food was delicious and unusual, and the drinks were splendid as well.
Since our guests weren’t leaving until July the 5th, it was only appropriate to have everyone over to celebrate July the 4th. I was finally able to make Fish House Punch (there is so much of it you need a large number of people to help drink it) and we did the usual 4th of July things such as cooking out on the grill.
The one thing we couldn’t do was fireworks, as there are pretty strict limits on them in North Carolina. I thought we could substitute a bonfire (I generate a lot of stuff to burn on the farm) but with the large amounts of rain we have been getting it really wouldn’t catch.
Then Jesse asked “Do you have any gasoline?”
Against my better judgment, I got some gas and while it improved things, the fire still wasn’t blazing like a bonfire should. Then someone suggested I get the leaf blower.
Now, I have a really nice leaf blower. It’s a four-cycle Makita that makes me feel like Magneto. It did the job.
Remember, don’t try this at home.
Speaking of home, everyone made it back safely. It was nice seeing them for an extended period of time.
Just a quick post as I’ve now upgraded two desktops to the latest Linux Mint, version 17.2, code named “Rafaela”.
The upgrade process was pretty painless. I was on 17.1 “Rebecca” so I made sure all the packages were up to date. Then I launched the “Update Manager” application and chose “Upgrade to 17.2” under the “Edit” menu.
I haven’t seen any new issues and some of the old ones seem to have disappeared. I used to have issues with a) the desktop background going all wonky, b) the screen resolution dropping down to 640×480 that was only fixable via reboot, and c) the screen not being responsive at all, necessitating Ctl-Alt-Fx and then back to Ctl-Alt-F8. No biggies and they were pretty infrequent, so I’m not certain they are fixed (I have an ATI Radeon PRO card in the desktop with the issue) but I haven’t seen them since the upgrade.
Plus, yay!, the screensaver is back. Ubuntu decided a long time ago to basically nix the screensaver and just power off the screen. I like screensavers, but I also like an integration with the desktop environment so I never hacked in xscreensaver. Well, in 17.2, they did. You will have to install the xscreensaver packages to get choices (well, more than the default two) and it is missing a randomizer (sniff) but one step at a time.
I just wish I could get the clickpad to work correctly on my new laptop. I’ve posted my problem to the forum but so far no suggestions.
Anyway, I’d recommend Mint users upgrade when able. So far so good.
Update: Problem a) is still happening. When the system comes back from a suspend the desktop background is distorted into squares of mainly black and white pixels. I have to change the desktop background away from what it is and then back to restore. Doesn’t happen on my NVidia desktop.
The last day of Dev-Jam is always bittersweet for me. I’m sad that it is over, but I also get to see all the wonderful “new shiny” people have been working on. Friday we do demos.
This year we made an attempt to record each demo. Just click on the picture to see it on the YooToobz. Videos, yay!
First up was Ben. Ben is the architect of our new mobile app, OpenNMS Compass. Available for both iOS and Android, it may even turn into our next overall user interface. To do that, it needs graphs, so Ben demonstrated how you can now display graphs in Compass. You can even set “favorites” so they show up on your main screen.
Markus von Rüden spent the week working on something fun: digitizing our mascot and kiwi overlord, Ulf. He demonstrated this work in a game. While it wasn’t completely finished, when Ulf died would he split in half to reveal a kiwi (fruit) center. Cute. Unfortunately, no video and no wiki page (yet).
Christian presented a new way to represent issues within OpenNMS, a “heat map“. It works with both alarms and outages.
Jesse presented something that literally gave me goosebumps. Using our new integration with Newts, you can search for similar data within OpenNMS. So if there is say, a spike, you can search through all the other metrics to see if there are other data sources that spike at the same time.
David S. presented a new northbound interface for sending alarms to other systems via JMS. He used ActiveMQ as a proof of concept.
Ron created a couple of new features. The first was the ability to see polls as events, including how long each poll took (if available). He also added the ability to create a consistent color scheme across performance graphs.
Umberto created another real exciting feature – the ability to export in real time OpenNMS events to Elasticsearch. Since OpenNMS can handle thousands of events a second, sending them to a system built to analyze such data could be very useful. Umberto was sponsored to attend by the OpenNMS Foundation.
A second OpenNMS Foundation attendee was Marcel. He worked on improving data collection for Fortinet devices.
Another cool feature was Dustin’s custom data collection script tool. Sometimes OpenNMS gets criticized for not using SSH to collect data and perform montoring. The reason it doesn’t is rather simple: it’s a stupid idea. It usually requires that you set up keys with null passphrases, and often they connect as root. Despite the security issues, it is also a resource hog and can’t scale. We have always recommended using an extensible SNMP agent like Net-SNMP, but it can be some effort to set up.
Dustin’s feature allows you to put collection scripts in a special folder on the server, and OpenNMS will automatically collect the data. All you need to do then is to add a graph definition and you’re done.
Ronny discussed running OpenNMS in Vagrant and Docker containers. Neato.
DJ was frustrated in how long it can take to compile OpenNMS if tests are enabled. OpenNMS is heavily instrumented with software tests. These can be broken into “unit” tests and “integration” tests. Maven (the build system used by OpenNMS) can be configured to separate them. Since unit tests should be small and quick, they can be run every time with the integration tests only run for regression.
Finally, Seth presented the work he did this week which was focused on changes needed to support OpenNMS Minion. Minions are little, stand alone processes that can perform basic monitoring and data collection, which is then forwarded up to an OpenNMS Dominion instance.
While the last Dev-Jam always seems to be the best Dev-Jam, I think it was true this year. This work will go along way toward positioning OpenNMS for the coming Internet of Things, and as always it is amazing to see what brilliant people can do when given the opportunity to work together.
We ended the day at Surly Brewing Company. The beer was delicious and the company stimulating. I only got one non-blurry picture, and unfortunately my pants fell down when I stood up to take it.
Okay. When it comes to tech, I want the latest and greatest. To me, the “greatest” must include as much open software as possible. As an ex-Apple user, I want the same experience I used to get with that gear, but with free and open source software.
It can be hard. Rarely is the open source world involved in new hardware decisions by the major vendors, so we learn about new devices after the fact. Thus there is an inevitable delay between when a product is announced and when it properly works with FOSS.
Now, I vote with my wallet, so back in 2012 when I needed a laptop I bought the second edition “Sputnik” Dell XPS 13, which shipped with Ubuntu. It served me well for many years and currently runs Linux Mint 17.1 with no problems. When the latest edition XPS 13 was announced, I immediately ordered it, but it didn’t work out so well.
When I discovered that the other option from Dell, the M3800, wasn’t for me, I decided to wait until they officially supported Ubuntu on the new XPS 13. I didn’t have to wait long, and I placed my order the day I learned it was available (I was happy to learn that they had to fix some kernel-level issues and it wasn’t just me).
Why didn’t I wait longer? The XPS 13 is gorgeous. I haven’t felt this strongly about a laptop since my 12-inch Powerbook back in 2013. Others seem to agree, with even Forbes praising this machine.
Anyway, the order process was simple. I got the XPS 13 with the i7 processor, 8GB of RAM, 512GB SSD and the HiDPI touchscreen. The laptop arrived about a week before it was scheduled. Go Dell.
Now for the obligatory unboxing pictures. The outer box arrived undamaged:
The laptop itself came in a separate box:
with the accessories shipped in a cardboard “square tube”:
While the small power supply came with a longer power cable with a “mickey mouse” connector, the XPS 13 comes with a small adapter that gets rid of the cable entirely (like the Apple laptop power bricks).
The laptop pretty much fills up its box:
Like with my original XPS, there is a cool little intro video that plays when you first start it up:
Please note that it only runs on the first start – you will not have to wait 40+ seconds to boot your system (usually less than 10).
The XPS 13 Ubuntu Developer Edition ships with 14.04, but I had some issues with it. First, it didn’t have the option for encrypting the home directory. I’m not sure how or why that got removed. The system also crashed when I attempted to make a backup image to a USB stick. Finally, there are apparently still outstanding issues with 14.04:
Ubuntu 14.04 includes kernel 3.13. The touchpad will run in PS2 mode and the soundcard will run in HDA mode. Currently (4/15) out of the box the HDA microphone will not work, and you will need some packages from the factory shipped image to make it work properly.
While I knew I was going to base the system, I logged in to the stock image to check out the apt repository. There really wasn’t anything outside of the vanilla Ubuntu (the few Dell packages seem to be just for recovery) so I felt fairly safe in reinstalling.
I immediately went to my default distro, Linux Mint 17.1, but found that a lot of things, especially the touchpad, didn’t work as expected. It did handle HiDPI screens just fine (you could actually see the mouse pointer increase in size when logging in). I figured I’d wait until 17.2 comes out and try it again.
On a side note, I don’t know why it is so hard to get a decent touchpad under Linux. We’re getting closer, but still, it tends to be the weakest point of the Linux laptop experience.
In search of a solution, I found Barton’s Blog and read the following:
With BIOS A00 or BIOS A01 the touchpad will run in I2C mode and the sound will not function. Please update to at least BIOS A02 and the touchpad will run in I2C mode and the sound in HDA mode. (4/15) All of the relevant patches have been backported and all functions will work out of the box.
I really liked the “will work out of the box” bit, so I installed Ubuntu 15.04.
It had been awhile since I’d used Unity, and it has really matured. I especially liked the little touches. When I changed my desktop background, the background of the Dock changed color to match it. Neat.
Where Unity still has some way to go is in HiDPI support. There is a scaling factor you can set, but it only applies to a small part of the UI. I still ended up having to customize many of my apps. For example, if you look at the settings page with scaling, a lot of the text under the icons are cropped:
Not a show stopper, and I used it for over a month without getting too annoyed.
Last week I saw that the release candidate for Mint 17.2 was out, so I dutifully backed up my Ubuntu install, based the system and installed Mint. Things seems to work better (although HiDPI support was not working by default), but I ran into a weird problem with trying to click and drag.
While everyone seems to deal with trackpads differently, the way I click and drag is to use the index finger of my left hand to click and hold the lower left corner of the trackpad, and then I use the index finger of my right hand to move the mouse pointer. This works fine under most desktop environments, but under Cinnamon it seems to interpret it as a right click (which usually causes a menu to drop down). If I just used a single finger to click on the window header and then move it, it worked as expected, but I couldn’t get used to it enough to continue to use it.
Oh well. I’ve posted a question on the Mint forums but no one has been able to help.
Anyhoos, since my system was based I decided to try out some other 15.04-based distros while I had the chance. I had heard great things about the new Plasma interface in KDE, so Kubuntu was next.
I can’t say much about Kubuntu since its HiDPI support is worse than Unity. Everything was so tiny I couldn’t spend much time in the UI. Oh well, what I saw was pretty.
And I should stress that this was a recurring theme in my experiments with desktop environments. Every UI I’ve tried has been beautiful and more than able to compete with, say, OS X.
By this point I decided to punt and just search on “Linux Desktop HiDPI”. Several of the results touted that Ubuntu Gnome was the best desktop to use for HiDPI systems. So, before going back to Unity I decided to give it a shot.
I haven’t used Gnome 3 in awhile, but I was encouraged in that even the install process handled the HiDPI screen well. It has become really mature, and so far has provided by far the best experience with the XPS 13. I’ve had to do little to get it to work for me.
Is it flawless? No. There is an issue with the touchpad where it occasionally translates touches into click (kernel patch approved). If you sleep the system, the touchscreen will stop working (but you can reload its module). Sometimes, the system doesn’t sleep when you close the screen, which can cause the laptop to get really, really hot.
But these are minor issues and I expect them to be addressed in the near future. I am confident that I’ve found a great combination of software and hardware, and that it will only get better from here.
I have just a few more notes to share. The battery life is outstanding – I can get 6-7 hours of use without recharging. The “infinity screen” is beautiful and bright, but by having almost no bezel they had to move the camera to the lower left corner, which creates a slightly odd viewing angle.
In closing, here are a couple of shots comparing the XPS 13 with the M3800.
Since I sincerely doubt even my loyal readers get to the bottom of my long posts, I figured I’d start this one with the group picture:
That antenna behind Goldy’s head is part of Jonathan’s project to use OpenNMS to collect and aggregate FunCube data from around the world. Can I get an “Internet of Things“? (grin)
There is this myth that just by making your software open source, thousands of qualified developers will give up their spare time to work on your project. While there are certainly projects with lots of developers, I am humbled by the fact that we have 30-40 hard core people involved with OpenNMS.
Unless you’ve gone through this, it is hard to understand. At one time, OpenNMS was pretty much me in my attic and an IRC channel. Luckily for the project that didn’t last long. My one true talent is getting amazing people to work with me. Then all I have to do is create an environment where they can be awesome.
It’s why I love Dev-Jam.
I also love pizza. Chris at Papa Johns was kind enough to send us some free pie for dinner:
Today we spent time talking about documentation. Documentation tends to be the weak point of a lot of software, and open source software in particular. The Arch Linux people do about the best job I’ve seen, but even then it is hard to keep everything current. For over a year now a group of people has been working very hard to improve the documentation for OpenNMS, and the new documentation site is most excellent.
It does take a little time to understand the navigation. The documentation is included in the source and managed on GitHub, so there is a new version for each release. But just as an example, check out the Administrator’s Guide for 16.0.2.
Written in AsciiDoc, it is now the best place for accurate information on how to use the software. We also want to extend a special thanks to the Atom project for creating the editor used to create it.
One of the things we discussed was how to deal with the wiki and the .org website. It’s not practical to duplicate the AsciiDoc information on the wiki, so the plan is to include the relevant part from the documentation in something like an iframe and use the wiki more for user stories. The “talk” page can then be used for suggestions on improving the documentation, and once those suggestions are merged they can be removed.
I had suggested that we make the wiki page the default landing page for the .org site, but Markus pointed out that we need to do a better job of marketing OpenNMS, and the landing page should be more about “why to use OpenNMS” versus “how”. I had to agree, as we need to do a better job of marketing the software. My friend Waleed pointed out in Twitter this weakness:
To better educate folks about why OpenNMS is so amazing, we are considering merging the .com and .org sites and using the .com WordPress instance for the “why you should use OpenNMS” with a very obvious link to the wiki so people can learn how to use OpenNMS. Part of me has always wanted to keep the project and commercial aspects of OpenNMS separate, but it then becomes really hard to maintain both sites.
In case you haven’t guessed, we do spend a lot of time thinking about stuff like this. (grin)
A lot of other cool stuff got done on Thursday. DJ announced that he had separated out the unit tests in OpenNMS (for features) from the integration tests (for regression). OpenNMS has nearly 7,000 junit tests (and growing). It’s the main way we insure that nothing breaks as we work to add new things to the software. But with so many tests it can take a real long time to see if your commit worked or not. This should make things easier for the developers.
It’s hard to believe that Dev-Jam is almost over. Luckily, it sets the stage for the next year’s worth of work. Since our goal is nothing less than making OpenNMS the de facto network management platform of choice, there is a lot of work to be done.
As most of my three readers know by now, I was a big fan of the OnePlus One handset until I experienced their customer support (which seems intent on covering up a major defect in the touchscreen of their devices).
So, it was time to get another smart phone. Andrea had been using a Nexus 6 for awhile, I thought the phone might be too big for me. The phone is huge.
David pointed out that the OnePlus was huge compared to my previous HTC One, and it only took me a day or so to get used to that size change, so I’d probably feel the same way about the Nexus 6.
He was right.
I ordered it from the Play Store and it showed up a couple of days later. The name of the phone was actually on the bottom of the box:
and once I cut the “tape” I flipped it over so I could open it.
The phone sits in a little cardboard cradle
and if you remove it you can see a little packet with documentation.
Under that is a high amp charger and that’s about it.
The phone has a gorgeous display and its six inch screen is big enough that I can watch movies on it, so I loaned my Nexus 7 (that I used to use when traveling) to Ben so he could play with OpenNMS Compass on Android.
It’s also blazingly fast, but all that power does come with a price: battery life. With the OnePlus I could easily go a day, even with playing Ingress to some degree, the Nexus 6 needs a little more juice. It is in no way horrible, and is much better than the HTC One, but it is still a factor. I just ended up buying a TYLT wireless charger for my desk so I can sit the handset there all day and it stays charged (yay wireless charging).
I did buy a case for the phone but that pushed it over the size limit for even my large hands. Caseless, I was worried about dropping it, so I bought a “grip” pad that sticks to the back and makes it feel less like a slippery bar of soap. So far so good.
The best thing is that, thanks in large part to Jake Whatley, I can now put OmniROM on it. It was a pretty simple process to unlock the phone using adb, install TWRP and then flash the latest OmniROM nightly. I was surprised at how much my Android experience was truncated by the stock ROM. I couldn’t shake my phone to dismiss an alarm or augment the power menu to add options like a reboot instead of just powering off. So far no problems.
The size of the Nexus 6 will be off-putting for some, but it is about the same size as an iPhone 6 Plus, so perhaps not.
As I was investigating alternative ROMs for the Nexus 6, I thought it was funny when I found out the code name for the device. Nexus devices tend to be named after fish.
Even though I am no longer a user of Apple products, I was eagerly awaiting the release of the Apple Watch. Why? Because Steve Jobs had a way of making stuff for me that I didn’t know I wanted. While I’ve owned an LG G Watch R for awhile now, the experience hasn’t been life changing (unlike using an iPhone was) and so I was looking for Apple to really “wow” me.
My friend Ben (who knows more about Apple products than anyone I know) thinks I’m more critical of Apple than the fiercest “fanboi” and he’s probably right, so I want to make sure to expressly state that I haven’t used an Apple Watch so anything I say about it needs to be taken in that context.
However, Matthew Inman, another person whose opinion I respect, recently did a comic on his experience with the Apple Watch, and his experience is very similar to mine with Android Wear. It’s interesting, it has potential, but it isn’t life changing … yet.
To me, my watch is like having a second screen on my phone. Remember when people first started getting dual monitors? It’s like that – it makes me more productive when using my phone but it is more of an extension than a feature in and of itself.
The main thing my watch gives me is a socially acceptable way to keep up with notifications. If I’m in a meeting, or at a meal, or in any other social situation where pulling out my phone and looking at it would be rude, I can glance at my watch and see if I need to address that text or e-mail.
The main difference between Wear devices and the Apple Watch is that the latter has a crown that spins and can be used scroll the display. Inman points out that he doesn’t use it, and so you are pretty safe choosing the smart watch you like that works best in your digital ecosystem.
The main thing I want from a watch is a stylish accessory that actually looks like a watch. Enter the LG Watch Urbane.
After my horrible experience with the OnePlus One phone, I was shopping for a replacement handset when I came across the Watch Urbane. I fell in love immediately.
I got the G Watch R because it looked like a watch and not a slab of glass. The Urbane takes that experience to a new level by adding a rose gold bezel and a nice leather strap. The display is amazing. The default watch faces are amazing. In short it is the perfect evolution for my favorite smart watch to date.
It’s a powerful watch with great battery life. While I tend to charge it overnight, I can get over two days of normal use out of it easily (I’ve had to test that when flying overseas).
I bought it on Amazon, and it showed up protected in a rather easy to open plastic cover:
The box was similar to other mechanical watches I have bought:
and opening it immediately revealed the watch:
The band was a little stiff at first, but after wearing it for a day or so it softened up a bit.
It came with a number of accessories. Like the LG G Watch R it requires a charging cradle that is powered via a microUSB connector.
The Urbane was one of the first watches to ship with the Andoird Wear 5.1.1 update that allows for such things as talking to the phone over Wi-Fi, but about a day after I got the watch the update was generally available for other devices, including my G Watch R.
The Urbane is a little smaller, and while I liked the “tick” marks around the outside of the G Watch R, so many watch faces include them due to the popularity of the Moto 360 that I was happy to see them removed on the Urbane (having two sets of tick marks is a little cluttered).
While I still wear the G Watch R if I’m going to be active (i.e. sweating), the Urbane is my go-to wrist accessory. I am constantly getting compliments on it, and I think the biggest problem LG has is that no one has heard of it.
It’s hard to believe that this year’s Dev Jam is half over. It seems to take forever to get here and then it is over too soon.
Lots of cool stuff going on. David Schlenk has written a Java Message Service (JMS) northbounder interface. While targeted at Apache ActiveMQ, it should work with any JMS provider, and it is another great tool to have for the OpenNMS platform.
Christian did a cool little hack using a Blink(1) USB light. If you have a Blink(1) you can plug it into your laptop and then run a little Java app. The app will connect to your OpenNMS instance and then the color will change based on the severity of alarms. Cool.
I also participated in my first GPG key signing. Jeff organized it to increase our “web of trust” and once I got into it, it was kind of fun.
He promised cake, and for once the cake wasn’t a lie:
The cake went well with dinner, which came from the always amazing Brasa:
Most of us ate out on the deck. This is the view looking out toward the Mississippi:
While we have held Dev-Jam in locations other than UMN, it has become a lot harder to do so since we get treated so well here. While most attendees have been to previous Dev-Jam events, we always have a few new people, and many of them end up staying off campus in a nearby hotel. There is something about staying in a dorm room that bothers them – perhaps it was a bad experience in college.
So I thought it would be a public service to actually show the rooms we get at Yudof Hall.
Each person at Dev-Jam gets their own room. While these rooms tend to hold at least two students when classes are in session, during the summer they are singles. You get a sink and a little kitchen with a microwave, two burner stove and refrigerator.
There is a single bed, desk, an armoire (closet) and a chest of drawers.
You even get to control the temperature in the room. I like mine on the cool side and the air conditioning works quite well.
Each room shares a bathroom with a toilet and a shower with one other person from Dev-Jam. While these rooms might be a little close with two people, they are perfect for one. Plus they are incredibly convenient since the event is held in the downstairs Club Room.
So, if you ever decide to come to Dev-Jam, don’t hesitate to stay on campus.