Thread:Project talk:WikiProject Extensions/template - extension code in wiki/reply

I can appreciate your concern. However, I hope that we do continue to place them, even during the migration.

Perhaps if for no other reason than the template is as a warning for system administrators as much as a request for extension developers. Also, you can now request access to git for your extensions, so there is a new solution. Documentation, including that template, is in the process of being updated. There are a couple weeks of overlapping messages during this transition while everything is being finalized. I'll admit, that's annoying.

Once the git migration is completed, there will be an effort to move any functional extensions that have code in wiki onto the git repository. It's better to house the code on the WMF tool designed to house code - if for no other reason than it makes it easier for folks to flag issues with it and tweak it. Whereas many folks are not comfortable doing that with code placed within wiki, and there's generally no awareness of the status of those extensions as again, they're outside the code repository. A part of assessing if an extension is "functional" will include a compatibility check and an effort to look into function overlap, etc. Some of this is being done now as a part of the same drive that's placing more of these templates. Extensions that are incompatible, not being maintained and do not show signs of active use (comments in user talk about its incompatibility, etc.) are being archived.

Regarding holding off, I'm hoping we don't hold off. We'd like to have all of these extensions tagged in time for some possible hackathons and other activities that could help address some of this workload. Again, I recognize during that time it's an inconvenience. However, it's volunteers reviewing hundreds of extension pages - so that effort alone won't be completed until after the git migration is completed.

Essentially, why wait until tomorrow what we can do and prepare for today?