BIoCurious has many Community Projects with an Open Science focus, the
three most active that might apply to your request are:

DIY BioPrinter: meeting for 4 years now with a goal to design an Open
Hardware BioPrinter and a system for DIY communities to explore this
technology. The project is open to collaboration via web conference
with project participants in Vancouver B.C, Florida, and even Brazil
joining in. Project wiki
https://sites.google.com/site/bioprinterwiki/

I'm not sure the depth of information you are looking for but I'd be
happy to fill in details for the projects I'm on (those listed above).

-Maria

On Mon, Feb 29, 2016 at 6:43 PM, Scott <synbiofablab@gmail.com> wrote:
> Hello all,
>
> I thought I would throw this question out to the greater DIYbio community.
> As a backgrounder, Public Health Agency of Canada is holding a DIYbio Summit
> in Ottawa on March 16th. Derek Jacoby and I, amongst others, are invited
> panelists at the summit. I believe it will be web-casted (details to
> follow).
>
> We are tasked with putting together a list of ways that DIY bio and
> community labs can positively impact human health. What existing DIYbio
> projects have already met this challenge and what new ideas do you think are
> possible ways that community biolabs can contribute? Are you working on any
> open DIYbio projects in this arena? Links would be greatly appreciated.
>
> some topics: health and the environment, biosensors, antibiotics discovery
> projects, health-related DNA barcoding, water quality biosensors, genomics,
> microbiome, waste treatment.
>
> Cheers,
> Scott
> Open Science Network, Vancouver, BC
>
> --
> -- You received this message because you are subscribed to the Google Groups
> DIYbio group. To post to this group, send email to diybio@googlegroups.com.
> To unsubscribe from this group, send email to
> diybio+unsubscribe@googlegroups.com. For more options, visit this group at
> https://groups.google.com/d/forum/diybio?hl=en> Learn more at www.diybio.org> ---
> You received this message because you are subscribed to the Google Groups
> "DIYbio" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to diybio+unsubscribe@googlegroups.com.
> To post to this group, send email to diybio@googlegroups.com.
> Visit this group at https://groups.google.com/group/diybio.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/diybio/f157d824-ac2d-49ec-8cca-5e27d0042ff6%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

I thought I would throw this question out to the greater DIYbio community. As a backgrounder, Public Health Agency of Canada is holding a DIYbio Summit in Ottawa on March 16th. Derek Jacoby and I, amongst others, are invited panelists at the summit. I believe it will be web-casted (details to follow).

We are tasked with putting together a list of ways that DIY bio and community labs can positively impact human health. What existing DIYbio projects have already met this challenge and what new ideas do you think are possible ways that community biolabs can contribute? Are you working on any open DIYbio projects in this arena? Links would be greatly appreciated.

That sounds really cool. I recently tried making a complete bibliography of academic litterature on DIY biology (including your thesis) as part of my current proces of writing a masters thesis in sociology about a local DIYbio community. If you're interested it's linked from here http://blog.buethastum.dk/research-on-diy-biology/

I'll start subscribing to your blog. Looking forward to see what future outputs you produce :)

