After tagging a release (7.x-1.0-beta1) on the drupalprojects/hotsauce, an updated build should have been pushed to kalacommitbot's fork of the hotsauce-drops-7 repo.

Although our Travis build came back as a-ok, something must be funky in getting this extra build (which is a handy time-saver for deployment of HotSauce! to all locals). @gremy originally built this and @labboy0276 has helped out in the past; @pirog might want to review now that he has become a Travis expert.

Right now, when a tagged commit is pushed to hotsauce, the travis script will automatically build a version of hotsauce and commit it to kala-travis's hotsauce-drops-7 account. Anyone can do this, which isn't ideal for our review process.

Our goal should be to not build/commit to kala-travis unless the commit is a pull request being merged into drupalprojects/hotsauce.

Get hotsauce core and residuals up to snuff

Note, I am doing this now and just creating this issue for a PR

We need to write documentation both for HotSauce! but more importantly for Kalatheme 4.x. THIS IS GOING TO BE SUPER IMPORTANT.

Here are some things we will need for HotSauce!

1. Project page for d.o
2. Read Me
3. How to's for installation and usage
4. @reynoldsalec other things?

Here are some docs we will need for Kalatheme 4.x

1. Probably something talking about all the changes
2. An extensive how-to on how to use all the magix
3. @bassettsj what else?

Upon a new (tagged) release Github webhook contacts the app server and creates new App Release node.

Error: Maximum function nesting level of '256' reached, aborting! in
/home/travis/build/drupalprojects/drupal/includes/module.inc, line
765

Thought I had fixed this with the following code in the before_script:

Expand max_nesting_level to prevent error

export ADDITIONAL_PATH=php -i | grep -F --color=never 'Scan this dir for additional .ini files'
echo 'xdebug.max_nesting_level=9999' | sudo tee ${ADDITIONAL_PATH:42}/drupal.ini

Get hotsauce core and residuals up to snuff, putting this in since I am doing this now

We need to be able to transfer our sites on the old Hotsauce to the new sub-distro based version.

Notice: Undefined variable: options in apps_profile_apps_select_form() (line 122 of /srv/bindings/88bc69aeba2d4570a5229486c6e0d244/code/profiles/hotsauce/modules/contrib/apps/apps.profile.inc)

This is a drupal core bug that may be fun to work on.
https://www.drupal.org/node/1334818

I am not sure how to delete projects on drupal.org but can someone research how to do this so we don't have a graveyard of unmaintained modules?

Here are the github pages of the modules that need to be eliminated.

Core HotProjects!

• HotCore!
• HotAdmin!
• HotPics!
• HotTheme!
• HotWidgets!
• HotSearch!
• HotUsers!
• HotWYSIWYG!
• HotPages!
• HotMagic!

I noticed one UX flaw when installing, I attached a screenshot.

When I select the subtheme the y overflow goes mad tall.

Since we are temporarily(permanently?) abandoning the app server paradigm we are going to need to bundle in some of our most useful apps into the project. Let's decide what those are and then roll them in.

@bassettsj @andrewmallis @reynoldsalec can you help determine what these are?

@bassettsj,

@reynoldsalec and i are putting together a new alpha1 roadmap for hotsauce based on discussions we had with snopek and populist.

Can you chime in here https://github.com/drupalprojects/hotsauce/wiki/Alpha1-Roadmap to post the relevant big issues that need to be resolved in 4.x so that we can ship it with alpha1?

We forked panopoly, but after discussions with snopek and populist we think there is great space to forge a mutually beneficial pathway forward. To that end we need to rebase hotsauce so that it is a panopoly subdistro again.

One issue that will need to be decided here is whether we dont include some panopoly features like search and pages, or if we attempt to override them using something like
https://github.com/kalamuna/panopoly_override

@andrewmallis and @reynoldsalec, can you help decide that we should do here?

I'm getting the following warning and notice on pages displayed using the node panelizer:
Warning: Missing argument 4 for entity_metadata_taxonomy_access() in entity_metadata_taxonomy_access() (line 797 of /srv/bindings/4d1d7571768d42bdaf394dc726162dc7/code/profiles/hotsauce/modules/contrib/entity/modules/callbacks.inc).

Notice: Undefined variable: entity_type in entity_metadata_taxonomy_access() (line 798 of /srv/bindings/4d1d7571768d42bdaf394dc726162dc7/code/profiles/hotsauce/modules/contrib/entity/modules/callbacks.inc).

Not sure if this is related to #17

Also getting these notices about kalatheme on the same panelized pages:
Notice: Undefined index: devices in theme_kalatheme_kalacustomize_render_region() (line 26 of /srv/bindings/4d1d7571768d42bdaf394dc726162dc7/code/profiles/hotsauce/themes/kalatheme/styles/kalacustomize/kalacustomize.inc).
Notice: Undefined index: pane_style in theme_kalatheme_kalacustomize_render_region() (line 27 of /srv/bindings/4d1d7571768d42bdaf394dc726162dc7/code/profiles/hotsauce/themes/kalatheme/styles/kalacustomize/kalacustomize.inc).

Everything seems fine in terms of functionality though, as far as I can tell.

reynoldsalec
Owner
reynoldsalec commented on Apr 25
To avoid the issues of keeping our package.json file up-to-date with our app's .info file, we should have an automated process to pull those dependencies into package.json. Could probably also pull some basic metadata (Drupal version etc) into package.json as well.

Any other relevant stuff in .info that we need to transfer?
reynoldsalec
Owner
reynoldsalec commented on Apr 26
The App Manifest project works pretty well, may have some code to steal from there: https://drupal.org/project/app_manifest

Let's leverage the Panopoly behat scripts in our Travis build. Will probably need to...

*Add panopoly_test module
*Run a travis-ci.sh script in our .travis.yml
*Adapt the Panopoly travis-ci.sh script to Hotsauce's needs (correct the Panopoly paths, any other incompatibilities)

Are there other modules/features that we want to include with hotsauce by default? What are they?

@bassettsj @andrewmallis @reynoldsalec discuss!

Kalatheme Wish List

• views_bootstrap
• magic
• speedy
• icon (most important)
• views_responsive_grid
• elements

@bassettsj,

Since we are now going to rely on other contrib modules to provide functionality that was in Kalatheme a la views plugins and libraries handling we are going to want to include those dependencies in hotsauce.

Can you list the dependencies here and any outstanding issues for those modules that may be blockers? ie if the bootstrap libraries module does not allow for 1 library for 1 theme.

We had a great discussion with snopek and populist about the direction of Panopoly/HotSauce! and we identified some common issues to work on.

Add "Manager" role: https://drupal.org/node/2282039
Move "Categories" taxonomy to panopoly_pages: https://drupal.org/node/2282059
Rename "Categories" Tags: https://drupal.org/node/2282057
Update Search API: https://drupal.org/node/2080893
Exportable Fieldable Panel Panes: https://drupal.org/node/2222727

@reynoldsalec @bassettsj

where are we with this?

i am moving this over from hotsauce-drops-7 so i can close that issue queue

From @pirog: "ok so right now im stuck on the deploy stuff on this corrupt image https://travis-ci.org/drupalprojects/hotsauce/builds/38875023 which i am assuming is part of d.o updating the dev package."

I'll take a look at this later today or Monday.

Packaging error messages

Build for hotsauce-7.x-1.x-dev-no-core failed:

Unable to download tinymce from https://github.com/downloads/tinymce/tinymce/tinymce_3.5.8.zip.

This is happening on D.o when it tries to build a new release.