[sudo-announce] East Bay DIYBio next meeting possible topics of discussion...

[Ryan Bethencourt]

Okay great, let's say 6.30pm to start just to give everyone enough time to
arrive, I'll probably be around from 6pm onwards.


So just a quick reminder

*East Bay DIY BIO meeting TODAY starts at 6.30pm* but I'll be around a
little earlier at 6pm (probably talking with Marc about the Open source
desktop biotech lab and doing inventory)

*Agenda*
PLEASE FIND THE EDITABLE AGENDA ATTACHED FOR THE MEETING BELOW FOR OUR
MEETING TODAY:
https://docs.google.com/document/d/1LHZdD9XVasdFDvGL2kyyMVyxZ_w8rXLuu7bw5nWIL3k/edit?usp=sharing


On Fri, Feb 22, 2013 at 5:53 AM, Stefan Hristu <romanian at gmail.com> wrote:

> I will not be able to make this.
>
> Stefan
> On Feb 21, 2013 11:14 PM, "Ron Shigeta" <rtshigeta at yahoo.com> wrote:
>
>> either works for me... will be about 6:30 p.m. tho
>>
>>   ------------------------------
>> *From:* Ryan Bethencourt <ryan.bethencourt at gmail.com>
>> *To:* Ron Shigeta <rtshigeta at yahoo.com>
>> *Cc:* East DIYbio <east-bay-diybio at googlegroups.com>; Carl Crott <
>> carlcrott at gmail.com>; John Schloendorn <zauberkugel at gmail.com>;
>> sudo-discuss <sudo-discuss at lists.sudoroom.org>
>> *Sent:* Thursday, February 21, 2013 1:24 PM
>> *Subject:* Re: East Bay DIYBio next meeting possible topics of
>> discussion...
>>
>> Dear All,
>>
>> I just wanted to confirm that we are indeed still meeting this Friday at
>> 6pm if that still works for everyone. At the moment I'm still trying to get
>> us access to the Berkeley space that we discussed before for the possible
>> East Bay DIY Bio hacker space but no word yet. So we have a choice
>>
>> 1. Meet at a Cafe/Bar/Restaurant (possibly Saturn Cafe) in Berkeley at 6pm
>> 2. Alternatively, we could meet back at Sudo room at 6pm just before the
>> hacker happy hour and talk for a while as people arrive until about
>> 7/7.30pm?
>>
>> My preference (for simplicity) would probably be Sudo Room
>>
>> Let me and our fellow Biohacker members know if you have a preference?
>>
>> Please also see the agenda below compiled by Ron:
>>
>> 1) How to build a self-sustaining community? What sorts of organization,
>> resources, people, physical requirements would there be to get a space off
>> the ground?
>>
>> Who will be in the community and what are their goals?
>>
>> How might membership work?
>> What are our self sustaining budget numbers?
>> How will the lease and other such legal obligations work?
>>
>> How can we collaborate with biocurious and nextgen? Who can be our
>> allies to build this momentum?
>>
>> Other topics related: legal, regulatory, fiscal requirements,
>> organization, volunteers, building momentum, lab rules
>>
>> 2) Projects.
>> Everyone loves talking about projects.  Given some idea of what the
>> community needs, how can projects build that community?
>>
>> Because it takes at least 6 months of focused experience to get up to
>> speed in actual biological hacking, team projects will probably be the
>> mainstay of the lab for a while.
>>
>> Team projects should probably be focused and supported by vote, but how
>> can we gauge what is too ambitious for a first round?
>>
>> For example:
>> - open benchtop*
>> - the bioprinter project is an experience to learn from
>> - bio Informatics support for the lab or diyBio
>> - open source bioreagent design.
>>
>>
>> 3) Appendix: Lessons learned:
>> - Biologists involved in the core of the startup process have been pretty
>> useful.
>> - getting members up to speed can take months and they need mentorship to
>> get to a level of creative practice.
>> - projects build enthusiasm as well as get people experience
>> - classes are important
>> - the community is made of people all of whom are needed to build the
>> community successfully (e.g. members, volunteers, class attendees, board
>> members (or something like board members anyway).
>>
>>
>> * BTW - This is the gogofuge link I mentioned - really a niceified dremel
>> centrifuge.
>> http://diybio.org/2012/06/12/gogofuge/
>>
>> All the best,
>> Ryan
>>
>>
>> On Sun, Feb 17, 2013 at 9:09 AM, Ron Shigeta <rtshigeta at yahoo.com> wrote:
>>
>>  Hey everyone,
>>
>> Really enjoyed seeing everyone in last month!
>>
>> Since we have decided to talk more about an East Bay DIYBio space... I
>> thought I'd suggest some structure for the meeting Friday...
>>
>> If Ryan can swing it, walking through the space and taking it in will
>> help establish the agenda more firmly, but in the interests of having a
>> focused discussion I wanted to send out an agenda proposal - please lets
>> change it, but have something like an agenda for the meet this month?
>>
>> Feel free to add or hold forth...just want to get the ball rolling.
>>
>> 1) How to build a self-sustaining community? What sorts of organization,
>> resources, people, physical requirements would there be to get a space off
>> the ground?
>>
>> Who will be in the community and what are their goals?
>>
>> How might membership work?
>> What are our self sustaining budget numbers?
>> How will the lease and other such legal obligations work?
>>
>> How can we collaborate with biocurious and nextgen? Who can be our
>> allies to build this momentum?
>>
>> Other topics related: legal, regulatory, fiscal requirements,
>> organization, volunteers, building momentum, lab rules
>>
>> 2) Projects.
>> Everyone loves talking about projects.  Given some idea of what the
>> community needs, how can projects build that community?
>>
>> Because it takes at least 6 months of focused experience to get up to
>> speed in actual biological hacking, team projects will probably be the
>> mainstay of the lab for a while.
>>
>> Team projects should probably be focused and supported by vote, but how
>> can we gauge what is too ambitious for a first round?
>>
>> For example:
>> - open benchtop*
>> - the bioprinter project is an experience to learn from
>> - bio Informatics support for the lab or diyBio
>> - open source bioreagent design.
>>
>>
>> 3) Appendix: Lessons learned:
>> - Biologists involved in the core of the startup process have been pretty
>> useful.
>> - getting members up to speed can take months and they need mentorship to
>> get to a level of creative practice.
>> - projects build enthusiasm as well as get people experience
>> - classes are important
>> - the community is made of people all of whom are needed to build the
>> community successfully (e.g. members, volunteers, class attendees, board
>> members (or something like board members anyway).
>>
>>
>> * BTW - This is the gogofuge link I mentioned - really a niceified dremel
>> centrifuge.
>> http://diybio.org/2012/06/12/gogofuge/
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "East Bay DIYbio" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to east-bay-diybio+unsubscribe at googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>>
>>
>> --
>> Ryan Bethencourt
>>
>> Tel: (415) 794 6463
>> ryan.bethencourt at gmail.com
>>
>> www.bamh1.com
>> www.linkedin.com/in/bethencourt
>> www.logos-press.com/books/biotechnology_business_development.php
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "East Bay DIYbio" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to east-bay-diybio+unsubscribe at googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>>   --
>> You received this message because you are subscribed to the Google Groups
>> "East Bay DIYbio" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to east-bay-diybio+unsubscribe at googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>


-- 
Ryan Bethencourt

Tel: (415) 794 6463
ryan.bethencourt at gmail.com

www.bamh1.com
www.linkedin.com/in/bethencourt
www.logos-press.com/books/biotechnology_business_development.php
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sudoroom.org/pipermail/sudo-announce/attachments/20130222/9badc556/attachment-0003.html>