1(petsc_developers_communication_channels)= 2 3# PETSc Developers Communication Channels 4 5## GitLab 6 7Day-to-day development happens at the [PETSc GitLab repository](https://gitlab.com/petsc/petsc). 8There, you can find the history and development version of the source code, 9[see or create issues](https://gitlab.com/petsc/petsc/issues), 10[see or create merge requests](https://gitlab.com/petsc/petsc/-/merge_requests), 11and more. 12 13## Mailing Lists 14 15Joining the {ref}`mailing lists <doc_mail>` and [PETSc on Discord](https://discord.gg/Fqm8r6Gcyb). 16 17Comments and questions regarding PETSc design and development should go to <mailto:petsc-dev@mcs.anl.gov>. 18 19Configuration issues (with `make.log` and `configure.log` attached) should be reported to <mailto:petsc-maint@mcs.anl.gov>. 20 21For bugs and other issues, we encourage developers to create a [GitLab](https://gitlab.com) account and 22[file issues directly](https://gitlab.com/petsc/petsc/issues); 23this allows better tracking of long-term bug reports and feature requests. 24 25General questions regarding the use of PETSc can, as usual, go to <mailto:petsc-users@mcs.anl.gov> (public) 26or <mailto:petsc-maint@mcs.anl.gov> (private, can handle large attachments). 27 28## Responding to User Requests and Questions 29 30PETSc users communicate to the PETSc team via the mailing lists 31<mailto:petsc-maint@mcs.anl.gov> and <mailto:petsc-users@mcs.anl.gov>, [PETSc on Discord](https://discord.gg/Fqm8r6Gcyb), and with 32[PETSc GitLab Issues](https://gitlab.com/petsc/petsc/-/issues). When responding there, 33please follow these guidelines: 34 35- Be polite and behave according to the [Code of Conduct](https://gitlab.com/petsc/petsc/-/blob/main/CODE_OF_CONDUCT.md). 36- Address the person by name (when you can determine a name). 37- Apologize for the problem when it is appropriate. 38- Thank the person for their patience if it is more than six hours since the report came in. 39- If the person drops "petsc-maint" or "petsc-users" from the reply list, add it back. 40- 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