Tracking the progress of Minotaur

Grok Headline matches for Tracking the progress of Minotaur

Broadlook--#1 Applicant Tracking
Software Solution--Empowers your
Applicant Tracking Software and fills
your Applicant Tracking Software with
applicant tracking relationships.

Broadlook--#1 Applicant Tracking
Software Solution--Empowers your
Applicant Tracking Software and fills
your Applicant Tracking Software with
applicant tracking relationships. 07/16/2004 03:14 AM
Whichever applicant tracking software your company uses, you need to look at the Broadlook Suite of Software which should seamlessly integrate with whichever applicant tracking software you are using. BroadLook is an integrated set of applications designed to harness the Internet as a powerful real-time data source--the data from which can be exported into your applicant tracking software. [PRWEB Jul 16, 2004]

Minotaur Monitor

Minotaur Monitor 05/03/2004 12:27 PM
Pre-Alpha Release

Center for American Progress - The
Progress Report - Page

Center for American Progress - The
Progress Report - Page 02/17/2004 06:09 AM
The President's Pal and Business Partner Will Make Millions From Drug Card Program He Helped Design .. The Progress Report: 'Imminent' Semantics; Playing the Blame Game 1/30 .. IRAQ - Intel Warnings Ignored

americanprogress.org/site/pp.asp?c=biJRJ8OVF&b=6228#1
track this site | 5 links

The continuing saga of Minotaur...

The continuing saga of Minotaur... 03/13/2003 10:14 AM
Should I get my hopes up? Bugzilla Bug 173084 Minotaur is getting resurrected again. Here is an updated config patch against the trunk. More to come...hopefully......

PC Case Roundup: Minotaur

PC Case Roundup: Minotaur 04/15/2004 01:09 PM

Diabolic Minotaur Mid-Tower ATX Case
Review

Diabolic Minotaur Mid-Tower ATX Case
Review 01/11/2004 07:55 AM

Clockware Releases Version 4.4 -
Significantly Enhances Timesheet Styles,
Expands Status Tracking, Employee and
Organizational Data Tracking Features

Clockware Releases Version 4.4 -
Significantly Enhances Timesheet Styles,
Expands Status Tracking, Employee and
Organizational Data Tracking Features 04/05/2005 04:50 AM
Clockware announces its seventh major release in eight years, adding enhancements to its enterprise timesheet software, time tracking, leave and exception time tracking and other key timesheet system features. [PRWEB Apr 5, 2005]

Tracking Blogs, Tracking Packages --
What's The Difference?

Tracking Blogs, Tracking Packages --
What's The Difference? 03/31/2005 09:04 AM
Extreme Tech Mar 31 2005 1:16PM GMT

Foxconn Casedge Diabolic Minotaur
Designer Computer Case Review

Foxconn Casedge Diabolic Minotaur
Designer Computer Case Review 04/22/2004 06:35 AM

HD Audio: Progress, But Still a Work in
Progress

HD Audio: Progress, But Still a Work in
Progress 09/10/2004 06:51 PM
Intel's High Definition Audio is beginning to ship on some 915 and 925-based motherboards, but is HD Audio a solution without a problem? And what about DVD-Audio support?

Victor Davis Hanson: Feeding the
Minotaur - Our strange relationship with
the terrorists continues

Victor Davis Hanson: Feeding the
Minotaur - Our strange relationship with
the terrorists continues 06/14/2004 05:48 PM
head

nationalreview.com/hanson/hanson200406140811.asp
track this site | 4 links

Web Tracking of Billable Time Improves
Productivity and Bottom Line/New Kyebot
Time Tracking and Billing Software
Announces Availability

Web Tracking of Billable Time Improves
Productivity and Bottom Line/New Kyebot
Time Tracking and Billing Software
Announces Availability 09/13/2004 02:58 AM
New Web-based time and billing application simplifies administrative tasks associated with tracking billable hours and virtually eliminates problems with under-billing. [PRWEB Sep 13, 2004]

Tracking the newsroom bug-tracking idea

Tracking the newsroom bug-tracking idea 02/01/2005 09:42 PM
I want to return to the idea I floated a few days ago about bug-trackin g software for newsrooms. The comment s response ranged from "neat idea!" to "it'll never work," so let's look it over again.

