Frontend Vision WG - Updates on progress
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
This issue will hold updates on the progress made on each item from the exit criteria in https://about.gitlab.com/company/team/structure/working-groups/frontend-vision/
2023-09-19
| Criteria | DRI | Update |
|---|---|---|
| Add introduction page to frontend documentation, explaining direction and high-level overview of the frontend codebase/architecture. | @f_caplette | |
| Include evolution of codebase over a three-year horizon. | @ntepluhina | |
| List frontend technologies used and the design principles that guide the frontend team's work. | @leipert | |
| Explicitly define deprecation/removal plans, including why these features are being deprecated. | TBD | |
| Communicate outcomes to the broader frontend functional group. | @donaldcook | |
| Discuss and document communication plan, including the frequency of updates from the working group. | @donaldcook | Updated this to 100% complete in exit criteria as cadence has been determined |
| Document the requirements for reusable components outside of GitLab UI. | @pslaughter | |
| Determine DRIs around specific parts of frontend documentation. | @andrei.zubov | |
| Determine how the exception to the main strategy process will work, and if there is a need for a separate area for "wild" ideas. | @ntepluhina | |
| Determine the evaluation and decision-making process for RFCs. | @f_caplette |
2023-09-05
| Criteria | DRI | Update |
|---|---|---|
| Add introduction page to frontend documentation, explaining direction and high-level overview of the frontend codebase/architecture. |
@f_caplette |
Global navigation is restructured: |
| Include evolution of codebase over a three-year horizon. | ||
| List frontend technologies used and the design principles that guide the frontend team's work. | ||
| Explicitly define deprecation/removal plans, including why these features are being deprecated. | TBD | |
| Communicate outcomes to the broader frontend functional group. |
[Internal] |
|
| Discuss and document communication plan, including the frequency of updates from the working group. | Updated this to 100% complete in exit criteria as cadence has been determined | |
| Document the requirements for reusable components outside of GitLab UI. |
This week, we'll push forward #422903 (closed) to the wider FE team and see if we can get manager/director interest for the formation of a WG. |
|
|
Determine DRIs around specific parts of frontend documentation. |
||
| Determine how the exception to the main strategy process will work, and if there is a need for a separate area for "wild" ideas. | ||
| Determine the evaluation and decision-making process for RFCs. |
@f_caplette |
N/A |
2023-08-22
| Criteria | DRI | Update |
|---|---|---|
| Add introduction page to frontend documentation, explaining direction and high-level overview of the frontend codebase/architecture. | @f_caplette | Restructur of the new index page on the way. Make it more organic, remove the list of headers and links AND update some sections that were outdated or lacking information. This might take multiple MRs |
| Include evolution of codebase over a three-year horizon. | @ntepluhina | No updates, I was on vacation |
| List frontend technologies used and the design principles that guide the frontend team's work. | @leipert | |
| Explicitly define deprecation/removal plans, including why these features are being deprecated. | TBD | |
| Communicate outcomes to the broader frontend functional group. | @donaldcook | [Internal] |
| Discuss and document communication plan, including the frequency of updates from the working group. | @donaldcook | Updated this to 100% complete in exit criteria as cadence has been determined |
| Document the requirements for reusable components outside of GitLab UI. | @pslaughter | |
| Determine DRIs around specific parts of frontend documentation. | @andrei.zubov | No updates since the last sync |
| Determine how the exception to the main strategy process will work, and if there is a need for a separate area for "wild" ideas. | @ntepluhina | No updates, I was on vacation |
| Determine the evaluation and decision-making process for RFCs. | @f_caplette | No progress here |
2023-08-08
| Criteria | DRI | Update |
|---|---|---|
| Add introduction page to frontend documentation, explaining direction and high-level overview of the frontend codebase/architecture. | @f_caplette | This has not moved since the last update. The intro page first version is merged and we've added a section on moving away from VueX. |
| Include evolution of codebase over a three-year horizon. | @ntepluhina | The first iteration was merged |
| List frontend technologies used and the design principles that guide the frontend team's work. | @leipert | |
| Explicitly define deprecation/removal plans, including why these features are being deprecated. | TBD | |
| Communicate outcomes to the broader frontend functional group. | @donaldcook | [Internal] |
| Discuss and document communication plan, including the frequency of updates from the working group. | @donaldcook | Updated this to 100% complete in exit criteria as cadence has been determined |
| Document the requirements for reusable components outside of GitLab UI. | @pslaughter | This hasn't moved yet, but it's next up on my TODO list. I'm looking into diving into what Modular Monolith could look like in the FE and how we'll establish a vision moving forward. |
| Determine DRIs around specific parts of frontend documentation. | @andrei.zubov | At the moment we have covered 25 topics out of 33. Subjectively most important ones have DRIs. Introducing the process and tooling around making changes to these pages is still pending. |
| Determine how the exception to the main strategy process will work, and if there is a need for a separate area for "wild" ideas. | @ntepluhina | |
| Determine the evaluation and decision-making process for RFCs. | @f_caplette | I did some research that I wrote about in: #417615 (comment 1496135376) which lead to some interesting finding. Tl;dr -> RFCs should empower individuals but are highly disruptive. MR incoming |
2023-07-25
| Criteria | DRI | Update |
|---|---|---|
| Add introduction page to frontend documentation, explaining direction and high-level overview of the frontend codebase/architecture. | @f_caplette | The initial MR has been merged! |
| Include evolution of codebase over a three-year horizon. | @ntepluhina | Created a draft of new "frontend goals" chapter (name is a subject for discussion) in the docs and described the goal for cluster SPAs: !127460 (diffs) |
| List frontend technologies used and the design principles that guide the frontend team's work. | @leipert | |
| Explicitly define deprecation/removal plans, including why these features are being deprecated. | TBD | |
| Communicate outcomes to the broader frontend functional group. | @donaldcook | @f_caplette communicated merging of MR on landing page: https://gitlab.slack.com/archives/C0GQHHPGW/p1689861079433029 |
| Discuss and document communication plan, including the frequency of updates from the working group. | @donaldcook | Updated frontend team on DRIs and bi-weekly cadence (aligned to meeting schedule) of updates: https://gitlab.slack.com/archives/C0GQHHPGW/p1689728990041869 |
| Document the requirements for reusable components outside of GitLab UI. | @pslaughter | Starting an RFC about enforcing top-level package cohesion. The goal of this is to help us be explicit and better organized about what's actually meant to be reusable. |
| Determine DRIs around specific parts of frontend documentation. | @andrei.zubov | At the moment we have covered 24 topics out of 33. Subjectively most important ones have DRIs except Vuex page. The next step is to introduce the process and tooling around making changes to these pages. |
| Determine how the exception to the main strategy process will work, and if there is a need for a separate area for "wild" ideas. | @ntepluhina | |
| Determine the evaluation and decision-making process for RFCs. | @f_caplette | No update right now, as I am wrapping up the initial work for the new guidelines, I am going to start working on this as well. |
Edited by 🤖 GitLab Bot 🤖