We will open with a meeting on Monday morning to coordinate plans for the week, and follow a pattern of “stand-ups” each day at around 9:00, to communicate what we plan to work on, and what we have worked on. In the mornings there will be canapés; coffee and snacks will be available throughout the day.
This schedule is subject to change.
Please note that these GAP Days will be in-person only.
As always, GAP Days are a chance to meet people, form connections, get help with your problems, listen to some nice talks, and so on.
But in addition, we plan to focus on a few topics.
During these GAPDays we will focus on improving the visualisation of objects created in GAP. During the last two GAP Days, this topic came up in many discussions and now the goal is to get stuff done.
The plan is to create a visualisation package that other packages can use, instead of rolling their own visualisation code again and again.
Moreover, we intend to work with package maintainers on switching their package to use the new visualisation package.
Everyone can contribute to this project by
Regarding the last point, we have a list of candidate packages which will be discussed at the beginning.
Documentation on creating, maintaining and submitting GAP packages is spread over the reference manual, several pages of the GAP website and the example package. The current submission process is not transparent and leaves the requirements vague. We want to fix both: consolidate the documentation, and, as agreed by the GAP Council, route submissions to the open mailing list gap@gap-system.org, which anyone can subscribe to, with the requirements stated upfront.
First drafts exist as a basis for further work and discussion; see gap#5976 for the details.
Package authors, and anyone who has struggled to create or submit a package, can help by pointing out where the current documentation or process failed them, and by reviewing drafts.
As is common during GAP Days, Max will work towards the next “major” GAP release. If you’d like to help with that, you can find out how by talking to him at GAP Days. See also gap#6578.