Board Thread:Wiki Discussion/@comment-26402117-20190305192154/@comment-26402117-20190307034951

wait for some time (~year), before going to the next step In terms of strategy & timescale, this is what I'd do:
 * 1) March: petition community on basis of user confusion
 * 2) April?: if successful, run bot job to:
 * 3) repopulate /code.js in documentation articles
 * 4) (templates are switched at this point)
 * 5) remove any defaults that fit our naming convention
 * 6) May?: start second thread and let community discuss the pull request
 * 7) May/June?: handover to Engineering for ResourceLoader & wikibits migration fixes (with robust QA & unit tests, as standard)

It's very likely that other Engineering work will get in the way if the community waits a full year - contexts change, and the fandom.com migration is the current focus.

Is there explicit benefit to waiting a very long time? (I feel PI & Scribunto defaults aren't a challenge to change. The full process just needs two bot jobs, a couple months for full community engagement, and delegation to Engineering after.)