14bcd95a3SBarry Smith(petsc_developers_communication_channels)= 24bcd95a3SBarry Smith 34bcd95a3SBarry Smith# PETSc Developers Communication Channels 44bcd95a3SBarry Smith 54bcd95a3SBarry Smith## GitLab 64bcd95a3SBarry Smith 74bcd95a3SBarry SmithDay-to-day development happens at the [PETSc GitLab repository](https://gitlab.com/petsc/petsc). 84bcd95a3SBarry SmithThere, you can find the history and development version of the source code, 94bcd95a3SBarry Smith[see or create issues](https://gitlab.com/petsc/petsc/issues), 104bcd95a3SBarry Smith[see or create merge requests](https://gitlab.com/petsc/petsc/-/merge_requests), 114bcd95a3SBarry Smithand more. 124bcd95a3SBarry Smith 134bcd95a3SBarry Smith## Mailing Lists 144bcd95a3SBarry Smith 15*d5edbea4SSatish BalayJoining the {ref}`mailing lists <doc_mail>` and [PETSc on Discord](https://discord.gg/Fqm8r6Gcyb). 164bcd95a3SBarry Smith 174bcd95a3SBarry SmithComments and questions regarding PETSc design and development should go to <mailto:petsc-dev@mcs.anl.gov>. 184bcd95a3SBarry Smith 194bcd95a3SBarry SmithConfiguration issues (with `make.log` and `configure.log` attached) should be reported to <mailto:petsc-maint@mcs.anl.gov>. 204bcd95a3SBarry Smith 214bcd95a3SBarry SmithFor bugs and other issues, we encourage developers to create a [GitLab](https://gitlab.com) account and 224bcd95a3SBarry Smith[file issues directly](https://gitlab.com/petsc/petsc/issues); 234bcd95a3SBarry Smiththis allows better tracking of long-term bug reports and feature requests. 244bcd95a3SBarry Smith 254bcd95a3SBarry SmithGeneral questions regarding the use of PETSc can, as usual, go to <mailto:petsc-users@mcs.anl.gov> (public) 264bcd95a3SBarry Smithor <mailto:petsc-maint@mcs.anl.gov> (private, can handle large attachments). 274bcd95a3SBarry Smith 284bcd95a3SBarry Smith## Responding to User Requests and Questions 294bcd95a3SBarry Smith 304bcd95a3SBarry SmithPETSc users communicate to the PETSc team via the mailing lists 31*d5edbea4SSatish Balay<mailto:petsc-maint@mcs.anl.gov> and <mailto:petsc-users@mcs.anl.gov>, [PETSc on Discord](https://discord.gg/Fqm8r6Gcyb), and with 324bcd95a3SBarry Smith[PETSc GitLab Issues](https://gitlab.com/petsc/petsc/-/issues). When responding there, 334bcd95a3SBarry Smithplease follow these guidelines: 344bcd95a3SBarry Smith 354bcd95a3SBarry Smith- Be polite and behave according to the [Code of Conduct](https://gitlab.com/petsc/petsc/-/blob/main/CODE_OF_CONDUCT.md). 364bcd95a3SBarry Smith- Address the person by name (when you can determine a name). 374bcd95a3SBarry Smith- Apologize for the problem when it is appropriate. 384bcd95a3SBarry Smith- Thank the person for their patience if it is more than six hours since the report came in. 394bcd95a3SBarry Smith- If the person drops "petsc-maint" or "petsc-users" from the reply list, add it back. 404bcd95a3SBarry Smith- Don’t ask too many questions or give too many suggestions in the same email. The user often responds only to the first of them or becomes confused. 41