Profile cover photo
Profile photo
Matt Raykowski
Matt's posts

Post has attachment

Post has attachment

A fellow from the Sails.JS community noticed that the domain was available but expensive. Him and some others put together an IndieGoGo campaign. Pledge $5 to get your own sub-domain.

Post has attachment
+Jan Boon decided to take on the demand for an updated roadmap. Winch Gate created our first roadmap and it was more of a pie-in-the-sky first attempt at the platform's future. I think Kaetemi's proposal is more realistic to the velocity of the project and its potential uses.

Check it out, let us know what you think so far.

Post has attachment
Hey everyone, I just wanted to let you know that I decided to move the blog away from Blogger. I moved the blog to a self-hosted Ghost blog. This will allow us a lot of control over the blog plus it looks a heck of a lot nicer than Blogger.

I don't have a great banner at the top so if you have something better please send it to me!

Post has attachment
I posted a sort of "Ryzom Core State of the Project" update on the blog.

Post has attachment
I really like +Atlassian products. We, with a fair amount of resistance, have got Confluence and Stash at work. For the most part these things start out on a VM that some IT guy with too much access creates for his team because there's not a lot of room for... pet projects... at our company. Well Confluence took off like wild fire, which is amazing. It's a real clear example of the perceived need by the people working being ignored by the people who manage the budgets, meaning we only have it because as a hospital we qualified for a non-profit license. Confluence has done great things for our company though, despite the fact that our silo-centric xenophobia has prevented us from even letting other non-IT beings know that such a cool solution exists within the organization.

That being said we're way way way behind on our Confluence upgrades. I don't even want to say how far behind we are. It's depressing. We had an issue this week where LDAP directory syncing began to fail because some inetOrgPerson object in eDirectory contained a character that Confluence disliked. The bug actually exists in Spring Security LDAP, not Confluence. However to get the new version I need to... DUN DUN DUN.... upgrade Confluence. So here's why we don't upgrade Confluence with regularity.

+CustomWare aka +ServiceRocket Scaffolds. Once upon a time I used Scaffolds when they were free and back then, in the early days of Confluence, they were amazing. Now lets be fair, they still are pretty darn cool but the fact that these plugins (and +Adaptavist plugins) are always at a minimum a full major release behind the curve is really frustrating and limiting. Also. They're cool plugins so they decided hey starting in Confluence 4 we're going to charge cash dollars for our cool plugins. They're not charging peanuts either. Scaffolds is like $800 plus $400 per year for unlimited users. Some companies think money is toilet paper but I fought for 2+ years to get a 2nd monitor. So guess what... this isn't an option.

I knew that Confluence 5.1 brought this new concept of Blueprints in. I have a couple OnDemand instances for open source projects, namely +Ryzom (actually Ryzom Core, but whatever), so I looked at them there. I was unimpressed. Ooh, fancier templates. Lame. Nothing really jumped out and I was provided with no reason to investigate Blueprints further, with the exception of looking at what Blueprints were made available on the Atlassian Marketplace.

Well I decided it was time to take another look at Blueprints. Scaffolds and their friends are killing us. We're in the Atlassian Dark Ages thanks to these awesome plugins. I looked into how to modify existing Blueprints and contained with the 'lame' track of thinking. How is this any different than templates? Is this really, truly, just another lame ass marketing tactic? I stumbled upon a link to Atlassian's wiki on Blueprints:

I read through this and thought... okay, there's a hell of a lot more substance here than I had originally thought. So I went back to the "Write a simple blueprint plugin" article and started working form there. Now lets just say I spent a lot of text to say that I think Atlassian has kicked some serious ass in this arena. I mean the tools and the workflow provided to plugin developers is nothing short of absolutely amazing.

When we talk about providing better tools for +OpenNMS we always talk about how cool it would be to provide an easy way for someone to go to a website and suck down a zip file filled with pre-made eventconf XML files and things of that sort. I think this is partially due to the fact that there's not a lot of OGP-worthy types in the community writing new plugins to OpenNMS. However... maybe it's because while OpenNMS has provided an open platform and, in some cases, phenomenal documentation on writing plugins (e.g. writing new pollers is super freakin simple) it has failed catastrophically at providing an easy to work with development environment. If there is one thing that I'd like for OpenNMS to steal, ideologically, from another project is is the way Atlassian handles plugin developers.

Now OpenNMS is just now really getting its feet wet in the OSGi world, with Karaf being shipped in the newest version as part of the distrubtion I admit that Atlassian has a bit of a head start on them. But it's not all about being able to easily load/unload bundles and features. That's cool. Actually that's really cool. But that's "free" with Karaf for OpenNMS. For people like me, organizations using OpenNMS and Atlassian, we need Atlassian-scale tools. Command line tools for ease of managing your plugin development environment, etc.

I mean take for example that if I want to start creating a plugin I type (assuming I have their SDK installed, which is super clearly documented) "atlas-create-confluence-plugin" and it creates my basic plugin skeleton, presumably from a Maven archetype because it comes with Maven all pre-configred. I make a couple changes and then I type "atlas-run" and, here's where it's cool, it starts up a standalone development Confluence instance. I can go check my plugin and see if it works.

Okay, so that's KIND OF neat. I fire up IDEA (or Eclipse, whatever) and edit some more plugin code, add a couple things, tweak the template. The usual kind of junk involved. What do I do next? Kill Tomcat and recompile then manually copy the WAR over and reset the DB and all of that kind of non-sense?


I just open the developer console, in the Confluence web app, and click the "fastdev" refresh icon. The freakin Confluence server executes Maven and rebuilds my plugin and redeploys it into its OSGi container, when it's done it brings me back to the Confluence dashboard ready to go. In about a minute.

These guys have this figured out. This is smoooooooth.

So, needless to say I've spent my evening trying to create a proof of concept to replace some of our Scaffolds with Blueprints.

Post has attachment
It was AJ's 6th birthday party with his friends from school. We went to Pinz, a bowling/lasertag/arcade place near by. Local parents - this place was awesome, they handled everything, and the kids had a blast.
2 Photos - View album

Post has attachment
+Geels NL requested updated pictures of the playhouse build. Here it is sportin fancy new railings. Roof is next.
3 Photos - View album

Post has shared content
+Matthew Lagoe , do you know if this is an open bug in BitBucket?
Wait while more posts are being loaded