...
...
- Vitro JMS messaging approaches
- Architectural diagrams - discuss at a future date
Notes
Debrief of Kafka
- Questions
- Deployability?
- Kafka is ideal for the job
- Externalizing producer may not be necessary
- Direct-connect to Kafka may be more efficient
- Clarivate is experimenting with Kafka
- Transforms
- Body
- Potentially direct mapping of a changeset
- How to make this into something that is useful for the community
- Documentation
- Installation
- Have TIB and UQAM to align
- Working towards a shared codebase
- VIVO sprints around community initiatives
- Converting scripts into Java
- Create specification of messaging in VIVO
- Where are producers/consumers in the code?
2021
- Is there anything that we can do differently?
- More paid development
- Improving review process
- Docker on commit?
- VIVO in a box
- Scholars
- Eventing/Kafka
- Frontend API
- Doug/TAMU will be upgrading to 1.10 (1.11?) over holidays
- Investigate BlazeGraph (HTTP
) - TDB recommendations
- dump/restore feature exists in siteAdmin
- Find triplestore that has direct integrations with Kafka
- Persistent connections
- Staging CI branch
- Need to specify relationship between related PRs from multiple repos
- Use develop branch that is being deployed at regular frequency (hourly?)
- Process:
- Team coordination into CI-branch
- GitHub Actions ??
- Build/deploy to persistent AWS server
- Employ more stylechecks
- Triage in-review tickets at committer meetings
- Require a committer review quota?
- Use semantic labels to indicate scope of a PR, e.g.
- trivial patch
- minor change
- major change
- Multi-tenancy for VIVO?
- Move away from JIRA?
- Handle completely in GitHub issues?
- Issue-tracking: project at vivo-project org
- Currently JIRA requires a JIRA account We use Jira because Lyrasis uses it... we presumably used it in the past because Cornell used it. Benjamin totally agrees that jumping between Jira and Github is annoying, and some people have a tendency to post comments on Github vs Jira. The nice thing about moving to Github issues is that the issue is not inherently removed from the code.
Actions
- ...
Previous Actions
...