@tobiaseigen Sorry for the slow reply!
I’m not averse to making ‘Add Location’ a post toolbar option as a site setting. If you’re still keen on it, I’ll take a look at it. Personally, I think it doesn’t make sense though.
If the ‘Add Location’ button were in the options menu or anywhere in the composer editor button bar it would be
The only context-dependent control.
The only control not related to the content in the composer editor.
All the other controls related to markup in the composer editor and are concerned with the content of the first post.
The Add Locations control adds custom fields to a topic and is not associated with the first post of the topic. It is more akin to the category chooser or the tag chooser: both also relate to topic fields and have their own seperate inputs.
A category in which locations and events are enabled are typically categories dedicated to location and event specific topics, such as meetups for a particular community. Within that particular context I think it would be odd to hide the controls concerning the event time/date and location by default.
Adding locations and time/date is an expected action when creating the first post in such a context. If you’re creating a topic in a category specifically about locations, but don’t add a location in the first post why are you creating a topic?
I can see where you’re coming from here, but I think this would be changing the ‘product’ for the wrong reasons. I reckon the way to roll out Locations and or Events would be:
Test them out in a staging environment (this should be done with any plugin).
Create a dedicated category with restricted permissions and test them amongst staff.
Decrease the required trust level to access and / or post in the category to your preferred level in a timeline that suits.