Re: [sage-devel] Owners and Managers of sage-devel and other Google Groups: Please identify

Thanks, David, that's very helpful. On Thursday, August 22, 2024 at 7:58:00 PM UTC-7 David Roe wrote: > On Thu, Aug 22, 2024 at 10:32 PM Matthias Koeppe > wrote: > >> We are currently collecting the information which individuals manage the >> project's infrastructure in >> https://github.com/

[sage-devel] Re: (I’m failing to build a working binary) Please provide a snapcraft package/container as now all but one Linux distributions no longer package Sagemath.

I recommend you install SageMath via Conda: https://doc.sagemath.org/html/en/installation/conda.html#install-from-conda-forge In my experience, this method "just works" even on seriously old and cranky Linux distros. Best, Nathan On Thursday, August 22, 2024 at 12:32:08 PM UTC-5 lael.c...@gma

Re: [sage-devel] Owners and Managers of sage-devel and other Google Groups: Please identify

On Thu, Aug 22, 2024 at 10:32 PM Matthias Koeppe wrote: > We are currently collecting the information which individuals manage the > project's infrastructure in > https://github.com/sagemath/sage/wiki/Infrastructure > > The information who is Owner or Manager of most of our project's Google > Gro

[sage-devel] Owners and Managers of sage-devel and other Google Groups: Please identify

We are currently collecting the information which individuals manage the project's infrastructure in https://github.com/sagemath/sage/wiki/Infrastructure The information who is Owner or Manager of most of our project's Google Groups lists does not appear to be publicly accessible. I would requ

Re: [sage-devel] Re: Policy discussion about hiding GitHub comments

On 22 August 2024 22:37:17 BST, Matthias Koeppe wrote: >On Thursday, August 22, 2024 at 2:19:36 PM UTC-7 David Roe wrote: > >We are starting this thread for two reasons. > >1. Kwankyu asked for clarity on who can mark comments as off topic. >2. You marked this comment >

[sage-devel] Re: message marked as off topic

I'll note that trying to enumerate things that someone might be offended by is a well-meaning but ultimately futile approach because that list will never be complete. More importantly, a discussion of governance cannot start with the consideration of what actions people may be "offended" by.

[sage-devel] Re: Package upgrade PRs waiting for review

On Wednesday, August 21, 2024 at 3:35:57 PM UTC-7 Nils Bruin wrote: I don't think *you* would need to maintain that set. It would just be something to maintained. :) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this gr

[sage-devel] Re: Policy discussion about editing GitHub comments and PR/issue descriptions

Of course, minor edits and fixes to help the author is not a concern here. This thread is for the cases when the author objects to the action of the editor, and about how to resolve the dispute. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: Policy discussion about hiding GitHub comments

On Friday, August 23, 2024 at 7:24:03 AM UTC+9 Martin R wrote: ... It appears to me that there is no consensus among the dozen or so contributors in what is considered off topic or offensive. Any criterion on the content of the comment that can be considered "off topic" or "spam" may risk o

Re: [sage-devel] Re: Policy discussion about hiding GitHub comments

On Thursday, August 22, 2024 at 2:19:36 PM UTC-7 David Roe wrote: We are starting this thread for two reasons. 1. Kwankyu asked for clarity on who can mark comments as off topic. 2. You marked this comment as off-topic, which

Re: [sage-devel] Re: Policy discussion about hiding GitHub comments

Hi Martin, The Code of Conduct Committee typically does let the author of a comment know if the committee hides the comment, with an explanation. Or at least the committee strives to do this. Regards, John On Thursday, August 22, 2024 at 3:24:03 PM UTC-7 axio...@yahoo.de wrote: > I fully a

Re: [sage-devel] Re: Policy discussion about hiding GitHub comments

I fully agree with the proposed policy. It appears to me that there is no consensus among the dozen or so contributurs in what is considered off topic or offensive. Therefore, I would hope that such a policy reduces tension. If possible (and the policy is adopted), it might be extra-nice if t

[sage-devel] Re: Policy discussion about editing GitHub comments and PR/issue descriptions

I would be happy with the proposed policy. I would tend to allow fixing typos and updating links in all comments. However, since there is already a lot of tension between some developers, it is probably easier to refrain from that. Martin On Thursday 22 August 2024 at 21:35:07 UTC+2 Matthias

Re: [sage-devel] Re: Policy discussion about hiding GitHub comments

We are starting this thread for two reasons. 1. Kwankyu asked for clarity on who can mark comments as off topic. 2. You marked this comment as off-topic, which asked for clarification on the action you had just taken removing th

[sage-devel] Re: Policy discussion about editing GitHub comments and PR/issue descriptions

I'll note that I have at several times edited other (privileged) people's comments after they (by mistake) clicked the "edit" button instead of the "reply" button on someone's comment, to restore the flow of the discussion. This is an example of a typical administrative actions that responsible

[sage-devel] Re: Policy discussion about editing GitHub comments and PR/issue descriptions

On Thursday, August 22, 2024 at 11:08:51 AM UTC-7 John H Palmieri wrote: This message comes from the Code of Conduct Committee, in response to a question from Kwankyu (labeled A4 in his message) about the authority to modify

[sage-devel] Re: Policy discussion about hiding GitHub comments

On Thursday, August 22, 2024 at 11:08:48 AM UTC-7 John H Palmieri wrote: This message comes from the Code of Conduct Committee, in response to a question from Kwankyu (labeled A1 in his message) about the authority to mark a

[sage-devel] Re: Package upgrade PRs waiting for review

On Thursday, August 22, 2024 at 2:41:57 AM UTC-7 tobia...@gmx.de wrote: People interested in maintaining sagelib should only care about the version constraint in the pyproject.toml file (e.g. if they decide that a new feature of numpy is needed, then the version constraint of numpy should be ch

[sage-devel] Policy discussion about editing GitHub comments and PR/issue descriptions

This message comes from the Code of Conduct Committee, in response to a question from Kwankyu (labeled A4 in his message) about the authority to modify a comment by someone else (including PR and issue descriptions).

[sage-devel] Policy discussion about hiding GitHub comments

This message comes from the Code of Conduct Committee, in response to a question from Kwankyu (labeled A1 in his message) about the authority to mark a comment as off topic, and more generally about hiding comments. Propo

[sage-devel] Re: Package upgrade PRs waiting for review

People interested in maintaining sagelib should only care about the version constraint in the pyproject.toml file (e.g. if they decide that a new feature of numpy is needed, then the version constraint of numpy should be changed accordingly). People interested in maintaining sage-the-distro sho