The Joomla core as well as the core extensions between them have lots of configuration settings. If you add 3rd Party extensions to the mix, these run into hundreds. If the Joomla core provided an import/export options setting as 'infrastructure' to any extension using Joomla's way of storing options, i think it will benefit a lot of Site builders and admins. 

If you have ever uninstalled an extension for whatever reason and needed to install it again, you will know the pain of having to reconfigure the extension. Also if you are a site builder who builds sites regularly, then you will have your own way in which you setup Joomla and its various extensions. If you had a way to store your pet way of doing things, you will get a head start when you start setting up a new site by importing your stored settings. 

What do you think about this as a new feature for Joomla ? Do you think its worth the time to code it in ? Do comment and let me know your feedback ! 

Joomla Git RFC : 

Joomla is extended by thousands of extensions and each of them manage various notifications to users in their own way. This means that there is no easy way for a Site Administrator to manage notifications centrally. It also means that 'end users' have no way to manage these centrally . This proposal aims to set a standard way to declare notifications and handle them in a unified way without loosing any of the flexibility that extension developers want in designing their notifications. 

In the past, I have written about how I believe Joomla to be more of a base for simple to complex 'End User focused applications'.

On the Joomla level, we need to be very flexible and create an infrastructure that 'enables' creation of systems for more specific use cases. This I believe is possible via distributions and one of the important things that are needed to be able to create a good distribution is a flexible admin template. This will allow distribution managers to easily tweak and brand a template as required and have a better UX. I've already posted a RFC for this on Github. I'm documenting it here as well to keep things in one place for me !