Yeah, I'll add a duplicate field for the user's email address. I wonder if we could have a direct link to a form to report a doc bug, so the user doesn't have to fight through all the JIRA levels of indirection.
On Mon, Apr 13, 2009 at 3:26 PM, P T Withington <[email protected]> wrote: > Another improvement suggestion for the doc system: Somehow verify email > addresses, either the standard 'type twice' or something... > > And, we still plan on making it so I can tell why I rejected a comment > using a web form? > > Maybe we should allow rejected comments to display for some length of time, > with the rejection reason? > > Begin forwarded message: > > From: P T Withington <[email protected]> >> Date: 13 April 2009 15:24:15.000 EDT >> To: [email protected] >> Subject: Re: OpenLaszlo doc comment for review: 1239648953 >> >> [Guess we should also make people type their email twice. I bet your >> email address is not 'gamil.com'.] >> >> Thanks for your comment, but I have to reject it because it is in fact a >> bug. Please file a bug at jira.openlaszlo.org. >> >> Author: Suzie >>> Email: [email protected] >>> >>> Is the following statement from above in Section 6.1 correct, or was it a >>> victim of search and replace over zealousness? >>> >>> "In earlier versions of LZX (before OpenLaszlo 4), there was an >>> asymmetric mapping between tag and class names, often of the form LzFoo <—> >>> <foo>, as in the correspondence between, say the class name lz.view and the >>> tag name <view>. (Notice in lz.view the mixed case, and the absence of the >>> period between lz and the tag name.) Also there was a distinction between >>> LFC classes and user-created classes. The new lz.foo form is consistent >>> across LFC classes ...." >>> >>> >>> Should the parenthetical statement read: >>> >>> "(Notice in lzView the mixed case, and the absence of the period between >>> lz and the tag name.)" >>> >> >> Personally, I think this is far more detail than is needed. Why document >> the old system, which was simply confusing. The new system is >> straight-forward. If there is a tag named <foo>, the class that implements >> it is named `lz.foo`, for all tags. >> > > -- Henry Minsky Software Architect [email protected]
