Am 13.03.2019 um 22:48 schrieb doctormo@...400...:
Names. New and Old are important.
Forecast party is an event where developers and users get together to discuss specific features.
The schedule depends on the timing of the event.
A regular schedule will include 10 minutes at the start for which problematic changes (things with code OR designs) can be shown and quickly voted on. Presenters will be highly encouraged to post an animated GIF to their flagged issue or merge request. Votes will be posted to the issue, issues without GIFs will not be discussed. Votes will be YES (change is good), NO (do not change) or RESEARCH (send the idea to proper UX testing, should be very rare).
The rest of the time will be taken by discussion a single idea or feature. The goal is to write up details into the forecast issue, including doing research on how other programs handle the design, who is interested or excited to work on the idea and what kind of release schedule the feature if implemented would fall into.
The specific idea will be announce ahead of time.
The goal of the Forecast party is to increase visibility of developments, to excite the developer community with new ideas and to plan out when an exciting idea is a good idea to land.
This is only a very rough outline of the process I'm personally thinking about.
Regards, Martin
Thanks! This makes it a lot easier to understand the general idea!
One specific question though on the following:
Presenters will be highly encouraged to post an animated GIF to their flagged issue or merge request.
How are presenters chosen? I believe by the "to forecast" label? If so, who assigns the label? The reporter? Any dev? The "forecast team"? Is the person who assigns the label also the person presenting the issue and making sure the necessary info (like the gif) is available?
Cheers Patrick