Hi,
Reviewing a PR is a technical work, but voting on a disputed PR has a
political element. So I want to make a political remark concerning most of
the disputed PRs.
The modularization project (making pip-installation packages that contain
portions of the sage library) started years ago with
At some point the help menu in jupyter notebooks started pointing to
doc.sagemath.org instead of the locally built documentation. I wouldn't
mind having a configuration option not to build the documentation, in which
case, of course, this would be expected. However, because the documentation
I think I will quit the Sage project as soon as decisions on technical merits
of PRs and issues will start to be taken in a nakedly political way.
I am very strongly against any political overtones in these matters - it
reminds me all too well what's wrong is in academia in general.
Dima
On Tuesday, April 9, 2024 at 3:36:32 PM UTC-7 Kwankyu Lee wrote:
1. The directories *.ci, .devcontainer, .github/workflows*. These are
special directories that control the GitHub workflows that run for example
on pull requests and when release tags are pushed.
2. The files *tox.ini* and
Thanks!
--
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
On Wednesday, April 10, 2024 at 1:30:21 AM UTC+9 Denis wrote:
At some point the help menu in jupyter notebooks started pointing to
doc.sagemath.org instead of the locally built documentation. I wouldn't
mind having a configuration option not to build the documentation, in which
case, of
1. The directories *.ci, .devcontainer, .github/workflows*. These are
special directories that control the GitHub workflows that run for example
on pull requests and when release tags are pushed.
2. The files *tox.ini* and *build/bin/write-dockerfile.sh*. They contain
the infrastructure for
On Tuesday, April 9, 2024 at 3:28:27 PM UTC-7 Dima Pasechnik wrote:
How about moving them out of the main Sage tree into separate repos, which
can be accessed from the main tree as git submodules?
That does not work.
.github/workflows orchestrates what runs in the repo -- so it has to be in
Oops. Experimenting with this idea, I accidentally pushed a "crazy" commit
to "develop". Please revoke the commit ASAP!
I *mv*ed ".github" directory to "github" and made a symlink ".github ->
github" to see if this works, in my own repo. But I accidentally pushed to
sagemath/sage!
I
On 10 April 2024 00:51:33 CEST, Matthias Koeppe
wrote:
>On Tuesday, April 9, 2024 at 3:28:27 PM UTC-7 Dima Pasechnik wrote:
>
>How about moving them out of the main Sage tree into separate repos, which
>can be accessed from the main tree as git submodules?
>
>
>That does not work.
On Tuesday, April 9, 2024 at 4:20:56 PM UTC-7 Dima Pasechnik wrote:
have a CI/sage-distro repo [...] with all that .github/ etc stuff needed
for CI, including a part of build/ - and checkout sagelib as a submodule.
Also that does not work. Part of the .github/workflows is to run the CI on
the
We added python_build as an optional "pip" package (see
https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packaging#package-types
for
the terminology),
-
https://deploy-livedoc--sagemath.netlify.app/html/en/reference/spkg/python_build#spkg-python-build
(added
in 2022).
On Wednesday, April 10, 2024 at 7:51:34 AM UTC+9 Matthias Koeppe wrote:
On Tuesday, April 9, 2024 at 3:28:27 PM UTC-7 Dima Pasechnik wrote:
How about moving them out of the main Sage tree into separate repos, which
can be accessed from the main tree as git submodules?
That does not work.
How about redefining the meaning of "CI Fix" label:
1. We designate a person to be the CI manager.
2. For PRs pertaining to the designated directories and files, we add "CI
Fix" label
3. The CI manager has the right to merge PRs with "CI Fix" label to develop.
4. The old meaning of "CI Fix"
On 9 April 2024 23:11:59 CEST, Matthias Koeppe wrote:
>Dear Sage developers:
>I propose to consider the following governance change for a small part of
>the Sage repository:
>1. The directories *.ci, .devcontainer, .github/workflows*. These are
>special directories that control the GitHub
Because of
https://groups.google.com/g/sage-devel/c/dEa3i2Fn3ZY/m/gIWG6UpBAAAJ
currently github workflows stopped working.
Please revoke the commit ASAP!
Sorry for inconveniences!
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
I've force-pushed the original tip of the branch.
On Tuesday, April 9, 2024 at 5:03:50 PM UTC-7 Kwankyu Lee wrote:
> Because of
>
> https://groups.google.com/g/sage-devel/c/dEa3i2Fn3ZY/m/gIWG6UpBAAAJ
>
> currently github workflows stopped working.
>
> Please revoke the commit ASAP!
>
> Sorry for
Dear Sage developers:
I propose to consider the following governance change for a small part of
the Sage repository:
1. The directories *.ci, .devcontainer, .github/workflows*. These are
special directories that control the GitHub workflows that run for example
on pull requests and when release
18 matches
Mail list logo
