I'm about to ask a very loaded and very blunt question, primarily directed toward project leadership but all feedback is welcome. Is there interest (as in should this be a roadmap item for a short term release schedule) in having a "proper" tool suite and API in core to help facilitate privacy (GDPR) related items? In essence this means having some high level APIs in the Joomla\CMS\Privacy namespace and a com_privacy at a minimum with some baseline functionality and a way for site owners to interface with said API.
Why does core need this functionality? For the most part, core itself works with a very limited set of data that might fall under the scope of privacy related laws such as GDPR, however it acts as the framework/facilitator for thousands of extensions to perform actions which do fall under that scope, and I do believe that we as that framework owe it to our userbase to at a minimum do the due diligence to either provide a set of tools to facilitate these types of activities in a consistent manner or to tell users that the core project does not feel it is its responsibility to offer these tools and they should be provided by the ecosystem.
Now, here is my offer if this is indeed something the project will accept and support with resources (that means I need you, casual reader, to assist with this effort; I will not do the entire project myself). Internally a discussion started about having a 3.9 release with privacy/GDPR related functionality added to core based on the many PRs that have already been opened and I offered to coordinate that release; that offer still stands. As it relates to this effort, I will offer to team lead, project manage, or whatever you want to call it, to steer the efforts in a coordinated manner so that we can have a releasable product in a reasonable timeframe (clearly we're already a few months too late to starting this work, so anyone expecting a finished product before May 25 has unrealistic expectations unless you're going to pay me full time to work on this, just being blunt about it).
In return, as I hinted at above, I need commitments from interested parties in working on this tool suite. Coders to help write the code, testers to help make sure we aren't building an unusable mess, writers to help document all the things, etc. etc. I will not take this project on by myself, I already do way too much with too little time and making my time offer here is stretching my available resources for other project tasks.
If agreed upon in principle, we can have a space set up relatively quickly and I will outline specifics of what I would consider the MVP for this effort to be at that time.
I'm about to ask a very loaded and very blunt question, primarily directed toward project leadership but all feedback is welcome. Is there interest (as in should this be a roadmap item for a short term release schedule) in having a "proper" tool suite and API in core to help facilitate privacy (GDPR) related items? In essence this means having some high level APIs in the
Joomla\CMS\Privacynamespace and acom_privacyat a minimum with some baseline functionality and a way for site owners to interface with said API.Why does core need this functionality? For the most part, core itself works with a very limited set of data that might fall under the scope of privacy related laws such as GDPR, however it acts as the framework/facilitator for thousands of extensions to perform actions which do fall under that scope, and I do believe that we as that framework owe it to our userbase to at a minimum do the due diligence to either provide a set of tools to facilitate these types of activities in a consistent manner or to tell users that the core project does not feel it is its responsibility to offer these tools and they should be provided by the ecosystem.
Now, here is my offer if this is indeed something the project will accept and support with resources (that means I need you, casual reader, to assist with this effort; I will not do the entire project myself). Internally a discussion started about having a 3.9 release with privacy/GDPR related functionality added to core based on the many PRs that have already been opened and I offered to coordinate that release; that offer still stands. As it relates to this effort, I will offer to team lead, project manage, or whatever you want to call it, to steer the efforts in a coordinated manner so that we can have a releasable product in a reasonable timeframe (clearly we're already a few months too late to starting this work, so anyone expecting a finished product before May 25 has unrealistic expectations unless you're going to pay me full time to work on this, just being blunt about it).
In return, as I hinted at above, I need commitments from interested parties in working on this tool suite. Coders to help write the code, testers to help make sure we aren't building an unusable mess, writers to help document all the things, etc. etc. I will not take this project on by myself, I already do way too much with too little time and making my time offer here is stretching my available resources for other project tasks.
If agreed upon in principle, we can have a space set up relatively quickly and I will outline specifics of what I would consider the MVP for this effort to be at that time.