Package development process: Difference between revisions

Revision as of 18:27, 8 May 2012

Revision as of 17:04, 12 May 2012

Line 26:

| title=The Comprehensive R Archive Network | url =http://cran.r-project.org}}</ref> and under development in companion open-source collaborative development web site, R-Forge <ref>{{cite web | title = R-Forge | url=http://r-forge.r-project.org}}</ref>. These checks compile the packages repeatedly on different platforms under different versions of the core R language. The results are made available to package maintainers. In this way, package contributors become aware of problems they might otherwise never encounter themselves, because they otherwise would not have easy access to those alternative test results.

An interesting research question would be to compare the quality of contributions to different [[software repository|software repositories]] and try to relate that to features of the language and accompanying package development process, i.e., the degreeThis ofcould formalityinclude andtrying enforcementto ofcompare standardsthe forrate documentation,of code,growth andof testingcontributed andsoftware to the ratedegree of growthformality ofand usageenforcement of contributedstandards softwarefor documentation, testing, and coding.

==See also==