Many of these are disputed for the same underlying reasons. Appointing a different editor for each PR is not likely to help. If you pick an editor from Camp A, he or she will always rule in favor of Camp A; pick an editor from Camp B...
The camps are roughly split across the question whether Sage the distro should be deemphasized, and the development process should be centered around sagelib, or not. As well, and it's not a coincidence, roughly the same partition is on the basis of the developer platform used by the camp member. It appears that the Linux users are primarily for deemphasizing Sage the distro, and macOS user are primarily against. As a general observation, this seems somewhat accurate. That said, as Martin R points out, many (most?) people don't seem to be in a "Camp". I suspect it's due to the latter used to Sage the distro as a "missing macOS package manager". So they are happy adding more and more spkgs to Sage. And Linux users rightly see adding to Sage spkgs, which package software available on their systems in a regular way, as a bloat, which moreover needs constant attention - while sagelib suffers. I don't think that without solving this conflict the disputed PRs dispute can be solved. I may go on discussing how the Sage macOS problems may be mitigated, but not here and now. I don't think it's off-topic to once again point out that this way of phrasing it is very developer-centric. That's not a wrong way to look at it, but an end-user-centric way of looking at it is also valid. And these are largely using Sage on Mac (without knowing about things like brew or conda, nor really wanting to) or even Windows (where not even these options exist, but people seem content to download whatever older version still is available - and they do). Let's ignore the cloud solutions available for now, since I still suspect that for "ordinary" solo uses this is not as significant a factor (as opposed to collaborative ones). So somewhere on sage-devel (probably not this thread) it would be really helpful for people *other* than the two or four primary "representatives" of Camps A and B to explain the vision of Camps A and B regarding both developers and end users. Because the developer time/bloat issue is real, and the end user not being able to use Sage issue is real (on Windows, at the very least, and it was nearly the case on Mac). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/34eb570c-6686-4ebd-b425-2d51a1371e11n%40googlegroups.com.
