Should we change the pace of TRAPI development?

[edeutsch]

There was a suggestion that we reduce the time spent on TRAPI between now and September so that everyone has more time to focus on crucial deployment issues. Please vote to indicate how you feel about the TRAPI pace so that we can decide how to proceed.

All regular team representatives/attendees of the TRAPI call are strongly requested to vote. All other Translator participants are welcome to vote.

Voting Scheme: Please only vote for one with the following emoji

Rocket ship - Maintain current pace, meet every two weeks, to keep working on existing backlog (negation, collections, etc.). The show should go on, we have much to do. Not much new work before June. But substantial development work in the June-Sep timeframe with TRAPI 1.5 implementation then planned for Oct-Dec.

Heart - Slow down current pace (meet once a month?) and work on only a few minor non-breaking changes and policy documentation (such as the publications encoding policy) for TRAPI 1.5 during the June-Sep timeframe with minimal implementation then planned for Oct-Dec.

Thumb down - Go on hiatus. Almost completely stop TRAPI meetings until after September. TRAPI is good and outstanding issues can wait and just aren't important at this point. Perhaps a few minimal things via GH and Slack as they come up. Pick things up again after the September release.

Eyes - Something else. Please post a suggestion.

Please vote!