Meeting notes in space

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3326345256/2022-02-08+DevEnv+Meeting+notes

1. We will use GitHub issues to keep track of our tasks
2. We will create a new public repo in the edx GitHub org to hold our issues
3. The project board will be org-level, to allow linking to issues in other repos later
4. Employees who wish to bring issues about development environment work will file a ticket on a issue specifically meant to be triaged, and from there the WG will decide whether to punt the ticket to a squad, work on it ourselves, or follow the Tutor process for errors in Tutor core

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3345023256/2022-02-23+DevEnv+Meeting+notes

1. If we need to get something from tCRIL, create a ticket in the 2U adoption project. Let them triage it. If a ticket is assigned to us, we can ask tCRIL to come to our meetings.
2. Internal requests from 2U engineers can be reported in Slack, and then triaged by the working group.
3. We are going to continue to use Docker Desktop for Macs for now and are planning on paying for it.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3375038554/2022-03-22+Marketing+WG

1. To update the Code of Conduct
2. To record future meetings to share with the community
3. To push Wikipedia article back to after the conference

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3395747843/2022-04-06+Marketing+WG

1. Members should start reporting their hours for each sprint

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3417735215/2022-05-04+Marketing+WG

1. Public sessions (webinars) will now take place on a monthly cadence instead of quarterly.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3594911745/2022-12-01+Frontend+Working+Group+Meeting+Minutes

1. The Frontend Working Group will start using asynchronous channels of communication more, in particular the #wg-frontend Slack channel, with the dual goal of making meeting attendance optional, but also making meetings more like meetups: less frequent and more interesting.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3589079058/2022-12-05+BTR+Meeting+notes

1. The Olive release ceremony will happen on Friday, December 9, 2022 Monday, December 12, 2022, at 15:00 UTC.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3595141121/2022-12-08+Frontend+Working+Group+Meeting+Minutes

1. The Frontend Development backlog will start being groomed as a regular communal activity of this group.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3612803073/2022-12-19+BTR+Meeting+notes

1. Our next meeting is going to be on January 9th, 2023, because nobody will be around on January 2nd, and January 16th is a federal holiday in the US.
2. BTR will pick a name for the “Q” release in January via a ranked vote on options members nominate

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3609264129/2022-12-22+Frontend+Working+Group+Meeting+Minutes

1. Due to holidays and vacations, the next 11:00 UTC meeting will be on January 12, 2023, and the next 15:00 UTC one will be on January 19, 2023.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3620012033/2023-01-09+BTR+Meeting+notes

1. Instead of having Tutor apply patches on top of release tags, when deemed sufficiently urgent we will consider tagging the next point release earlier

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3661725697/2023-02-09+Frontend+Working+Group+Meeting+Minutes

1. After a piece of code undergoes the proper deprecation process, we should strive to actually remote it! Otherwise, we’re saddled with a rotting mass of tech debt that no-one cares to maintain, but must be dealt with.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3684597807/2023-02-24+FC-0011+Meeting+notes

1. General alignment on RG-POC as solid basis (based on demo) for accelerating mobile development, though much more work to ratify this + get input from community

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3695411217/2023-03-08+Data+WG+Meeting+notes

1. test

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3712581633/2023-03-24+FC-0011+Meeting+notes

1. Use of a survey to gather input on prioritization for capabilities / features in the existing Open edX Mobile applications from the community with simplified P1,P2,P3 scheme.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3717464065/2023-04-03+BTR+Meeting+notes

1. Olive.3 tag and Palm.1 cutting will be done on Tuesday, April 11 instead of Monday, April 10 due to the Easter holiday.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3742040068/2023-05-04+Frontend+Working+Group+Meeting+Notes

1. If the Node 18 PRs don’t make it to master in time, we will merge them to the Palm branches so that the Tutor release can all be on the same version

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3756720129/2023-05-11+Meeting+notes

1. Scheduled recurring meeting for FC-0011 / Mobile

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3766910998/2023-05-24+Translation+WG+Meeting

1. We are having our meeting as
2. We are moving from Trello to wiki
3. We more from Trello to github board

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3757735951/2023-05-25+Frontend+Working+Group+Meeting+Notes

1. (Majority, but not unanimous) When deprecation .env files, their replacement shouldn't be committed to MFE repos with hard-coded assumptions about the environment they're running in
2. No new code should be written in enzyme as of today: the DEPR process will start ASAP