Skip to content

Commit

Permalink
enginerring cyucle and update liaisons task
Browse files Browse the repository at this point in the history
  • Loading branch information
@lhao03
lhao03 committed Mar 8, 2024
1 parent 0b59e0a commit 70b994d
Show file tree
Hide file tree
Showing 6 changed files with 97 additions and 23 deletions.
18 changes: 9 additions & 9 deletions src/SUMMARY.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,15 @@
- [Overview](./wet-lab/index.md)
- [Notebook](./wet-lab/notebook/index.md)
- [March](./wet-lab/notebook/march.md)
- [Design](./wet-lab/design/index.md)
- [Solid phase DNA Synthesis](./wet-lab/design/solidphase-experiment.md)
- [ssDNA to dsDNA](./wet-lab/design/dsdna-experiment.md)
- [Thermostable TdT](./wet-lab/design/tdt.md)
- [Engineering Success](./wet-lab/engineering/index.md)
- [Parts](./wet-lab/parts/index.md)
- [Results](./wet-lab/results/index.md)
- [Protocols](./wet-lab/protocols/index.md)
- [Safety](./wet-lab/safety/index.md)
- [Design](./wet-lab/design/index.md)
- [Solid phase DNA Synthesis](./wet-lab/design/solidphase-experiment.md)
- [ssDNA to dsDNA](./wet-lab/design/dsdna-experiment.md)
- [Thermostable TdT](./wet-lab/design/tdt.md)
- [Engineering Success](./wet-lab/engineering/index.md)
- [Parts](./wet-lab/parts/index.md)
- [Results](./wet-lab/results/index.md)
- [Protocols](./wet-lab/protocols/index.md)
- [Safety](./wet-lab/safety/index.md)

# Dry Lab

Expand Down
17 changes: 7 additions & 10 deletions src/documentation/liaison.md
View file
Original file line number Diff line number Diff line change
@@ -1,16 +1,13 @@
# For wiki liaisons

Your role of wiki liaison well ensure our goals:
<!-- toc -->

