Merge branch 'master' into lschriml-patch-1

Author: deepakunni3

_config.yml

@@ -574,7 +574,7 @@ ontologies:
     github: amalik01
     label: Adnan Malik
     orcid: 0000-0001-8123-5351
-  depicted_by: https://www.ebi.ac.uk/chebi/images/ChEBI_logo.png
+  depicted_by: https://www.ebi.ac.uk/chebi/chebi_logo.svg
   description: A structured classification of molecular entities of biological interest
     focusing on 'small' chemical compounds.
   domain: chemistry and biochemistry
@@ -1428,9 +1428,9 @@ ontologies:
   browsers:
   - label: DO
     title: DO Browser
-    url: http://www.disease-ontology.org/
+    url: https://disease-ontology.org/
   build:
-    source_url: https://github.com/DiseaseOntology/DiseaseDriversOntology/tree/main/src/ontology/disdriv.owl
+    source_url: https://raw.githubusercontent.com/DiseaseOntology/DiseaseDriversOntology/refs/heads/main/src/ontology/disdriv.owl
   contact:
     email: [email protected]
     github: lschriml
@@ -1440,7 +1440,7 @@ ontologies:
     ExO ontology exposure stressors. An application ontology. Built in collaboration
     with EnvO, ExO, ECTO and ChEBI.
   domain: health
-  homepage: http://www.disease-ontology.org
+  homepage: https://disease-ontology.org/
   id: disdriv
   layout: ontology_detail
   license:
@@ -1465,13 +1465,13 @@ ontologies:
   - description: Human Disease Ontology
     examples:
     - description: fetal alcohol syndrome, has exposure stressor some alcohol
-      url: https://www.disease-ontology.org/?id=DOID:0050665
-    user: https://www.disease-ontology.org
+      url: https://disease-ontology.org/?id=DOID:0050665
+    user: https://disease-ontology.org/
 - activity_status: active
   browsers:
   - label: DO
     title: DO Browser
-    url: http://www.disease-ontology.org/do
+    url: https://disease-ontology.org/do
   build:
     infallible: 1
     method: obo2owl
@@ -1481,11 +1481,11 @@ ontologies:
     github: lschriml
     label: Lynn Schriml
     orcid: 0000-0001-8910-9851
-  depicted_by: http://www.disease-ontology.org/media/images/DO_logo.jpg
+  depicted_by: https://disease-ontology.org/media/images/DO_logo_teal.png
   description: An ontology for describing the classification of human diseases organized
     by etiology.
   domain: health
-  homepage: http://www.disease-ontology.org
+  homepage: https://disease-ontology.org
   id: doid
   in_foundry_order: 1
   layout: ontology_detail
@@ -1531,8 +1531,8 @@ ontologies:
   - description: MGI disease model annotations use DO
     examples:
     - description: physical disorder
-      url: http://www.informatics.jax.org/disease/DOID:0080015
-    user: http://www.informatics.jax.org/disease
+      url: https://www.informatics.jax.org/disease/DOID:0080015
+    user: https://www.informatics.jax.org/disease
   - description: Immune Epitope Database
     examples:
     - description: Antibody and T cell epitopes associated with human diseases

_data/alumni.yml

@@ -10,6 +10,10 @@ members:
   name: Mathias Brochhausen
   orcid: 0000-0003-1834-3856
   wikidata: Q57161944
+- github: pbuttigieg
+  name: Pier Luigi Buttigieg
+  orcid: 0000-0002-4366-3088
+  wikidata: Q41566750
 - github: mcourtot
   link: http://purl.org/net/mcourtot
   name: Melanie Courtot

_data/operations.yml

@@ -198,16 +198,6 @@ members:
   name: Paul Fabry
   orcid: 0000-0002-3336-2476
   wikidata: Q108555457
-- affiliation:
-    name: Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research, Bremerhaven
-    ror: 032e6b942
-  country: Germany
-  github: pbuttigieg
-  groups:
-  - outreach
-  name: Pier Luigi Buttigieg
-  orcid: 0000-0002-4366-3088
-  wikidata: Q41566750
 - affiliation:
     name: La Jolla Institute for Immunology, La Jolla, CA
     ror: 05vkpd318

_includes/header.html

@@ -137,8 +137,11 @@
                                 Mail List</a>
                         </li>
                         <li>
-                            <a class="dropdown-item" href="https://join.slack.com/t/obo-communitygroup/shared_invite/zt-1oq48ttk7-kKo0i6TwntYtAq~Jcjjg4g">OBO
+                            <a class="dropdown-item" href="https://join.slack.com/t/obo-communitygroup/shared_invite/zt-3gs80gmrk-9yZT913GViLUg04pgE3wOA">OBO
                                 Community Slack channel</a>
