jeromedockes.github.io

Jérôme Dockès is a research engineer in the SODA lab at Inria, France, who works on open-source software related to machine learning. According to his personal site, he is a maintainer of skrub and Nilearn, and he developed and maintains NeuroQuery (with Romain Primet and Hande Gözükan), pubget, and labelbuddy.

Projects at a Glance

How the Roles Differ

The site draws a distinction worth noting: for skrub and Nilearn he describes himself as one of the maintainers, implying shared stewardship of established projects. For NeuroQuery, pubget, and labelbuddy, he states that he developed and maintains them, which points to original authorship alongside ongoing upkeep.

Machine learning and neuroimaging

His stated focus is open-source software for machine learning, with skrub named as the main project. Nilearn and NeuroQuery sit at the intersection of machine learning and neuroimaging, and NeuroQuery is the one project where the site credits co-developers by name.

Text and annotation tooling

pubget and labelbuddy are listed without further description on the page, so the site itself does not specify their scope beyond his role in creating and maintaining them.

Where to Verify Details

The page lists a contact address ([email protected]), a GitHub account, a publications section, and an OpenPGP public key with fingerprint for secure contact. For current project status, releases, or contribution guidelines, the GitHub account linked from the site is the authoritative entry point, since the personal page only summarizes his roles.

Jérôme Dockès's personal site, jeromedockes.github.io, is the central place to start: it links to his publications section and his GitHub account, and identifies him as a research engineer in the SODA lab at Inria, France. Use the site when you want an official, self-maintained pointer to his work; use GitHub directly when you need code, issues, or contribution history.

What the Site Provides

The page is a short professional profile rather than a full publication database. According to the site, it includes:

• Affiliation and role: research engineer in the SODA lab at Inria, France.
• Contact: a public email address, [email protected].
• GitHub account: a link to his GitHub profile.
• Publications: a publications section.
• OpenPGP public key: an RSA 4096 key with key ID BB047DAC040B35F4 and a published fingerprint.

The site also states that he is one of the maintainers of skrub and Nilearn, and that he developed and maintains NeuroQuery (with Romain Primet and Hande Gözükan), pubget, and labelbuddy.

Finding Publications

1. Open jeromedockes.github.io.
2. Follow the link labeled for publications.
3. Use the listed works as the authoritative starting point, then cross-check individual titles on the publisher or preprint page for the version you need.

The site does not present itself as a searchable bibliography, so expect a list rather than filters or export tools. If you need citation metadata, take titles from the site and confirm details such as venue and year at the source.

Finding the GitHub Profile and Code

The site links directly to his GitHub account. From there you can reach the repositories behind the projects named on the page:

For questions about a specific project, the repository's issue tracker is usually more useful than the personal site, which does not host discussion.

Contact and Key Verification

The site gives one contact route: email at [email protected]. For encrypted mail, it publishes an OpenPGP public key (RSA 4096, key ID BB047DAC040B35F4) and a fingerprint. To verify a signed message or key, compare the fingerprint shown on the site with the one attached to the key you received, and treat a mismatch as a reason not to trust that copy. The site does not describe a preferred response time or alternate contact channel.

When to Use Which Source

• Personal site: affiliation, contact details, key fingerprint, and a curated list of projects and publications.
• GitHub: source code, releases, issues, and maintenance activity.
• Publisher or preprint pages: final citation details and full text where available.

Start at the personal site for orientation, then move to GitHub or the publication source for the specific artifact you need.

The site lists a direct contact email, [email protected], and links to his GitHub account. It also publishes an OpenPGP public key, rsa4096/BB047DAC040B35F4, together with its fingerprint, so you can check that a signed message or key really belongs to him. These details come from the page itself; the site does not describe response times or any contact preferences beyond the email address.

Contacting Jérôme Dockès

The page gives one direct channel:

He is a research engineer in the SODA lab at Inria, in France, and works mainly on skrub, an open-source machine-learning library. If your question is about a specific project, naming it in your message helps route it to the right context. The page does not state which channel he prefers for project questions, so treat the email as the general route and GitHub as the place to inspect code, issues, and contribution activity.

Verifying the OpenPGP Key

The page publishes the key ID and fingerprint so you can confirm a key you already hold, or one you receive, matches the published one.

1. Get the key from the source you are checking — for example, a signed release, a keyserver result, or a message from him.
2. Read its fingerprint with gpg --fingerprint BB047DAC040B35F4 (or with the full key ID you were given).
3. Compare the output against the fingerprint published on jeromedockes.github.io. A match confirms the key is the one he publishes; a mismatch means you are looking at a different key.
4. Import and use it only after the fingerprints match, e.g. gpg --import key.asc followed by decryption or signature verification.

The expected result is a fingerprint identical to the published one. The common snag is comparing only the short key ID: short IDs are easier to spoof, so compare the full fingerprint character by character. Another pitfall is fetching a key from an unverified keyserver and assuming it is his — the published fingerprint, not the keyserver listing, is the reference point.

What the Page Does and Does Not Tell You

The page is a personal homepage for a research engineer, not a company site or a support portal. It confirms his role at Inria's SODA lab, his maintainer work on skrub and Nilearn, his development of NeuroQuery with Romain Primet and Hande Gözükan, and his work on pubget and labelbuddy. It also lists publications and the OpenPGP details above.

It does not publish a phone number, a postal address, office hours, or a stated turnaround for email. If you need a formal or time-sensitive response, the page alone will not tell you whether email is the right route — you would need to confirm that through the channel itself.

jeromedockes.github.io is the personal homepage of Jérôme Dockès, a research engineer in the SODA lab at Inria, France. The site is a brief professional profile rather than a blog or product page: it states his role, the open-source machine-learning software he develops and maintains, and how to reach him or verify his identity.

What the site covers

The page is short and factual. It identifies Dockès as a research engineer at Inria's SODA lab and describes his work as the development of open-source software related to machine learning, with skrub named as his main project. It then lists the projects he maintains or has developed, his publications, and his contact and cryptographic details.

Who each part is useful for

• Developers looking for the maintainer behind a library. If you use skrub, Nilearn, NeuroQuery, pubget, or labelbuddy and want to know who is behind it, this page gives the maintainer's own account of his involvement.
• Researchers and collaborators. The listed publications and the Inria/SODA affiliation are the relevant starting points for academic contact.
• Anyone verifying a signed message or package. The OpenPGP key ID and fingerprint are published here, so you can check that a key you received matches the one the author advertises.

What the site does not offer

The page is a profile, not a documentation hub. It does not host tutorials, API references, or downloads for skrub or the other projects; for those, follow the project links from his GitHub account. It also does not state pricing, licensing terms, or availability details for any software, so treat the site as a pointer to the projects rather than a source for their terms.

Practical use

To contact him about a project, use the email address listed on the page. To confirm a signed release or message, compare the key fingerprint against rsa4096/BB047DAC040B35F4 as published there. To follow or contribute to his software work, start from the GitHub account linked on the site, where the maintained projects are listed.