Skip to content
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

Closed
ergonlogic opened this issue Sep 23, 2013 · 4 comments
Closed

Support for Backdrop? #141

ergonlogic opened this issue Sep 23, 2013 · 4 comments

Comments

@ergonlogic
Copy link
Member

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:

The thing to do would be to start a discussion in the Drush queue and see what everyone really thinks.

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.

@greg-1-anderson
Copy link
Member

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?

@weitzman
Copy link
Member

Right.

  • Someone needs to volunteer to maintain this.
  • I can't say right now if we'll have one Drush or if Backdrop will use a downstream Drush variant. It depends on how hairy the code gets. If it is a variant, we'll do what we can to make life for those maintainers. I will say that we already support 3 versions of Drupal and a 4th doesn't sound like a tasty idea.

@ergonlogic
Copy link
Member Author

@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.

@weitzman
Copy link
Member

weitzman commented Oct 7, 2013

I think the position of Drush maintainers is well articulated here. Not much to do until someone wants to maintain this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants