This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
Package healthcheck tool and tasks following from its reports #49
Labels
gapdays2020-spring
Issues and PRs that could be worked on during GAPDays2020
Comments
|
Now committed in 9deb525 - this is what it produces for GAP 4.9.1: |
|
This reminds of a number of tasks for GAP packages ranging from low-hanging fruits to large projects:
|
34 tasks
olexandr-konovalov
changed the title
|
For the record, this is the report for my GAP 4.9.3 installation: |
|
Update: this is what is coming in GAP 4.10: |
|
This is in GAP 4.10.1: |
35 tasks
|
This is the report for GAP 4.10.2 distribution: |
|
TODO: when sufficiently many packages will have a It may be useful to make this script more prominent, e.g. in some regression test, or a Jupyter notebook demo hosted on Binder - where we may have also outputs for containers for release branches to see how much the situation will improve in the next GAP release. Pinging @fingolfin to remind where this info could be found. |
|
Someone may also undertake a quest of standardisation of author names. We have now
|
|
As far as I can tell, the alternate "Chris Wensley" only appears in the 4.10.2 report. If the healthcheck tool has not changed, where is this coming from? |
|
@cdwensley the tool gathers information from PackageInfo.g files. in the GAP |
|
Hah - never thought of AutoDoc. I think it's best to change to "Chris Wensley" in all the Bangor packages, and to leave AutoDoc as it is. |
|
I can also change it in AutoDoc, no problem, just let me know :-) |
|
@fingolfin you may be interested to see what's collected for GAP 4.11 so far: |
|
@fingolfin actively helped to add Some of these 67 already have License in their source code repositories, waiting for their next release. For packages with this field, license info is displayed on their overview page on the GAP website, see. e.g. http://www.gap-system.org/Packages/io.html |
|
So, for me, the ideal way to display this would be on a dedicated website -- it could be in the Then there could be a subpage for each GAP release you run it on, and the top page would always link to the latest. Or just contain a list of all the subpages. Or whatever (easy to auto-generate either of that using Jekyll). And then the output could be formatted very mildly with Markdown and/or HTML Thoughts? |
|
I think of a different approach: a Jupyter notebook in the style of https://github.com/alex-konovalov/gap-teaching and https://github.com/gap-system/try-gap-in-jupyter and possibly using JupyterViz package to also produce some diagrams. |
|
@fingolfin I've added license report to the healthcheck script in #90 - this is for what's coming in GAP 4.11: "none" is from anupq, see gap-packages/anupq#34 |
ruthhoffmann
added
the
gapdays2020-spring
|
Update for GAP 4.11.0: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
An idea - it wouldn't be difficult to extract from the
GAPInforecord details about packages:etc.
The text was updated successfully, but these errors were encountered: