Lines Matching refs:petsc
7 Day-to-day development happens at the [PETSc GitLab repository](https://gitlab.com/petsc/petsc).
9 [see or create issues](https://gitlab.com/petsc/petsc/issues),
10 [see or create merge requests](https://gitlab.com/petsc/petsc/-/merge_requests),
17 Comments and questions regarding PETSc design and development should go to <mailto:petsc-dev@mcs.an…
19 …th `make.log` and `configure.log` attached) should be reported to <mailto:petsc-maint@mcs.anl.gov>.
22 [file issues directly](https://gitlab.com/petsc/petsc/issues);
25 General questions regarding the use of PETSc can, as usual, go to <mailto:petsc-users@mcs.anl.gov> …
26 or <mailto:petsc-maint@mcs.anl.gov> (private, can handle large attachments).
31 <mailto:petsc-maint@mcs.anl.gov> and <mailto:petsc-users@mcs.anl.gov>, [PETSc on Discord](https://d…
32 [PETSc GitLab Issues](https://gitlab.com/petsc/petsc/-/issues). When responding there,
35 - Be polite and behave according to the [Code of Conduct](https://gitlab.com/petsc/petsc/-/blob/mai…
39 - If the person drops "petsc-maint" or "petsc-users" from the reply list, add it back.