[META] Stay on top of contrib module updates

[jenlampton]

Here is a list of contrib modules that were moved into core. Each should have a link to an issue where we can evaluate continuing commits for that project, to see if they are applicable to Backdrop core as well:

• Admin Menu
  • Include Admin Menu 7.x-3.0-rc6 updates #5015
  • Include Admin Menu module 7.x-3.0-rc7 updates #6872
• Block Class
• CKEditor
• Date | [META] Stay on top of date module updates #4027
• Elements
• Email | N/A -- last release 10 April 2014
• Entity View Mode
• Entity Cache | [META] Include all D7 Entity Cache module updates #6232
• Field Formatter Settings
• File Entity
• Instant Filter
• Link | [META] Link module commits #2076
• Menu Block
• Options Element
• Pathauto
• Project Browser
• Rabbit Hole
• Redirect | [META] Stay on top of redirect module updates #5008
• Role Assign
• Scheduler
• Token | [META] Stay on top of token module updates #5012
• Views | [META] Include all D7 Views module updates #3685
• Views Bulk Operations

[klonos]

Perhaps it would be a good idea to be including the last D7 version of these modules that we have checked and merged changes for. Where would a good place be for us to be storing such info? Separate file per module? A single file for all these modules? Comments in the respective .info files?

[klonos]

I would like to discuss this during the next dev meeting if possible.

I thought that we could perhaps set a D7 instance somewhere (the cheapest hosting we could find would do), then install the D7 contrib modules we have merged into Backdrop core in that instance (the versions that we have ported), and finally enable update notifications and have them be emailed to a group email list like the PMC email (I would like to be in that list).

Each time there is an update for one of these modules, one of the people receiving the notifications should create a ticket here and list changes. Then we can file PRs.

Once the changes have been merged (or deemed N/A to Backdrop), we should update the instance with the current version of the module, and wait for the next update.

Repeat...

Does that sound like a good plan?

[klonos]

Update: after today's dev meeting, @jenlampton has created https://github.com/backdrop-ops/dcu.backdropcms.org (DCU for Drupal Contrib Updates), which currently includes just vanilla D7 core. The plan now is:

1. Gradually go over the Backdrop code and old issues and identify which specific versions of D7 modules have been merged in Backdrop core. For a list of modules that have been merged, see https://backdrop-ops.github.io/slides/intro-mini.html#/19

2. Once a module version has been identified, we should file a PR to merge that into the GitHub repo.

3. @jenlampton is to be merging/deploying these PRs so that they are "live" on https://dcu.backdropcms.org

4. That site needs not to have any of these modules enabled; just the "Check for updates of disabled and uninstalled modules and themes" setting under /admin/reports/updates/settings enabled.

5. Whoever wants to help with keeping Backdrop core up to date with changes from the respective d.org modules can request to have their email added to the list of recipients of update notifications from dcu.backdropcms.org (again, to be set under /admin/reports/updates/settings)

   ...the idea there is that at some point we will have identified and installed all the D7 contrib modules merged into Backdrop core. As updates for these modules are being released in d.org, dcu.backdropcms.org will be sending notifications out to the people that have subscribed. These people will then:

6. Open a ticket in https://github.com/backdrop/backdrop-issues/issues about the update, and file a PR with any changes that are applicable to Backdrop.

7. Once the PR from step 6 has been merged, file a PR against https://github.com/backdrop-ops/dcu.backdropcms.org in order to update this site with the recently released version of the D7 module.

Repeat, keep up to date 😄

Bonus: we get notified about D7 core updates too!

PS: at some point, we should explore options of tracking D7 contrib modules that have been ported to Backdrop contrib. Ideally, we would have a way to notify only the respective contrib maintainers instead of everyone receiving notifications about everything (might require a custom D7 module that overrides how the updates email notifications work).

[klonos]

...we might need to install https://www.drupal.org/project/disable_updates or https://www.drupal.org/project/update_advanced at some point (in order to be ignoring/excluding specific versions of modules from the check).

[klonos]

https://dcu.backdropcms.org redirects to the API site currently. I guess @quicksketch or somebody else (@larsdesigns ??) will need to set up the hosts and also work on server security/hardening etc.

Eager to get this started. The sooner we start, the less bulk work we'll need to do as D7 contrib deviates from what we have.

[larsdesigns]

@klonos, I am happy to help and have been thinking about backdropcms infrastructure lately.

Do you need a new Virtual Machine setup and hardened for you project?