Skip to content

CDM 2020 03

Christian Murphy edited this page Mar 5, 2020 · 4 revisions

openEQUELLA Community Dev Meeting March, 2020

2020-03-05 (US) / 2020-03-06 (AU)

Attendees

  • Chair: IanS
  • Scribe: SamF

List of attendees:

  • CB - Chris Beach
  • CF - Cath Fitzgerald
  • CM - Christian Murphy (Scribe)
  • IS - Ian Stevenson (Chair)
  • NC - Nick Charles
  • P - Penghai

Agenda

General Topics

  • Review Action Items
  • Specific Topics (Please add to below list, or email the equella dev list to have an item added)
  • Discuss code enhancements since last CDM
  • Review tech choices, code structures, direction
  • Any tech debt concerns
  • Open PRs to discuss
  • Q&A
  • Assign next Chair and Scribe

Specific Topics

  • Will be doing a Moodle Module 1.1.0 (IS)
  • Bb LTI / REST update (CB)
  • GhostCat update (CB)
  • Releasing 2020.1.0 on Monday US time (CB)
  • Please add more

Review of Previous Action Items:

  • CB: is talking with Ian Dolphin from Apereo to shutdown the unused Open Equella Slack Channel
  • CB: has finished a pull request documenting known working environments for OpenEquella
  • NC: is continuing work on installation guide
  • CB will send out an update on BlackBoard timeline to mailing list
  • NC: will test D2L and Moodle in the coming weeks
  • CB: is continuing to look into same site cookie handling in the Blackboard integration
    • Issue may be related to EBI tool
  • IS: briefly reviewed renovate bot integration, it started working again without changes
  • IS: will setup shared account for Travis CI to use for releases
  • CB: reviewed security audits, Java version was not flagged
  • CB: Axiom cannot be updated without web services, web services is being sunsetted.
  • CB: Working on a document on committer ship guidelines for oEQ organization
  • CB: The checkfiles task has been helpful for North American adopters, at some point enable by default in oEQ.
  • CB: Researching governance

New Action Items:

  • IS will create issue relating to Java LTS

Specific Topics:

  • IS: A version 1.1 of moodle-mod for oEQ with some fixes these are tracked in the milestones https://github.com/openequella/moodle-mod_openEQUELLA/milestone/2
    • Major add will be the Moodle Privacy API, to help Moodle understand the GDPR compliance of oEQ
  • CB: A new REST version of oEQ Blackboard is ready for testing
    • More features will be added over time
  • CB/IS: GhostCat CVE, related to Tomcat with AJP, should not affect openEquella since most adopters who do not use AJP
    • current release candidate has updated Tomcat and removes secret requirement
    • there are some remaining quirks with Apache not connecting as expected
    • NC: secret is still recommended, including it may help
    • NC: we continue to recommend adopters avoid AJP
    • IS: openEquella does not use AJP by default
    • IS: The default port/host binding may have changed
    • CB: will continue to investigate
  • CB: Release of version 2020.1.0
    • Will be released Monday US time around noon CST
    • IS: Note there is an Australian holiday Monday
  • IS: with recent release there was trouble getting artifacts out of S3
    • Will review AWS release process
    • Adding new share release account may help (same as admin console)
  • CB: Moodle licensing, Apereo has not responded, Ian Dolphin is reaching out to contacts.
  • CB: When openEquella was open sourced there was a test link tool also open sourced, but has not been used, Unicon has been hosting, tests will be archived to Github, and the server will be turned off.

Code Enhancements:

  • CB: Be aware Tika updates will be involved, they will require a Spring and Hibernate update
  • IS: Edelex is looking into moving search into new UI/React
    • working to migrate code from PureScript to TypeScript
    • Updating settings to include a new search section, with some sub-sections
    • Material UI is a major version behind, this version will be updated to latest in the coming weeks
    • REST APIs will be updated to be tidier, specifically settings and configuration will be centralized into more defined collection of APIs
    • CB: would this include removing scala code from these APIs?
      • IS: the plan is to continue to Scala for these APIs

Review tech choices, code structures, direction

  • No topics

Any tech debt concerns

  • No topics

Open PRs to discuss

  • No topics

Q&A:

  • CF: Will material UI update be backported?
    • IS: there is not currently a plan to do this