Skip to content

new top-level "Credits" section#13953

Open
drammock wants to merge 1 commit into
mne-tools:mainfrom
drammock:sponsors
Open

new top-level "Credits" section#13953
drammock wants to merge 1 commit into
mne-tools:mainfrom
drammock:sponsors

Conversation

@drammock

@drammock drammock commented Jun 8, 2026

Copy link
Copy Markdown
Member

This PR:

  • adds a new top-level website section "Credits", containing a landing page and three sub-pages:
    • Project Leadership (previously "Current Project Leadership and Institutional Partners" AKA doc/overview/people.rst)
    • Contributors (previously "Credit" AKA doc/credit.rst, which is auto-generated)
    • Sponsors (previously "Funding and other support" AKA doc/funding.rst)
  • removes current/former institutional partners from the "people" page (it was in 2 places before); now they're only on the "sponsors" page
  • on the "sponsors" page, separates the funding into current/former (to mirror how institutional partners are handled on that same page)
  • adds logos to the "sponsors" page
  • reduces the funder and institutional partner logos on the homepage to only the current sponsors
  • adds Steph Jones to the advisory board (was originally invited during a sabbatical, but has since returned and accepted)
  • side quest: pull the massive dict of institutions out of conf.py and into a dedicated YAML file.

The main motivation for this is to make current support more prominent, as incentive to potential institutional sponsors (fewer homepage logos / dedicated "current sponsors" section == better visibility)

@larsoner

larsoner commented Jun 8, 2026

Copy link
Copy Markdown
Member

FYI these errors

/home/circleci/project/mne/time_frequency/tfr.py:docstring of mne.time_frequency.tfr.EpochsTFR:59: WARNING: py:mod reference target not found: joblib [ref.mod]

are being fixed in #13938, which should merge imminently

@larsoner

larsoner commented Jun 8, 2026

Copy link
Copy Markdown
Member

Looks good to me! Style CIs are not happy with you though 😄

@drammock

drammock commented Jun 9, 2026

Copy link
Copy Markdown
Member Author

Looks good to me! Style CIs are not happy with you though 😄

Time to take a look at our pre-commit config. There shouldn't be conflicts between what it wants and what style CI job wants

@larsoner

larsoner commented Jun 9, 2026

Copy link
Copy Markdown
Member

pre-commit also failed

But the style job in general does run more stuff than pre-commit, IIRC for speed reasons (e.g. vulture is too slow to run on every commit and operates on the repository as a whole not individual files)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants