MAINTAINERS

Rules

All content inside GPT4All shall have a documented maintainer
If a maintainer decides to retire or resign a call for volunteers will go out
If no further maintainer can be found in a reasonable time frame, then the content will be marked deprecated and removed in time

Job

Maintainers will be...

Responsible for overseeing content under their stewardship
Responsible for triaging new issues, reviewing PRs, assigning priority to tasks
Responsible for keeping content in sufficient quality in a timely fashion

List

Adam Treat (@manyoso)
E-mail: [email protected]
Discord: @gonzochess75

Overall project maintainer
Chat UI

Jared Van Bortel (@cebtenzzre)
E-mail: [email protected]
Discord: @cebtenzzre

gpt4all-backend
Python binding
Python CLI app

Jacob Nguyen (@jacoobes)
Discord: @jacoobes
E-mail: [email protected]

TypeScript binding

Dominik (@cosmic-snow)
E-mail: [email protected]
Discord: @cosmic__snow

Community documentation (GitHub Wiki)

Max Cembalest (@mcembalest)
E-mail: [email protected]
Discord: @maxcembalest.

Official documentation (gpt4all-bindings/python/docs -> https://docs.gpt4all.io/)

Thiago Ramos (@thiagojramos)
E-mail: [email protected]

pt_BR translation

Victor Emanuel (@SINAPSA-IC)
E-mail: [email protected]
Discord: @sinapsa_ic_56124_99632

ro_RO translation

不知火 Shiranui (@supersonictw)
E-mail: [email protected]
Discord: @supersonictw

zh_TW translation

Jeremy Tayco (@jstayco)
E-mail: [email protected]
Discord: @vertana

es_MX translation

Riccardo Giovanetti (@Harvester62)
E-mail: [email protected]
Discord: @harvester62

it_IT translation

Tim (@Tim453)
E-mail: [email protected]
Discord: @Tim453

Flatpak

Jack (@wuodoo)
E-mail: [email protected]>
Discord: @mikage

zh_CN translation