While I agree with this shouldnt this be for 3.5 in line with the Roadmap

On 15 October 2014 11:52, Dimitri Grammatiko notifications@github.com
wrote:

This is obsolete and can be safely removed

###P3P is UNSUPPORTED since 2007
More on that here: http://en.wikipedia.org/wiki/P3P
Enabling this plugin will get a header like:
[image: screenshot 2014-10-15 13 40 10]
https://cloud.githubusercontent.com/assets/3889375/4644260/ab0951ee-5458-11e4-83b1-4557629706fb.png

When the normal is:
[image: screenshot 2014-10-15 13 40 38]
https://cloud.githubusercontent.com/assets/3889375/4644266/b4a6f602-5458-11e4-87fd-35f81d9b7f40.png

The problem is that this extra response is ONLY supported by IE6. So no
real use for all of us. We can keep it in Extensions directory if somebody

needs it…

You can merge this Pull Request by running

git pull https://github.com/dgt41/joomla-cms kill_p3p

Or view, comment on, or merge it at:

#4678
Commit Summary

• kill it

File Changes

• D plugins/system/p3p/index.html https://github.com/joomla/joomla-cms/pull/4678/files#diff-0 (1)
• D plugins/system/p3p/p3p.php https://github.com/joomla/joomla-cms/pull/4678/files#diff-1 (41)
• D plugins/system/p3p/p3p.xml https://github.com/joomla/joomla-cms/pull/4678/files#diff-2 (32)

Patch Links:

• https://github.com/joomla/joomla-cms/pull/4678.patch
• https://github.com/joomla/joomla-cms/pull/4678.diff

—
Reply to this email directly or view it on GitHub
#4678.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

I would say the sooner the better ????

its hardly getting in anyones way right now nor is it causing any support
issues. so I say stick to the roadmap

On 15 October 2014 12:23, Dimitri Grammatiko notifications@github.com
wrote:

I would say the sooner the better ????

—
Reply to this email directly or view it on GitHub
#4678 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

According to our strategy we can only remove it with 4.0.

We could of course pull it out similar to the weblinks extension, but why would we want to do that and invest time into it, setting up a repo and everything?

Imho, just deprecate the thing and let us remove it with 4.0.
Maybe make the plugin disabled by default on new installations but leave it as is for existing ones.

As long as there is no harm done by having these headers, I don't see a reason to remove or disable it now.

Ah yeah I forgot that the strategy doesn’t allow removal in the current release.
@Bakual the option to set up a repo for something obsolete I think is unacceptable. Let’s not do that!
I hoped that the board could make an exception to the rule, as this one is more than obvious that is totally garbage.
Joomla! say’s IE8 and newer and still render IE6 compatible headers?
Doesn’t really makes any sense...

I hoped that the board could make an exception to the rule

I'm not opposed to make exceptions if it's important. But to me it looks like this just doesn't matter at all if it's present or not. So following the rules does no harm at all and I prefer to properly deprecate it then.

I agree with @Bakual. While I do very much appreciate wanting to remove likely unused code, we should leave it in until 4.0, and the work involved with moving it to it's own repo seems to outweigh the benefit.

I thought it will be no brainer this one.
The work on this was postponed 7 years ago from W3C, and removing it will not harm the project at all.
The strategy is better suited for code or assets that have some dependancy or might have some undesired consequences. I really don’t see that happening here, so deprecating something abandoned almost a decade ago is kinda funny…

See #4688