ArtTeam
|
Size: 6026
Comment:
|
← Revision 93 as of 2008-08-06 16:33:43 ⇥
Size: 3947
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Ubuntu Art Team = | ## page was renamed from ArtTeam ##(see the SpecSpec for an explanation) ''Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.'' * '''Launchpad Entry''': UbuntuSpec:art-team * '''Packages affected''': == Summary == In order to function well, the art team needs a defined process for the contribution and sharing of information. == Rationale == A large number of people are interested in the Ubuntu artwork and everyone wants to offer their opinion. Without a well defined process things fall apart quickly. == Design == Clearly define the process. Define all of our information channels and ensure that communication flows across channels. Attract new contributors by reaching out to them in the channels they already use. == Implementation == === Restructure the wiki page to match the other team layout pages (done) === === Point to the official info everywhere === Again and again people seem to lack information on how the artwork process works. In order to avoid confusion we need to point to the fact that the Wiki and Mailing List are the official lines of communication. (underway) === Add channels to draw new contributors === In order to gain new contributors we need to allow them to contribute in the manner in which they already feel comfortable with. A gallery (art.ubuntu.com), a flickr group with official tags, and the forum seem to be popular ways for people to communicate artistic ideas which we should also use. For the community art packages a digg like process could be used to determine which works should be included. Note: Art.ubuntu.com is in the works and should be back online sometime soonish (waiting on code review) === Define roles for communicators between channels === The many varied channels for contribution create confusion and possible duplication of efforts. We need to pick individuals from the community who have shown a talent for relaying information so that information flows between channels. === Developer relations === After artwork has been created it often never goes any further due to packaging and other technical issues. We need to define a process which allows artists to do what they do best (artsy stuff) and developers to do what they do best (technical stuff). By creating one official place on the wiki for all finalized ideas we can present a forum of ideas worth working on for developers who wish to help out. === Bugs === Most artwork bugs end up being upstream and/or technical issues. We need to organize our effort on triaging bugs and getting the information where it needs to go. Unfortunately many artwork related bugs need someone with technical savvy to really understand where the problem lies. Planning bug squashing days/weeks would help in any case. |
| Line 4: | Line 45: |
| The Ubuntu Art Team strives to establish and maintain a consistent and familiar look to themes, artwork, wallpapers and other graphics for Ubuntu. == Scope == Ultimately, the Art Team should be responsible for all art-related aspects of the Ubuntu distribution. In many of these cases, there is already a plethora of art available. Part of the challenge facing the Art Team is how to organise that material, how to make it accessible, how to have an appropriate level of consistency (e.g., many of the promotional items work best when there is only one item of a given class, a single look and feel, etc). As this is a relatively new team, we'd like to suggest specific, near term goals for the Breezy Release. * The Art Team should develop and select six desktop calendar images to be used within the Breezy release cycle. The desktops can be selected in any method the team chooses. Disputes, if any, will be resolved by the Community Council. This should be a Breezy goal. * We would like to develop an Ubuntu-specific icon set. [mailto:andrew@fitzsimon.com.au Andy Fitzsimon] is already working on this, and will continue to lead the effort. Contributions and comments from the Art Team will be appreciated. This should be a Breezy goal. * There should be official "powered by Ubuntu" or buttons (or similar) developed. Many community members have made versions of these. The Art Team should select those which should be officially endorsed and make them readily available (note that while new art solicitations are encouraged, there is a danger to having too many variants of the same object). This should be a near term goal. * Many community members would like to have posters and banners which can be printed for use in local conferences. The Art Team should establish some standard promotional material. This should be a near term goal. * The Art Team should identify the tools and processes needed to organise themselves and the artwork. This wiki should be used where appropriate; Canonical will make a site (art.ubuntu.com) available for purposes not as well suited to a wiki. This should be a near term goal. * In the future (likely post-Breezy, due to current timelines), we would like to rely on the Art Team for other aspects of the distro (e.g., login, splash, etc). This is a longer term goal. |
== BoF agenda and discussion == |
| Line 18: | Line 48: |
| Wiki, IRC and Mailing list are the official lines of communication | |
| Line 19: | Line 50: |
| Gallery - ubuntuforums gallery, a.u.c, ubuntu-art.com ??? Flickr Forums - post sticky detailing official communication resources (send to Mike) and ambassadors if people are interested |
|
| Line 20: | Line 54: |
| == Resources == | Meetings every month |
| Line 22: | Line 56: |
| * ArtTeamTools covers the tools you'll need to start making and helping with the Artwork project * IconGuide for all ArtTeam members who would like to help contribute to the production of the Icon set. '''You do not have to be an artist to help out''' * WebsiteButtons is a nice collection of "Powered by Ubuntu" buttons to look at, comment, edit, and use as reference. * UbuntuTitle is the official Ubuntu font used in the ubuntu logo. It is released under the LGPL |
Info needs to flow back--to this end '''ambassadors are needed''' A plan to "cherrypick" or grab valuable people from flickr, forums, etc |
| Line 27: | Line 59: |
| == Reference sites == | Need to add art team info to forum |
| Line 29: | Line 61: |
| * Note that the [http://udu.wiki.ubuntu.com/BreezyReleaseSchedule Breezy Release Schedule] now incorporates an Artwork Deadline of '''29 September 2005'''. The Art Team must respect this deadline. | digg like process for things going into community art package * WIP threads, as part of community building * Talk to Matthew Nuzum on this w/Drupal * Any popularity or rating system, needs to be clear on actual authority Need a go-to developer guy for stuff like packaging |
| Line 31: | Line 68: |
| * Also note that official logos, palettes and policys are on this wiki at UbuntuArtwork. | == Key Issues == === Artwork Submission Process == * Clear instructions posted on BOTH the wiki and the forums === Bugs === * 90% of bugs end up being upstream issues * triaging important, need process for this |
| Line 33: | Line 75: |
| * The ArtTeam spends a fair amount of time exchanging info on the #ubuntu-artwork freenode IRC channel. These chats are now being logged, so you can catch up if you miss something by going [http://people.ubuntu.com/~fabbione/irclogs/ here]. * This [http://udu.wiki.ubuntu.com/DesktopArtwork Breezy specification] outlines some of the artwork goals for Breezy (realistically, not all of this is possible). * There are some valuable pieces on the CommunityArtwork page. * KubuntuArtwork == Projects == * HumilityIcons - Ubuntu-specific icon set project == Members == If you are interested in becoming a member of the team, and think you've got the experience needed - please put your name on the list below: * [mailto:andyfitz@gmail.com Andy Fitzsimon], Australia * [mailto:volvoguy@gmail.com Aaron Waite], United States ( ArtTeam Coordinator ) * [mailto:vidar@kanelsaft.com Vidar Rapp], Sweden * [mailto:sloss@free.fr Sébastien LOSS], France * [mailto:julian.turner@gmx.de Julian Turner], Austria * [mailto:eproxus@gmail.com Adam Lindberg], Sweden * [mailto:m-ubuntu@emailias.com Marc Audette], United States * [mailto:mikeman2k4@gmail.com Mike Belanger], United States * [mailto:jonathan@tsf.org.za Jonathan Carter], South Africa * [mailto:luka.cehovin@gmail.com Luka Čehovin], Slovenia * [mailto:wings774@gmx.net Arpad Olasz], United States * [mailto:davoodifar@gmail.com Ali Davoodifar], Iran * [mailto:mm@mpathy.de Markus Majer], Germany * [mailto:rickyharris@gmail.com Ricky Harris], United States * [mailto:yetzero@gmail.com Luis Santander], Chile * [mailto:fred@mentalwarp.com Frédéric Van der Essen], Belgium * [mailto:kori.mendocino@gmail.com Stanimir Djevelekov], Bulgaria * [mailto:myles.braithwaite@gmail.com Myles Braithwaite], Canada * [mailto:manu.cornet@gmail.com Manu Cornet], France * [mailto:agnogueira@gmail.com Andre Nogueira], Brazil * [mailto:kamstrup@daimi.au.dk Mikkel Kamstrup Erlandsen], Denmark * [mailto:dylan.dunne@gmail.com Dylan Dunne], United States * [mailto:bwhiting@gmail.com Bryan Whiting], United States * [mailto:afterburn1@gmail.com Jayson Hickle], United States * [mailto:insondavel@gmail.com Krysamon Cavalcante], Brazil * [mailto:svl@imbiss-media.de Susanne Vestner-Ludwig (Suzan)], Germany * [mailto:tux@webofdallas.com Rick Gillespie], United States * [mailto:pascal.potvin@gmail.com Pascal Potvin], Quebec, Canada * [mailto:mhz.chile@gmail.com Mauricio Hernandez Z.], Santiago, Chile * [mailto:benhaim_jerome@yahoo.fr Jérôme Benhaïm], Nice, France * [mailto:anbujawahar@gmail.com Anbu Jawahar], Bangalore, India Technical contact (packaging, uploads etc): * [mailto:ogra@ubuntu.com OliverGrawert], Germany |
|
| Line 86: | Line 76: |
Read more on the CommunityArtwork page. ---- CategoryUbuntuTeams |
CategorySpec |
Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.
Launchpad Entry: art-team
Packages affected:
Summary
In order to function well, the art team needs a defined process for the contribution and sharing of information.
Rationale
A large number of people are interested in the Ubuntu artwork and everyone wants to offer their opinion. Without a well defined process things fall apart quickly.
Design
Clearly define the process. Define all of our information channels and ensure that communication flows across channels. Attract new contributors by reaching out to them in the channels they already use.
Implementation
Restructure the wiki page to match the other team layout pages (done)
Point to the official info everywhere
Again and again people seem to lack information on how the artwork process works. In order to avoid confusion we need to point to the fact that the Wiki and Mailing List are the official lines of communication. (underway)
Add channels to draw new contributors
In order to gain new contributors we need to allow them to contribute in the manner in which they already feel comfortable with. A gallery (art.ubuntu.com), a flickr group with official tags, and the forum seem to be popular ways for people to communicate artistic ideas which we should also use.
For the community art packages a digg like process could be used to determine which works should be included.
Note: Art.ubuntu.com is in the works and should be back online sometime soonish (waiting on code review)
Define roles for communicators between channels
The many varied channels for contribution create confusion and possible duplication of efforts. We need to pick individuals from the community who have shown a talent for relaying information so that information flows between channels.
Developer relations
After artwork has been created it often never goes any further due to packaging and other technical issues. We need to define a process which allows artists to do what they do best (artsy stuff) and developers to do what they do best (technical stuff). By creating one official place on the wiki for all finalized ideas we can present a forum of ideas worth working on for developers who wish to help out.
Bugs
Most artwork bugs end up being upstream and/or technical issues. We need to organize our effort on triaging bugs and getting the information where it needs to go. Unfortunately many artwork related bugs need someone with technical savvy to really understand where the problem lies. Planning bug squashing days/weeks would help in any case.
BoF agenda and discussion
Wiki, IRC and Mailing list are the official lines of communication
Gallery - ubuntuforums gallery, a.u.c, ubuntu-art.com ??? Flickr Forums - post sticky detailing official communication resources (send to Mike) and ambassadors if people are interested
Meetings every month
Info needs to flow back--to this end ambassadors are needed A plan to "cherrypick" or grab valuable people from flickr, forums, etc
Need to add art team info to forum
digg like process for things going into community art package
- WIP threads, as part of community building
- Talk to Matthew Nuzum on this w/Drupal
- Any popularity or rating system, needs to be clear on actual authority
Need a go-to developer guy for stuff like packaging
Key Issues
=== Artwork Submission Process ==
- Clear instructions posted on BOTH the wiki and the forums
Bugs
- 90% of bugs end up being upstream issues
- triaging important, need process for this
DesktopTeam/Specs/ArtTeam (last edited 2008-08-06 16:33:43 by localhost)