Thanks to Gareth Ma for pointing out that I got some links wrong. I'll try again:
1. Please vote +1 on https://github.com/sagemath/sage/pull/36561 and https://github.com/sagemath/sage/pull/36951 ("Move metadata from setup.cfg to pyproject.toml"). Straightforward PRs, held back since November/December by hostile demands that have nothing to do with our standards of review. 2. Please vote -1 on https://github.com/sagemath/sage/pull/37387 and https://github.com/sagemath/sage/pull/37740 (documentation preview notifications). I've got some more requests: 3. Please vote +1 on https://github.com/sagemath/sage/pull/37351 ("update Linux platforms"). An update of our CI, which among other things will make workflows such as Build&Test and Docbuild faster. 4. Please vote -1 on https://github.com/sagemath/sage/pull/36580, https://github.com/sagemath/sage/pull/36753, and https://github.com/sagemath/sage/pull/37138, which attempt to obstruct the modularization project and the mechanism for the distribution on PyPI. 5. Please vote +1 on https://github.com/sagemath/sage/pull/36869, for completing the support for Python 3.12. 6. Please vote -1 on https://github.com/sagemath/sage/pull/36725, https://github.com/sagemath/sage/pull/36610, which attempt to sabotage the portability testing infrastructure that I built for Sage. On Monday, April 8, 2024 at 11:19:03 AM UTC-7 Matthias Koeppe wrote: > Dear Sage developers, > I need your help on these PRs. Please vote. > > Special expertise is not required for voting. You will find the comments > in these PRs instructive -- also as illustration for a (long overdue) > *discussion > about governance and review standards* in the Sage project. > > *1. Please vote +1 on both https://github.com/sagemath/sage/pull/36561 > <https://github.com/sagemath/sage/pull/36561> and > https://github.com/sagemath/sage/pull/37138 > <https://github.com/sagemath/sage/pull/37138>* ("Move metadata from > setup.cfg to pyproject.toml"). > These are trivial "chore" PRs. They update metadata of our > pip-installable packages "sage-conf" and "sagemath-standard" to the latest > format. > These straightforward and appropriately focused PRs have been held back by > months by *bundling the review of the PRs with unrelated issues.* I call > this "artificial friction"; see the discussion in the PRs. To help overcome > this artificial friction, please vote. > > *2. Please vote -1 on both https://github.com/sagemath/sage/pull/37387 > <https://github.com/sagemath/sage/pull/37387> and > https://github.com/sagemath/sage/pull/36951 > <https://github.com/sagemath/sage/pull/36951>. *These PRs are about a > Developer Experience issue, namely the workflow on GitHub that notifies > developers when the HTML documentation is ready for inspection by PR author > and reviewers. Now a few developers have made it known that they are > annoyed by the notifications (whether received by email or the notification > tool on the GitHub website), and the PRs seek to turn off most or all of > the notifications. That *these notifications enable a productive > notification-driven development style, and that the notifications serve the > project's need for quality control on the formatted documentation*, has > not received meaningful consideration. > What's happening on these PRs is exactly what I had cautioned about in > https://github.com/sagemath/sage/pull/36726#issuecomment-1820148873 > regarding the (then-proposed, now established) system of majority votes as > a conflict resolution mechanism for PRs. To balance it, we need the > involvement of the larger developer community: please vote. > > Matthias > > -- 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/63a6733b-16a1-4da9-9aaf-3dde24ab1f3dn%40googlegroups.com.
