Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-10 Thread David Roe
On Sun, Mar 10, 2024 at 1:44 PM seb@gmail.com wrote: > Personally I don't mind if a maintainer would correct my typos in the PR > description (or something else according to Volker's white list). However, > since this is a privileged action and we cannot be sure that everyone feels > this

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-10 Thread seb....@gmail.com
Personally I don't mind if a maintainer would correct my typos in the PR description (or something else according to Volker's white list). However, since this is a privileged action and we cannot be sure that everyone feels this way, I think this point should be addressed generally. Perhaps the

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-10 Thread David Roe
I agree with both Tobias and Matthias that we should have a discussion about the roles of maintainers (since they have defined privileges on github) and changes to Sage's governance model more generally. Martin and Tobias have commented on trying to include some additional principles into the

[sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-05 Thread Matthias Koeppe
I think it's important to point out that a "Code of Conduct" is merely one document, of limited scope and purpose. In particular it does not touch matters of *governance* of a project. Open source projects with very different governance structures can share the same Code of Conduct. Questions

[sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-04 Thread Volker Braun
Thanks for working on this, John! I like that they are aspirational goals, being nice to each other shouldn't be that hard. There are always going to be questions "what exactly is now allowed", but its impossible to enumerate everything. Is it OK to push to somebody else's branch, or change

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-04 Thread 'tobia...@gmx.de' via sage-devel
I think Martin raises important points and agree that 0-4 should be added to the code of conduct (more in spirit than in this particular formulation; for example, I like the proposed reformulations of David). Point 5 is important as well, but I would say it's enough to spell out the rules

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-01 Thread John H Palmieri
There are suggestions along maybe similar lines at https://github.com/sagemath/sage/pull/36844, and I am trying to think of how we might incorporate your suggestions and the other ones. I've had the thought before about other documents (like our department's by-laws) that there should be two

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-01 Thread 'Martin R' via sage-devel
Thank you for the thoughtful reply! You gave me a lot to think about, and I'll do so over the weekend, rather than rushing. Best, Martin On Friday 1 March 2024 at 18:21:59 UTC+1 David Roe wrote: > Thank you for starting the conversation Martin. I certainly think that > all of these

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-01 Thread David Roe
Thank you for starting the conversation Martin. I certainly think that all of these suggestions are appropriate to discuss, and that sage-devel is probably a better venue for discussion like this than the PR. On Fri, Mar 1, 2024 at 5:49 AM 'Martin R' via sage-devel < sage-devel@googlegroups.com>

[sage-devel] Re: Sage's Code of Conduct: proposed changes

2024-03-01 Thread 'Martin R' via sage-devel
I would like to ask whether we might want to add some of the following to the code of conduct, I could not find it covered there. I admit that it is unclear to me whether the discussion should be on pull requests only. I don't want to add the following to John's pull request, because it