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
Also it has no maintainer. Anybody interested to maintain?
Flood Unblock analogue
Because it doesn't have a release yet?
Flood Unblock analogue
It's already been done, https://github.com/backdrop-contrib/flood_unblock how did we miss it?
Flood Unblock analogue
Solution: porting the Flood Unblock module using Coder Upgrade (https://backdropcms.org/project/coder_upgrade)...
Flood Unblock analogue
You may need to re-install your Backdrop site and restart the import after a failed import. While I've never used that module, rolling back the import may not be enough. I would be sure to have...
Importing Posts/Pages from Wordpress