What I imagined was something similar to the way open-source software development projects manage bug reports. When people file bugs against such a project, they go to a publicly available online resource and enter a form that says "Here's a problem I encountered," and provide details. Different projects follow different organizational structures, but generally speaking, other developers will review the bug and try to classify it: Sometimes they'll say it's a duplicate and point to previous entries in the database that dealt with it; sometimes they'll say it's a simple problem and go fix it right away and close it out; sometimes they'll say it's a big one and leave it open to be dealt with in the future; sometimes they'll say it's a "known bug" that for one reason or another is never going to be fixed; sometimes they'll say it's not a bug at all.

For a newsroom, the idea is to provide a structure and a channel for reader dissatisfaction. You wouldn't have to follow the software model detail for detail, but the general outline could be valuable: Provide a form for readers to enter complaints, one that requires them to present details. Post the complaint publicly as soon as it's entered, and record the publication's response in a reasonably prompt fashion -- anything from "Thanks, we fixed the spelling on that name" to "we chose the phrase 'private accounts' because it is an accurate description of the president's proposal, and the label was in wide use by supporters of the idea until very recently, so we do not plan to stop using the term." The explanation is on record, and if other readers keep filing the same complaint they can simply be pointed back to the original answer. Spam? Just delete it. Letters to the editor that don't have a specific complaint? Re-route them to the letters box.

The most common objection seems to be, forget it -- this will become another free-for-all for political partisans to work out their agendas, another wide-open Internet forum that will degenerate into circular debate. Such forums already exist, to be sure; the point of a bug tracker is to avoid that outcome by choosing a narrower environment for the feedback that allows you to quickly aggregate and dispose of duplicate complaints, and that provides a public record of responsiveness and accountability. If 500 people all holler that you shouldn't say "private accounts," you can answer them once and be done with it -- but you can point each individual complaint back to your explanation, so those people understand that you actually heard them and offered some sort of response. There's a big difference between the silence of no response and "no, we're not doing that, here's why." The latter won't satisfy everyone, but it at least acknowledges that there's been an exchange on the subject.

Ross Karchner proposed a somewhat different model based on wiki practices: "1) A publically viewable changelog, where you can see, in detail, the changes made to an article. 2) A place where the author(s) and editor(s) can discuss the changes needed and made. This is also in public view..." I'm not sure whether Ross means the changelog and the writer/editor dialogue to commence from the first time the writer composed a draft, or only upon publication. The former is, I think, too wide open -- even a blogger has the right to compose a posting and revise it in private before choosing to push the "publish" button. The latter is fine -- but since most reputable publications rarely change articles once they're published, and note the changes as corrections if they do, then it's just codifying an existing practice in slightly different ways.

As for the idea of trying all this out at Salon: Who knows, I might well advocate it, though my current on-leave status doesn't put me in a good spot to work on it. But Salon has been dealing with the back-and-forth of online criticism of our work for 9 years plus. Whatever problems we may suffer from, a failure of responsiveness to online feedback is not, I think, one of them, and we have a pretty sturdy process for reviewing complaints fast and correcting them where needed.

I think this approach would pay off best for a newsroom that is having difficulty convincing readers that the publication is actually listening to them. If you showed the public that you were recording and responding to the issues they raised -- whether you end up publishing a correction or simply saying, "We don't think that needs correcting, and here's why" -- I think you'd start to bank some confidence and trust pretty quickly.

I'm not suggesting that this idea is the single, one-fix-solves-all-problems answer to the ills of journalism today. It's a pragmatic, you-could-do-it-real-soon suggestion for beginning to deal with professional journalism's biggest problem: the public's loss of trust, which begins with the sense that media companies are big institutions that pay no attention to their own mistakes.

Building a Progress Bar that Doesn't
Progress

Building a Progress Bar that Doesn't
Progress 09/23/2004 12:55 AM
In many situations, accurately estimating the length of a certain process (copying a large file, loading data from a server, retrieving files from the Internet) would be both difficult and inefficient. What you end up with is a process that is going to take long enough to make the user wait, yet you have no easy way to indicate the percentage of the task that has completed. A regular progress bar would be rather meaningless, so you need some form of "Working…" indicator.

"More from Think Progress"

"More from Think Progress" 03/17/2005 02:51 AM

From Think Progress,

From Think Progress, 03/24/2005 08:43 AM
Tom DeLay Uncensored .. CAP

thinkprogress.org/index.php?p=503
track this site | 4 links

"think progress "

"think progress " 03/23/2005 04:58 PM

This is Progress?

This is Progress? 01/04/2004 03:53 AM
From an iBook on my lap, wirelessly connected to a router plugged into a cable modem connected to my service provider, wired into the internet backbone with countless hops between here and Nasa's web servers, which dish up live...

"Mod in Progress"

