I am on the fence, because 1) i've been told that I can't use the badges in my final presentation format anymore, 2) team http://pol.is|pol.is has not been able to help me resolve an technical issue that would be important, and it's unlikely to get sorted in the next two weeks, and 3) my other "translation bridge" project is one that I'm told will feel more relevant to participants.

so I'm leaning toward pitching that, but I would wholeheartedly support a badge pitch if you were willing! I'm pretty decent at running community projects, and I think I could still help you out if you wanted to get started on the right foot (and have some enthusiastic collaborators in taipei, if not academic ones!)

ditto for @kevinphy, but I feel like he's got a billion other projects, so I can imagine it might be tough :stuck_out_tongue:

it's pretty low key. i've never been to a g0v one either, you just kinda get up and say "hi, I'm ___, this is what we hope to do, here's what people we need." ("we"s are encouraged even if it's just you at the time.) it can be polished, but doesn't need to be. and if no one shows up, it's ok if your ego can take it. i've had no one show up to my pitches _plenty_ of times, but it help me learn what works and what doesnt :slightly_smiling_face:

oh, and pro-tip, instead of asking for "hard skills", then asking for software ones like "people interested in xxxxxx, or community dynamics" or whatever, then you at least get some other people who are noncoders but will be engaged in convo and stay in the loop

oh man, that is PERFECT pitch size! seriously. just "we're going to assemble a programmer. and then you could kick it off with explaining the goals, and if there are hardware people, they will totally show up and help, and maybe stick around.

if you said "if you're intersted in assembling hardware, drop by," then you would prob get people. these things aren't about finding experts, but about finding community to motivate the work and surprise us out of what we think we know :slightly_smiling_face:

it's pretty low key. i've never been to a g0v one either, you just kinda get up and say "hi, I'm ___, this is what we hope to do, here's what people we need." ("we"s are encouraged even if it's just you at the time.) it can be polished, but doesn't need to be. and if no one shows up, it's ok if your ego can take it. i've had no one show up to my pitches _plenty_ of times, but it help me learn what works and what doesnt :slightly_smiling_face:

oh, and pro-tip, instead of asking for "hard skills", then asking for software ones like "people interested in xxxxxx, or community dynamics" or whatever, then you at least get some other people who are noncoders but will be engaged in convo and stay in the loop

oh man, that is PERFECT pitch size! seriously. just "we're going to assemble a programmer. and then you could kick it off with explaining the goals, and if there are hardware people, they will totally show up and help, and maybe stick around.

if you said "if you're intersted in assembling hardware, drop by," then you would prob get people. these things aren't about finding experts, but about finding community to motivate the work and surprise us out of what we think we know :slightly_smiling_face:

20181214-NR.pdf

2018-12-13

Hey @kevinphy :) was researching the stencil technique that Oren mentioned on mailing list, and wondering whether our solder paste technique on accelerometer will actually work, or instead connect all the pads. From an article I found on the technique:

> When you lay this stencil over your bare board, you can squeegee a layer of solder paste over it, leaving a nice, uniform layer of solder on all of your SMD pads. This makes it easy to assemble your next prototype, where the natural alternative is to *apply solder one pad at a time with a syringe*, then times that by 100, 200…1000!?