Skip to content
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

Create 2024-10-14-6th-issue-newsletter.md #2642

Merged
merged 3 commits into from
Oct 16, 2024
Merged

Conversation

LK112019
Copy link
Contributor

@LK112019 LK112019 commented Oct 14, 2024

@matentzn @nlharris Newsletter issue 6th is ready! Thank you!

Summary by CodeRabbit

  • New Features
    • Introduced the sixth issue of the OBO Foundry Newsletter, featuring updates on the bio-ontology community.
    • Highlights include new ontologies under review, community member spotlights, and recent research developments.
    • Discussed important principles regarding term stability and deprecation, along with updates on relevant tools and events.

Copy link

coderabbitai bot commented Oct 14, 2024

Walkthrough

A new file, _posts/2024-10-14-5th-issue-newsletter.md, has been added to introduce the sixth issue of the OBO Foundry Newsletter. This issue details recent developments in the bio-ontology community, featuring updates on ongoing discussions, new ontologies under review, community member spotlights, research initiatives, and upcoming events. Key highlights include a report on term stability principles, profiles of community contributors, and information on tools and resources relevant to the field.

Changes

File Path Change Summary
_posts/2024-10-14-5th-issue-newsletter.md New file created introducing the sixth issue of the OBO Foundry Newsletter, covering community developments, new ontologies, member spotlights, research, tools, and events.

Poem

In the meadow where knowledge grows,
A newsletter blooms, as everyone knows.
With new ontologies and friends to cheer,
The OBO Foundry spreads joy far and near!
Hop along, let’s share and explore,
Together we’ll learn, forevermore! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
_posts/2024-10-14-5th-issue-newsletter.md (1)

10-30: Consider enhancing the highlights section with more specific details.

The introduction effectively outlines the newsletter's content. However, the highlights section could be more impactful by including specific details about the new dashboard release, such as key features or improvements.

🧰 Tools
🪛 Markdownlint

28-28: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

(MD001, heading-increment)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a87a5eb and 38e9db8.

📒 Files selected for processing (1)
  • _posts/2024-10-14-5th-issue-newsletter.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
_posts/2024-10-14-5th-issue-newsletter.md

[style] ~104-~104: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... effectiveness research on medications. He also leads the development of the Ontol...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~104-~104: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...egories, and intimate partner violence. He previously held R01 funding from NIGMS ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[uncategorized] ~146-~146: Do not mix variants of the same word (‘modeling’ and ‘modelling’) within a single text.
Context: ...cs, variant prioritization, and disease modeling.

<span style="col...

(EN_EXACT_COHERENCY_RULE)


[misspelling] ~156-~156: Possible spelling mistake found.
Context: ...grim, Sofia MC Robb, Peter N. Robinson, James Seager, Erik Segerdell, Damian Smedley, Elliot...

(EN_MULTITOKEN_SPELLING_TWO)


[style] ~169-~169: This phrase is redundant. Consider using “subject” to avoid wordiness.
Context: ... should have a well-specified domain or subject matter it intends to cover, and its content sh...

(SUBJECT_MATTER)


[misspelling] ~169-~169: Did you mean “principal” (=main)?
Context: ...uld adhere strictly to that scope. This principle aims to avoid overlaps between ontologi...

(IN_PRINCIPAL)


[style] ~234-~234: Consider using a different adverb to strengthen your wording.
Context: ...e and pull request descriptions. We are very grateful to everyone who participated. ...

(VERY_DEEPLY)


[style] ~236-~236: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... for backing the microgrant initiative. We also encourage everyone to get involved...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 Markdownlint
_posts/2024-10-14-5th-issue-newsletter.md

28-28: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

(MD001, heading-increment)


110-110: Expected: atx; Actual: atx_closed
Heading style

(MD003, heading-style)


46-46: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


47-47: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


48-48: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


49-49: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


50-50: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


51-51: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


52-52: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


54-54: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


55-55: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


56-56: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


252-252: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


178-178: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


222-222: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


73-73: null
Spaces inside link text

(MD039, no-space-in-links)


78-78: null
Spaces inside link text

(MD039, no-space-in-links)


