Sunday, December 31, 2006

Business Experience Open Sourcing Code

Well hello everyone from lxer and rootly. My weblogs tell me there are a lot of linux enthusiasts in many countries reading blogs on New Years Eve. Don't you all have anything better to do? :)

But while I have your attention, I do have a question: What are the common characteristics of successful open source software projects? How about ones that are incorporated into proprietary profit driven products?

The Background

I run a little project management company here in Washington State. You might know something about my neighbor in Redmond. We write TeamDirection Project, they write MS Project. We do some nice things in my little shop, but one thing we would never be able to do is compete with Microsoft on a feature by feature basis-- only a handful of companies even have the resources to contemplate such a thing.

However, one can't help but marvel at the power and energy harnessed by the Linux community to create a truly great operating system. The Apache Group also comes to mind for an open source effort that many programmers from every corner of the earth participate in. And more recently the Mozilla group developing Firefox.

There are so many things I'd like to do with this piece of code, and so little time and even fewer developers. Open source has this appeal of, somehow (worry about the details later, right?), bringing a critical mass of talented developers together to improve your product for free. Sounds even better than outsourcing! :)

The one common denominator among the aforementioned is each one has a significant backer with *very* deep pockets: IBM backing Linux and Apache, Google backing Firefox.

The Question Rephrased

So the question is really: Do you need a big backer to make an open source project successful these days? Or would a charismatic leader, someone of Linus Torvalds ilk, be enough to get the ball rolling and hope for the best?

I say this because I've been debating opening our scheduling engine to open source. But it seems like it would be such a shot in the dark, that so far I haven't been able to see the benefits for the loss of intellectual property and loss of goodwill with Microsoft and Microsoft partners (Linux doesn't quite have the partner channel Microsoft does, or I'm not aware of it).

So for now my thoughts are to keep our project scheduling engine in-house, but I'm open to examples of reasonably successful applications built on open source-- other than Linux, Apache and Firefox.

Saturday, December 30, 2006

Can I Toot My Own Horn Yet?

It's not even 2007 yet and already one of my predictions (#6) seems to be coming true.

Michael Arrington over at TechCrunch has just picked up on Blake Ross's blog post questioning Google's latest feature, and weighs in with insight of his own.

Actually, can I take credit if Google starts losing its shine at the end of 2006? I hope so.

If you combine this with my #8 prediction (purchase, download and watch a movie via my broadband connection) I have an excellent shot to be 2 for 10!

Friday, December 22, 2006

Red Hat Might Just Be Getting Serious

I admit it. I've always discounted Red Hat a little bit-- like the kid down the street you have fixed in your mind as perpetually 10 years old. Until he looks you in the eye and says 'Hello' in a baritone.

Such is the state of affairs with their last earnings report.

The Oracle announcement was supposed to do this. The Microsoft/Novell pact was supposed to do that. All Red Hat did was execute, execute and execute.

What immediately came to mind is Red Hat actually might turn into a major player in any brewing OS war/evolution. There's been a bevy of speculation over at ReadWriteWeb about Google producing some sort of GoogleOS.

I do not agree Google would want to wade into the OS game, but perhaps they would consider throwing their weight behind Red Hat. Google's weight is considerable. If Red Hat, as they have just shown, has the momentum... who knows.

I wonder if I should amend my predictions.

New Release Posted

We just posted a nice update to our TeamDirection Project 2007-- just in time for Christmas (I think it'll make a *great* stocking stuffer :).

We fixed over 40 bugs of varying severity, and included a couple feature requests. Bugzilla is our bug tracker of choice, and here's the delta:


2190

nor

P3

Wind

VERI

FIXE

It is only possible to insert tasks above from the right ...

2092

nor

P3

Wind

VERI

FIXE

Unsharing and sharing a project to the same SP site will ...

2108

nor

P3

Wind

VERI

FIXE

Tasks with IW don't get pushed out far enough when linking

2114

nor

P3

Wind

VERI

FIXE

IW causes backward links when removed

2551

nor

P2

Wind

VERI

FIXE

Thing2 should update task durations for MindManager

2579

nor

P2

Wind

VERI

FIXE

Exporting with MM closed will still export the project

2580

nor

P2

Wind

VERI

FIXE

Wrong message when trying to export the project with no M...

2600

nor

P2

Wind

VERI

FIXE

MS Project export doesn't close wizard when done

2609

nor

P2

Wind

VERI

FIXE

Trying to notify members from Share Wizard with no Outloo...

2614

nor

P2

Wind

VERI

FIXE

3.1 project with no resources or links fail to import

2615

nor

P2

Wind

VERI

FIXE

Implement 'Publish Summary Task' option

2564

nor

P2

Wind

VERI

FIXE

Sharing on SP site with members will always ask to 'Map c...

2566

nor

P2

Wind

VERI

FIXE

Release version appears expired after upgrading from Beta...

2575

nor

P2

Wind

VERI

FIXE

If breaking link with MS Project or MM file, project stay...

2578

nor

P2

Wind

VERI

FIXE

Tab Control needs to update Go To Task when swi...

2581

nor

P2

Wind

VERI

FIXE

There is no "open task list" option in Member Pane in Plu...

2587

nor

P2

Wind

VERI

FIXE

'Copy Task' should probably be enabled for projects in lo...

2591

nor

P2

Wind

VERI

FIXE

'I want to buy a license' in activation dialog should ope...

2597

nor

P2

Wind

VERI

FIXE

Undo doesn't work in any Linked mode

2598

nor

P2

Wind

VERI

FIXE

Cannot edit Date2 field from task information dialog whil...

2603

nor

P2

Wind

VERI

FIXE

Arrows keys in Project Save dialog are backward

2606

nor

P2

Wind

VERI

FIXE

'Go to task ..' counting tasks wrong in projects with sum...

2608

nor

P2

Wind

VERI

FIXE

Need to hide Map Tab in Resource management dialog window

2618

nor

P2

Wind

VERI

FIXE

Custom Resources that contains only numbers are align to ...

2619

nor

P2

Wind

VERI

FIXE

Able to select several resources in Reassign tab

2620

nor

P2

Wind

VERI

FIXE

Trying to reassign Me when there is no other members caus...

2623

nor

P2

Wind

VERI

FIXE

In Members list project creator appears with Groove bubbl...

2626

nor

P2

Wind

VERI

FIXE

Trying to click 'Go to task' for the summary task giving ...

1437

nor

P2

Wind

VERI

FIXE

'Schedule a meeting' option is available when no Outlook ...

2542

nor

P2

Wind

VERI

FIXE

Updating marks unchanged project as unread

2612

nor

P2

Wind

VERI

FIXE

Can't open project linked to a MS project with an excepti...

2617

nor

P2

Wind

VERI

FIXE

Publish Summary task check box in SW doesn't work

2625

nor

P2

Wind

VERI

FIXE

Workspace members stays in members list after unsharing

2582

nor

P2

Wind

VERI

FIXE

Projects can be dragged/dropped onto Search folders.

2583

nor

P2

Wind

VERI

FIXE

App does not recover from deleted project

2593

nor

P2

Wind

VERI

FIXE

Yes in 'Want to activate?' dialog when 1 day left doesn't...

2594

nor

P1

Wind

VERI

FIXE

Able to work with Plus edition after activating standard ...

2599

nor

P2

Wind

VERI

FIXE

Error occurs when updating dirty linked MS Project file

2602

nor

P2

Wind

VERI

FIXE

Task dependencies not getting exported to MS Project

2613

nor

P2

Wind

VERI

FIXE

Help>About for Plus does not say Plus


Phew, that was a lot of work! I hope you enjoy it and have a great holiday.

Thursday, December 21, 2006

Ten Predictions

Now that the storm of 2006 has passed, its time to welcome 2007. In the spirit of ReadWriteWeb, I offer 10 mostly web related technology predictions:

1) One of Microsoft's top 10 revenue apps will succumb to a competitor-- and not a big one.

2) A mobile application will crack the monthly top 20 for software sold.

3) A new 'solution' will appear successfully combining desktop, web and mobile. iTunes was the first of these types of apps, but with a specific mobile component (made by Apple). Maybe its a successful implementation of Adobe Flash or Apollo's coming out party. Maybe its a broad solution tailored for specific roles each user assumes as part of a larger problem. What it will do is offer a blueprint for how companies can tie three related pieces (desktop, web and mobile) together.

4) BitTorrent will get a distribution deal from a movie studio.

5) Microsoft Live will do better than people anticipate and put significant pressure on Google.

6) Google will lose its 'do no wrong' halo (Note, this does not mean Google will go broke or somehow fail to make tons and tons of money-- just lose a little Goodwill).

7) Hospitals and clinics will start investing in IT and Electronic Medical Records in a big way as a way to combat soaring healthcare costs.

8) I will purchase, download and watch a movie via my broadband connection.

9) iTunes will be licensed to a media company or consortium.

10) ClearWire WiMax will be adopted by several municipalities and put pressure on DSL and Cable broadband.

Bonus Prediction: Social metaphors will become more and more available in all types of apps-- consumer, business, scientific-- as people look for ways to establish connections beyond the TCP/IP stack and put faces, names and personal information on the other end of the web line.

Meet back in 365 days!

Tuesday, December 19, 2006

A New Perspective on Christmas Lights

It's been a fun few days here in the Pacific Northwest. A major storm blew through the entire region Dec. 14th and took down lots of trees, poles and power lines. As utility crews have struggled for the past few days to restore power (and I wish I could thank every crew member personally for their hard work and dedication!), you start noticing things that rub you the wrong way.

Like Christmas Lights.

My wife and I enjoy a particular holiday ritual around the lights people like to put on the exterior of their houses to show their holiday cheer. She wonders aloud over several days what it would take for one of us to hang up some lights. I wonder aloud about our lengthy list of ToDos-- and lately I've been finding particularly good success by bringing up Christmas gifts for the kids. My neighbor even got in the act this year by hanging lights of his own. It was a pitched battle until last Thursday when it all became moot.

As power is coming back online, so are the Christmas lights. I walk my dog every day and with each passing day more houses again have power, and more happy blinking porches and eaves are piercing December's gloom. But the electrical insouciance seems to be having the opposite effect on me.

We have a happy conceit that we are above Nature, which is fine as long as we seem to be. However, I've noticed our darkest hours are when Nature blithely intrudes on our stagecraft. While Seattle, and the entire Northwest, was socked by a storm, were conditions really so grave as to warrant fighting at gas stations or robbing houses in unlit blocks like my neighbors?

'Oh, this was like Katrina!'

As a measure of the storm's power, not at all-- the scale was completely different. While I may have a better understanding of unsettledness-- of moving from house house to keep my kids warm-- I fully expect my power to be on shortly and life to continue quite nicely after this hiccup.

As a measure of our conceit, inattentiveness and complacency, then sure, I'm up for a comparison. I've lived all my life in the Northwest and while this storm may be unusual, its very common-- even predictable. You don't have to go back very far to read well documented storms of yore with similar outcomes.

For instance, we had a 'famous' Columbus Day Storm back in 1962. As people compare this storm to that one the thing I notice is all the utility trucks repairing the damage look like they are from the 1960s themselves.

It's all about priorities. Schools versus Sports Stadiums. Transportation versus Development. Urban versus Suburban versus Exurban. 1950s and 1960s infrastructure versus the needs of the 21st century....

Oh wait, the lights are on. There's still time for me to hang some Christmas Lights this year.

Friday, December 15, 2006

