The Social Geolocation module extends the Open Social distribution to add geolocation functionality for Groups, Events and Users. Additionally it provides a submodule that can display a map of the events that have been given a location.
This feature is released as a separate module because we recognize that not all users of the Open Social distribution may require this functionality. The module takes care of setting up the required configuration for Open Social's default content types and uses the geolocation module to perform the actual geocoding. It also integrates with search for both SQL and SOLR back-ends.
My application for the IMCE Plupload module was approved 7 years ago, but I seem not to have been given the vetted role.
Project link
https://www.drupal.org/project/social_geolocation/
Git instructions
git clone --branch 8.x-1.x https://git.drupalcode.org/project/social_geolocation.git
PAReview checklist
https://pareview.sh/pareview/https-git.drupal.org-project-social_geoloca...
Comments
Comment #2
kingdutchSome more work on our side is needed to satisfy PA Review :)
Comment #3
avpadernoComment #4
kingdutchFixed issues raised by PAReview. DrupalPractice has some warnings that can be safely ignored:
Comment #5
vuilThank you for your contribution!
- I can not understand why you have the following (not-present) modules as dependencies in
.info.ymlfile?Please replace them with:
- Please add the following modules in your
.info.ymlfile (some of them will be also incomposer.json):Comment #6
kingdutchHi vuil,
Thanks for your review.
We have on purpose removed the namespace from the dependencies. You can see the change here: https://github.com/goalgorilla/social_geolocation/commit/04ef81d2fb2490a...
Namespacing modules in an installation profile causes issues. Drupal.org will try to create a composer.json module that downloads the modules directly. However, there is no
drupal/social_eventmodule. Drupal does not expose modules from an installation profile as separate composer packages. I've already filed a detailed issue about this here: #3099771: Don't expose submodules in Drupal's packagist at allThe
geocoderandsearch_api_locationmoduels should not be added to the .info.yml file. They're not actually dependencies of the current version of the module. They are still in the composer.json to ensure that sites that upgraded from an earlier internal version didn't suddenly break. I've created a follow-up here: #3100305: Remove geocoder and search_api_location dependencies and update README.mdThe group and profile module dependencies are taken care of through
social_profileandsocial_group.I'm moving this back to needs review, I hope I've addressed your concerns.
Comment #7
klausiThanks for your contribution!
Did not see any security issues, looks good to me!
Comment #8
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.