[SGVHAK] Apr 7th HAK meeting

[Lan Dang]

For what it is worth, I am planning on attending the Hackaday event.  The talks seem interesting and I am eagerly looking forward to a Show and Tell at the new Design Lab.
That said, I hope we won't have too many conflicting meetings as I don't want to have to make this decision too many times.

Lan 
 
  On Thu, Mar 31, 2016 at 5:31 PM, nopbin at gmail.com<nopbin at gmail.com> wrote:   
Perhaps a helpful guide would be to know how many people plan to attend the work meeting.

Personally I think an overriding consideration is what Dave as host wants to do, which might be informed by how many people plan to come.

In general I don't see any problem with auxiliary activities that interest members.  Though perhaps best if it doesn't infringe too often on its core meetings since this groups consistency is one of its assets.

Kind of ironic that coming from one who doesn't attend consistently... :/
On Mar 30, 2016 8:50 AM, "Michael Starch" <starchmd at umich.edu> wrote:

I think we should stick to our normal meet-up, and let people choose to go to the other if they would like.  Seeing as Hackaday's format is a show-and-tell and ours is work-on-projects, canceling our session in lieu of theirs would be a deviation from our groups' unspoken philosophy.

-Michael

On Tue, Mar 29, 2016 at 10:45 PM, Lan Dang via HAK <hak at sgvhak.net> wrote:

Hi all
Hackaday has a Meetup on Apr 7th at the new Design Lab.  They have lined up interesting speakers and they are still looking for more speaker or show and tell.  And they are providing food.
It conflicts with our usual HAK meet-up at Dave's workshop.  Should we update our Meetup to converge on thee Supply frame Design Lab?  Or should we just let people choose which Meetup to go to?
Hackaday Prize Talks: Quake-Catcher Network and Cryptocurrency

http://meetu.ps/e/BqDqp/df9DF/d


Lan




  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sgvhak.net/pipermail/hak/attachments/20160401/ecae27e1/attachment.html>