forked from alxp/islandora
-
Notifications
You must be signed in to change notification settings - Fork 118
TAG Meeting June 28
B. Seeger edited this page Jun 28, 2019
·
9 revisions
- Daniel Lamb
- Bethany Seeger 🌠
- Bryan Brown
- Derek Merleaux
- Jared Whiklo
- Jonathan Green
- Rosie Le Faive
- Will Panting
Previous meeting notes: https://github.com/Islandora/islandora/wiki/TAG-Meeting-May-31-2019
- Security response protocol
- current workflow: https://github.com/islandora-interest-groups/Islandora-Security-Interest-Group/blob/master/workflow/ISRT_workflow.md
- updated workflow document with edits from last meeting: https://docs.google.com/document/d/10d4F2_-xtdRam101Mfz_SO0D0rkvNmWgYYUj3NigKaI
- How does one de-CLAW a lobster?
- Ticket with some discussion: https://github.com/Islandora-CLAW/CLAW/issues/1082
- Dockerization for Islandora 8
- More frequent release schedule
The team is satisfied with where the Security Response Protocol is. Discussion of a community response period so we know what others thinks (esp. the response team).
- We discussed how to bring Islandora-CLAW repositories into the Islandora organization. Landed on bringing in the repositories and having Islandora 8 release branches, like how things have worked with Islandora 7 and 6 branches. CLAW will be split into "docs and issues" repo and "versions" repo.
- Travis setup needs to be considered. Probably a separate repository - they could probably go into dev-ops repo to pull for setup and testing.
- Tickets on CLAW repo need to be moved. Right now they can go into a "docs and issues" repository. Islandora 7 uses Jira, whereas Islandora 8 uses Github Issues. Need to make sure we can keep things separated and workflow clear. We can use this method to transfer tickets: https://help.github.com/en/articles/transferring-an-issue-to-another-repository
- Down the road, we might want to use more drupal.org features for tickets / code. Right now it's not really a good option as the tools there are a little outdated.
- Once the repos are moved, there will be two sets of committers operating on the same repositories. It appears that restrictions can be applied to branches.
- Danny will start moving things around - migrate the repositories, move issues and sort out the committer permissions. A few new committers might need to be added to the Islandora organization, if they aren't already Islandora7 committers.
- Bethany and Derek talked about the Islandora Collaboration Group's (ICG) work on ISLE and our trajectory to dockerize Islandora 8.
- Concern is that Islandora is a small community with not a lot of folks to maintain things.
- Some want to install on bare metal and some want containers.
- Danny talked about responses from the recent survey about Islandora 8. Docker in survey got a lot of “no’s”. There are “yes’s”, but lots of “no’s”, which is surprising. Danny thinks it makes sense to be dockerize because CLAW has a lot of microservices, and also to maybe use kubernetes someday.
- ISLE is working towards monthly updates. Concern regarding this from Islandora7 perspective - who will maintain this?
- We should also think about the community building side of things as well as the technical side of things. This type of thing can democratize the use of Islandora software.
- Maybe we can see how Ansible scripts can work with docker? Can Ansible scripts bootstrap docker? Some merging of techniques here?
- We need to balance work and technical debt in taking on something new.
- More research needs to be done about the synergy between Ansible and Docker. Maybe they could work together. https://docs.ansible.com/ansible-container/ https://github.com/geerlingguy/drupal-container
Danny will start moving CLAW repository around.
You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups