I would second that and also volunteer to look at the issues and pull requests as I'm more active on github lately. An Open Source security project I use and also contribute to (ossec-hids) switched to github completeley and they got a huge influx of new contributors and also pull requests that are easily merged and testet. They have an automated compilation running with every pull request using travis-ci so you see if compilation fails before merging changes with the master branch.
There is already an organization for BOINC setup by Rom. How mirroring works is described here: https://help.github.com/articles/about-github-mirrors/ I would think that the github support would help setting this up too. MfG / Regards Christian Beer Am 06.01.2015 um 19:13 schrieb Nicolás Alvarez: > The SourceCodeGit wiki page says "You don't need direct write access > to contribute code to BOINC. Given the distributed nature of Git you > can publish your contributions elsewhere (e.g. on GitHub) [...]". > > But how exactly do people contribute via Github? Push the entire BOINC > repo and post a link to it on the mailing list? > > I think it would be better if there was an official GitHub mirror of > the BOINC repository, which people can 'Fork' and send pull requests > to. I'm not proposing that development is moved to GitHub; the > really-official repository will remain the one hosted on > boinc.berkeley.edu, and the GitHub mirror would only be used for > external contributors to fork. > _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
