Difference between revisions of "Get Involved/design"

Jump to: navigation, search
m (Entriken moved page Getinvolved/art to Get Involved/art: Consistent name)
 
(15 intermediate revisions by 4 users not shown)
Line 1: Line 1:
__NOTOC__
+
== About the VDG ==
== Becoming a KDE Artist ==
+
[[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. VDG maintains and updates the [https://hig.kde.org/ KDE Human Interface Guidelines].
 +
 
 +
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.
  
[[Image:art.png|Art|left]] Are you able to create images that move people? Projects in KDE are always in need of good art. Icons, splash screens and themes create an identity for an application. By creating art for the KDE project, your portfolio will be seen by a large audience and will help KDE products have a strong branding.
 
  
== Communicating with the team ==
+
== 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/icon.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 [[Infrastructure/Phabricator | Phabricator]]) for corrections and improvements to the [http://hig.kde.org Human Interface Guidelines]
  
New KDE Artists are encouraged to start at [irc://irc.kde.org/kde-artists <nowiki>#kde-artists</nowiki>] on irc.freenode.net, (or [http://kde.org/support/#irc learn more about IRC]), which is the most active. The team also discusses activities on the [http://mail.kde.org/mailman/listinfo/kde-artists kde-artists mailing list], [http://kde.org/support/#mailinglists learn about mailing lists].
 
  
== Documentation ==
+
== 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. You'll also want to become a watcher for the [https://phabricator.kde.org/project/profile/89/ VDG project] in Phabricator. 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]]).
  
The art in KDE follows certain guidelines, you will want to keep these for reference. These links may be outdated, so it is always best to check with the team:
+
Most VDG discussions start out informally, in IRC. 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]] and should be hosted on [https://phabricator.kde.org/pholio/ Pholio].
  
* [http://web.archive.org/web/20080116142850/kde-artists.org/node/102 Artwork Guidelines] - explain the proper use of logo and implementation of splash screens
+
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!
* [http://techbase.kde.org/Projects/Oxygen/Style Icon Guidelines] - detail the proper creation of icons
 
* [http://techbase.kde.org/Projects/Oxygen/Style#Color_Usage Oxygen Color Palette] - colors for KDE 4
 
  
== Tasks ==
+
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.
  
To get started, demonstrate your skills by completing the [http://web.archive.org/web/20071217104813/kde-artists.org/node/116 KDE Icon Bootcamp] and bringing the results to the team.
+
Once there's general agreement in the Phabricator task, work should begin and folks can start submitting patches!
  
Then find inspiration at [http://websvn.kde.org/trunk/playground/artwork/Oxygen/docs/ The KDE Icon Request List].
 
  
== Mentor program ==
+
== Know thyself ==
 +
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. 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!
  
For getting started, feel free to direct any questions to a mentor for this project:
+
==Old Things==
 +
* [[KDE_Visual_Design_Group/Archive | Archive of outdated documents that may still be useful for reference]]
  
* Nuno Pinheiro (<span class="mailme">nuno at oxygen-icons dot org</span>)<br /> Style theme and cursor theme art director and core icon designer
+
__NOTOC__

Latest revision as of 14:17, 11 June 2019

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 maintains and updates the KDE Human Interface Guidelines.

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.


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 watcher for the VDG project in Phabricator. 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 IRC. 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 and should be hosted on Pholio.

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 thyself

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. 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!

Old Things



This page was last edited on 11 June 2019, at 14:17. Content is available under Creative Commons License SA 4.0 unless otherwise noted.