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