PreviousNext…

Blimey!

No posts for a week. Tsk, disgraceful. So what has been happening in the world of me? I know you’re just itching to find out! Well, lots of meetings, lots of consulting, etc., etc. I’m conscious of the fact that I have neglected the next release of DominoWiki: I will release this imminently, as I’ve been playing with it in the wild for a month or so now, no ill effects. It’s a minor bug fix release, nothing to jump around about. Watch this space.

Other than that, I have been indulging in plenty of tinkering with ssh (via PuTTY), Tomcat and Verity. Oh yes! We’re also in the throes of rolling an enterprise wiki out into production. The software we chose is called Confluence, and it rocks. Confluence is a J2EE application which provides flexible “spaces”, wiki pages and “news posts” (basic weblog functionality), all wrapped up in a pleasing user interface with RSS all over the place. I recommend it. I believe it has some pretty decent developers working on it too… ;-)

In terms of IT function use, amongst other things we’re using Confluence to document various bits of developer guff (e.g. how to get started with Verity, Websphere and Domino processes, etc.), and a few of us are even ’blogging. Hopefully project weblogs, and full leverage of RSS will follow. Which brings me to a discussion point: what do you use for documentation in your organisation?

Comments

  1. This doesn't answer your question, but I tried out the Atlassian bug tracking tool (whatever that one was called) for a bit. It was really well done, but a bit overkill for our environment. Pretty inexpensive, too.

    - Julian
    Julian Robichaux#
  2. A couple of months ago I wrote one for use here. We are an ISV who sells consulting on an hourly rate, and products built for a fixed price. It's not documentation as such, but tracks the whole process mapping releases (the project's not over just because it's implemented!) and features requested by the client (which then map to specific functions we IT bods need to build). Key for us is managing the $$. We have a customer facing side as well so the customer can see their projects and interact with them (add new features, comments, documents, what time was billed where, etc). So far it's working out really well.Brendon Upson#
  3. At my organisation we use toilet paper. It means that the Completed, Final, Signed-off and 'Guaranteed Never To Change After This' document in question has a use tomorrow.

    ;-)Anonymolloyus#
  4. That would be JIRA Julian, and yes ’tis very nice. As for you Molloy, I’m stealing that idea :-) Ben Poole#

Comments on this post are now closed.

About

I’m a software architect / developer / general IT wrangler specialising in web, mobile web and middleware using things like node.js, Java, C#, PHP, HTML5 and more.

Best described as a simpleton, but kindly. You can read more here.

";