78-78: null
Spaces inside link text

(MD039, no-space-in-links)


82-82: null
Spaces inside link text

(MD039, no-space-in-links)


83-83: null
Spaces inside link text

(MD039, no-space-in-links)


164-164: null
Spaces inside link text

(MD039, no-space-in-links)


180-180: null
Spaces inside link text

(MD039, no-space-in-links)


195-195: null
Spaces inside link text

(MD039, no-space-in-links)


216-216: null
Spaces inside link text

(MD039, no-space-in-links)

🔇 Additional comments (7)
_posts/2024-10-14-5th-issue-newsletter.md (7)

1-8: LGTM: Front matter is well-structured and consistent.

The YAML front matter is correctly formatted and contains all necessary metadata for the post. The date and issue number are consistent with the filename and content.


35-58: LGTM: Comprehensive overview of Principle 19 development.

This section provides a detailed and well-structured overview of the ongoing discussion about Principle 19. The use of bullet points effectively presents the key points, and the inclusion of a link to the issue encourages community participation.

🧰 Tools
🪛 Markdownlint

46-46: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


47-47: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


48-48: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


49-49: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


50-50: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


51-51: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


52-52: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


54-54: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


55-55: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


56-56: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


64-84: LGTM: Comprehensive overview of new and established ontologies.

This section effectively introduces new ontologies under review and spotlights established ones. The descriptions are informative, providing clear insights into the purpose and scope of each ontology. The inclusion of links for further information is helpful for readers interested in learning more.

🧰 Tools
🪛 Markdownlint

73-73: null
Spaces inside link text

(MD039, no-space-in-links)


78-78: null
Spaces inside link text

(MD039, no-space-in-links)


78-78: null
Spaces inside link text

(MD039, no-space-in-links)


82-82: null
Spaces inside link text

(MD039, no-space-in-links)


83-83: null
Spaces inside link text

(MD039, no-space-in-links)


126-198: LGTM: Comprehensive coverage of research, principles, and tools.

These sections provide detailed and well-structured information on recent research, OBO Principle 5, and tool updates. The inclusion of figures and citations in the research section enhances the content. The explanation of Principle 5 is clear and informative. The updates on SSSOM and BioPortal provide valuable information for the community.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~146-~146: Do not mix variants of the same word (‘modeling’ and ‘modelling’) within a single text.
Context: ...cs, variant prioritization, and disease modeling.

<span style="col...

(EN_EXACT_COHERENCY_RULE)


[misspelling] ~156-~156: Possible spelling mistake found.
Context: ...grim, Sofia MC Robb, Peter N. Robinson, James Seager, Erik Segerdell, Damian Smedley, Elliot...

(EN_MULTITOKEN_SPELLING_TWO)


[style] ~169-~169: This phrase is redundant. Consider using “subject” to avoid wordiness.
Context: ... should have a well-specified domain or subject matter it intends to cover, and its content sh...

(SUBJECT_MATTER)


[misspelling] ~169-~169: Did you mean “principal” (=main)?
Context: ...uld adhere strictly to that scope. This principle aims to avoid overlaps between ontologi...

(IN_PRINCIPAL)

🪛 Markdownlint

178-178: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


164-164: null
Spaces inside link text

(MD039, no-space-in-links)


180-180: null
Spaces inside link text

(MD039, no-space-in-links)


195-195: null
Spaces inside link text

(MD039, no-space-in-links)


201-237: LGTM: Comprehensive coverage of community events and activities.

This section provides a detailed and engaging overview of recent and past events in the OBO community. The information about the COB Workshop and OBO Academy is valuable for community members. The comprehensive report on the ICBO OBO Tutorial, including the Community Challenge and prize winners, adds a personal touch and highlights community engagement.

🧰 Tools
🪛 LanguageTool

[style] ~234-~234: Consider using a different adverb to strengthen your wording.
Context: ...e and pull request descriptions. We are very grateful to everyone who participated. ...

(VERY_DEEPLY)


[style] ~236-~236: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... for backing the microgrant initiative. We also encourage everyone to get involved...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 Markdownlint

222-222: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


216-216: null
Spaces inside link text

