Peter,
Regarding "Has SumTotal given up on ToolBook"... Let me share a story...
Perhaps a bit of my history with ToolBook will help show just how much
SumTotal values this product (I should mention that my memory of who came
and went when, and exact timelines, is rather fuzzy - I'm trying to forget
this stuff :) )...
For nearly my entire 14 years at SumTotal, ToolBook ran on the barest
minimum of staff. When I first started, there was a decent sized team. Many
names you'll recognize - Mike Florence, me, Charley Delaney and others, and
later Slade Mitchell, on OpenScript stuff, and Michael Ormes, Joel
Kittinger, John Gossman and 3 or 4 other guys on the system side. There
were 7 or 8 QA guys. When we acquired Aimtech, ToolBook gained three extra
guys who did the initial HTML runtime work. As people left, however, they
were never replaced. So it wasn't long before it was pretty much me,
Michael and Joel on the dev side, Aaron Smith as QA, and Denny as tech
support. And that was pretty much it. Charley came back for a stint for a
while. We used contractors a few times. But essentially we were the team.
Shipping a product that cost people a couple of grand.
At one point (2001 I think), the entire team was pulled off ToolBook -
ToolBook was essentially mothballed, and we were all moved over to the LCMS
team (this was before the release of Aspen 2.0 I think). At that point,
there was actually no expectation that any further work would be done on
ToolBook. We had a TBCON somewhere in the middle of that - the first TBCON
where we didn't have a "look ahead" session (because there was nothing to
"look ahead" to) - it was pretty depressing for those of us from
Click2learn (as it was at the time) knowing the product was dead but not
able to say anything.
Towards the end of that year, Michael Ormes (I think) came up with a plan
of how we could cost-effectively get ToolBook 9 (that is, the 32-bit
version of ToolBook) done - we were ramping up an India office, and we
could hire a larger team there than we could in the US. So, after almost a
year of no development work at all, ToolBook was reborn.
So we started hiring guys in India. Joel and Michael started working on the
32-bit port, and I started working on interim releases of ToolBook (to keep
the cash flow coming until 9.0 was done). New features in ToolBook 8.5, 8.6
and 2004 (8.9) were pretty much entirely me (though Denny contributed a
bunch of stuff as he does for most releases) - 2002 to 2005 were incredibly
stressful years for me, as I was carrying a considerable amount of the
weight for getting features done for new releases while the rest of the dev
team were focused on the ongoing 32-bit port. Somewhere in there we had the
India team helping out with the HTML runtime - in particular scrapping our
old IE4/NS4 support and moving to support Mozilla based browsers.
In 2006 we hired Drew Gillies to work with me in Australia.
In 2007 we finally got TB 9.0 - the first 32-bit version - released. By
this time we had built up a reasonable sized team in India, and put many
many hours of effort into training them up to be solid developers. 9.0 was
short on features, since the effort was getting to 32-bit, but we felt we
were now in a good place - good size team, all familiar with the code base
- to move forward and get some solid new, modern features into the product.
We should have known better. We really should have.
Shortly after 9.0 was released, the company reallocated the entire India
ToolBook team (except one dev - Vishal) to other products. Sigh. Nice thing
was these guys were widely recognized as the best devs on the teams they
went to - thanks to the hard work we had put into training them.
So we were essentially back to me, Joel, Drew, Michael and Vishal in dev,
Aaron Smith as QA and Denny as tech support (and contributing to OpenScript
dev stuff as always). But we were told we had to lose *yet another* dev,
and since Drew was the most recent hire, he was to go. Michael, however,
decided it was time to move on, so Drew got a reprieve. So, things were
back to being as bad as they were before we built the India team - 4 guys
were supposed to add enough features each year to make the product worth
buying, and to somehow remain modern and competitive. And one guy was meant
to QA all of those changes. Sadly, because of this, we were never really
able to do any feature properly - they were always rushed, and always
significantly cut down versions of what we really wanted to do, and always
buggy because of being rushed, and because of limited QA resources.
Beginning of 2010 we got some good news (or so we thought) - two new devs!
These guys were fresh out of college, but we had been there before - we
knew we could train them up and hopefully turn them into solid devs. What
we didn't know at that point was that these guys were hired to be our
*replacements*. In July 2010, Drew, Aaron, Joel and myself got our marching
orders. I was given a couple of months to finish some stuff I was working
on, and spec out features for the next release (of which 1/2 a feature got
kind of done). And then it was all over. Interestingly, during that time I
never received a word of thanks from anyone at the company for the years of
sweat I had put into this product (though of course losing my job at
SumTotal was the best thing that every happened to me).
But let me make this point clear - someone in management thought that two
guys fresh out of college could successfully work on a complicated 20 year
old product with around 4 million lines of code, on their own, without any
help from more experienced devs who knew the product. The words "false
economy" come to mind (well, actually I think "simple stupidity" is
probably closer). For example - the "1/2 a feature" I mentioned above? I
probably could have completed the entire feature in a month, but it took
these two guys 3 months to complete *half* the feature. So that's 6 man
months to do half of what I could have done in a month. This wasn't their
fault - they were inexperienced devs and new to the product. But someone in
management thought this was cost effective. This kind of thinking is why
ToolBook is where it is.
The worst thing for junior devs is to work in an environment without any
more experienced devs to guide and train them. Not surprisingly, those two
guys didn't hang around long.
ToolBook 11 was pretty much entirely the work of two people - Vishal and
Denny. Last year Vishal was let go. The ToolBook team is now down to one
guy.
Denny now truly is Mr ToolBook :)
So... Has SumTotal given up on ToolBook? Yes, I think many years ago,
really. However, for the last couple of years it has gotten much worse. All
I see now is a cynical attempt to suck as much money as possible out of
unsuspecting customers, without putting any real money into developing the
product. Personally I don't want to see *anyone* sinking thousands of
dollars into annual maintenance contracts, since there is simply no
possible way you will get value for money. Well, I actually hope *just
enough* people keep doing it so that Denny can keep his job :)
Tim