Update Release Shortly

We're going through testing right now preparing a release addressing bugs and some new features.

Thanks for your feedback!


It means so much to us as we make TeamDirection Project a world class product. Speaking of world class, we're getting so much interest from Russia that there could be a Russian version coming soon! And yes, we do have plans for other languages too. French and German will most likely be next.

I would also very much like to do a Japanese version. In fact, if you're a reseller in Japan and are able to help us with translation, please contact me.

Back to the bug fixes and features...

Bug fixes:

1) TeamDirection wasn't handling some of the add-on business templates for SharePoint from Microsoft very well, so we've improved this.

2) We had an issue with imported custom resources causing problems with SharePoint synchronization. This has been fixed.

3) We had an issue with vacation days in MS Project files. This has been fixed.

Enhancements:

1) One user requested that we NOT publish summary tasks to SharePoint since it can add many more tasks to the list. We heard him and we agreed. There is now a checkbox when you publish tasks asking if you want to publish summary tasks too. The default is not to publish summary tasks.

Why would you want to publish summary tasks? We've seen projects that are mini-workflows where the tasks is a repetitive function and the summary task gives it context. For instance, the summary task might be 'Update Website' and the subtask is 'Copy Files'. Then the next summary task is 'Update Internal Server' and the subtask is 'Copy Files'. That kind of thing.

2) Presence information is now in the resources lists. This aligns better with our philosophy of turning resources back into real people. As such, you can see when real people are online.

We should have this update on our website early next week. Again, thanks for the feedback! We're happy to respond, both in writing and in product.

And we should have a nifty 'sneak preview' of something else we're working on soon. What is it? Get ready to head to BaseCamp :)

Monday, December 11, 2006

TeamDirection a Mindjet Partner

It's always exciting when you meet someone new. I can't speak for Mindjet, but I'm exicited!

We just became a bona fide partner today. If you haven't seen our nifty MindManager demo, check it out. If you want more information on our integration, go here.

There's a full benefits/features list available on the integration page, but the one I think is most important is now MindManager can be involved in your projects from beginning to end-- TeamDirection keeps it in the loop!

This means people who like their maps can keep them. Conceptualize your project with MindManager, let TeamDirection know about it and TeamDirection will keep that original map updated! If its on a network, then everyone can see the project execute from the comfort of their maps.

Its one way we are providing the right tools for the right people. Task information is more mobile than ever now!

Friday, December 08, 2006

IE 49, Firefox 38

I was looking at my traffic log today and noticed Firefox showing up alot. So I went to my stats:



I wondered if this was skewed toward an international audience, which might be using Firefox more than IE. But not so much:



Now I normally don't get 11 hits from Uganda in a week, much less a couple hours, so its very possible this is a silly sample. (The hits from Uganda were all IE 6, by the way)

However, what I am thinking about is the next applications we will write and how web-based we should make it (answer: very). So I start looking at browser statistics. I know there are a several reputable sites sharing statistics, but I wonder what the blogosphere composite IE/Firefox ratio would look like?

It should track to what the accepted ratio is, but does it? I'd love to know what everyone's 'Last Hundred' browser list looks like.

Thursday, December 07, 2006

.NET Click Once can Learn Something from a Web Browser

In my day job I get to write software and try to run a company. When I moonlight, I get to be a pundit. It's really quite fun-- while scurrying about the code preparing for a release I use one side of my brain. Once the release is out, I start writing and hopefully use the other side of my brain.

In this post I'll try to use both sides of my brain to support an argument I've presented over at Read/WriteWeb. Its a two-part article that basically states Microsoft holds all the cards for capturing the next generation of computing platform, IFF they can get past themselves and improve .NET just a little bit. That is, take a cue from what makes web applications great, apply it to the .NET framework and make rich applications great again.

The article points out how .NET can be improved, but several people claim .NET already has the feature I have in mind. I claim .NET has the marketing checkbox for the feature I have in mind, but not an actual, usable implementation of it. The market must think so to, because up to now 'Smart Clients' have gone nowhere.

