@Javier and Chris Gammel (from the Amp Hour podcast) and I were discussing the GOSH “production events” at our dinner after FOSDEM and one of the things that came up from Chris, speaking from experience of helping with the Hackaday contest, and a sentiment that seemed to be echoed by @Javier was that it will be super important to keep the problem description narrow and focused.
I think that this focus is already clear from the draft application outline, however, what could be fleshed out is the definition of how the problems themselves are sourced. For instance: it could be interesting to source the problem definition from outside GOSH from citizens and scientists. A problem that is present in the community so to speak, and then select the participants based on their skill sets rather than start with a GOSHer’s “passion project” and then select participants based on proximity.
I don’t know if it would work, but I thought it was an interesting alternative approach. What are your thoughts?
Either way I’d definitely want to help move this idea forward but at this point I am not clear on how to best do that. Hit me up with some suggestions on how I can help.
@dusjagr is organazing a collaborative, electronics and kit focused event in Switzerland towards the end of the month which I will be joining. Our focus will be to document existing and create new electronics kits of all sorts: a KitSprint. (Though I should probably let @dusjagr announce himself and explain more.)
I know @mariob is another person interested in seeing the “collaborative production events” idea develop as we managed to catch up after FOSDEM and I reminded him about what this idea was about. (@unixjazz we didn’t really manage to talk about this when we met in person but would be interested in your thoughts as well)