Update "Drupal 6 contributed modules that are in Drupal 7 core"

Moving this issue to the Documentation queue, since it is not an issue with Drupal code. Please open a separate ticket in the Drupal queue for linking to this page from UPGRADE.TXT (although it will probably be postponed on #949102: Polish UPGRADE.txt).

Ok, I had a go at editing that page. Let me know what you think.

I looked over the edited page, and it looks good. I'm not super familiar with all of those modules, but after looking at the project pages and some of the issue queues it looks like they are categorized correctly. My only suggestion would be that maybe CCK should be listed in the second category: "Modules that may also be uninstalled, depending on the functionality you require".

Like the note on that page says, CCK will still be a contrib module for node reference and user reference. Of course it also fits the description of being an upgrade path, so maybe it could be in both categories?

Those are just my thoughts. Great work on splitting the list out,
-Josh

Seems on the right track to me - though I'd definitely want a core dev or two to review that list (will see if I can get someone to look at it).

As far as CCK, my understanding is that you *definitely* need it installed when upgrading a site, as it contains the migration code for bringing D6 CCK stuff into D7 (sidenote: we will probably need to write some more extensive documentation on that, I don't think it exists yet).

I was under the same impression about needing CCK installed to do the upgrade. What wasn't clear to me was weather or not I would still need CCK after I upgraded my fields or not (assuming I don't need node reference or user reference). I guess that will probably be answered when the documentation comes out.

My thinking for my previous comment was that there are several modules in the first category that my be needed for an upgrade, but their functionality (apart from an upgrade path) is fully reproduced in D7 core. That's why I thought maybe CCK should change categories.

It would be great to see a core developer look over the list whenever the time is right. In the meantime, what else can I do here to help move these doc issues along?

@bonobo aha, awesome!!! (i'll try and keep an eye on here in case you need any reviews)

i'll keep trying to get one of the really involved core devs to review this...

The list of contrib modules moved into core includes http://drupal.org/project/documentation, and that's not a module.

Just created #984444: Page on modules now in core in D7 needs reorganization, table of contents based off a remark about UPGRADE.txt. Maybe these two tasks should be consolidated?

I already mentioned in IRC that http://drupal.org/node/895314 is not really useful. Problem space being:

We've crossed the 100 mark (of modules moved into D7 core) in the meantime, and people are still reporting further modules in the Upgrade Status queue. A few modules were only moved partially. Some need a note or two clarifying minor differences or whatnot. A couple need to link to specific upgrade modules and/or d.o issues, community initiative handbook pages, or similar upgrade tutorials/discussions for major modules.

But most importantly, it takes hours to figure out whether you actually need to do something or not, depending on the site you are upgrading. Clearly, this is a task for a module like Upgrade Status, because it is able to show site administrators only the information they really need to care for, since it can simply evaluate the currently enabled D6 modules to show upgrade information tailored to your site.

@sun, et al.: How about this then?

On http://drupal.org/node/895314, only talk about the most commonly used modules (80/20 principle or something like that), and their upgrade paths. That would allow us to give more detail for things like CCK and its most common contrib add-ons, which should probably be at the top of the page, as per #984444-4: Page on modules now in core in D7 needs reorganization, table of contents.

For the rest, make a recommendation that people download Upgrade Status.

that sounds more reasonable to me evandonovan - i think the concern sun voices is a legitimate one, if there is really that many modules, it will certainly be more info than is useful.

i like the idea in #12 of just outlining in general, and then adding details on any specific needs that relate to very major work items such as the CCK migration.

do note also, that some of those details may be best served by being put with the module's docs and then linked to from this page/section.

@arianek: Linking to the module's documentation would be great, as well (although I think CCK doesn't yet have detailed docs on this?)

So I guess then, in the new way forward, we aren't actually splitting the page further, but rather removing a lot of the module list information from the page, in favor of a cross-reference to Upgrade Status, as well as making the most major upgrade tasks into sections at the top?

that sounds like a good plan, in light of sun's comments.

as far as i know there are only really docs for current core d7 modules, as well as the install guide + a semi-finished upgrade guide. so maybe some of this would do well to go in the upgrade guide? http://drupal.org/node/548922 - it's in-progress and will be moved to the main docs area once it's done.

but yes, there is a large amount of documentation yet to be written. hopefully some of it will get completed at the docs sprint this saturday! http://groups.drupal.org/node/105309 in case anyone wants to join via irc ;)

adding tags, changing title, changing status (to reflect need to document core module changes/upgrade info)

downgrading task priority

(update - the https://www.drupal.org/docs/7/upgrade-to-drupal-7/drupal-6-contributed-m... page is "Last updated on 19 August 2016", this means that the functionality of the modules listed under "Modules that can be uninstalled from your D6 site prior to upgrade" category are all in D7 core prior "19 August 2016", and no major data migration needs to be performed.

the final D7 version release of module imageapi is on 24 December 2008, jquery_ui is on 16 June 2009, both prior "19 August 2016", they could be considered already all in D7 core by "19 August 2016" and both could be uninstalled and removed before upgrade to D7.

but the final D7 version release of module autoload is on 5 May 2018, simpletest is on 22 May 2018, both after "19 August 2016". does this means the functionality of these two modules haven't been all in D7 core by the date of "19 August 2016"? so the modules autoload and simpletest were in the wrong list on this page by this date "19 August 2016" and should be moved to the list of "Modules that may also be uninstalled, depending on the functionality you require" or "Modules that require data migration" on this page?

anyway what I mean is that the modules listed on the page https://www.drupal.org/docs/7/upgrade-to-drupal-7/drupal-6-contributed-m... may not be accurate, cause confusion, and need to be updated to their current and correct status.

it is much appreciated if anyone, e.g. the maintainers, know this better can give it an update. this will help to provide the correct information to the Druplers who plan to upgrade D6 to D7 tremendously)

in the https://www.drupal.org/docs/7/upgrade-to-drupal-7/drupal-6-contributed-m... page, under "Modules that can be uninstalled from your D6 site prior to upgrade" list, the modules autoload, imageapi, jquery_ui, simpletest all have D7 version. however as stated in this page, all the modules in this list "The functionality of these modules is in D7 core, and no major data migration needs to be performed", why the modules autoload, imageapi, jquery_ui, simpletest still have D7 version? should these 4 modules need to be moved to different list? could anyone help to inform the maintainer to respond to this inquiry? thanks.

I take that, by now, there should not be sites that still need to update to Drupal 7.
Drupal 7 will be probably marked unsupported by the end of this year. While having a complete list of Drupal 6 modules that are now part of Drupal 7 would be nice, I think this is not a priority.