Skip to main content

I'm gonna be the Wiki-techie! (oh no)

I was recently contacted by Atlassian's Wiki Evangelist (yes, appearantly that's a real title!), Stewart Mader. He asked me to consider their new site, Wikipatterns.com, and also forward the site to my dear readership. Done!

In other but related news, I've been (somewhat unwillingly) appointed our next Confluence administrator. This means I'll be given full control over the wiki (muhuhaha) , meaning in effect I'll be able to try out new plug-ins, manage spaces, bully people around, etc.

It also means I'll have to do upgrades, booring user adminstration, figure out funky stacktraces that are appearing in Confluence for some odd reason, fix the database, etc, etc.

The main reason I have volunteered to do this job is that no-one else wanted to do it, and I believe our Wiki is far too critical to leave in the hands of our IT service provider like our CTO would've had it. When are you people gonna understand that Windows is not meant for hosting?

Additionally, I'll hopefully learn alot about Linux, DNS stuff, routing, network, hosting java applications, databases and user management (with LDAP).

These things aren't always relevant in my daytime job, but sooner or later the software we produce will end up in the hands of IT techies who want the software to work, log and do error reporting in a certain way.

And when all boils down to it, Confluence is still a java web application that runs on Tomcat, which is very similar to the products I develop. Having been responsible for hosting Confluence will therefore make me a better software developer.

I've got lots of other things to blog about, but no time to do them right now. Subjects include:

  • Finalizing the CMS requirements with its most important element: Extendability
  • How I became a certified Scrum Master (and what I learned)
  • The programming designer, the new breed of web developers
Stay tuned.

Comments

  1. Anonymous4/3/07 23:19

    Thomas,

    If you need assistance translating those "funky stacktraces" please feel free to submit a support issue (with logs) at http://support.atlassian.com. Even better, from the same website, you can hop on live chat to discuss Confluence issues with one the Atlassian support engineers. As your company's new Confluence administrator, we're here for you!

    Cheers,
    Donna McGahan
    --Atlassian Support Engineer

    ReplyDelete
  2. The Wikipatterns website is a good source of information if you need any Wiki Adoption Patterns.

    Looking forward to see the post on Scrum!

    ReplyDelete
  3. Anonymous6/3/07 01:31

    I have two words: "Virtual Machine". Ok, four: "MindTouch Deki". I've just upgraded from the free version to the pro version. It's delightfully easy to use and install. Also, they update the application automatically. http://mindtouch.com/deki&subsection=Download

    I came to them by way of www.opengarden.org.

    ReplyDelete
  4. Hi Thomas,
    As Donna said, we're here to help. Thanks for mentioning Wikipatterns, BTW!
    Best regards,
    Stewart Mader
    Wiki Evangelist, Atlassian

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration