Hi Richard, On 29/03/2017 17:07 , Richard Haselgrove wrote: > Not every project updated (or updates) their BOINC servers > synchronously, > and http://boinc.berkeley.edu/dev/forum_thread.php?id=7704&postid=45186#45186 > shows > how I was able to demonstrate that - *even after the project said they > had updated their server code* - a missed include file was still > responsible for misleading task outcome information on their website.
This isn't whole truth though. Christian described the problem well in another reply in this thread. I just added a few comments to that in my mail from Thu, 30 Mar 2017 09:25:07 +0200. > That diagnosis would not be possible today. To the contrary: if the project *wants* external help it can always choose to publish *their concrete fork* of BOINC on some Git hosting platform, either in private for a closed group of volunteers or fully public (beware of sensitive details!). This way helpers like you would even be more powerful as they can review the code that's *actually* running, not just its original base version. You can trace back everything that happened locally to create the current state. That wasn't possible with svn. Again, it's up to the project to decide to harness that power. Also, regarding the "intermediate level between 'cruncher' and 'developer'" discussion: if you understand svn you can also understand git to a useful level :-) You don't have to be a "full-blown developer" and you don't even have to "master" git. Cheers, Oliver _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
