Date
Call-in Information
Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)
To join the online meeting:
- Go to: https://duraspace.zoom.us/j/823948749
- Or iPhone one-tap :
- US: +14086380968,,823948749# or +16468769923,,823948749#
- Or Telephone:
- Dial(for higher quality, dial a number based on your current location):
- US: +1 408 638 0968 or +1 646 876 9923 or +1 669 900 6833
- Meeting ID: 823 948 749
- International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5
Slack
- https://vivo-project.slack.com
- Self-register at: https://goo.gl/forms/JxQFkut4TYj4Ehww1
Attendees
Indicating note-taker
- Jim Blake
- Andrei Tudor
- Christian Hauschke
- Muhammad Javed
- Ralph O'Flinn
- Benjamin Gross
- Kitio Fofack
- Mike Conlon
- Brian Lowe
- Greg Burton
- Robert Nelson
- Andrew Woods
- Martin Barber
- Huda Khan
Discussion items
- Sprint topics
- Sprint dates - weeks of May 21 and 28?
- Removing 1.10 blockers?
- Roll-back Jena updates (Fedora example)?
- Maven discussion from last week
- Join the development team!
- Process
- create a JIRA
- fork
- create a branch
- make a minor PR
- review other's PRs and approve/request-changes
- Candidate tickets (everyone please take one)
- - John Fereira
- Defining style guidelines (including non-Java files)
- Adding a GitHub "contributing" file
- Others?
- Thanks for leading the way, Benjamin Gross!
- Minor process question: Who commits changes?
- Process
- Review and testing needed
- https://github.com/vivo-project/jenatools/pull/2
- Ready for testing and merge
- Mike Conlon
- https://github.com/vivo-project/VIVO/pull/62
- Where do we stand?
- Are there salted hashes in Vitro/VIVO for passwords? If yes, documentation should be updated accordingly,
Notes
- Sprint topics
- Sprint dates - weeks of May 21 and 28?
Project strategy meeting taking place on 01/03/2018 (March 1st)
The strategy meeting will define some priorities and might therefore influence the sprints following.
Having some outputs from sprints at this stage on the project seems to be the top priority.
Andrew is going to call for interest on end of April (2 weeks) Sprint leadership.
Making a successful sprint is more or less :
Institutional support is necessary
1 call at the beginning
1 retrospective call
And virtual stand ups through Slack
Leading a sprint does not necessarily require deep knowledge of VIVO code. Review, coordinating etc. is the main task.
Javed is taking the lead for April Sprint. Ralph can assist.
- Maven discussion from last week
Lot of people might be having issues on using Maven. There should be a documentation on how to proceed on builds with their customizations.
On VIVO Maven is used to build but also to deploy the application. There is a ticket on how we use Maven on the project cause for the moment the process is very developer oriented.
There is a use case on a non developer person being able to evaluate the application without having to do developer’s modifications. Having a War file to drop in a application container and a setup a database
The idea of having a vagrant or virtual machine with VIVO installed is proposed for that use case
A pre-packaged VIVO is an executable jar file with Jetty inside is also a possibility. It would just require the user to have Java installed. An evaluation system using TDB for installation on a Mac has been developed for VIVO Camp. Download, unzip, startup: https://drive.google.com/open?id=19jqP9jyiQpzxTeR_n401WIHsbWvRTXR7
- Join the development team!
- There is a need to clarify on what are the expectations from VIVO committer team members
- Process, We need more people taking this contribution process.
- review other's PRs and approve/request-changes
There a need of people engaging in this task.
A committers list with their respective expertise needs to be created.
Action items
- ...
Recent JIRA Tickets
Tickets created in the last 30 days:
Tickets resolved in the last 30 days:
Bugs
