Re: [boinc_dev] [boinc_projects] keywords

Details of the project I described are no longer available on the web, but they can be explored here: https://web.archive.org/web/19961221214555/http://www.funderfinder.org.uk/ On Monday, 17 July 2017, 11:44, Richard Haselgrove wrote: That intervention

Re: [boinc_dev] [boinc_projects] BOINC 2017 Workshop - Paris - Sept 6-8

Hello Jord, When planning the BPINC 2017 workshop we originally included as possible dates to start from the day after the end of BOINC fast to allow people to combine trips. Unfortunately and as may have been noticed from the current agenda, the workshop is intended to have significant

Re: [boinc_dev] [boinc_projects] keywords

That intervention has prompted me to look more closely at the 'Job and Project Keywords' design document. It reminds me very much of a project I was involved in between 1990 and about 2005. I was the sole coder on the team, but the philosophy and design were led by a project leader above me.

Re: [boinc_dev] [boinc_projects] keywords

I just want to voice my disagreement with the process in which this proposal was handled. There was barely time to comment and so far no one did but implementation into the master branch has already started for what seems to be a major change to Client and Server code. As a volunteer contributor

Re: [boinc_dev] [boinc_projects] keywords

Richard: Thanks for the comments. In the current framework, keywords have "symbols" as well as integer IDs: https://boinc.berkeley.edu/keywords.php?header=c https://boinc.berkeley.edu/keywords.php?header=python This makes it easy to specify them e.g. in job-submission programs. I think it's