Hello Everyone,
I have recently turned my attention to Project Naming Conventions, as a consequence of attempting to locally MIRROR certain parts of the Drupal codebase. For example, the Drupal 7 oriented codebase (from which Backdrop is/was derived) is rather large:
- ~170,000 files
- ~340Gb
My MIRROR effort is being complicated by the inconsistent application of what appears to to me to be at first an emergent, then semi-official Drupal Project Naming Convention:
Project_name-Backdrop_version-Project_version.Extension_A.Extension_B
The inconsistent application of Project Naming Conventions has resulted in an exceptions list of over 7,000 items, mostly due to the inconsistent application of Drupal Project Name separator(s). Some used a dash ("-") instead of using an underscore ("_") in their Project Name, like these entries:
MyDrupal-Tidy-5.x-1.0.tar.gz
MyDrupal-Tidy-5.x-1.0.zip
Others did not use a version number:
CiviCRM-HEAD.tar.gz
...and so on.
My question
Has Backdrop officially adopted a Project Naming Convention?
I assure you, it would make any visitors from the future very grateful :)
The consistent use of underscore ("_") and dash ("-") and period (".") in filenames can really simplify filename processing.
g.
----
Recent comments
Hi Mike, try user/login, that should work.
Admin login - help
I wrote a blog post a while back about how the color module works, in case that is helpful. https://www.triplo.co/blog/color-module-backdrop-cms
Color module aggressive search and replace custom css color values
You are asking this question at the right time. Work has been done on the Content Moderation module for Backdrop CMS, but it's still not working fully. We would welcome help getting this...
Workflow module or equivalent?
Hi, Olafski, Thanks for your reply. Thank goodness we have the resources of Drupal 7 to look at when these questions arise -- questions new to me (yet another unknown part of Drupal /...
Color module aggressive search and replace custom css color values
Hi DonM, I guess there isn't an option for the color module to behave in another way, but there are workarounds: Don't use the color module, maybe even disable it, and use only...
Color module aggressive search and replace custom css color values