Skip to content

Minutes

Jump to bottom
Romain Deltour edited this page Oct 10, 2018 · 14 revisions

EpubCheck developers meetings

2018-09-08

Participants: Avneesh, Daniel, Romain.

Topic: work plan until December

  1. set up infrastructure.
  • Organize the issues + review the labelling strategy
  • Move the repository to W3C.
  • Do we need to rename the Java namespaces (legacy adobe and IDPF names). This can be handled in phase 2 during the code clean up.
  • Infrastructure work can start Before TPAC
  1. Maintenance release for existing fixes (v4.10)
  • Deadline is November.
  1. EPUBCheck updated to EPUB 3.2 - alpha release.
  • In December or early January.

Topic: development “infrastructure”

To help us triage GitHub issues, create "epics" meta-issues (group related issues, identify dependencies / development critical path, manage separate Pull Requests, etc.), and ultimately assign tasks / action items within a timeline, using:

...but there are also more powerful alternatives:

Romain knows Huboard; Daniel knows ZenHub; We all know Waffle, Trello, GitHub Projects.

Proposal (to be discussed further): exclude Trello (too disconnected from GitHub, more suitable for higher-level project management), exclude Waffle (there are slightly better alternatives than this simple GitHub "overlay"), exclude GitHub Projects (limited feature-set), consider Huboard and Zenhub (we need to verify accessibility). ACTION ITEM: Avneesh to check screen reader accessibility of the current Github Projects (Avneesh already uses GitHub issue tracker label-based filtering, etc.) ACTION ITEM: Romain to explore ZenHub and setup a test instance

We discussed the human resources needed to achieve the EPUB 3.2 milestone. ACTION ITEM: Romain should get in touch with the team and kick-off the development.

Topic: communication

Communication channels for development team:

  • the development team can use the #epubcheck Slack channel (in the daisy-dev orgnization)
    • ad-hoc audio calls when necessary
  • setup a weekly timeframe for developers chat
  • the discussions will be summarized and published on a wiki page, under the heading of the date of call/interaction.

Communication call with steering committee:

  • schedule a monthly audio call on Zoom.
  • Create EPUBCheck twitter account? (requires approval of Luc/Tzviya). Its objective is to keep the public updated about the technical developments.
  • We should formulate plan for providing some light weight updates that can be used by Luc/Tzviya for marketing. It may be posted on a blog or news, social media page etc.

ACTION ITEM: Avneesh to get in touch with Luc and Tzviya to invoke discussions on these topics.

Clone this wiki locally