We use git already, the directory is merely a directory of „entries“ linking to the respective plugin repo
We use this for two reasons:
- It is an official list and allows us to „control“ plugins
- It allows us later to produce an update mech that can push updates to installs
- we may later also accept plugins not stored on git but other providers
Unfortunately i don’t think at this point we can hide it again - we blog posted, we announced, we talked.
Taking it away now is going to be a classic „they aren’t ready“ move and it’s like shooting our own foot.
It’ll take 15 hours to scan each plugin by my calculations.
Done that, we can take down what’s inappropriate and contact + maybe take down unclear ones
Then at least the repo is clean.
So within one week, 2 or 3 people can fix that.
@ozfiddler each error if still experienced has to be reported and fixed with urgency.
We can’t afford error 500 for some weeks.
However since we did indeed use laravel and I personally for example don’t even know where to start when it comes to laravel ….I agree we should have done that with what we all know and that’s cp/php (like the doc site). At least any dev could then debug and even commit things.
But that train has departed. Too late unless we re_start.
Im very much in favour of only using our tools and not using some sophistication that only few do understand, but taking down/hiding the repo at this point is going to hurt us I think more than the work we need to fix it all.
If we hide it it’s just going to take longer because no one will actually think about it anymore
So - let’s gather the issues, list them, make git issues for our laravel folks to fix what is to fix in laravel and I’d be happy to receive help from one or 2 folks who do understand how to install and use wpcs + do know our brand policies and the directory guidelines to scan the remaining (ca 75) plugins.
I already started with that but had to stop as other things came up.
Since we now have an active plugin review - later this step won’t be necessary anymore
Please inbox me if you can help with scanning of code, brand guidelines and directory requirements
Let’s list actual laravel/directory issues each in one new ticket on GitHub? Does that sound good?
If we all pack it tgt by end of next week this all is just a bad memory