Thank you Mark, this is what I was looking for. On Sunday I will read again in detail previous discussion's facts, and attach the pros and cons here, so that they remain for the future, and the topic can be closed.
Juan El 4 ene. 2018 11:06 a. m., "Mark van der Loo" <mark.vander...@gmail.com> escribió: > This question has been discussed before on this list: > http://r.789695.n4.nabble.com/Why-R-project-source-code-is- > not-on-Github-td4695779.html > > See especially Jeroen's answer. > > Best, > Mark > > Op do 4 jan. 2018 om 01:11 schreef Juan Telleria <jteller...@gmail.com>: > >> UNBIASED FACTS: >> • Bugzilla & R-devel Mailing Lists: Remain unchanged: Understood as >> Ticketing platforms for bug pull requests on the R-devel Git Repository. >> >> • Git Repository Options: >> A) Github (Cloud with Automated backups from GitHub to CRAN Server): >> https://github.com >> B) Gitlab (Selfhosted on CRAN): https://about.gitlab.com >> C) Phabricator (Selfhosted on CRAN): https://www.phacility.com >> D) Microsoft Codeplex: https://www.codeplex.com >> E) Others: Unknown >> >> GOOGLE TRENDS: >> https://trends.google.com/trends/explore?date=all&q=Git,Svn,Github,Gitlab >> >> EXAMPLE >> Git Repository on Core Python: https://github.com/python >> >> PERSONAL OPINION / MOTIVATION: >> I think that moving efforts in this direction is important because it >> would >> allow a true Open Source Innovation & Open Collaboration in R between: >> * R Community. >> * And R-Core. >> For: >> * R Bug Fixes. >> * And Core Feature Wishlist. >> As anyone would be able to: >> * Check the unassigned bugs in Bugzilla (apart from R-Core). >> * And propose bugs fixes by themselves as Pull requests (by mentioning the >> Bug ID of Bugzilla or the Mailing Lists). >> >> This would allow that _individuals_ either from Universities or Companies >> interested in the Development of R: >> * apart of donating economical resources to the R Foundation. >> * could help to maintain core R Code by themselves. >> Which aligns with the true spirit of R, which shall be done from >> contributing individuals, for individuals themselves. >> >> It would also allow to put the focus on the precise lines of code changed >> with each Commit, and revert changes in an easy way, without verbose >> E-mails: Tidy, Clean, Maintainable, and Fast. >> >> At last, I noticed R-devel Archives do not have an E-mail Id (Unique >> Unsigned Integer), so it would be a good idea to add one for pull requests >> if Git was adopted. >> >> Juan >> >> [[alternative HTML version deleted]] >> >> ______________________________________________ >> R-devel@r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel > > [[alternative HTML version deleted]] ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel