Skip to content

CDM 2019 06

Jump to bottom
Nick Charles edited this page Jul 4, 2019 · 7 revisions

openEQUELLA Community Dev Meeting June 2019

2019-06-13 (US) / 2019-06-14 (AU)

Attendees

NickC, IanS, ChrisB, ChristianM, Penghai, JolseM, SamF, AaronH, JoeS

  • Chair : Chris B
  • Scribe : Nick C

Working Agenda

Specific Topics

  • Release branch now in play
  • Should we stay with SBT or move to Gradle (IS)
  • Should we abide by a Design System, and have that be part of the PR process? (CB)
    • Adopters will most likely have different Design Systems, so we need to consider deep flexibility
  • Should we break out parts of the core code into components that we can pull in from Maven? (CB)
    • This would have a high value add for integrations where the oEQ community does not control when the app on the other side (such as Blackboard and Canvas) will upgrade and possibly affect the stability of the integration.
  • Consider a better method (Trello?) to handle action items. (CB)

Please add more.

General Topics

  • Review Action Items
  • Specific Topics
  • Discuss code enhancements since last CDM
  • Review tech choices, code structures, direction
  • Any tech debt concerns
  • Open PRs to discuss
  • Q&A

Minutes

Action Items Review

  • Create ticket for JestJS on unit tests - Chris B
    • Still in progress, will be carried over to next meeting's action items
  • Figure out what to do with Tiny MCE's license - Chris B
    • Still waiting to hear from Apereo legal
  • Send out a note for community to agree / align on abbreviation - Chris B
    • Carrying over
  • Ian to review PR generalize headers soon - Ian S
    • Carrying over

Specific Topics

  • Release branch now in play

    • Hoping to release at the end of July
    • Any new releases should be made in release branch. This branch will be merged into develop upon release of 2019.1

  • Should we stay with SBT or move to Gradle

    • Ian suggests that we move to use Gradle over SBT as openEQUELLA’s build tool of choice. Gradle is quicker, and has better ide/community support.
    • Chris B is onboard - more familiar with gradle
    • It will be a gradual move, import/export utils now use gradle, as well as the updated Blackboard building block.

  • Design System

    • Chris B asks if the Edalex has been using any design system for new ui development
    • Jolse M / Nick C indicates that we have just been using the standard material design guidelines.
    • We could expand it out in the future to make it more openEQUELLA specific

  • Should we break out parts of the core code into components that we can pull in from Maven?

    • Could make it easier to support client’s LMS integrations (eg. Blackboard, canvas)
    • Chris B has seen that uPortal uses a similar concept. But openEQUELLA’s architecture and install path may mean it’s not applicable in the same way
    • Ian S indicates that Edalex is already doing something like this, with the new cloud provider functionality, as well as the admin console package.
    • Jolse S says his main concern would be around version compatibility issues. It may not be worth doing unless demand is high enough.
    • Chris B agrees that there may not be enough need to make the effort worthwhile. Will explore further down the line if necessary.

  • Consider a better method (Trello?) to handle action items.

    • Our current way of tracking action items in the wiki can cause them to be missed, and aren’t easily trackable
    • Ian S and Chris B both agree that trello could be a good alternative
    • Christian M indicates that it may be possible to integrate a trello board directly into the wiki. He will investigate further.

  • Code enhancements

    • Admin console package beta release
    • Works with 2019.1
    • Comes bundled with open jre
    • Everyone encouraged to try it out

  • Removing applets

    • Both Unicon and Edalex are waiting to hear back from key clients that use the applet functionality in openEQUELLA

  • Tech debt

    • IE11 compatibility with new ui
      • Edalex have made efforts to get the new ui running better in IE11
      • Highlights need to look into cross browser autotests on the new ui. Currently autotests are run using the old ui on a chrome browser

  • React router / template changes in new ui

    • Navigating around pages should be snappier now

  • Template system has been rewritten in typescript, to aid in maintainability

  • Open PRs

    • #694 Update openJDK docker digests
      • Jolse to look into further

  • Update JodaTime

    • Need to find out everywhere in code that uses the library
    • Ian S concerned about test coverage in that area

  • Axios update

    • Used in blackboard, Ian suggested changes to Chris to make
    • Won’t make it into the 2019.1 release

  • Q&A

    • 4 Issues still assigned to Chris B in 2019.1 Milestone
      • Chris to look at closing the issues

Action Items

  • Create ticket for JestJS on unit tests (CB)
  • Follow up with Apereo legal about TinyMCE licence (CB)
  • Send out a note for community to agree / align on abbreviation (CB)
  • Ian to review PR generalize headers (IS)
  • Investigate integrating Trello into wiki (CM)
  • Open PRs (all)

Navigation

Clone this wiki locally