[Meta] Tasks to deprecate RDF

Added #3243121: Remove RDF module from the Standard profile under this but not sure where it comes in the list of tasks; if we are deprecating this in 9.4.x then we shouldn't be installing it under Standard.

We should do that one as a first step.

The contrib project RDF already exists, but is abandoned: https://www.drupal.org/project/rdf

I can't find where anyone has yet volunteered to maintain RDF in contrib. When this is done they will need to apply to become maintainer of the abandoned contrib before we can create a release.

@longwave if you don't find anyone when the time comes I don't mind look after the module. Least making sure deprecation is fixed, tickets answered, etc. I maintain a few modules currently.

Will say I would like to clear all those D6, D7 tickets out. Not sure worth starting a new project like rdf_d8?

As noted in slack, i can help setting up contrib and make it work. Had some experience doing that in the last few moths.

I opened #3303278: Decouple NodeDisplayConfigurableTest from RDF module as that test is quite tightly coupled to RDF and needs some detailed surgery to remove it while keeping the test intact.

Parent is closed, reparenting to #3273976: [Meta] Tasks to remove RDF from core and move to contrib

Added #3303435: Move RDF-related optional config to RDF module

Added #3303453: Remove rdf from \Drupal\Tests\system\Functional\Common\NoJavaScriptAnonymousTest

So did you need me to take over the rdf module? If so what next steps should I take

@smustgrave I think at the moment you're the only volunteer, so that sounds great and very necessary!

The first step is to request maintainership of the RDF module https://www.drupal.org/project/rdf following the procedure on https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... There is usually a two week grace period before the initial issue goes to the Drupal.org project ownership queue. I'm not sure if that's necessary in this case since we're talking about a Drupal 6 project that was moved into core and being moved back out again, but also not entirely sure who to ask about expediting it either. However the quicker the issue is in the RDF queue the better so the process is started, there's still blockers in the core queue to get done in the meantime anyway.

The next step (although it could probably happen in parallel in an MR) would be an 1.0.x branch of the contrib module based on a subtree split from core - ideally once all the core blockers like tests being moved around have been committed so it only has to be done once. That way the contrib module matches the final state of the core version with the same history. Then once there's an active maintainer and the MR is committed, after a bit of manual testing, a stable release. Once all that is done, the removal/deprecation patches can be committed and everything is done.

The 6.x issues that are open against the contrib module should probably all be marked closed (outdated).

Opened up https://www.drupal.org/project/rdf/issues/3304913

Closed out all the D6 issues but this one https://www.drupal.org/project/rdf/issues/470750 if someone could take a look? There's no comment field, meta update or anything appearing for me.

Once granted access I'll start a 1.0.x branch for the new rdf, update the module page, etc.

I've commented on the same issue. I'll help out with the code splitting and such. There is always some bumps in the road we have seen and I've got decent experience with this by now.

Tests have been committed. Seems this is ready for a subtree split into a new branch in contrib. I think its wise to wait for maintainership first though.

Created #3306737: Create a release of the subtree split of Drupal Core

Subtree split is done, there is a 2.x branch and instructions on how to test in #3306737: Create a release of the subtree split of Drupal Core. After testing by someone else we can create a release stable for 2.x and continue the work.

RDF now has a stable release.

If i look at the IS everything is done? #3267703: Deprecate RDF module has just been committed, RDF is deprecated :)

Yes!