seantwalsh → credited anoopjohn → .
anoopjohn → created an issue.
anoopjohn → created an issue.
This would be a great feature to have. Especially with projects that are under active development / enhancements / customization, there would be a lot of time savings for its developers.
Is that all you need to enforce namespacing and preventing collisions?
Don't we want to enforce module name prefix when we are loading permissions from the file
Also any reason whey we can't auto prefix the module name to the permission name when we load permissions from the file?
The patch works correctly on a 10.1.6 drupal site and stops showing warnings against views in the database.
Yes, he has been contributing in the queue as well. Thanks @Grevil. I have also set you up as a maintainer.
I have set up 'Anybody' as a maintainer on the project.
The project is maintained by the company and different developers working in the company are requested to look into these issues when they are allocated to work on this. However, I definitely do agree that the module could do with some 'love'. Hope @Anybody will be able to bring that to the table.
anoopjohn → created an issue.
anoopjohn → created an issue.
anoopjohn → created an issue.
Committed and pushed to dev branch
Wouldn't this be an easy update to show the date in the releases listing? If a patch is created, would it make it as a feature that goes live?
anoopjohn → made their first commit to this issue’s fork.
Ok. Let me get somebody on this and get a first cut done and get back.
This is absolutely fabulous.
Drupal agencies should rally behind this. All commercial Drupal organizations, who have the ability to send out press releases, should send out a press release saying this and also cover this in all of their newsletters going out and also on their websites.
Drupal can emerge as the platform of choice for all Government organizations across the world. That would be a huge win for the Drupal community.
Thanks specially to @Daniel for taking that first step and also putting in all the effort through the collection of data for the application. Thanks also to Tim Lehnen, Tim Doyle, Von Eaton, Kristin Romaine, Rachel Norfolk and all the anonymous contributors who have contributed towards the application process and also to Dries for supporting and taking this through formally. Thanks to Tim Lehnen and Tim Doyle for taking this through the formal application process both at DPGA and within DA.
We should use geolocation and show targeted local event ads - both camps and meetups - to all visitors on Drupal.org. If we can promote our local communities better and get better participation and support, we will be able to get more people to come become part of the larger Drupal ecosystem.
Sorry, missed this earlier. Happy to see this fixed. Thanks for pushing the fix @Gábor Hojtsy
nicxvan → credited anoopjohn → .