+                        </li>
+                         <li>
+                            <a class="dropdown-item" href="https://www.linkedin.com/groups/14485140/">LinkedIn group</a>
                         </li>
                         <li>
                             <a class="dropdown-item" href="/docs/NewOBOFC.html">Join the OBO Operations Committee</a>

_posts/2025-10-22-9th-issue-newsletter.md

@@ -5,7 +5,7 @@ title: Principle Review Process
 
 This page describes the process for reviewing, updating, and creating [OBO Foundry Principles](http://obofoundry.github.io/principles/fp-000-summary.html). Most of the steps are done by the OBO Foundry Editorial Working Group (EWG).
 
-For the following, steps 1-5 are internal to the EWG and steps 6-7 are internal to the OBO Operations Committee. 
+For the following, steps 1-5 and 12-13 are internal to the EWG and steps 6-7 are internal to the OBO Operations Committee. 
 
 1. Discuss the principle during an Editorial Working Group (EWG) call.
 2. Write up proposed revisions as a [GitHub issue](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/new?assignees=nataled&labels=attn%3A+Editorial+WG&projects=&template=obo-foundry-principles.md&title=Principle+%23%3CENTER+NUMBER+HERE%3E+%22%3CENTER+NAME+HERE%3E%22) (not a pull request).
@@ -14,10 +14,11 @@ For the following, steps 1-5 are internal to the EWG and steps 6-7 are internal
 5. If necessary, discuss changes made during the commenting period and finalize the text.
 6. Once the EWG agrees on a final version, a member presents the text to the OBO Foundry Operations Committee for discussion during a meeting or via the issue tracker.
 7. Once the wording is approved by OBO Operations, a member of the EWG makes a pull request reflecting the consensus of previous discussions. Note that the pull request should be marked as 'draft' if it is a new principle.
-8. For new principles or major changes to existing principles, announce the proposal on the [obo-discuss mailing list](mailto:[email protected]) and the [obo-community #general Slack channel](https://join.slack.com/t/obo-communitygroup/shared_invite/zt-1oq48ttk7-kKo0i6TwntYtAq~Jcjjg4g) and request public feedback.
-9. Allow a two-week commenting period on the pull request.
-10. If the feedback includes major changes or objections, re-discuss during an OBO Operations call and re-do any relevant steps indicated above.
-11. At the end of the commenting period, assuming no major changes are needed, a member of the EWG will merge the pull request (removing 'draft' status if appropriate) and thereby make the changes public.
-12. Add the new principle to the [Principles Summary](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/principles/fp-000-summary.md) list and to the [Principles dropdown menu](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/principles/all.yml).
+8. For new principles or major changes to existing principles, announce the proposal on the [obo-discuss mailing list](mailto:[email protected])
+   and the [obo-community #general Slack channel](https://join.slack.com/t/obo-communitygroup/shared_invite/zt-3gs80gmrk-9yZT913GViLUg04pgE3wOA) and request public feedback.
+10. Allow a two-week commenting period on the pull request.
+11. If the feedback includes major changes or objections, re-discuss during an OBO Operations call and re-do any relevant steps indicated above.
+12. At the end of the commenting period, assuming no major changes are needed, a member of the EWG will merge the pull request (removing 'draft' status if appropriate) and thereby make the changes public.
+13. Add the new principle to the [Principles Summary](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/principles/fp-000-summary.md) list and to the [Principles dropdown menu](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/principles/all.yml).
 
 The need for a new principle can arise when an existing principle tries to cover too much and requires splitting, or as new needs arise within the community.

docs/PrinciplesReviewWorkflow.md

@@ -8,7 +8,7 @@ The OBO Foundry is currently a volunteer-run organization. There are many ways t
 - Submit a bug report, question, or feature request to the [OBO Foundry issue tracker](https://github.com/OBOFoundry/OBOFoundry.github.io/issues)
 - Join the [OBO-Discuss mailing list](https://groups.google.com/forum/#!forum/obo-discuss)
 - Join the [OBO-Tools mailing list](https://groups.google.com/forum/#!members/obo-tools)
-- Participate in the [OBO Community Slack channel](https://join.slack.com/t/obo-communitygroup/shared_invite/zt-1oq48ttk7-kKo0i6TwntYtAq~Jcjjg4g)
+- Participate in the [OBO Community Slack channel](https://join.slack.com/t/obo-communitygroup/shared_invite/zt-3gs80gmrk-9yZT913GViLUg04pgE3wOA)
 - [Submit your ontology](/faq/how-do-i-register-my-ontology.html) to be considered for inclusion in the OBO Foundry
 - [Create a pull request to improve this website](/faq//how-do-i-modify-website.html)
 - Nominate yourself to [join the OBO Foundry Operations Committee](/docs/NewOBOFC.html)