This is a list of packages (from GAP 4.9.3 release) without known (to us) public repository. Please help to reduce it - by letting us know if the repository exists, of if you're a package author, by establishing it.
We offer help in migrating your package to GitHub, and we can prepare for you a repository with revisions history populated from the past releases of your package, which may be very useful to see when changes were introduced.
Packages with public repositories are getting more help from the GAP developers, because:
- they are more visible
- it's easy to submit changes via a pull request
- we can run tests for the development version of the package to check that changes in GAP do not break tests in the package.
- the author/maintainer keeps admin rights on the repository, and has the lead role in technical decisions, but if asked, several other GAP team members may publish a release and update the website for you.
Having a public repository on GitHub helps a lot to authors/maintainers who want to overlook to the package, but do not want to be involved in technicalities of publishing releases.
To run regular tests for packages with known public source code repositories, I've set up a Travis test at https://travis-ci.org/gap-packages/gap-docker-pkg-tests-master-devel. This service provides an opportunity to test changes that have been made in a GAP package but are not yet included into its official release, for their compatibility with the current development version of GAP and with other GAP packages prepared for the next GAP release. You can see the README https://github.com/gap-packages/gap-docker-pkg-tests-master-devel for further details.
This is a list of packages (from GAP 4.9.3 release) without known (to us) public repository. Please help to reduce it - by letting us know if the repository exists, of if you're a package author, by establishing it.
We offer help in migrating your package to GitHub, and we can prepare for you a repository with revisions history populated from the past releases of your package, which may be very useful to see when changes were introduced.
Packages with public repositories are getting more help from the GAP developers, because:
Having a public repository on GitHub helps a lot to authors/maintainers who want to overlook to the package, but do not want to be involved in technicalities of publishing releases.
To run regular tests for packages with known public source code repositories, I've set up a Travis test at https://travis-ci.org/gap-packages/gap-docker-pkg-tests-master-devel. This service provides an opportunity to test changes that have been made in a GAP package but are not yet included into its official release, for their compatibility with the current development version of GAP and with other GAP packages prepared for the next GAP release. You can see the README https://github.com/gap-packages/gap-docker-pkg-tests-master-devel for further details.