I would rather keep the init: namespace and and the following commands to it:

• init:front-controller for creating front controllers in your web directory (I will send a PR for this)
• init:container-extension for bootstrapping a DIC extension
• init:core-bootstrap what's currently in the sandbox's 'build_bootstrap.php` script

I think it makes sense to group all code-generation commands under a common namespace to raise their visibility to the beginning user.

Yeah, I thought of that too, but it's semantically incorrect WRT the other commands (as said in symfony/symfony#117). And if we add other stuff to bundle, like bundle:enable for example. Then you'd have init:bundle and bundle:enable, which would suck. I agree with you for now but I think grouping by resource type is more future-proof.

I didn't realize this was the docs repo :)

i guess this can be closed now since symfony/symfony#117 was closed