Release candidate for next documentation section

5 views
Skip to first unread message

Alan Jump

unread,
Mar 29, 2011, 8:00:55 PM3/29/11
to open-sourc...@googlegroups.com
Here's the "operation" section of the manual for final review. Barring
qualms, complaints or error reports, I plan to integrate this with the
Configuration section and release it as one document.

I'll be starting on the "advanced configuration" section next, which
will go into detail on the settings on the Config page and (if I can
ever get it to work!) setting up automatic emails for dispatching and
notifies.

73 de N5ILN/6
Alan

Using Tickets.pdf

Arnie Shore

unread,
Mar 29, 2011, 9:08:15 PM3/29/11
to open-sourc...@googlegroups.com
Alan, thanks for sticking to this; a difficult job, but mandatory IMO for tickets to mature.  We've had other startups, but yours is the only one to reach this level of completeness and quality. 

Now some odds and ends:

Page 5.

      Re Multiple: this attribute is oriented to use by those shops where a given unit may be assigned multiple "incidents" for a given run, Animal Control being an example, or lab/hospital pickup, etc..

      Re the tracking selection.  It's worth noting that the Config screen offers a testing capability for each tracking system, to assist in confirming that the selected tracking settings work.

Page 6.

      Your call re how to handle this, but the next release will allow unit association with ANY user category.

Page 7.

      We've discussed this before, but NO system can " ... predict the correct route of travel between ... "  The best we can do is to  report the shortest straight-line-distance.

Page 8.

      As you say, location may also be entered as something like "Route 50 and 97" when intersection information is available rather than street address.

      The signal can be any commonly used phrase to save some keyboarding;  e.g., "unit instructed to return to base ASAP".

AS

Alan Jump

unread,
Mar 29, 2011, 11:52:48 PM3/29/11
to open-sourc...@googlegroups.com
The feedback is greatly appreciated. Now, you know your release schedule
better than I do. Should I hold off on the general release of this
section, or go ahead and put it out for use? If there are significant
changes coming up soon, I'd rather have an up-to-date document users can
refer to (and Kevin can put in the installer). If it's still a couple of
weeks or more out, I'd like to get the manual up for users to grab and
put to use.

73 de N5ILN/6
Alan

Arnie Shore

unread,
Mar 30, 2011, 12:26:12 AM3/30/11
to open-sourc...@googlegroups.com
Alan, pls go ahead and publish it at yr schedule, but do make it clear to readers that it documents version xxx.

AS
Reply all
Reply to author
Forward
0 new messages