You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More importantly, Drupal will have access to version information and we will no longer get the annoying message that update information could not be obtained for open_framework in the module status report.
Hi Ken,
We are definitely aware of the benefits of putting OFW on d.org. We've wanted to for a while now... but there are two main reasons why this has not happened:
The theme as-is includes Bootstrap and we'd have to modify the structure of it to adhere to the d.org guidelines about including code packaged under a difference license. This, to us, would mean making a duplicate, different version of the theme for d.org.
Second, it's a lot of work being code maintainers. To be honest, Brian and I were nervous about the extra time commitment if we released the theme to a wider audience, as theme work is already extra work beyond our primary responsibilities. I know this sounds like a silly reason to not release the theme, but we were concerned we would not have the time to handle the increased load.
I can't comment on reason 1, but, as for reason 2, once it's up on drupal.org, you can ask for additional maintainers if (when) you find yourselves overwhelmed.
I really like this theme, but putting on Drupal.org will make installing/updating easier using drush.
The text was updated successfully, but these errors were encountered: