Closed (fixed)
Project:
Drupal core
Version:
9.5.x-dev
Component:
quickedit.module
Priority:
Critical
Category:
Plan
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Aug 2021 at 18:37 UTC
Updated:
9 Sep 2022 at 08:49 UTC
Jump to comment: Most recent
Comments
Comment #2
xjmComment #3
xjmComment #4
gaurav.kapoor commentedHi. I would like to volunteer for this. How can I get maintainer access? Should I start working on linked issues? Thanks.
Comment #5
gábor hojtsy@guarav.kapoor: yay! Did you build with and/or on top of quickedit before? Are you familiar with some of the current issues of the core component? (https://www.drupal.org/project/issues/search/drupal?project_issue_follow...) -- It is definitely not required to fix any of them in core or neither when the project moves to contrib, so its more of a question if you think you could help out with them if others are working on them.
Comment #6
gaurav.kapoor commented@Gábor Hojtsy I haven't build anything on top of quick edit. I have started checking the codebase of the quick edit module and checking issues reported under https://www.drupal.org/project/issues/search/drupal?project_issue_follow.... I can definitely help out other contributors working on this.
Comment #7
wim leersComment #8
wim leers#3238626: [Follow-up] Move tests for integrations between QuickEdit and other modules into QuickEdit is done too!
That means we can now do #3227033: Remove Quick Edit from core 🤓
Comment #9
longwaveWe missed the window for doing this in 9.3.0.
What needs to happen next to get this done before 9.4.0?
Comment #10
catchThe current blocker is #3252214: Move tests for integrations between QuickEdit and CKEditor5 into QuickEdit so that it can more easily be moved into contrib
Comment #11
spokjeBlocker #3252214: Move tests for integrations between QuickEdit and CKEditor5 into QuickEdit so that it can more easily be moved into contrib is committed.
Updated IS to reflect gaurav.kapoor has volunteered to become a maintainer for the Contrib Module QuickEdit in #4.
Comment #12
spokjeLooking at @Gábor Hojtsy's comment in the (very) similar issue about moving the HAL module from Core to Contrib (#3049857: Remove HAL module from core and create a contrib project for it), I think this issue should also be postponed on #3215043: Indicate the non-stable statuses in admin/modules page and #3215045: [Duplicate] Highlight obsolete module's status at admin/reports/status page, providing warning and link with explanation
Comment #13
gábor hojtsyUpdate related issues.
Comment #14
spokje#3215043: Indicate the non-stable statuses in admin/modules page just got committed, only postponed now on #3250585: Highlight deprecated modules and themes at admin/reports/status page, providing warning and link with explanation.
Comment #15
spokjeUnpostponing after #3250585: Highlight deprecated modules and themes at admin/reports/status page, providing warning and link with explanation was committed.
Comment #16
spokjeRemoval patch is in #3227033: Remove Quick Edit from core
Comment #17
catch@gaurav.kapoor are you still interested in maintaining Quickedit in contrib? If so creation of the contributed project is the last blocker for #3227033: Remove Quick Edit from core.
Comment #18
gaurav.kapoor commented@catch Not anymore. Thanks.
Comment #19
spokjeUpdated IS to reflecting were still looking for a maintainer for QuickEdit in Contrib.
Comment #20
dwwPer #3227033-76: Remove Quick Edit from core, I did a subtree split of 9.4.x quick edit into 1.0.x branch of the contrib project and made a 1.0.0-rc1. I’m not really planning to maintain it, other than cooperation with the sec team if needed. So if anyone else wants to help, please do. But at least the deed is done. ;)
Comment #21
quietone commentedComment #22
quietone commentedComment #23
quietone commentedComment #24
dwwUpdating remaining tasks with some things that are already done.
Comment #25
dwwQuestion on scope and issues. Currently both of these points:
have patches in #3227033: Remove Quick Edit from core. Given the very next point is "Commit the deprecation patch and the removal patch within 24 hours of each other." is it better to leave these in the same issue, or would it be preferred to split out the 9.4.x deprecation patch into a separate issue?
Thanks,
-Derek
Comment #26
xjmComment #27
xjm@dww The whole notion of committing them 24 hours apart is weird; normally, we wouldn't even have deprecations allowed at the point where the major branch is open at all. However, separate issues are still preferable because they're totally different code-wise, being committed to different branches, and part of different steps of the meta.
Comment #28
dwwCool, makes sense. #3270434: Mark Quick Edit deprecated
Comment #29
quietone commentedComment #30
quietone commentedComment #32
wim leersSorry, this triggered my OCD too much too many times to resist 🙈😬
Comment #33
dwwI believe we're just down to #3270434: Mark Quick Edit deprecated now. 🎉 Minor summary edit to update all the
[#]statuses.Comment #34
xjmComment #35
quietone commentedMove to a child of the 9.5 beta1 parent
Comment #36
dwwNow that contrib quickedit 1.0.2 is out, I believe we're ready, and all that remains is to commit #3270434: Mark Quick Edit deprecated and we can mark this plan fixed...
Comment #37
quietone commentedThanks for the huge effort to deprecate Quick Edit!
The unfinished related issue in the IS is an issue in the contrib project.
Comment #38
wim leers🥳
🙏 Many thanks to all of you who devised and executed this intricate web of tasks to allow Quick Edit to be removed from Drupal core!