Okay, cool. Let us make it official.
----- Rom -----Original Message----- From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Christian Beer Sent: Friday, January 09, 2015 5:56 AM To: boinc_dev@ssl.berkeley.edu Subject: Re: [boinc_dev] Official GitHub mirror? I fiddled a bit with travis-ci and got it up and running for my github fork. See: https://github.com/ChristianBeer/boinc-v2/tree/travis-ci-test there is also a nice picture at the bottom of the page build information: https://travis-ci.org/ChristianBeer/boinc-v2 The current config just builds the components (libraries, server, client+manager) and fails if the compiler reports an error. It just monitors the travis-ci-test branch. I would be willing to maintain the travis configuration. A possible roadmap for this could be: - split up client and manager - add a simple syntax test for php code - add some more elaborate tests (it should even be possible to create a project inside the VM) - add a windows build test (this seems not to be trivial and a build node should be provided for this) travis-ci is free for open source projects and uses ubuntu based VMs as build nodes by default (community supported). MfG / Regards Christian Beer Am 08.01.2015 um 19:58 schrieb Rom Walton: > You can find the mirror here: > https://github.com/BOINC/boinc-v2 > > ----- Rom > > -----Original Message----- > From: Rom Walton > Sent: Thursday, January 08, 2015 1:58 PM > To: Rom Walton; Filip Rydlo; BOINC-dev email list > Subject: RE: [boinc_dev] Official GitHub mirror? > > The github mirror should be up and running. > > I'm not sure what to do about the pull requests yet, it looks like the web > services just send json requests to a remote server. I was hoping for a > simple "if pull request accepted, push to origin" type of thing. > > I guess we will cross that bridge when we get there. > > ----- Rom > > -----Original Message----- > From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf > Of Rom Walton > Sent: Thursday, January 08, 2015 12:19 PM > To: Filip Rydlo; BOINC-dev email list > Subject: Re: [boinc_dev] Official GitHub mirror? > > We'll investigate getting this setup. > > ----- Rom > > -----Original Message----- > From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf > Of Filip Rydlo > Sent: Wednesday, January 07, 2015 12:30 PM > To: BOINC-dev email list > Subject: Re: [boinc_dev] Official GitHub mirror? > > me too! > > I would welcome this very very much! > This would let me experiment and make the Grand *redesign* of the advanced > view's "Tasks" tab. > > Not only the columns will be "checkable" which are to be > displayed and their *order* can be selected by the user in the GUI, but > the user will be able to *CREATE* and save/load *several* "profiles" > !! So that he / she does NOT need to change it manually whenever he / she > needs to "switch" to different point of view to solve / check different > issues / idling cores / GPUs etc... resource-share / backup projects.... > also the ordering will be much more optional and will remember up to 5 > columns by which it will sort - sorting order of the columns will also > be saved/loaded in the *profile*. :) > > > * This should make the LIFE of many scientists and power-users much > much easier!* > > It will take me some time, however .... I will *design* the > internal (optimal / ideal) API for this with "Apiary" and API > Blueprint tools ... then I will create a good WRAPPER which will kinda > "isolate" me from the *awful wxWidget low-level code* and then ... it > is EASY ----- "The path ahead is clear. ..." ! :-) > > So, thats the plan. What do You say? > > > (attending in person the meetup in Prague ... which is a workshop for the > Apiary + API Blueprint ! So I will know to use them *directly from > their author*!! Hopefully, it will be enough-GREAT a lecture. Wish me > luck - I need to learn this really *WELL* if I am to use it inside of > BOINC Manager ;) ) > > > *Namaste* > Filip > > > 2015-01-07 16:04 GMT+01:00 Christian Beer <christian.b...@posteo.de>: > >> 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. >> > _______________________________________________ > 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. > _______________________________________________ > 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. > _______________________________________________ > 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. _______________________________________________ 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. _______________________________________________ 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.
