Hello dear R users,

*Here is the background for my question:*

I just had a look at the help file for
? Yeast
in the "HistData" package.

In it, I found a small spelling mistake where the word "*c*istribution" was
written instead (so I imagin) "*d*istribution".
I thought maybe I should e-mail the developer. Since there is no link to
contacting the developer inside that help page, I went and googled the
package name. Found it's place on cran (in the third result), where I found
the maintainer to be Michael Friendly <friendly at yorku.ca>  (Whom I am
corresponding to this e-mail).

So it took me three steps to send a tiny typo: search the package on google,
find the maintainer e-mail (where "at" should be changed to "@"), and
writing an e-mail.
How could this have been faster?

*Proposed solutions:*

One (simple) way, is for the help page to have the maintainer e-mail present
at the bottom of every help page. Where upon clicking the link - an e-mail
will popup with the e-mails subject header containing the package and the
relevant help page title.
Another (more complex, but more scalable) way, is if the help page could
have been also present on some wiki. Inside the help page, there would be a
link to an "edit" section on the online wikipedia (R-help-epidia)- where I
could have just went and fixed the type.

 What do you think, and who should I propose this to?

Best,
Tal






----------------Contact
Details:-------------------------------------------------------
Contact me: tal.gal...@gmail.com |  972-52-7275845
Read me: www.talgalili.com (Hebrew) | www.biostatistics.co.il (Hebrew) |
www.r-statistics.com (English)
----------------------------------------------------------------------------------------------

        [[alternative HTML version deleted]]

______________________________________________
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

Reply via email to