The question looks more like a Python syntax problem, rather than something involving the MariaDB Jupyter kernel.

On the other hand, we could answer StackOverflow questions involving MariaDB with a deployment of MariaDB Jupyter kernel, though this doesn't look like an MDBF on its own, rather a direction we could take.

True that this is a Python syntax problem. But the guy tries to do stuff that the Jupyter kernel would answer. We can in general do as you say, i.e. answer SO questions with an .ipynb, but this is clearly more specific than that, as the person already is on Jupyter.

As for "MDBF on its own", sure, this is bordering on tracking todos outside development. But we'd rather get this done, and open up the direction of showing Jupyter for MariaDB to those already interested – as opposed to developing stuff and then not telling the world about it.

The debate here is probably solved, but I'll leave this here as a clarification for future me trying to look this up.

It is a python syntax problem indeed and as Kaj said, the answer to these questions can be the MariaDB kernel because it enables users to write such things within a notebook. This MDBF should be part of MDBF-75 to be more accurate, but we should probably leave it as is because it seems like a good first action point for starting. From what I understand, Vicentiu's suggestion has a different nuance than what MDBF-75 says, i.e. provide answers to general MariaDB questions (not related at all to jupyter) that contain code snippets written in notebooks using the mariadb kernel (Example: "Hi user! You can display the name of the plugins currently loaded by the server using this statement: [link to github ipynb code snippet]")