[META] Unpublish contrib projects that were moved in core and update their README.md

[klonos]

As per issue title. Now that for example Token and Pathauto are in core, what is the point of having the contrib projects still available? It will confuse people I think, even more when we get the project browser implemented as well as the modules section on BackdropCMS.org

Projects moved into core (or not needed in contrib)

• [x] token
• [x] pathauto
• [x] ckeditor
• [x] date
• [x] link
• [x] email
• [x] transliteration

Projects not needed in contrib for Backdrop

• [x] views
• [x] panels
• [x] ctools
• [ ] libraries?

Update README.md

• [ ] ckeditor
• [ ] link
• [ ] email
• [ ] transliteration

[jenlampton]

I think we should unpublish the projects from backdropcms.org so that people don't install them manually (or with drush) but I don't see any harm in leaving the projects up in GitHub.

It might also be a good idea to add a line to the top of the README file that states that the project has been included in core, so if people do stumble across the GitHub version they don't try to install it.

[klonos]

...I will make a list of them soon as I get some time.

[jenlampton]

Fantastic, thanks @klonos :)

[klonos]

I never got back to this, but I think these projects should have a final commit with a line added to their .info files like status = inactive or status = unpublished or something. Then, bd.org can pick this and ignore them ...and that should work with the Project Browser too.

[klonos]

https://github.com/backdrop-ops/backdropcms.org/issues/100

[jenlampton]

@klonos can you add a comment to that issue (or update the main issue) with a status line, so we don't forget? Maybe we also need a follow up issue in backdropcms.org to make the project module not create project or release nodes for inactive projects on GitHub.

[jenlampton]

It might also be a good idea to create placeholder projects for popular drupal modules that are not needed in backdrop, things like Views and Ctools. We've gotten some complaints that "views is not ready" because people search for it and can't find it.

It would be good to have these appear in search results, but with no publishes releases. The description can say something like "Views module has been moved into core in Backdrop CMS, no need to install!" to help people understand what's not needed anymore.

I've turned this issue into a meta so we can be sure we've updated all these contrib projects adequately.

[klonos]

I think it might also be a good idea to create placeholder projects for popular drupal modules that are not needed in backdrop, things like Views and Ctools.

:+1:

...then perhaps also a status = in core [version] that indicates that a project has been merged. The corresponding placeholder project node in bd.org could then display a "Included with Backdrop since version [version]".

[jenlampton]

Good idea! For now I am using the Enable releases checkbox to determine if something is in core or not, and if releases should be shown. We could use that value in the info file to set this value on the project.