(MD039, no-space-in-links)


242-255: LGTM: Comprehensive guide for community participation.

This section effectively outlines various ways to be part of the OBO Foundry community. The list of participation options is comprehensive and well-organized, covering everything from joining mailing lists to contributing to the codebase. The inclusion of links for each option makes it easy for readers to get involved.

🧰 Tools
🪛 Markdownlint

252-252: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


1-255: Overall, excellent newsletter with minor improvements needed.

This newsletter provides comprehensive coverage of various aspects of the OBO Foundry community, including recent developments, ongoing discussions, research highlights, and community events. The content is well-structured, informative, and encourages community engagement.

A few minor improvements could enhance the newsletter further:

  1. Fix the image rendering issues in the members and volunteers section.
  2. Consider adding more specific details to the highlights section about the new dashboard release.

These small changes will make an already strong newsletter even better.

🧰 Tools
🪛 LanguageTool

[style] ~104-~104: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... effectiveness research on medications. He also leads the development of the Ontol...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~104-~104: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...egories, and intimate partner violence. He previously held R01 funding from NIGMS ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[uncategorized] ~146-~146: Do not mix variants of the same word (‘modeling’ and ‘modelling’) within a single text.
Context: ...cs, variant prioritization, and disease modeling.

<span style="col...

(EN_EXACT_COHERENCY_RULE)


[misspelling] ~156-~156: Possible spelling mistake found.
Context: ...grim, Sofia MC Robb, Peter N. Robinson, James Seager, Erik Segerdell, Damian Smedley, Elliot...

(EN_MULTITOKEN_SPELLING_TWO)


[style] ~169-~169: This phrase is redundant. Consider using “subject” to avoid wordiness.
Context: ... should have a well-specified domain or subject matter it intends to cover, and its content sh...

(SUBJECT_MATTER)


[misspelling] ~169-~169: Did you mean “principal” (=main)?
Context: ...uld adhere strictly to that scope. This principle aims to avoid overlaps between ontologi...

(IN_PRINCIPAL)


[style] ~234-~234: Consider using a different adverb to strengthen your wording.
Context: ...e and pull request descriptions. We are very grateful to everyone who participated. ...

(VERY_DEEPLY)


[style] ~236-~236: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... for backing the microgrant initiative. We also encourage everyone to get involved...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 Markdownlint

28-28: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

(MD001, heading-increment)


110-110: Expected: atx; Actual: atx_closed
Heading style

(MD003, heading-style)


46-46: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


47-47: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


48-48: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


49-49: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


50-50: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


51-51: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


52-52: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


54-54: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


55-55: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


56-56: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


252-252: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)


178-178: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


222-222: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


73-73: null
Spaces inside link text

(MD039, no-space-in-links)


78-78: null
Spaces inside link text

(MD039, no-space-in-links)


78-78: null
Spaces inside link text

(MD039, no-space-in-links)


82-82: null
Spaces inside link text

(MD039, no-space-in-links)


83-83: null
Spaces inside link text

(MD039, no-space-in-links)


164-164: null
Spaces inside link text

(MD039, no-space-in-links)


180-180: null
Spaces inside link text

(MD039, no-space-in-links)


195-195: null
Spaces inside link text

(MD039, no-space-in-links)


216-216: null
Spaces inside link text

(MD039, no-space-in-links)

_posts/2024-10-14-5th-issue-newsletter.md Outdated Show resolved Hide resolved
Copy link
Contributor

@nlharris nlharris left a comment

Choose a reason for hiding this comment

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

This looks fine except for the images. See previous newsletters for examples of how to include the images.

@matentzn matentzn changed the title Create 2024-10-14-5th-issue-newsletter.md Create 2024-10-14-6th-issue-newsletter.md Oct 16, 2024
@matentzn matentzn requested a review from nlharris October 16, 2024 14:00
Copy link
Contributor

@nlharris nlharris left a comment

Choose a reason for hiding this comment

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

looks good! thanks for fixing, leila, and thanks for the image instructions, nico!

@nlharris nlharris merged commit fe4e4c2 into OBOFoundry:master Oct 16, 2024
3 checks passed
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.

3 participants