-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Backdrop? #141
Comments
I'd prefer to see one Drush, but opinions here are mixed. Are you volunteering to be the maintainer for this support, or has someone else volunteered to do that? |
Right.
|
@greg-1-anderson No, that wasn't a veiled offer to support Backdrop, but nice try :-P I'm not even sure of the scope of such an undertaking. There was a suggestion that Backdrop could essentially imitate Drupal 7 to maintain compatibility with Drush. This seems feasible for the time-being, as it puts the burden on Backdrop to not diverge too far. Since determining version appears to be part of the difficulty, I also submitted: Make determining version easier for external applications to the Drupal core issue queue. But @greg-1-anderson's suggestion should solve the immediate issue. |
I think the position of Drush maintainers is well articulated here. Not much to do until someone wants to maintain this. |
I'll just go ahead and apologize in advance for any acrimony that may arise from this issue...
According to @greg-1-anderson over in BackdropCMS' issue #47: Keep drush compatible or create sibling:
Let's, for the moment, just assume that someone will step up to maintain support for Backdrop in Drush. To be blunt, would such work be welcome in Drush, or is a fork required here too?
FWIW, there's fairly strong support for providing Backdrop CMS Support in Aegir.
The text was updated successfully, but these errors were encountered: