-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modules Folder Clean-Up #198
Comments
I'm pretty sure you'l need to rebuild the registry after you do that. |
@willykaram do it!!! |
If people still think we should do this, then I can do so late tonight. My concern is that it's going to make quite a few updates to everyone's branches, and we should ensure that everyone is on board with this. I will implement this on a separate branch/multidev and test thoroughly before implementing on live. I think that this is pretty much the last day when we can do this. After today, I'd rather not undertake this change as it's too close to the camp. FWIW, at this point, I think we could just leave it as is until after the camp. As this is really a behind the scenes change that we're making for best practices purposes, but that doesn't have any UX or other benefit for camp attendees. |
Don't do this. It's really not necessary. Leave the modules folder as it is. We can get to this after the camp. |
I agree with Eric's comment right now. Unless anyone strongly objects, let's defer on this until after the camp. |
I just notices that our sites/all/modules folder is a bit jumbled. We don't have a separate folder for /contrib vs/custom modules. I would like to fix that quickly in the course of some other work. Does anyone object?
The text was updated successfully, but these errors were encountered: