April sprint | Kickoff call notes

[ruebot]

No description provided.

[manez]

Notes ✨

• A few weeks ago, @ruebot marked off a bunch of things for the sprint. No over-arching goal, just keep working on php microservices and get new sprinters up to speed. All listed handily here.
• New sprinters @edf and @br2490 (cue theme song) have got tickets to start with. Ben has Deletion of proxies from the ResourceService #150 and Ed has Update Vagrant to use fcrepo 4.5.1 #183 and Get vagrant config/variables to use correct line endings on Windows machines #188 . Might as well use this meeting time to check in and answer questions.
• @br2490 is diving in. Had some issues with vagrant. @ruebot recommends building from @whikloj 's PR Provide copy of composer, install PHP5.6. #187 , but this is what @br2490 was trying. Nick has a procedure to share:

14:07 ruebot: git clone [email protected]:Islandora-CLAW/CLAW.git
14:07 ruebot: cd CLAW
14:07 ruebot: git remote add jared https://github.com/whikloj/islandora.git
14:07 ruebot: git remote add me your fork
14:07 ruebot: git fetch --all
14:07 ruebot: git checkout sprint-002-issue-186
14:07 ruebot: cd install
14:07 ruebot: vagarant up

• @whikloj says it may have problems if you don't check it out on your local machine. If detached from HEAD, it doesn't work. Check it out as a branch. So, git checkout -b new-branch whikloj/jareds-branch or (to fit with @ruebot's above commands) git checkout -b new-branch whikloj/sprint-002-issue-186
• @edf asks: when upgrading Fedora, what Tomcat version should be used? @whikloj says both are on Tomcat 7 and changing the variables should cover the bases. Details. For 4.5.0 it should be fine. Might be problems for 4.5.1. @ruebot says if it isn't working, he's happy to troubleshoot. Ping in irc. More details
• Might be seeing some variations because @br2490 is working in multiple environments (Windows at home). Ignoring checksum might be a fix for that.
• @br2490 asks: Once it's up and running, it's essentially talking to Silex? We've coded whatever microservices to talk to Fedora and Blazegraph? @whikloj confirms that's right, except we don't currently write directly to Blazegraph.
• @whikloj suggests testing Deletion of proxies from the ResourceService #150 by creating an object and a collection, adding the object to the collection, and then deleting the object. Then checking via the Fedora interface to the collection's /members child and ensure there is no resource inside.
• When vagrant dies upon downloading Solr, @ruebot kills is and @whikloj waits. @edf asks what the best practices are for the vagrant up process, in terms of monitoring what;'s going on (logs, etc). @ruebot says he was sloppy making them and welcomes pull requests to make things quiet. @edf wonders if there is a vagrant log. Answer is: you have to redirect it. @whikloj notes we should allow a debug variable to turn on and off so we can have it quiet and complaining as needed. @ruebot notes that @nigelgbanks updates are coming over soon, giving us Ansible and Docker, which will require more updating. @edf is going to fork, make some changes to make it quiet, and @ruebot will test. Ticket: Make vagrant quieter  #192
• @ruebot notes that we're coming up on having many dev-ops environment and need to decide what we will maintain. @whikloj says Ansible - we may not know it well yet, but we need to learn, and it will be better in the long run for development and production. Suffer now for long term benefit.
• Waiting for a vote from @daniel-dgi to finish up Add LICENSE -- Address #4 chullo#13, then we cut a new release of chullo.
• @edf asks what is best practice for running on HEAD. @ruebot notes that running on HEAD is pretty much the only viable option for now. The current HEAD is sprint-002. @edf asks what practice is to pull in changes without doing a complete vagrant-up, for example, changes to microservices or a change made by another sprinter. @whikloj says you can edit the microservices on the host machine in the services directory, it's sym-linked into the VM. Live edit from outside. For stuff not in that linked directly, a rebuild of the machine would be needed - or go in and do the commands in apt get. But make sure everything is up to date and clean before a PR.
• @br2490 has a unicorn issue with the vagrant, working in Windows:

14:47 arebenji: - Installing islandora/resource-service (dev-jw-rocks)
14:47 arebenji: Symlink failed, fallback to use mirroring!
14:47 arebenji: Mirrored from ResourceService/
14:47 arebenji: - Installing islandora/transaction-service (dev-jw-rocks)
14:47 arebenji: Symlink failed, fallback to use mirroring!
14:47 arebenji: Mirrored from TransactionService/
14:47 arebenji: - Installing islandora/collection-service (dev-jw-rocks)
14:47 arebenji: Symlink failed, fallback to use mirroring!
`14:47 arebenji: Mirrored from CollectionService/``

• Might be Windows permissions on underlying filesystem are different. But he did get it working, so this is all academic.

The Wobster is proud of everyone's efforts:

WAKE UP, SHEEPLE CLAW IS COMING!!

[ruebot]

Sprint complete.