Aleksey Vorona <voronaam <at> gmail.com> writes: > > Hi all, > > Could anyone describe what is the proper way to contribute to R? So > far I was going over r-bugs and trying to write patches for bugs I can > fix. My questions is should I also send an email to somebody? > > It seems that for some old bugs Bugzilla does not send emails. For > example, I went over an old bug #412 and most of it is fixed. I left a > comment about its current status and Bugzilla notified me that no > email has been sent. > > Also, I would really like to get a feedback on the proposed patch to > bug #15211. It would be interesting to see the patch logistic, since > the bug is in Lapack code, not in R itself. > > The "developers" page is more for svn committers. And I am feeling a > bit lost here. If there are casual contributors on this list, could > you sent the best practice description, please? Better still would be > to document it somewhere. >
(1) This might be a better question for the r-de...@-project.org list ... (2) Some (slightly related) discussion on StackOverflow: stackoverflow.com/questions/8065835/ proposing-feature-requests-to-the-r-core-team [url broken to respect gmane's line length limit] ______________________________________________ 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.
