2012/9/22, Bartosz Kaszubowski <[email protected]>: > Hello BOINC Devs, > > Did you ever discuss or dispute about moving BOINC development to GitHub? I > am sure that I do not have to write about all advantages of this platform > and community gathered around it so I have just move on to the question. > > I'm very curious - because I did not have enough knowledge about any > limitations according to university status of BOINC project - is it the > major reason why to this day BOINC source is not avaiable at GitHub?
To make the source "available" on github, first the SVN repository would have to be converted to Git, which is a hard task (already in progress). But I see absolutely no reason to move the *official* development of BOINC to github instead of keeping everything in the local infrastructure of the university. What advantages would that have? Github's bug tracker has significantly less features than Trac. I'd dare say the same applies to the wiki. And who would migrate our 1210 bugs and 414 wiki pages? (are you volunteering? ;) So yes, you do have to write about all the advantages of the platform if you want to argue for moving to it... -- Nicolás _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
