[petsc-dev] NumFocus questions on Code of Conduct
Barry Smith
bsmith at petsc.dev
Wed May 28 17:12:40 CDT 2025
Location for discussion and voting https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/issues/1768__;!!G_uCfscf7eWS!fk3eqIyBIzqqE1RZ1Utr_BISrbl4xS6N2d86e7TS0E9C3bnekYSovLjCZUyLEYjVx2aT7XtpRKhgqbV5eSOoKQ$
Everyone is invited to participate in the discussion
> On May 28, 2025, at 3:19 PM, Barry Smith <bsmith at petsc.dev> wrote:
>
>
> I had the NumFocus meeting today and have two questions for discussion and eventual answer
>
> 1) Regarding the previous Code of Conduct question. I now understand the code of conduct questions we should answer
>
> 1) Will PETSc keep its own C of C or replace it with the NumFocus C of C? https://urldefense.us/v3/__https://numfocus.org/code-of-conduct__;!!G_uCfscf7eWS!fk3eqIyBIzqqE1RZ1Utr_BISrbl4xS6N2d86e7TS0E9C3bnekYSovLjCZUyLEYjVx2aT7XtpRKhgqbVZuPTXpw$ NumFocus
> has an outside group to investigate violations.
>
> 2) If PETSc adopts the NumFocus C of C do we decide
> a) the outside group makes "recommendations" to the PETSc governance board if problems come up
> b) the outside group also imposes changes if a violation has occurred (XXX is banned from GitLab issues due to violations)?
>
> It is hard to see much practical difference between a and b, since no one can forcibly impose changes IMHO.
>
> We should ideally have a PETSc governance board decision by September.
>
> 2) We need another "official" (one or more) PETSc contact for NumFocus. In case I die or am cancer ridden etc. Ideally, they would go to
> the annual meeting and meet with NumFocus a couple of times of year etc, like I do. It is a low-maintenance role unless you want it to be more.
>
> I nominate Jed (as one of them) since he was the instigator of PETSc joining NumFocus and understands it better than the rest of us.
>
> Volunteers?
>
> Barry
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20250528/2e0aeecb/attachment.html>
More information about the petsc-dev
mailing list