Skip to content

Participation in contribution themed month: frontend

This issue is a single source of truth for my activities during contribution themed month. It will be linked in MRs opened by community contributors

🕰 Schedule

  • 1️⃣ 📷 before Apr 24. Create videos regarding "quick setup" for frontend contributors in three languages:

  • 2️⃣ 📓 before Apr 24 prepare list of at least 15 issues which I would like to provide support. State that people are welcome to work on anything with Seeking community contributions frontend labels, but this list of issues means that I've initially analyzed them and ready to provide support. Make sure issues have three different levels of complexities (simple just to scratch gitlab processes, require basic JS knowledge, require Vue knowledge). Have a couple of them ready for someone who would like to commit more than others

  • 3️⃣ 📣 Apr 24 Make an announcement on my social networks, linking videos and this issues. Create separate ukrainian/russian speaking group in messenger. Communicate https://gitter.im/gitlab/contributors as an official channel, make clear statement that my group in messeger is not affiliated with GitLab by any means and is my personal activity

  • 4️⃣ 💻 Run three live-support session providing people with a zoom-link where they can jump-in and obtain help for any struggles they encounter:

    • 📆 Apr 25
    • 📆 Apr 28
    • 📆 Apr 30

  • 5️⃣ work with community contributions to finalize these contributions and move them towards the merge line

  • 6️⃣ 🎉 Celebrate!

Goal

My goal is to have at least 10 contributions done within April as a part of this activity

Suggested issues

Everyone can contribute! You can seek my help with any frontend issue. This list is just issues I've verified and find them suitable for our time scale.

Black circles describe my feeling on issue complexity - from ⬤◯◯◯◯ to ⬤⬤⬤⬤⬤. Compexity is not just about "complexity of coding" - but includes requirements about various GitLab features, etc. and might serve as a wild estimate how long it will take to complete an issue, but as usual - your mileage may wary

First column ( 🙇 ) indicates if issue is 🔍 looking for community contributor hero to take it or 🙇 if it is already assigned to a community contributor. ✅ if it is done

🙇 Complexity Issue Comments
✅ ⬤◯◯◯◯ Streamline decision making for importing a project by URL does not require any JS knowledge. Just reordering elements in HAML
🙇 ⬤◯◯◯◯ Remove unused computed prop shouldDisplayFilters just a cleanup on Vue component. Perfect for getting your hands dirty with Gitlab MR review process 😄
✅ ⬤◯◯◯◯ Fix milestone overflow on smaller viewports minor CSS-related work in HAML
✅ ⬤⬤◯◯◯ Group Import history - Rename 'New group' to 'Destination group'
✅ ⬤⬤◯◯◯ Update all importers filtering field visuals is 2/5 just because requires some messing with Vue tests 😄
✅ ⬤⬤◯◯◯ Checkbox is disabled when returning to import from external repo does not involves any Vue-specific knowledge
🙇 ⬤⬤◯◯◯ Run CI/CD pipelines for external repositories - form should be hidden by default does not involves any Vue-specific knowledge
✅ ⬤⬤◯◯◯ Minor improvements to the shared confirm danger form has storybook to take a quick-look 🎉
🙇 ⬤⬤⬤◯◯ Update cleanup icon container registry
✅ ⬤⬤⬤◯◯ Focus color picker input when selecting input label this will require some investigation why we're generating double color-picker id in html (might be an issue and fix in gitlab-ui or here)
🙇 ⬤⬤⬤◯◯ Group Import history - Page size not persisted requires minor Vue experience and will require some messing with @vue/test-utils stubs
✅ ⬤⬤⬤◯◯ Group Import history - Link to history page from group import page involves some tiny HAML work to pass prop
✅ ⬤⬤⬤◯◯ Auto-focus "Project" selector when adding new issue to group-level board
🙇 ⬤⬤⬤⬤◯ Migrate upload license page to Vue
🙇 ⬤⬤⬤⬤⬤ Delete Releases in UI of Release Page this involves building small feature in gitlab - ability to delete releases. It involves multiple Vue components, altering tests, etc. Take a look at this one if you have enough time to contribute - there might be multiple back-and-forth during review, I will be happy to provide proper guidance and assistance 😄
Edited by Illya Klymov