Option 3: move to GitLab issues

Issue: One issue may not belong to multiple projects, and we need to create many issue-only repos. It also lacks a Kanban

@Demian Thank you! You're the second person who discussed about my main points! Comments are always welcomed!

To be honest, the another reason that I'm glad to see @EvanYou here is because he is the first person who reacted with my main points. I've read the IRC meeting logs of #wikimedia-office on Feb 22, and no one reacted to my comments. It seems like the decision to use Vue.js has already been made.

Hi @EvanYou I'm actually grateful to see you here! Since the framework authors rarely participate in discussions on which framework to use.

In T241180#5851832, @Michael wrote:

That sounds intriguing, but unfortunately, it uses template literals which are not available in IE 11. So since IE11 still considered a modern browser that gets the highest level of support from MediaWiki, we would still need a build step to ensure that all features are working there as well.

22:43:28 <Krinkle> #info It is required for our scale and range (core/extensions, multiple orgs/teams, community gadgets) that the framework strictly follow a no-breaking-change rule other than removal of deprecated functionality after replacements are added in a previous release.

Update (2020-02-27T03:53+0900): "Vue is Evan You's one-person project" → "Vue core is Evan You's one-person project"