[Koha-devel] Vote on Vue3 (for ERM) at the next dev meeting

[dcook at prosentient.com.au]

Voting on it at the next dev meeting sounds like a good idea, and I think that all your points are reasonable. I probably won't be at the dev meeting, but +1 for moving ahead with Vue3 for the ERM module. (I wonder if we should have pre-polls/mail-in votes for dev meetings sometimes...)

I think that my only concern is with the current implementation. As I note at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30225#c13, I think we should be using more generic CRUD components and then inheriting from those. However, that's arguably a naïve comment, since I don't have much experience with Vue3 myself (beyond reading and 1 hello world exercise). That said, I would guess that all of us are inexperienced with Vue3 though, so that might pose some QA difficulties... 

Actually, I notice in https://lists.katipo.co.nz/pipermail/koha/2022-February/057447.html that it mentions that a team of people from Bywater, BibLibre, and PTFS Europe are supporting the eRM project. Are they gaining experience with Vue3 as well? 

I would be interested in getting more involved with this project as a Vue3 project in terms of development and QA. I'll email Jonathan Fielding more about that.

Here's hoping a majority agree about moving forward with the ERM module being written in Vue3. 

David Cook
Senior Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia

Office: 02 9212 0899
Online: 02 8005 0595

-----Original Message-----
From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf Of Jonathan Druart
Sent: Friday, 8 April 2022 5:44 PM
To: koha-devel <koha-devel at lists.koha-community.org>
Subject: [Koha-devel] Vote on Vue3 (for ERM) at the next dev meeting

Hi devs,

Could we vote at the next dev meeting that the ERM module will be written in Vue3 and that it will not be a problem for its integration into Koha?

This module will contain a lot of CRUD operations and simple forms.
And so all the necessary REST API routes will be provided from the beginning.
I thought it would be a good candidate to introduce a new and modern solution to Koha.
Using it in an isolated module will allow us to try it, find the different problems we can face, fix them, and not force other developers to be onboard if they don't want to.

There is already a POC of this module using Vue3, with the different REST API routes, and UI testing using Cypress (see link below).

Other solutions are:
* Use another JS framework (but in that case you will show us on the "cities" view a simple implementation case)
* Use the old/traditional way

Links related to ERM and Vue3:
* Electronic Resource Management for Koha https://lists.katipo.co.nz/pipermail/koha/2022-February/057447.html
* Sandbox - https://staff-erm.sandboxes.biblibre.eu/cgi-bin/koha/erm/agreements.pl
* Git remote branch - https://gitlab.com/joubu/Koha/-/commits/erm
* Cities rewrites
** Bug 30160 - Rewrite cities admin view in React
** Bug 30225 - Rewrite cities admin view in Vue
** "I played with React"
https://lists.koha-community.org/pipermail/koha-devel/2022-February/046926.html
* "I played with Cypress (and ERM and Vue)"
https://lists.koha-community.org/pipermail/koha-devel/2022-March/046956.html

Cheers,
Jonathan
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/