Difference between revisions of "Get Involved/design"

(First shot at revamping this page)
(→‎Know Yourself: Make it a list)
 
(21 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
== About the VDG ==
 
== About the VDG ==
[[File:Konqui_artistic_cropped.png|frameless|right|200px|]]
+
[[File:Mascot konqi-app-graphics.png|frameless|right|200px|]]
The VDG started out as the Visual Design Group, but has grown into a team dedicated to the whole user experience, including what is often called human interface design. The aim is to help KDE create software that is both beautiful and a pleasure to use.
+
The VDG started out as the Visual Design Group, but has grown into a team dedicated to the whole user experience, including what is often called human interface design. The aim is to help KDE create software that is both beautiful and a pleasure to use. VDG has created and maintains the [https://hig.kde.org/ KDE Human Interface Guidelines] and the [[Get_Involved/design/Breeze | Breeze theme]] used throughout KDE Plasma and applications.
  
VDG is always looking for people with skills in art, visual design, and human-computer interaction--or even just an interest in elegant design! If you have good ideas about how software should look and behave, you are a designer too, and we'd love you to join in.
+
VDG is always looking for people with skills in art, visual design, and human-computer interaction--or even just an interest in elegant design! If you have good ideas about how software should look and behave, you are a designer too, and we'd love you to join in. Our group regularly interfaces with users, developers, and the Promo team, so flexibility and the ability to communicate with many different kinds of people are a boon.
  
 +
{{Note|VDG task and project tracking will be in GitLab in the future once the GitLab migration is complete. However for now we still use Phabricator for this.)}}
  
== Current projects ==
 
VDG's current projects are listed on the [https://phabricator.kde.org/project/board/89/ Phabricator workboard].
 
  
 +
== Current Projects ==
 +
Feel free to have a look at VDG's current projects, which are are listed on the [https://phabricator.kde.org/project/board/89/ Phabricator workboard]. In addition, here are some timeless ways to get involved in ongoing work:
 +
* Learn how to design Breeze icons by reading [https://hig.kde.org/style/icons/index.html the applicable HIG page], and then work on [https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Icons&list_id=1536878&product=Breeze&query_format=advanced Breeze icon bugs]. Here's [[Guidelines and HOWTOs/Submit an icon | how to submit an icon]].
 +
* Submit patches (using [https://invent.kde.org/websites/hig-kde-org/merge_requests GitLab]) for corrections and improvements to the [http://hig.kde.org Human Interface Guidelines]
  
== Communication and workflow ==
+
== Communication and Workflow ==
First, subscribe to the [https://mail.kde.org/mailman/listinfo/visual-design visual-design] mailing list to hear about general news and updates.
+
First, subscribe to the [https://mail.kde.org/mailman/listinfo/visual-design visual-design] mailing list to hear about general news and updates. You'll also want to become a member of the VDG team in GitLab. YOu can request access here: https://invent.kde.org/groups/teams/vdg/-/group_members Finally, join the [https://webchat.kde.org/#/room/#kde-vdg:kde.org #kde-vdg] channel on [[Matrix]] or the freenode [[Internet Relay Chat | IRC channel]] (which is bridged to the [https://telegram.me/vdgmainroom VDG] Telegram room, if you prefer [[Telegram]]).
  
Most VDG discussions start out informally, in the [http://webchat.freenode.net/?channels=kde-vdg #kde-vdg] freenode [[Internet Relay Chat | IRC channel]] (which is bridged to the [https://telegram.me/vdgmainroom VDG] Telegram room, if you prefer [[Telegram]]).
+
Most VDG discussions start out informally, in the chat channel. Once there's general agreement in the real-time chat, the discussion moves to a Phabricator task. The goal here is to open the discussion to include developers, and make the proposal more concrete using images and mockups. Mockups can be created using KDE's [[KDE Visual Design Group/HIG/MockupToolkit | Mockup Toolkit]].
  
Once there's general agreement in the real-time chat, the discussion moves to a Phabricator task. To be apprised of these, become a watcher for the [https://phabricator.kde.org/project/profile/89/ VDG project] in Phabricator. It's important that VDG Phabricator tasks task include as subscribers all the developers who may be affected by the proposed work. If there's a pre-existing task for the work, use that. If the discussion is proposing new work and there is no pre-existing Phabricator task, create one. Try to honestly and fairly summarize the discussion and initial VDG conclusion when writing the task's initial description. It's important not to lose context or history!
+
It's important that VDG Phabricator tasks subscribe all the developers who may be affected by the proposed work. Try to honestly and fairly summarize the discussion and initial VDG conclusion when writing the task's initial description. It's important not to lose context or history!
  
In the Phabricator task, it's common for the details or scope to change based on developer feedback. This is normal! Developers have a better idea of what's technically possible or reasonable to change. Listen to developer feedback and change the design accordingly, where necessary. At the same time, encourage them to listen to your expertise, and gently stand your ground if a developer tries to dictate design decisions to you.
+
In the Phabricator task, it's common for the details or scope to change based on developer feedback. This is normal! Developers have a better idea of what's technically possible or reasonable to change. Listen to developer feedback and change the design accordingly. At the same time, encourage them to listen to your expertise, and gently stand your ground if a developer tries to dictate design decisions to you.
  
 +
Once there's general agreement in the Phabricator task, work should begin and folks can start submitting patches!
  
== Know thyself ==
+
== Know Yourself ==
In a highly technical field like programming, it's easy to know the limits of your expertise. This is more difficult in more subjective fields like art and design, and it's very important to have a firm grasp of your own limitations. If you know you're not very artistically skilled, don't involve yourself heavily in icon design work, for example. If you don't have any skill or background in human/computer interaction, leave those discussions to the pros!
+
In a highly technical field like programming, it's easy to know the limits of your expertise. This is more difficult in subjective fields like art and design, and it's very important to have a firm grasp of your own limitations. For example:
 +
* If you know you're not very artistically skilled, don't involve yourself heavily in design work, and accept direction from experienced designers
 +
* If you produce designs that people aren't very enthusiastic about, try to solicit honest feedback regarding what could be improved rather than pushing on them
 +
* If you don't have any skill or background in human/computer interaction, leave those discussions to the pros
  
 +
== Lessons learned ==
 +
Over the years, certain design conversations and ideas seem to recur. We have collected the result at [[Get Involved/Design/Lessons Learned]].
  
{{TODO|ask the VDG about mentoring - add a section to [[Mentoring]] and link from here}}
+
==Old Things==
__NOTOC__
+
* [[KDE_Visual_Design_Group/Archive | Archive of outdated documents that may still be useful for reference]]

Latest revision as of 23:49, 23 June 2020

About the VDG

Mascot konqi-app-graphics.png

The VDG started out as the Visual Design Group, but has grown into a team dedicated to the whole user experience, including what is often called human interface design. The aim is to help KDE create software that is both beautiful and a pleasure to use. VDG has created and maintains the KDE Human Interface Guidelines and the Breeze theme used throughout KDE Plasma and applications.

VDG is always looking for people with skills in art, visual design, and human-computer interaction--or even just an interest in elegant design! If you have good ideas about how software should look and behave, you are a designer too, and we'd love you to join in. Our group regularly interfaces with users, developers, and the Promo team, so flexibility and the ability to communicate with many different kinds of people are a boon.

Note
VDG task and project tracking will be in GitLab in the future once the GitLab migration is complete. However for now we still use Phabricator for this.)


Current Projects

Feel free to have a look at VDG's current projects, which are are listed on the Phabricator workboard. In addition, here are some timeless ways to get involved in ongoing work:

Communication and Workflow

First, subscribe to the visual-design mailing list to hear about general news and updates. You'll also want to become a member of the VDG team in GitLab. YOu can request access here: https://invent.kde.org/groups/teams/vdg/-/group_members Finally, join the #kde-vdg channel on Matrix or the freenode IRC channel (which is bridged to the VDG Telegram room, if you prefer Telegram).

Most VDG discussions start out informally, in the chat channel. Once there's general agreement in the real-time chat, the discussion moves to a Phabricator task. The goal here is to open the discussion to include developers, and make the proposal more concrete using images and mockups. Mockups can be created using KDE's Mockup Toolkit.

It's important that VDG Phabricator tasks subscribe all the developers who may be affected by the proposed work. Try to honestly and fairly summarize the discussion and initial VDG conclusion when writing the task's initial description. It's important not to lose context or history!

In the Phabricator task, it's common for the details or scope to change based on developer feedback. This is normal! Developers have a better idea of what's technically possible or reasonable to change. Listen to developer feedback and change the design accordingly. At the same time, encourage them to listen to your expertise, and gently stand your ground if a developer tries to dictate design decisions to you.

Once there's general agreement in the Phabricator task, work should begin and folks can start submitting patches!

Know Yourself

In a highly technical field like programming, it's easy to know the limits of your expertise. This is more difficult in subjective fields like art and design, and it's very important to have a firm grasp of your own limitations. For example:

  • If you know you're not very artistically skilled, don't involve yourself heavily in design work, and accept direction from experienced designers
  • If you produce designs that people aren't very enthusiastic about, try to solicit honest feedback regarding what could be improved rather than pushing on them
  • If you don't have any skill or background in human/computer interaction, leave those discussions to the pros

Lessons learned

Over the years, certain design conversations and ideas seem to recur. We have collected the result at Get Involved/Design/Lessons Learned.

Old Things


This page was last edited on 23 June 2020, at 23:49. Content is available under Creative Commons License SA 4.0 unless otherwise noted.