Skip to content

Update lab_meetings.md #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Dec 5, 2024
Merged

Update lab_meetings.md #28

merged 4 commits into from
Dec 5, 2024

Conversation

EleGdt
Copy link
Contributor

@EleGdt EleGdt commented Sep 19, 2024

Update lab meeting section

Summary by Sourcery

Update the lab_meetings.md documentation to include comprehensive information about different types of lab meetings, their schedules, and relevant resources.

Documentation:

  • Add detailed descriptions of various lab meetings, including regular lab meetings, journal club, one slide meeting, and method meeting, along with relevant links and schedules.

Update lab meeting section
Copy link
Contributor

sourcery-ai bot commented Sep 19, 2024

Reviewer's Guide by Sourcery

This pull request adds a new file 'lab_meetings.md' to the 'doc' directory, providing information about different types of lab meetings, their schedules, and related resources.

File-Level Changes

Change Details Files
Add new file with lab meeting information
  • Introduce regular lab meetings schedule and resources
  • Describe journal club meetings
  • Explain one slide meeting format and rotation
  • Define method meetings and their purpose
doc/lab_meetings.md

Tips
  • Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
  • Continue your discussion with Sourcery by replying directly to review comments.
  • You can change your review settings at any time by accessing your dashboard:
    • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
    • Change the review language;
  • You can always contact us if you have any questions or feedback.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @EleGdt - I've reviewed your changes - here's some feedback:

Overall Comments:

  • Consider standardizing the heading styles throughout the document. Currently, there's a mix of '#' and '##' being used for headings of seemingly equal importance.
Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟡 Documentation: 4 issues found

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

@@ -0,0 +1,13 @@
## Lab meetings (person in charge: Eleonore Giraudet)
# Regular lab meeting
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (documentation): Consider using consistent heading levels throughout the document.

The main heading uses '##' while this subheading uses '#'. Using consistent heading levels (e.g., '##' for main heading, '###' for subheadings) would improve document structure.

Suggested change
# Regular lab meeting
### Regular lab meeting

@@ -0,0 +1,13 @@
## Lab meetings (person in charge: Eleonore Giraudet)
# Regular lab meeting
At the moment, they happen every thursday at 10:30. Here you can find the [calendar](https://docs.google.com/spreadsheets/d/1aIu8WcYoRpC9p3fIiilZWTgR7i03lulYj8B5ZyUW_Qc/edit?gid=6486503#gid=6486503) and [here](https://drive.google.com/drive/folders/1Pb75jpul71mMXiP4fSZGEwK34V5meg12) the main gdrive folder where we archive relevant files.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (documentation): Remove extra space before '[calendar]' and consider restructuring the sentence for clarity.

The sentence is quite long. Consider splitting it into two sentences for better readability. For example: 'At the moment, they happen every Thursday at 10:30. You can find the [calendar] here and the main Google Drive folder for archived files [here].'

Suggested change
At the moment, they happen every thursday at 10:30. Here you can find the [calendar](https://docs.google.com/spreadsheets/d/1aIu8WcYoRpC9p3fIiilZWTgR7i03lulYj8B5ZyUW_Qc/edit?gid=6486503#gid=6486503) and [here](https://drive.google.com/drive/folders/1Pb75jpul71mMXiP4fSZGEwK34V5meg12) the main gdrive folder where we archive relevant files.
At the moment, they happen every Thursday at 10:30. You can find the [calendar](https://docs.google.com/spreadsheets/d/1aIu8WcYoRpC9p3fIiilZWTgR7i03lulYj8B5ZyUW_Qc/edit?gid=6486503#gid=6486503) here and the main Google Drive folder for archived files [here](https://drive.google.com/drive/folders/1Pb75jpul71mMXiP4fSZGEwK34V5meg12).

They happen once a month, here you can propose and/or pick up a paper to be discussed.

# One slide meeting
The one slide meeting is once a month, the lab is divided in 3 batches [see here] and 1 batch will present alternatively.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue (documentation): Replace '[see here]' placeholder with actual information or link.

Copy link
Contributor

@marcobarilari marcobarilari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, thanks for it. I added a couple of comments + edited how the markdown titles and subtitles should be "coded" according to markdown rules

Co-authored-by: Marco Barilari <38101692+marcobarilari@users.noreply.github.com>
@marcobarilari
Copy link
Contributor

Hey @EleGdt, let me know if you are still in for this and need any help.

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
@EleGdt EleGdt requested a review from marcobarilari December 5, 2024 12:42
@EleGdt
Copy link
Contributor Author

EleGdt commented Dec 5, 2024

Ok thqnk you for the review, can you check now?

@EleGdt EleGdt merged commit 046ae8c into main Dec 5, 2024
@EleGdt EleGdt deleted the EleGdt-patch-1 branch December 5, 2024 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants