AiiDAlab Meeting Notes 2023-01-24

AiiDAlab Meeting Notes 2023-01-24 === ###### tags: `Meeting` :::info - **Location:** https://psich.zoom.us/j/69116696576 *(Please request password on slack)* - **Date:** Jan 24th, 2023 11h (CET) - **Agenda** 1. How to running biweekly meeting discussio `30 min` 1. General Updates (Based on Roadmap) `30 min` (This is for next time) 1. Technical discussions (This time we'll focus on refactoring the QeApp architecture) `30 min` - **Participants:** - Jason [PSI] (jy) - Xing [PSI] (xw) - Sasha [Empa] (ay) - Marnik [EPFL] (mb) - Carlo [Empa] (cp) - Daniel [ISPG] (dh) - Andres [Empa] (ao) - **Host:** jy - **Reference:** - Roadmap: https://github.com/orgs/aiidalab/projects/7/views/2 - @cpignedoli could you share the notes at MARVEL retreat for the AiiDAlab app structure redesign? ::: ### Discussion on how to running the biweekly meeting I propose that everyone join the meeting using the meeting notes to list the tasks they are responsible as 1st RP, and describe the status of tasks as 2nd RP. As the 1st responsible person (RP), he/she is responsible for proposing the method to solving the issue or implementing the features. That is he/she need to opening the pull requests, making the decision of new feature implementation and coordinate for the deployments etc. Every tasks in the roadmap need to have a 2nd RP, to help 1st RP to review the pull requests to correct the route of implementations. To avoid 2nd RP blindly approve the implementation or not actively help the 1st RP, the 2nd RP need to report the status of task progress. We keep the roadmap as the records for the tasks, during the biweekly meeting, we running the meeting looking at the hackmd notes, where the notes are converted from the roadmap. It is encourage that everyone in the AiiDAlab team has at least one on task as 1st RP and at least one as 2nd RP (some developer has more than one 1st RP tasks so need to other one has more than one tasks as 2nd RP). The goal is to: 1. Make the biweekly meeting more efficient rather than dorwned in the technical details. 2. Everyone join the meeting has tasks to do before the next AiiDAlab meeting. It is okay to mention they are focus on other stuff, but once the person anounce to devote on a task he need to make a deliverable (close the high priority issue.) before next meeting. 3. Encourage the discussion besides the biweekly meetings. The responsiblities are blancely loaded to developers. Every task has two people make responsibility as 1st responsible person (RP) and 2nd RP. The discussion should not only happened in the biweekly meeting, but amoung the 1RP and 2RP frequently to settle down the issue and make the decisions. ### The priority of the tasks - High: Must give the deliverable ~~before next biweekly meeting.~~ ?For the incomming release. - Medium: Relatevily ~~long term~~ but must delivered before the next release. We need a DDL also for the for this priority. - Low: Ask by no one, but you want to tackle it some day. - No priority: all other new things not yet noticed by others. ### Meeting notes for 1st session discussion - Daniel: In the hackmd, people writing down things in their sence what need to be done in the next two weeks. :spiral_note_pad: Notes -- Jason: * 1st RP * https://github.com/aiidalab/issues/issues/1 Deploy AiiDAlab @ THEOS#1 * https://github.com/aiidalab/aiidalab-qe/issues/339 The QeApp has aiida2.x supported version released but not supported by the current materials cloud aiidalab deployment (as an example how the 2nd RP is assigned or self-assigned in the meeting.) * 2nd RP * Xing is working on replace the old aiidalab index page https://www.materialscloud.org/work/aiidalab with https://aiidalab.github.io/ We decide to move the role of every person (only keep PI), update shape of the pictures and use the current images. * Sasha is working on the script to migrate AiiDAlab postgresql database automatically. The PR open at https://github.com/aiidateam/aiida-prerequisites/pull/63. I test it locally but stuck in a the step says that the user `aiida` already existed in DB. * misc but very important: * The demo AiiDAlab for MARVEL review on Sept. On azure maybe. The goal is to user can see quickly everything about QeApp without launching calculations and waiting. The authentication need to be as dummy as possible, maybe edu-ID as used by Switchdrive. * The Materials Cloud deployment not migrated and QeApp is broken if updated to the latest version. Xing: * 1st RP * New aiidalab website https://aiidalab.github.io/. Please visit this link https://aiidalab.github.io/about/, check the infos (photo, name, affiliation), please let me know if there is any typo. Send me a new photo if you want to update it. * * 2nd RP * Deploy AiiDAlab on THEOS server. (.: what the status of deployment and what Jason need to finalized, what I(Xing) need to review and test.)