Skip to content

Commit

Permalink
edit
Browse files Browse the repository at this point in the history
  • Loading branch information
lhao03 committed Feb 1, 2024
1 parent a6bbd04 commit 84fef4e
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/documentation/liaison.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,12 +24,12 @@ To have subteam transparency and integration, you will help the wiki lead ensure

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.
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!

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

## Who do I ask for help?
If you feel overwhelmed at any point, you can DM Lucy and she can either give you a break or get someone else to help you with being wiki liaison. At anytime if you feel this role is overwhelming let the co-directors or Lucy know. We will probably have weekly asynchronous updates on Slack, with meetings if necessary.
At anytime if you feel this role is overwhelming let the co-directors or Lucy know. We will probably have weekly asynchronous updates on Slack, with meetings if necessary.

If you have any questions that are not of a personal nature, send a message in #wiki-liaison, otherwise DM Lucy.

Expand Down

0 comments on commit 84fef4e

Please sign in to comment.