>sf.net: >+ move there already done >+ "open" platform (though it does not really matter much with git, right?) >+ already used for Wesnoth mainline file hosting >- - webinterface sucks (and full of ads so adblocker seem to be a must have) >- - slow clones, pushes, and pulls based on geographic location
>github.com: >+ "cool" (with highly usable webinterface) >+ already used for several wesnoth subprojects >+ documentation already written >+ official clients for Mac and Windows >+ the poll results are leaning heavily github >- - some parts are not open source >- - will not host our files Github's interface is far more than "cool". It is highly useable. Potential contributors are able to fork the repository in seconds online. Then after cloning their fork and pushing their changes, they can make what is called a "pull request" online in a few seconds. We are then able to view the full diff of this patch and accept or deny it - again online in a few seconds. You literally click a single button and their patch (containing one or more commits complete with their user info) is automatically merged. The full diff of every commit can be viewed online with syntax highlighting for every language imaginable, and that part of the site is open source (as are many others). If a syntax highlighting scheme is invented for WML, we can submit a pull request. (source code here: https://github.com/github/linguist ) We're able to leave comments on these commits down to individual lines of code. Their site is full to the brim with tutorials on how to use git. Everything you could want to know is there and well explained. They have developed highly functional Windows and Mac git clients - again with tutorials on how to do everything. If I understand correctly, sourceforge doesn't mirror the repositories. That high bandwidth is only true for the file downloads. Others in #wesnoth-dev have reported clone speeds of 17 kilobytes a seconds. The bandwidth point is null and void as far as code hosting goes. I believe it was said earlier in the mailing list that Github integrates very well with external bug trackers. We're able to create and submit our own post-commit hooks. (source code here: https://github.com/github/github-services ) We can also create pages on wesnoth.org that Github will make POST requests to on-commit.
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
