PREFACE:
29 Participants from 10 organizations
Funds (registrations + sponsors) paid for:
- Food, proceedings, swag
- Future workshop budget cushioning
- Build server
Sponsors: Centaur Technology and Oracle
Here is a list of possible topics. (Please contact the co-chairs
(Shilpi Goel and Matt Kaufmann) to suggest
additional topics.)
- Where will the next ACL2 Workshop be held, and who will co-chair
it?
- Should we continue calling for 2-page extended
abstracts, given issues with arXiv?
- Are there any suggestions for improving the workshops, in
particular based on this year's workshop?
- How many participants this year would not have come if ACL2 had
been by itself, rather than co-located with FMCAD?
- Are there any infrastructures issues to discuss? In particular,
how might we deal with elimination of commit emails by GitHub?
How might we improve the
leeroy.defthm.com testing
mechanism, in particular to avoid certification failures due to the
need to rebuild certain books after ACL2 changes?
- Do we like having publications at the workshop? Does our community
benefit from written papers? What other activities and presentations
might be good at future workshops?
- What can be done so that more existing ACL2 books are contributed
to the Community Books at GitHub?
- Do we want printed proceedings in future workshops? Or instead, a
memory stick? Is web access sufficient?
- Should IRC be moved to slack or ...?
- Who might like to contribute to the build server?