Closed triska closed 4 years ago
@triska This is a very good initiative (next to all the other formidable work you are contributing)!
The dispersion over multiple Github repos may be a good thing: a user can follow specific repos that s/he is interested in an then all the issues are enumerated under https://github.com/issues (once logged in).
Here are some of the concrete things that people who want to contribute can do:
When a whole bunch of issues around a unified topic accrue it may be beneficial to group them together in a Github wiki. I've done this for improvements to the Semweb API and the package infrastructure.
Thank you Wouter for the encouragement!
I have updated my comment with a link to an overview page that displays many filed issues, updated twice a day.
@triska Nice!
I believe this overview page should be integrated into plweb so that we can easily see the state of SWI issues in one place.
I'll integrate @triska 's HTML view into plweb later (https://github.com/triska/swissues).
Many important and concrete issues and pull requests are constantly being filed.
Due to the dispersed nature of the SWI packages and the project management infrastructure of Github, some of them linger longer than necessary and are in some cases even inadvertently overlooked.
I have created an overview page for filed issues that are related to SWI-Prolog and its packages. At least the first page of each repository is displayed. This page is updated twice a day and is generated with swissues.
All users who would like to contribute to SWI-Prolog are highly encouraged to systematically go through the already reported concrete issues. See if you can reproduce and fix any of them. If the issue is no longer reproducible, ask for it to be closed. Also, go through the list of pull requests for each repository and see if there are any that warrant more attention.
All reported issues are blocking or impeding some users in their work on great applications, and fixing these issues will benefit many users at once.