<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=360690) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal - Making Discussion Comments (notes) User Friendly - Modifying Individual notes in issue and merge requests look like chat messages - Showing Edit History of comments (notes) - Adding Upstream Fetch Button in Forks - Enable fetching upstream in Fork Projects from the web IDE <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> ### Details 1. Right Now GitLab Discussions are harder to read and not friendly to new comers, as the UI is a little bit unfriendly compared to GitHub and Gitea, which uses a chat like discussion UI which most users are familiar with. Another issue in Comments when a developer's comments was to be edited by maintainer, there should be a history of the changes, and only administrators and Owners should have permission to delete those histories 2. Forked projects in GitLab can't fetch upstream project if new commits were to be added in the parent project which can be a little bit tiring to new comers, or user who have used GitHub in the past ### Design Proposals 1. Commenting user avatar placed outside of comment area, and the comment area made chat message like area 2. Add a fetch upstream Button in forked project's Web IDE <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ --> ~"Beautifying our UI" ~"UX Research request" ~"Category:Web IDE" ~"UX Dev Team"