I would suggest considering the following topics:
- CD/CI (Continuous Development / Continuous Integration) of ZAP and extensions (how it would be done after move to Github - through Travis? any pieces that are missing and need to be added? What are the priorities, sub-projects, and who will be working on them?)
- Contributions and Code Review process and guidelines after move to GitHub. It would be great to have CONTRIBUTING.md file in the root directory (as described in https://github.com/blog/1184-contributing-guidelines
) with the main information for active and prospective contributors (how to submit a contribution, any style guidelines (even if just "follow the style of the surrounding code"), how to verify that you didn't break the build, requirements for the commit messages and the history style (like "rebase away the non-significant commits like 'ouch... yet another typo fixed'"), etc.
- Commits and ownership - I see that there are currently 49 committers for the project. Will all those 49 people get commit rights for the zaproxy github repository? Or should there be a different system where a few project members would be designated as owners and committers (possibly for specific areas of code and project), and rest of contributors would submit their change requests in some form (like Pull Requests) which after review and approval would be merged in by the owners. This could help the designated owners to maintain and promote consistent quality standards (overall project direction, system architecture, coding style, testability and test coverage, etc.)
I'll be able to attend only a later portion of the summit as I arrive to Amsterdam midd-day but I'm looking forward to meeting you guys and learning more about the zaproxy project and development! I will also present a talk about security scanning on Friday http://sched.co/375P
("Finding Bad Needles on a Worldwide Scale") and hope to see many of you there! My modest contributions to the ZAP project so far consist of opening recently a few issues with "XSS" in the subject found in the course of doing research for that talk.