1. [Subteam Transparency](index.md#subteam-transparency)
2. [Knowledge Transfer](index.md#knowledge-transfer)
3. [Concrete, small steps (with deliverables) towards our goal](index.md#concrete-small-steps-with-deliverables-towards-our-goal)
## Why was this role created?

are met.
This role was created out of frustration from Lucy and Piyush. We noticed a disconnect between subteams, and during wiki development, only a few members could contribute to the wiki because frankly, many members did not know what was happening outside their subteam. This resulted in a wiki that was low effort, unclear, and did not meet the requirements that iGEM judges were looking for.

## Why was this role created?
Wiki liaisons are expected to have a greater understanding of **all** subteam work, ensure team members (in their own subteam) are contributing to the internal wiki and help Lucy plan for a final competition wiki that aligns with what iGEM is looking for. Wiki liaisons will be a helping hand to the leads, and can offer new perspectives that leads may not notice. Being a wiki liaison will also give you an idea of what a lead's responsibilities are; if you are staying on the team this will help you decide if you want to be a lead. You will help ensure [subteam transparency](index.md#subteam-transparency), [knowledge transfer](index.md#knowledge-transfer) and [concrete, small steps (with deliverables) towards our goal](index.md#concrete-small-steps-with-deliverables-towards-our-goal).

This role was created out of frustration from Lucy and Piyush. We noticed a disconnect between subteams, and during wiki development, only a few members could contribute to the wiki because frankly, many members just did not know what was happening outside their subteam. Wiki liaisons are expected to have a greater understanding of **all** subteam work, ensure team members (in their own subteam) are contributing to the internal wiki and help Lucy plan for the final competition wiki. Wiki liaisons will be a helping hand to the leads, and can offer new perspectives that leads may not notice. Being a wiki liaison will also give you an idea of what a lead's responsibilities are; if you are staying on the team this will help you decide if you want to be a lead or if you want to join another subteam.

### Our wiki liaisons are:

Expand All @@ -20,15 +17,15 @@ This role was created out of frustration from Lucy and Piyush. We noticed a disc

## What is a wiki liaison?

Generally, a wiki liaison is a subteam member who is not a lead that is helps ensure the work of **other** subteams are well integrated into with **their own** subteam's work. This means the wiki liaison helps the wiki lead enforce standards like the internal wiki so that we can meet the three goals listed above. They will also have a greater hand in helping design, edit and complete the wiki for the iGEM Jamboree.
Generally, a wiki liaison is a subteam member who is not a lead that is helps ensure the work of **other** subteams are well integrated into with **their own** subteam's work. This means the wiki liaison helps the wiki lead enforce standards like the internal wiki so that we can meet the three goals listed above. Additionally, wiki liaisons will make sure all information that could contribute to iGEM requirements are being documented. They will also have a greater hand in helping design, edit and complete the wiki for the iGEM Jamboree.

## What are my tasks?

To have subteam transparency and integration, you will help the wiki lead ensure the entire team is putting their project related content onto the internal wiki, as related to _your_ subteam. This means if you're in wet lab, you make sure all experimental designs and changes are being committed to the internal wiki on a daily/weekly basis.
To have subteam transparency and integration, you will help the wiki lead ensure the entire team is putting their project related content onto the internal wiki, as related to _your_ subteam. This means if you're in wet lab, you make sure all experimental designs and changes are being committed to the internal wiki on a daily/weekly basis, most likely to the wet lab notebook.

Secondly, after each subteam uploads content to the internal wiki, wiki liaisons are responsible for reading other team's content on the internal wiki. Generally, you are trying to form an overall sense of the goals, directions and motivations of the other subteams. This will help you for the third task.

Thirdly, after you have ensured your subteam is contributing to the internal wiki, and have an understanding of what other subteams are doing, you will be responsible for critically analyzing the work of other subteams. For instance, if you are the dry lab liaison, you will have read over the wet lab and HP pages. If the wet lab plasmid design pages are hard to understand or missing information, you will create a GitHub issue stating what is missing and why this information is important, then send a message to the #wiki-liaison channel with the link of the issue, and a lead will alert the appropriate subteam members. If human practices has described a computational concept incorrectly, or you can enhance the educational material, similarly, make an issue and complete the previously listed steps. The point of all this work is to have all our subteams be cohesive and integrated. You are also encouraged to attend other subteam specific meetings, but only if you have the time!
Thirdly, after you have ensured your subteam is contributing to the internal wiki, and have an understanding of what other subteams are doing, you will be responsible for critically analyzing the work of other subteams. For instance, if you are the dry lab liaison, you will have read over the wet lab and HP pages. If the wet lab design pages are hard to understand or missing information, you will create a GitHub issue stating what is missing and why this information is important, and Lucy will alert the appropriate subteam members to add more information. If human practices has described a computational concept incorrectly, or you can enhance the educational material, similarly, make an issue and complete the previously listed steps. The point of all this work is to have all our subteams be cohesive and integrated. You are also encouraged to attend other subteam specific meetings, but only if you have the time!

Finally, when we are writing the wiki for the iGEM Jamboree, you will have a greater hand in helping the leads design the wiki. You may also help assign other subteam members to writing and reading content.

Expand Down
11 changes: 8 additions & 3 deletions src/dry-lab/design/index.md
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,11 @@
# Design

## Hardware
<!-- toc -->

## Why these projects?

## Projects Overview
### Hardware

| Component | Priority | Objective | Assigned to | Report to |
| --------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- | -------------- | ------------ |
Expand All @@ -10,7 +15,7 @@
| Microfluidic Chip (DNA Capture) | 2 | TBD | Samuel, Piyush | Tina, Piyush |
| Bioreactor | 2 | Create a Bioreactor to allow Wet Lab to Culture E Coli for their experiments | Samuel, Piyush | Tina, Piyush |

## Software
### Software

| Component | Priority | Objective | Assigned to | Report to |
| ----------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | --------- |
Expand All @@ -20,7 +25,7 @@
| Error Correction | 1 | Create an error correction algorithm to work with semi-specific encoding, short nucleotide sequences and high rate of deletion errors. | Riya, Lucy | Lucy |
| GUI | 3 | Design a user friendly interface that can be used by our iHP interviewees to try out our DNA storage software, and also visually display our file system | All software + other dry lab if desired | Lucy |

## Modelling
### Modelling

| Component | Priority | Objective | Assigned to | Report to |
| --------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ------------- |
Expand Down
28 changes: 28 additions & 0 deletions src/dry-lab/engineering/index.md
View file
Original file line number Diff line number Diff line change
@@ -1 +1,29 @@
# Engineering Success

<!-- toc -->

## Iteration 1

### Software
| | Relevant Pages/Commits | Date(s) |
|--------|------------------------|---------|
| Design | | March |
| Build | | |
| Test | | |
| Learn | | |

### Hardware
| | Relevant Pages/Commits | Date(s) |
|--------|----------------|---------|
| Design | | March |
| Build | | |
| Test | | |
| Learn | | |

### Modelling
| | Relevant Pages/Commits | Date(s) |
|--------|------------------------|---------|
| Design | | March |
| Build | | |
| Test | | |
| Learn | | |
26 changes: 25 additions & 1 deletion src/wet-lab/design/index.md
View file
Original file line number Diff line number Diff line change
@@ -1,3 +1,27 @@
# Design
<!-- toc -->

All experiment, plasid, and other designs for wet lab go here. For each design, create a new file in SUMMARY.md. Include pictures, graphics, external sites to help explain your designs to the other subteam members.
## Why these projects?

## Projects Overview

### TdT Production

| Component | Priority | Objective | Assigned to | Report to |
|-----------|----------|-----------|-------------|-----------|
| | | | | |
| | | | | |

### Solid Phase Synthesis

| Component | Priority | Objective | Assigned to | Report to |
|-----------|----------|-----------|-------------|-----------|
| | | | | |
| | | | | |

### ssDNA to dsDNA

| Component | Priority | Objective | Assigned to | Report to |
|-----------|----------|-----------|-------------|-----------|
| | | | | |
| | | | | |
20 changes: 20 additions & 0 deletions src/wet-lab/engineering/index.md
View file
Original file line number Diff line number Diff line change
@@ -1 +1,21 @@
# Engineering Success

<!-- toc -->

## Iteration 1

### TdT Production
| | Relevant Pages/Commits | Date(s) |
|--------|------------------------|---------|
| Design | | March |
| Build | | |
| Test | | |
| Learn | | |

### Solid Phase Synthesis
| | Relevant Pages/Commits | Date(s) |
|--------|------------------------|---------|
| Design | | March |
| Build | | |
| Test | | |
| Learn | | |

0 comments on commit 70b994d

Please sign in to comment.