Re: [sage-devel] Re: Labels and Reviewing

2024-03-08 Thread David Roe
Dear Sage developers, Dima is correct that there are several developers who have blocked each other. The Sage Code of Conduct Committee is aware of several cases and is working on resolving them. We believe both that the presence of these blocks is harming the Sage project, and that it can be

Re: [sage-devel] Re: Labels and Reviewing

2024-03-08 Thread Dima Pasechnik
On 8 March 2024 14:11:41 GMT, 'Martin R' via sage-devel wrote: >I don't know exactly what case of blocking you have in mind, on GitHub you can block a user - such a block prevents the blocked user from commenting and changing the status of your PRs and issues. Currently there are a few

Re: [sage-devel] Re: Labels and Reviewing

2024-03-08 Thread 'Martin R' via sage-devel
I don't know exactly what case of blocking you have in mind, but I'm going to be bold and state that blocking among fellow developers (this is not about private messages, right?) cannot really be a solution, in my opinion: * either there has been a substantial breach of conduct, in which case I

Re: [sage-devel] Re: Labels and Reviewing

2024-03-08 Thread Dima Pasechnik
On Thu, Mar 7, 2024 at 8:39 PM David Roe wrote: > Addressing a comment from Travis > on > the voting thread: > > "but might want to consider cases when its 2 vs 1 as requiring at least > one other person involved. (Sorry for

Re: [sage-devel] Re: Labels and Reviewing

2024-03-07 Thread David Roe
Addressing a comment from Travis on the voting thread: "but might want to consider cases when its 2 vs 1 as requiring at least one other person involved. (Sorry for being late to realize this.)" This border case was actually

Re: [sage-devel] Re: Labels and Reviewing

2024-02-28 Thread Dima Pasechnik
On Wed, Feb 28, 2024 at 11:29 AM Giacomo Pope wrote: > Apologies for the basic question in this thread, but recently I have seen > lots of conversation about the different labels and I want to clarify > something for myself. > > In the past few PR I have made for Sage, randomised testing has

Re: [sage-devel] Re: Labels and Reviewing

2024-02-28 Thread Kwankyu Lee
If there is code causing CI failure in random testing, should I mark the fix for this as a "blocker", even if the chance of this failure is small? No. A "blocker" blocks the release. We use it for serious fixes worth the delay. -- You received this message because you are subscribed to

Re: [sage-devel] Re: Labels and Reviewing

2024-02-28 Thread Giacomo Pope
Apologies for the basic question in this thread, but recently I have seen lots of conversation about the different labels and I want to clarify something for myself. In the past few PR I have made for Sage, randomised testing has uncovered (usually) trivial bugs. I then write new PRs to fix

Re: [sage-devel] Re: Labels and Reviewing

2024-02-27 Thread David Roe
On Wed, Feb 28, 2024 at 1:01 AM Kwankyu Lee wrote: > Thank you for making progress on these urgent issues. I suggest the > following: > > 1. Open two other new threads, each of which is for voting on each > proposal. > 2. On a proposal, it should be clear that *a positive vote (+1) is for > the

[sage-devel] Re: Labels and Reviewing

2024-02-27 Thread Kwankyu Lee
Thank you for making progress on these urgent issues. I suggest the following: 1. Open two other new threads, each of which is for voting on each proposal. 2. On a proposal, it should be clear that *a positive vote (+1) is for the whole proposal,* and if one is negative to any part of the