It would be a wise marketting move to have some sort of slogan or branding of Backdrop CMS as being Drupal Classic. With that said, given the long term success of Drupal 7 having penetrated 1 million plus installs and still around 500,000 installs 12 years later, I would think that forking Drupal 7 as-is and backporting the look and feel of Backdrop into Drupal 7 Fork Classic , leveraging nearly or possibly ALL of Drupal 7 contrib would seem like a very logical way to go.
There's some very strong developers in the Backdrop CMS project that have dedicated years to the project , I realize that it would be difficult to convince these members of the idea of Forking Drupal 7 and porting some of the Backdrop CMS look and feel and functionality to it while maintaining a high degree of drop-in compatibility.
I guess what I'm looking for is a way to unify Backdrop CMS with Drupal 7 in a compatible way to harness a super easy drop in replacement upgrade path for Acquias Drupal 7 core.
I have a script that managed to clone over 42000 repositories linked to Drupal.org , however so much intelligence of Drupal is in the actual drupal.org site, it would pretty much be necessary to clone that as well and fork it with all the comments and patch files.
Maybe talking into the wind here but I think many will see what I'm saying and understand it.
Dries seems bound and determined to end Drupal classic so I think the only option is to fork and clone. The way way back machine probably not powerful enough to store drupal.org so we'd have to probably find some way to keep that intelligence before they break it.
This might be a crazy idea and/or impossible. BUT...
It's my understanding that there is legacy code from Drupal 7 that is still in Backdrop but not necessarily exposed or required for new Backdrop sites. That some Drupal 7 things that are not officially supported for Backdrop, will work if folks know how to access them.
Would it be possible to provide alternative upgrade paths for some Drupal 7 sites that making upgrading easier, but doesn't provide all of the new features for Backdrop - and that sites have a way of doing a minimal upgrade with the hope that we might be able to provide easiser upgrade paths for other Backdrop features in the future.
I'm thinking about a world in which a Drupal 7 site is able to upgrade to Backdrop, but bypass the layout system and use their Drupal 7 theme on a temporary basis. Would they be able to get some basic Backdrop features, but not have access to the ones that make upgrading more complicated for them?
It has been argued quite persuasively to me, that the term 'recipes' implies a list of instructions on how to do something. In Drupal land there is a recipe initiative which centers around a collection of "best practices" and or tested instructions on how to acheive specific goals.
Is our use of "recipes" confusing? Is there a better term?
Personally, I think that this concept is still new enough that we could change the terminology with little cost (and potentially an improved understanding of what we intend).
In Drupal 7 these were "features," but the term features has a very specific meaning to former Drupal 7 users and we think it would be confusing to use it for this purpose in Backdrop land.
Many of my D7 modules rely on adding controls to existing settings pages, and looking to porting to Backdrop CMS I wonder what the strategy is for doing this sort of thing without the page array.
It would be a wise marketting move to have some sort of slogan or branding of Backdrop CMS as being Drupal Classic. With that said, given the long term success of Drupal 7 having penetrated 1 million plus installs and still around 500,000 installs 12 years later, I would think that forking Drupal 7 as-is and backporting the look and feel of Backdrop into Drupal 7 Fork Classic , leveraging nearly or possibly ALL of Drupal 7 contrib would seem like a very logical way to go.
There's some very strong developers in the Backdrop CMS project that have dedicated years to the project , I realize that it would be difficult to convince these members of the idea of Forking Drupal 7 and porting some of the Backdrop CMS look and feel and functionality to it while maintaining a high degree of drop-in compatibility.
I guess what I'm looking for is a way to unify Backdrop CMS with Drupal 7 in a compatible way to harness a super easy drop in replacement upgrade path for Acquias Drupal 7 core.
I have a script that managed to clone over 42000 repositories linked to Drupal.org , however so much intelligence of Drupal is in the actual drupal.org site, it would pretty much be necessary to clone that as well and fork it with all the comments and patch files.
Maybe talking into the wind here but I think many will see what I'm saying and understand it.
Dries seems bound and determined to end Drupal classic so I think the only option is to fork and clone. The way way back machine probably not powerful enough to store drupal.org so we'd have to probably find some way to keep that intelligence before they break it.
This might be a crazy idea and/or impossible. BUT...
It's my understanding that there is legacy code from Drupal 7 that is still in Backdrop but not necessarily exposed or required for new Backdrop sites. That some Drupal 7 things that are not officially supported for Backdrop, will work if folks know how to access them.
Would it be possible to provide alternative upgrade paths for some Drupal 7 sites that making upgrading easier, but doesn't provide all of the new features for Backdrop - and that sites have a way of doing a minimal upgrade with the hope that we might be able to provide easiser upgrade paths for other Backdrop features in the future.
I'm thinking about a world in which a Drupal 7 site is able to upgrade to Backdrop, but bypass the layout system and use their Drupal 7 theme on a temporary basis. Would they be able to get some basic Backdrop features, but not have access to the ones that make upgrading more complicated for them?
Just a crazy idea...
It has been argued quite persuasively to me, that the term 'recipes' implies a list of instructions on how to do something. In Drupal land there is a recipe initiative which centers around a collection of "best practices" and or tested instructions on how to acheive specific goals.
https://foxvalleydrupal.org/article/announcing-drupal-recipes
Is our use of "recipes" confusing? Is there a better term?
Personally, I think that this concept is still new enough that we could change the terminology with little cost (and potentially an improved understanding of what we intend).
In Drupal 7 these were "features," but the term features has a very specific meaning to former Drupal 7 users and we think it would be confusing to use it for this purpose in Backdrop land.
Are there potential core features that have been blocked by the lack of references in core in the past?
What kinds of features have been added to Drupal 8/9/10 that are related to references (if any)?
Not sure where to put this...
Many of my D7 modules rely on adding controls to existing settings pages, and looking to porting to Backdrop CMS I wonder what the strategy is for doing this sort of thing without the page array.