When you build a web page, you write the html and include references to things that help you present a page: an image here, a nifty javascript widget there and a form button yonder. What you don't have to do is compile and link everything together-- the browser does it for you. Better yet, it uses the client machine to make smart choices about what to cache and what to update. Very rarely do you need to download all the pieces comprising a web app at one time again.

And when you need to download some pieces, you never see this:



or this:



This is the advantage web browsers and web apps enjoy over desktop apps today. The current solutions I've seen are not transparent. They involve checking for updated install files, which tend to be large for desktop apps, and reinstalling newer setup.exe packages.

I'd rather it be behind the scense and done piecemeal the web way. Two rules:

  • Don't Bug The User -- they don't care they are downloading updates to the app
  • Don't Bug The User -- they don't care they are reinstalling an app
When I make a change to a web application, everyone gets the updates on their next page refresh without any proclamations or calls to action. .NET apps, if they want to be smart, should do the same.

Obviously there are many ways to solve this problem, so this is just an example.

A .NET app still goes through two steps in order to run: compilation and linkage. After compilation, all the component parts of a .NET app are laid out as object files in a directory structure. Usually these object files are quite small. Then the linker performs the final assembly and produces a larger output-- executables or libraries.

What if, for deployment purposes, the linkage step is not done on a build machine, but on a clients computer? What if, when starting a .NET app, a 'smart linker' is used to check for updates by making HTTP requests once in a while to all the objects files referenced on a deployment server somewhere? Then, if it finds an object file or two has been updated, it pulls down a couple kilobytes of data, links it into the app and runs.

Then the next time user with a problem runs the app, they see the problem has been fixed and they write me a note saying, 'Thanks for fixing the problem'.

As a rich application developer and publisher, I want that.

Wednesday, December 06, 2006

Comparing Project Server and TeamDirection Project 2007

And this would be elephant number two in the room. While I could blithely write how we do this and how project server does that and we both do the online web-based project thing in perfect harmony....

I would be lying.

OK, I admit it. TeamDirection Plus 2007 is providing a nice, simple way to connect your MS Project projects to MS SharePoint. Project Server does it by requiring several components, lots of consulting time and training. We do it by selling TeamDirection Project Plus 2007 for $549.

For that price you get:

  1. A desktop app your project manager can install and start sharing tasks in 5 minutes or less.
  2. A flexible bidirectional synchronization that updates data from MS Project to SharePoint, and from SharePoint to MS Project with one click.
  3. The ability to not only share entire projects, but parts of a project. Have a project with 1,000 tasks but only want to share 100 of them? We can do that.
  4. Rich integration with a great project conceptualization-- Mindjet MindManager-- and a cutting edge collaboration tool-- MS Groove 2007.
  5. Multiple project view letting you see many projects at once in a grid and gantt. And foldering to let your organize your projects.
  6. A nice UI, integrated Instant Messaging, Resource that can not only be assigned to tasks but also inherit their permissions from SharePoint or Groove, simple costing and more...

Normally I wouldn't point out in my blog where we compete with Microsoft-- I am in Seattle after all. But really, there's lots of companies that both compete and partner with them. We are no different. For instance, as I mentioned, we also talk to MS Groove 2007-- one of the first companies to do so. We've leveraged our rich history with Groove and its Project Edition and created an excellent solution for the next generation.

In fact, I can make a claim: TeamDirection Project 2007 is the only project application in the world that lets you share MS Project plans with SharePoint and Groove. Hopefully that makes the SharePoint and Groove groups at Microsoft happy. I even think it will make members of the Project team happy because it gives smaller companies-- and departments within large companies-- more flexibility and power for project managers to use the richness of MS Project and the distribution of SharePoint and Groove.

And if they see a grumpy member from the Project Server team, tell him or her its ok to share.