"Mod in Progress" 08/19/2004 09:20 AM

3G Progress in Europe

3G Progress in Europe 11/05/2003 06:27 AM
3G Nov 5 2003 5:42AM ET

NetNewsWire 1.0.2 progress

NetNewsWire 1.0.2 progress 03/19/2003 10:44 PM
In case you’re curious on how NetNewsWire 1.0.2 development is going...

It’s a four-step process:

1. Move low-level, relatively bug-free code into separate frameworks. The RSS parser, for instance, goes into a framework. (The main reason is that it makes code maintenance and testing easier, and it makes it so I can re-use this code easily in other software.)

2. Fix a bunch of small quick-hit bugs. Things like bugs with date display and keyboard shortcuts. A particular crashing bug in the weblog editor. That kind of thing.

3. Fix—or at least dramatically improve—performance and memory issues when one has lots of subscriptions and lots of unread headlines.

4. Add a few new features—mostly weblog editing features such as supporting more Radio and Movable Type options. (Some other things too.)

I gave myself a week to do step 1—but it’s already finished. I did it over the weekend. It was totally fun, by the way. If you’re a Cocoa developer, but you’ve shied away from building frameworks, you should know that it’s a piece of cake.

So now I’m in the middle of step 2, doing a bunch of quick-hit bug fixes. This is one of my favorite things to do, because it’s all about polish, getting the details right. With some good hours of brain-time you can knock off bugs by the anthill.

Later this week I’ll move on to performance and memory issues, then on to adding new features probably next week. Then I’ll release the first beta of 1.0.2.

ISS expects Progress

ISS expects Progress 08/10/2004 05:47 PM
USA Today Aug 10 2004 10:27PM GMT

Redesign *Still* in Progress

Redesign *Still* in Progress 01/09/2004 09:56 PM

Yes, yes, I'm still working on it. A few of the designs aren't uploaded yet, but you will find that the default "Clean" look is very similar to the previous Safari design (for those of you who objected to the other designs).

iCommons Progress

iCommons Progress 04/26/2004 06:08 AM
In the first quarter of the current year, iCommons has made significant progress in porting the CC licences - based on US-copyright law - to other jurisdictions, thereby internationalizing the movement. By early April, three European countries (Germany, Croatia and the Netherlands) as well as Australia and Jordan had come up with the first drafts of their respective licences. Austria and South Africa are scheduled to be next. In total, some sixteen jurisdictions have now launched their final or preliminary drafts.

to promote ... progress

to promote ... progress 06/05/2004 01:42 PM
More from Jerry Lobdill, who writes about his own wonderful experiences with the existing copyright system:

I am a small businessman. Among other things I am interested in publishing a few things. I have multiple interests, so the subjects I'm interested in vary. One of my interests is the history of the US, especially the era of the wild west. I have discovered an out of print book that is extremely important to students of the wild west. It is extremely rare and was published only in first edition in 1928. This book was renewed in the name only of the author in 1955, and under present law will not enter public domain until 2022. (According to my research no published works will enter the public domain until 2019.) However, the author died in 1963. He had no children, and his wife died in 1976. Her will does not mention any copyrights. I am obtaining a copy of the will of the author but have not seen it yet. I have had the US Copyright Office do a paid search, and all they have on record is that the author renewed the copyright in 1955. There is no record of transfer of ownership on file. I inquired of the original publisher if they knew anything about the author's copyright and was first told that they knew nothing about the book of interest. Then, they said they thought they owned the copyright but were investigating to be certain. Then I was told that they definitely owned the copyright. When I asked for a xerox of the copyright transfer document that law prescribes, transferring the renewed copyright to them, they refused to produce it, saying that their policy is not to provide such information to "private parties". When I explained that I was thinking of republishing the book and that the US Copyright Office records show that the renewal belonged to the author only, and that I needed proof of their claim before negotiating for publishing rights, I was told that I was too small a publisher to qualify. So...here I sit, with an extensive file that contains no transfer document. The US Copyright Office has no record of a transfer of ownership, and I feel that there is a strong possibility that the publisher is lying about ownership. If so it would not be unusual in today's environment. They probably hoped that I'd negotiate with them without proof. As a result of this situation I have spent money and time and have only a written assertion of ownership without proof. Were it not for this unsupported claim I would know that there was a transfer or that there is no one alive who is likely to challenge my republication of the book. The law is flawed in my opinion if it requires a written transfer of ownership (like real property) but does not require a claimant to produce the proof of ownership except in the context of a copyright infringement suit. If you agree, what can be done to get the law repaired? The way it is now it invites and rewards false claims of this sort to the detriment of reasonable use of works that are effectively public domain.

(cf. "It's simple.)

Check out Think Progress

Check out Think Progress 02/05/2005 09:06 PM
New weblog: Think Progress, a project of the American Progress Action Fund. They did a terrific job tonight live-blogging the State of the Union. They took something that Bush said, and then pointed out the facts, with links to backup...

Progress Report

Progress Report 01/27/2003 08:03 PM

I've been making some progress on polishing off the new web design. Below are some things I've fixed worth noting:

• Disabling of Javascript in comment links.
• RSS improvements
  • The RSS feed works in aggregators now (like Sinderella and Amphetadesk).
  • I've added the dc:date field to my feed now for easier viewing in aggregation programs.

And some things I'm working on:

• I am working on getting my CMS ready for release.
• New email validation for the comments.
• Extensive mac testing (the Mac I was using for testing at work was taken away for repair. I've heard Safari doesn't work with the dynamic stuff here, I'll be correcting that ASAP).
• Comment previewing
• Non-dynamic commenting
• Switching to a new webhost (reccomendations?)

Elsewhere, one of my two cats is being features over at Stonefishspine's ZenCat. This is the rather large, but perpetually friendly (despite how he looks in the photo) Monty. Drop by and leave a haiku.

Progress on TopStyle Pro 3.11

Progress on TopStyle Pro 3.11 06/24/2004 02:46 PM

Even though I'm posting more about FeedDemon lately, most of my work these days has been with the upcoming TopStyle Pro 3.11. Version 3.11 will focus on bug fixes rather than new features, and will be a free upgrade for existing 3.10 customers. I don't have an expected release date at the moment, but it shouldn't be more than a few weeks before a beta is available.

BTW, among the problems fixed already are these two bugs, which have been the most commonly reported ones:

• The file panel paints a "ghost" image when the screen resolution is above 1024x768 (only occurs on certain graphics cards)
• Access violation on Windows 98 when viewing files that have a corrupt (or missing) creation date

Progress: The .4A Milestone

Progress: The .4A Milestone 07/23/2004 11:19 AM
The team hit the .4A milestone. It took an extra week and we got 90% of the way there, not 100%, but it was an impressive performance. The new planning and scheduling system is working, and we're on track for the rest of 0.4B (August) and 0.4 itself (October). We've...

Redesign in Progress

Redesign in Progress 12/16/2003 09:57 PM

Pardon the mess. Redesign currently in progress.

Tomato Progress

Tomato Progress 10/29/2003 12:10 AM
I have 33 tomato seedings, ranging from 2 to 6 inches in height. The Amish Paste, Orange Banana and Glacier tomatoes look pretty healthy (perhaps a bit too tall). The Brandywine are still very short; I received these from a friend, and I suspect they're a long-season tomato. I'll need to transplant the tomatoes into the garden sometime in the next few days.

Progress on new net domains

Progress on new net domains 06/06/2005 12:07 AM
News.bbc.co.uk - Fri Jun 3, 11:12 am GMT

Progress Paralysis

Progress Paralysis 09/16/2002 05:39 AM
WebTechniques Sep 16 2002 4:25AM ET

Corporate Development Progress

Corporate Development Progress 12/17/2004 06:43 PM
Long before I joined Six Apart, I chose Movable Type for my first weblog VentureBlog. It was an easy decision...

X-Prize Progress Update

X-Prize Progress Update 12/16/2003 07:38 PM
savuporo writes "The X-Prize organization has released a summary document (PDF), detailing the recent progress and immediate plans of 13 different competing ...

Progress on second home tax move

Progress on second home tax move 12/27/2004 07:04 AM
Plans to give local authorities new powers to vary council tax rates for holiday homes take a step forward.

Have 25 Years of Progress Helped?

Have 25 Years of Progress Helped? 09/01/2004 05:51 AM
At this year's Ars Electronica, the largest annual festival of technology and art, organizers are focusing on a simple question: Have the technological advancements of the last quarter century helped or hurt us? By Michelle Delio.

X.org Making Fast Progress

X.org Making Fast Progress 09/05/2004 08:16 PM

Net turns 35, but still work in progress

Net turns 35, but still work in progress 08/30/2004 03:37 PM
San Jose Mercury News Aug 30 2004 7:12PM GMT
Grok Description matches for Tracking the progress of Minotaur
GrokA matches for Tracking the progress of Minotaur

Tracking the progress of Minotaur

The following phrases have been identified by the grok system as matching this entry: