-
Notifications
You must be signed in to change notification settings - Fork 43
CDM 2019 12
5 Dec 2019 (US) / 6 Dec 2019 (AU)
- Chair: Ian S
- Scribe: Sam F
List of attendees: Samantha Fisher, Chris Beach, Aaron Holland, Cath Fitzgerald, Nick Charles, Christian Murphy, Ian Stevenson, Penghai Zhang, Troy Williams, Zander Potgieter
- 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
- January Meeting - should we shift a bit? (IS)
- Jest testing - no in place (IS)
- GitHub releases version checking in 2019.1.2 and 2019.2 (IS)
- Admin console package build now stand-alone - using Travis GitHub release integration (IS)
- Discuss how to handle documenting configs and special URLs - commented out in the various config files, or on a single page in openequella.github.io or ... See https://github.com/openequella/openEQUELLA/pull/1361 for example discussion. (CB)
- Setup an openEQUELLA GitHub 'machine user' for automations. (IS)
- What places should we review for repo changes (eq > apereo > oEQ) (CB on behalf of the oEQ AB)
- Need a list of committer guidelines to propose to the oEQ AB (CB on behalf of the oEQ AB)
- Please add more
-
Ian and Chris: Share knowledge about travis builds
Nothing has happened as of yet Chris would be interested in setting up a quick call regarding this Next wednesday at 9am
-
look into the process of encorporating checkfiles into oEQ
Chris still holding off on that, some enhancements still to be made Chris has talked to Al about other people testing it
-
Research governance and committersship tools similar to unifiedjs for oEQ
These are tools for automating adding and removing team member access Automatic management of teams based upon a config file Nothing has quite happened regarding this Might be worth waiting for the dev community to expand for this one
-
Chris: Look into JS testing and follow up on existing ticket
Recent work was done to check the version against github This was also wrapped in a jest test Movement has been made towards the direction of using Jest.
-
In Progress - Chris: Ask advisory board about shutting down slack
fell off the radar, will wait for next CDM
-
Look into change to Github releases page and the work involved with migrating away from the server
Now in place with 2019.1.2 onwards Checking against GH releases Previous versions still use the version server Once these versions are unsupported we'll stop the version server
-
January Meeting - should we shift a bit? (IS)
This is the last meeting for 2019 Should we push out the next meeting a week or so
-
Jest testing - now in place (IS)
Jest tests are now in place, can be seen in Travis Does not apply to the new UI, more the AJAX side Planned to be used in the new UI
-
GitHub releases version checking in 2019.1.2 and 2019.2 (IS)
Now in place as of these versions
-
Admin console package build now stand-alone - using Travis GitHub release integration (IS)
The travis build that was doing the admin console package, for 2019.1 onwards - used to store artifacts. Work has been done on CD for this If tagged, the push will publish the release automatically. Long term that would be good for oEQ, would require work
-
Discuss how to handle documenting configs and special URLs - commented out in the various config files, or on a single page in openequella.github.io or ... See https://github.com/openequella/openEQUELLA/pull/1361 for example discussion. (CB)
Several URLs that are not really shown - scheduledtaskdebug.do for example Where should we document these tools, special URLs and config options? Chris will start the ball rolling on this one Note: versions for features should be added where possible
-
Setup an openEQUELLA GitHub 'machine user' for automations. (IS)
At the moment this is done with Penghai's account key Github and travis recommend a machine user (e.g openEquellaHelper) Use this account to generate tokens for automated processes That way the user's permissions dont have to be the same as the bots Ian will look into this.
-
What places should we review for repo changes (eq > apereo > oEQ) (CB on behalf of the oEQ AB
Came up in advisory board Want to check whether we can come up with an informal list of places we should go and check that the links have changed Documentation site, Apereo landing page, oEQ Twitter, edalex site, unicon site
-
Need a list of committer guidelines to propose to the oEQ AB (CB on behalf of the oEQ AB)
We need a set of guidelines for committer ship The advisory board would like to put out a set of guidelines Pull ideas from other open source projects - maybe even apereo projects? E.g active on CDM, reasonable amount of contribution to the repo
- This week a tweak was made to stalebot
Now that the backlog has been cleaned out, decreased the frequency from 60 days to 120 days with 2 weeks until close off.
- We are optimistically hoping for an 2019.2 RC today or monday
Chris will work on his assigned tickets today and Monday oEQ beautification project will go into this release, should be tested
oEQ beautification project - new style sheets for legacy content Taxonomy API refactoring and extension - can now sort whole taxonomy as well as any sub tree Added a config for turning off the staging area removal
Chris is curious about the work on the new UI, is the plan to remove all Purescript Short answer: yes We are starting with re implementing the search UI with React and Typescript to remove the PureScript We will not be adding any more Purescript
Christian created a set of PR regarding tidying up the react side of things Ian is hoping that post-2019.2 we come back in and get these into the repo, along with renovate issues Chris will have an opportunity to pick up some of the dependency updates in the next few months
Troy Williams and Zander Potgieter, welcome!
Just started to use this in learning works in NZ Troy is looking at this im the context of moodle integration Where can we look to start developing? Read CONTRIBUTING.md in the repo Set up a dev environment and get it building Use the mailing list if you get stuck A number of other repos under openequella might be useful - namely openEQUELLA-moodle, moodle-mod_openEQUELLA.
Next meeting: Sam: Scribe, Chris: Chair, date 9th Jan US, 10th Jan AU