Break apart github repos for islandora modules

[dannylamb]

Composer works with a 'package per github repo' fashion, so let's break them apart. Use the git subtree command to preserve history on the islandora_collection module and pull it into its own repo. Also, move the contents of the remaining islandora folder to the top level of the repository.

[ruebot]

Wouldn't this violate our one repo on Drupal.org rule that we've been going with?

[dannylamb]

Sadly, yes it would. I'm not happy about it.

[ruebot]

Agenda item for Wednesday's call? I'd prefer to talk about this more so I can understand it better before we move forward.

[dannylamb]

np

[ruebot]

Added: https://github.com/Islandora-CLAW/CLAW/wiki/January-4,-2017#agenda

[dannylamb]

#27

[dannylamb]

https://github.com/dannylamb/islandora_collection

[dannylamb]

https://github.com/DiegoPino/claw-jsonld/pull/2

[DiegoPino]

@dannylamb @ruebot. To add to the discussion tomorrow some alternatives we discussed via other media.

• https://packagist.org/packages/mile23/drupal-merge-plugin or the better supported wikimedia/composer-merge-plugin
  This plugin searches for composer.json files in user contributed modules and tries to satisfy it's dependencies. Does not require that we transform or move all modules or whole drupal to composer.
• Make this just an install task, without any code change or repo reorganization until we have a better solution (yes, not intended to be an automatic, good for all solution)
  on drupal root directory run

 composer update
 composer require stomp-php/stomp-php

Some last thoughts: Composer is the way to go of course. But the composer way of drupal is still a bit "betaish", not straight forward, still depends many times on drush(to enable modules) and requires in any case a lot of modifications to the composer.json file itself or adding extra install tasks.

[ruebot]

https://packagist.org/packages/mile23/drupal-merge-plugin

"Note: This project is in development. It currently does not have even any releases."

[dannylamb]

@DiegoPino Yes, there are other ways of installing the requirement for stomp-php that do not involve breaking up the repositories. I'm proposing this restructuring to get something potentially very costly and time consuming out of the way early before we start collecting more modules.

@ruebot The real concern for me is what this shift means for our yet to be defined release process.

[whikloj]

@ruebot @dannylamb I think this is done, no?

[ruebot]

@whikloj I'd say so

[whikloj]

Resolved with various PRs referenced in this ticket and the new https://github.com/Islandora-CLAW/claw_vagrant repo