On Aug 21, 2013, at 5:51 PM, 永豪 <[email protected]> wrote:
> I haven't go through many codes indeed, but TS-2143 make me sad, I love ATS
> because in most case, we can provide a working solution for your requirement.
> when you grow up, with big volumes, you will find out that ATS still work,
> and you may discover more features than your imagine. it is a good user
> experience compare to some other system, when you find out that the system
> builder is really 'user oriented'.
>
> while we are still on the way to codes revolution, I really don't want we
> break that promise, turns ATS into another low quality codes just because we
> are free as in beer.
>
> most of our active committers are working for big company, with tons of good
> servers, but we have newbies everyday, they need a good start from any point,
> one easy start. ATS is a big monster compare to the others, why can't we make
> it nice for the freshmen?
>
> things I'd like to keep:
> 1, feature should be outlined, and should keep revolution in a user friendly
> way
> 2, provide basic system 'it just work'
> 3, user interface changing should get more review before we can release into
> public
Yes, I strongly agree with all 3 of these points, though I don't think this
particular commit is too problematic, particularly since we never actually
installed the example_alarm_bin.sh script :)
I looked at the alarm documentation and there's a few things that we can
improve:
- the docs still reference example_alarm_bin.sh though it no longer
exists
- the docs reference proxy.config.alarm_email, though it's no longer
clear what this is for
- there's no documentation of how to configure ATS to invoke your
custom alarm script
- we don't provide any real-world sample scripts or real advice on how
to write one
- we don't provide any documentation on what an alarm is or what kind
of events cause alarms
All these issues can (and should) be fixed. There's quite a bit of alarms
material in the original Inktomi documentation that is not present in out
current docs.
J
