Move certain Issues to Discussions

[tbreuss]

I'm wondering whether it would make sense to move certain GitHub Issues to GitHub Discussions.

Why?

1. Although there are currently only three discussions, we are already using them.

2. Some issues are actually pure discussions, which, however, would be better placed under GitHub Discussions.

3. We could clean up open issues.

4. Other projects also use GitHub Discussions (i.e. Hyperapp, Bootstrap, Deployer, Doctrine ORM, and more).

5. There is the possibility to move GitHub Issues to GitHub Discussions. See: How to move existing issues into Discussions community/community#2952

6. Discussions are centralized, votable, better organized, searchable, and trackable.

7. Internally discussions are the same as issues.

8. Discussions can be marked as answered.

If thats's okay with you, we could plan the migration something like this.

• Test whether moving GitHub Issues to GitHub Discussions really works
• Identify GitHub Issues that should be moved to GitHub Discussions
• Move identified GitHub Issues to GitHub Discussions
• Start discussing certain topics at GitHub Discussions

What do you think?

[tbreuss]

As a newbie it is not easy to identify issues, that could be moved to GH Discussions. So, I would do it in two steps.

1) Move open GH Issues labeled with "Type: Question" (9 Issues)

• #2665
• When utilizing shared mithril components imported from another node package, mithril render and routing do not work as expected #2662
• Possible to render fragment 'null' instead of '[' ? #2640
• Mithril not respecting base href #2377
• Is MITHRIL.js fit fot mobile development? have beachmark? #2204
• Can used next.js to server render Mithirl.js #2196
• Latest Mithril with latest Meteor demo request #1980
• Suggestion: allow Hyperscript selectors to be used in the diffing algorithm #1976
• Route query params change does not trigger remount #1757

2) Move closed GH Issues labeled with "Type: Question" (155 Issues)

Since there are many good answers in closed issues I would try to:

• identify closed issues with relevant information and helpful answers
• re-open those issues and move them to discussions
• mark the best answer as "answered"

Examples for closed issues with relevant answers:

• how to import the Vnode<any, any> type? #2658
• using key in attrs causes onupdate. Expected oninit #2650
• Recommendation for handling large (SVG) documents #2606
• How to run code after a RouteResolver has finished rendering? #2571
• How to set body class? #2044
• How to re-enter a route?  #1954

[orbitbot]

Excellent initiative, sorry for not being able to return to this earlier.

I took a slightly different approach, mainly reviewing the open issues, and in an initial pass didn't consider if any of the open issues should be closed or further processed. There is certainly opportunity to help with tracking ideas and perhaps closing outdated issues, and I assume some should be possible to mark as fixed with an upcoming release.

At the time of writing, the open issues contained the following issues that could be better served by being converted to Github Discussions posts;

• Reasons we use Mithril #1026
• Website design #1599
• onremove and key change #1713
• Docs/simple app: experience could be better #1717
• Mithril Realworld Example App #1823
• Mithril's copy should be emotional #1860
• [Discussion] Mithril Community Blog - ideas and implementation details #2101
• Can used next.js to server render Mithirl.js #2196
• Is MITHRIL.js fit fot mobile development? have beachmark? #2204
• Official component/utility library #2284
• Should Mithril vnodes be fully JSON-compatible? #2356
• Why should m.request and m.jsonp be split? #2367
• Mithril as UI Lib #2404
• Stream Extras #2410
• Add quote about the guiding philosophy of Mithril #2429

The highlighted issues seem to have been posted in a question format before Github Discussions existed, or have ended up more evolving into discussions rather than something (urgent enough) to be acted upon.

[orbitbot]

• Test whether moving GitHub Issues to GitHub Discussions really works

This has been done earlier, and works roughly as expected. I'd personally suggest rather to iterate on the specific issues to be turned into discussions rather than trying to be complete, as the latter tends to lead to nothing changing in an OS environment.

[orbitbot]

Moved an initial batch of the issues listed above. Seems like some are listed on GH projects, which doesn't immediately seem to be supported, so we'll see where that ends up.

Re: the list that @tbreuss provided, on a surface level (ie. title) some of them seem to be actual bugs that should probably not be transferred before a possible fix.