You may want to take a second look. This article does not prescribe one
governance model. It describes several governance models. After reading it,
a more informed discussion will be possible among those who care about
questions of governance.
Indeed, the article offers some useful terms.
On Wednesday, May 15, 2024 at 1:47:48 AM UTC-7 Travis Scrimshaw wrote:
On Tuesday, May 14, 2024 at 9:48:32 AM UTC+9 Matthias Koeppe wrote:
Perhaps a good reference:
https://www.redhat.com/en/blog/understanding-open-source-governance-models
That's not relevant to how we do things. You could
Or instead you have a whitelist for those that want it.
I think at least one of these changes (whitelist or blacklist) should just
be done in the same general way that these labels were introduced: no vote
and just do it. This really should have had a vote, or at least a
notification on
On Wednesday, June 12, 2024 at 2:17:43 AM UTC+9 Gareth Ma wrote:
In the documentation of `ProjectiveSpace` constructor, it says
> Projective spaces are not cached, i.e., there can be several with
> the same base ring and dimension (to facilitate gluing
> constructions).
However, that
In the documentation of `ProjectiveSpace` constructor, it says
> Projective spaces are not cached, i.e., there can be several with
> the same base ring and dimension (to facilitate gluing
> constructions).
However, that doesn't seem to be true, since (1) it's a `UniqueRepresentation`,
and (2)
Please Dima, let me stop this quoting business from your private messages.
Dima's response:
> It is perfectly avoidable, as I explained in more details, which you have
chosen not to copy here.
OK. Then which one of these quotes from you is the details explaining how
to install sage from
OK. Sage tarballs and the wheels are uploaded to our mirror sites. So wheel
packages end up in the mirror sites. This is what you say "mirroring PyPI".
You object to "mirroring PyPI", that is, wheel packages. For its
replacement, you propose to fetch wheels directly from PyPI by switching to