As resources: I am a PhD student researching the DIYbio movement. So I have the time and funding. I am part of the Citizen Science Research team at the University of Geneva (http://citizensciences.net/). Hopefully you will be hearing from us more often!

For the project, we are gathering a worldwide comprehensive database of all DIYbio initiatives.

We are well aware of 'survey fatigue' among DIYbio, therefore we are trying to construct our research in a way that is useful and meaningful for us and for the DIYbio community.

So it seems as if Jekyll+Github pages wins? I think that for now it might be the easiest way to start-off... Eventually we can migrate to another git repository manager—like gitlab—and another static site generator—like HUGO, and move it to our own server (eventually is the key word here).

For now, I have the resources to get it started. Anyone interested? Please share your ideas on what should the website have, look like, etc.

Meantime, I suggest we sync the repo to multiple git servers. We could start with github bc it's so easy (and use git-hooks to automatically push it to other servers - callingBryanBishop... Please stand up...).

GitHub wiki works as a git repository, push to git@github.com:namespace/whatever.wiki.git (the .wiki.git repo is automatically setup by github). Otherwise, I suggest using ikiwiki for static html compilation from git wiki. This wiki can be hosted as a github repo as well. The github wiki git repository feature does not have all the same features as github git repos, like no pull requests or whatever. Jekyll is probably more friendly than ikiwiki, these days, even lacking the wiki front-end interface. I have found that users are profoundly confused by wikis that don't look like mediawiki's default stylesheet, so jekyll (without wiki features) seems probably fine.

Please go through below description and reply with your resume, contact details and current location, if you feel comfortable

Job Role: Python Engineer

Location: MILPITAS, CALIFORNIA 95035 UNITED STATES

Duration: 12 Months+ Contract

CITG division of Client is seeking a candidate with Linux systems experience to write python scripts for Development Operations. Responsibilities will include: involvement with build with Jenkins, in automating the process to make different artifacts, and working with the different docker containers. Ideal candidate should have between 4-10 years overall experience.

As resources: I am a PhD student researching the DIYbio movement. So I have the time and funding. I am part of the Citizen Science Research team at the University of Geneva (http://citizensciences.net/). Hopefully you will be hearing from us more often!

For the project, we are gathering a worldwide comprehensive database of all DIYbio initiatives.

We are well aware of 'survey fatigue' among DIYbio, therefore we are trying to construct our research in a way that is useful and meaningful for us and for the DIYbio community.

So it seems as if Jekyll+Github pages wins? I think that for now it might be the easiest way to start-off... Eventually we can migrate to another git repository manager—like gitlab—and another static site generator—like HUGO, and move it to our own server (eventually is the key word here).

For now, I have the resources to get it started. Anyone interested? Please share your ideas on what should the website have, look like, etc.

Meantime, I suggest we sync the repo to multiple git servers. We could start with github bc it's so easy (and use git-hooks to automatically push it to other servers - callingBryanBishop... Please stand up...).

GitHub wiki works as a git repository, push to git@github.com:namespace/whatever.wiki.git (the .wiki.git repo is automatically setup by github). Otherwise, I suggest using ikiwiki for static html compilation from git wiki. This wiki can be hosted as a github repo as well. The github wiki git repository feature does not have all the same features as github git repos, like no pull requests or whatever. Jekyll is probably more friendly than ikiwiki, these days, even lacking the wiki front-end interface. I have found that users are profoundly confused by wikis that don't look like mediawiki's default stylesheet, so jekyll (without wiki features) seems probably fine.

So it seems as if Jekyll+Github pages wins? I think that for now it might be the easiest way to start-off... Eventually we can migrate to another git repository manager—like gitlab—and another static site generator—like HUGO, and move it to our own server (eventually is the key word here).

For now, I have the resources to get it started. Anyone interested? Please share your ideas on what should the website have, look like, etc.

Meantime, I suggest we sync the repo to multiple git servers. We could start with github bc it's so easy (and use git-hooks to automatically push it to other servers - callingBryanBishop... Please stand up...).

GitHub wiki works as a git repository, push to git@github.com:namespace/whatever.wiki.git (the .wiki.git repo is automatically setup by github). Otherwise, I suggest using ikiwiki for static html compilation from git wiki. This wiki can be hosted as a github repo as well. The github wiki git repository feature does not have all the same features as github git repos, like no pull requests or whatever. Jekyll is probably more friendly than ikiwiki, these days, even lacking the wiki front-end interface. I have found that users are profoundly confused by wikis that don't look like mediawiki's default stylesheet, so jekyll (without wiki features) seems probably fine.

So it seems as if Jekyll+Github pages wins? I think that for now it might be the easiest way to start-off... Eventually we can migrate to another git repository manager—like gitlab—and another static site generator—like HUGO, and move it to our own server (eventually is the key word here).

For now, I have the resources to get it started. Anyone interested? Please share your ideas on what should the website have, look like, etc.

Meantime, I suggest we sync the repo to multiple git servers. We could start with github bc it's so easy (and use git-hooks to automatically push it to other servers - calling BryanBishop... Please stand up...).

GitHub wiki works as a git repository, push to git@github.com:namespace/whatever.wiki.git (the .wiki.git repo is automatically setup by github). Otherwise, I suggest using ikiwiki for static html compilation from git wiki. This wiki can be hosted as a github repo as well. The github wiki git repository feature does not have all the same features as github git repos, like no pull requests or whatever. Jekyll is probably more friendly than ikiwiki, these days, even lacking the wiki front-end interface. I have found that users are profoundly confused by wikis that don't look like mediawiki's default stylesheet, so jekyll (without wiki features) seems probably fine.

So it seems as if Jekyll+Github pages wins? I think that for now it might be the easiest way to start-off... Eventually we can migrate to another git repository manager—like gitlab—and another static site generator—like HUGO, and move it to our own server (eventually is the key word here).

For now, I have the resources to get it started. Anyone interested? Please share your ideas on what should the website have, look like, etc.

Meantime, I suggest we sync the repo to multiple git servers. We could start with github bc it's so easy (and use git-hooks to automatically push it to other servers - calling BryanBishop... Please stand up...).

GitHub wiki works as a git repository, push to git@github.com:namespace/whatever.wiki.git (the .wiki.git repo is automatically setup by github). Otherwise, I suggest using ikiwiki for static html compilation from git wiki. This wiki can be hosted as a github repo as well. The github wiki git repository feature does not have all the same features as github git repos, like no pull requests or whatever. Jekyll is probably more friendly than ikiwiki, these days, even lacking the wiki front-end interface. I have found that users are profoundly confused by wikis that don't look like mediawiki's default stylesheet, so jekyll (without wiki features) seems probably fine.

So it seems as if Jekyll+Github pages wins? I think that for now it might be the easiest way to start-off... Eventually we can migrate to another git repository manager—like gitlab—and another static site generator—like HUGO, and move it to our own server (eventually is the key word here).

For now, I have the resources to get it started. Anyone interested? Please share your ideas on what should the website have, look like, etc.

Meantime, I suggest we sync the repo to multiple git servers. We could start with github bc it's so easy (and use git-hooks to automatically push it to other servers - calling BryanBishop... Please stand up...).

GitHub wiki works as a git repository, push to git@github.com:namespace/whatever.wiki.git (the .wiki.git repo is automatically setup by github). Otherwise, I suggest using ikiwiki for static html compilation from git wiki. This wiki can be hosted as a github repo as well. The github wiki git repository feature does not have all the same features as github git repos, like no pull requests or whatever. Jekyll is probably more friendly than ikiwiki, these days, even lacking the wiki front-end interface. I have found that users are profoundly confused by wikis that don't look like mediawiki's default stylesheet, so jekyll (without wiki features) seems probably fine.