Stephen Connolly wrote:
On 10 March 2010 21:48, Ron Wheeler <[email protected]> wrote:
Post things to JIRA (especially with patches) to get things changed. I
assure you, patches with good/useful changes in content will be
well-received and the site/documentation will be updated in due
course.
I am not going to get into "patching". I leave that to the author. I will
suggest rewording or request that clarifying text be added but I will not
create patches.
Then I think you are misunderstanding what we mean by "patches"...
If it is documentation,
* obviously a .patch file for the .apt file would be great (it'll get
reviewed and applied very fast)
* failing that something like:
--- On this page: http://maven.apache.org/....../blah.html current content
is ---
Blah blah blah blah
--- Suggested replacement content is ---
Waffle Waffle Blah Blah
--- On this paget: etc
would be IMHO perfectly fine as a "patch" and it would be reviewed and
applied quite fast
That is much better.
That only leaves my reluctance to open a JIRA without some discussion
first as to whether my "improvements" actually are correct and clearer
than the original author's text.
In other projects, I usually have a chance to present my suggestions to
the author and get his feedback or to ask him/her for additional
clarification or examples before determining that my suggestions are
actually the right way to go.
I have a sense - perhaps misguided - that opening a JIRA issue is a
definite statement that something is wrong and needs fixing.
Ron
-Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
