<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffcc" text="#000000">
Andreas Nilsson wrote:
<blockquote cite="mid44170244.1000306@home.se" type="cite">Mark
Shuttleworth wrote:
<br>
<blockquote type="cite">Tangerine would be managed by the community
as follows:
<br>
<br>
- one person will be selected by the community to be the Tangerine
Lead
<br>
- up to three people will get direct write access to the repository
<br>
- the rest of the community would contribute icons to those core theme
writers, who would choose which icons go into Tangerine, using your own
community processes
<br>
<br>
</blockquote>
Hello Mark!
<br>
I can step up and maintain this, and I bet I have lapo with me on this,
however there are some problems.
<br>
</blockquote>
OK, thanks for volunteering! I'm happy to make you preliminary leader
of Tangerine to work with Daniel Holbach in setting up the theme
skeleton and the packaging, and the revision control processes.<br>
<br>
I say "preliminary" because the Art Team needs to select the leaders of
subprojects like Tangerine and the major community-contributed themes.
And the Community Council needs to appoint a leadership structure for
the art team. So let's go ahead if you are comfortable getting that
process completed and confirmed over the coming weeks.<br>
<br>
<blockquote cite="mid44170244.1000306@home.se" type="cite">Gnome-icon-theme
is licensed under GPL, while Tango is licensed under CC-SA and I'm not
sure it is legally possible to create a theme with a mishmash of
licenses. It would probably be possible to keep the themes in separate
packages, delete icons like stock-save in tango and tangofy that icon
in gnome-icon-theme (and as tango depend on g-i-t it would fall back to
that and it would use the one from g-i-t). I'm not sure that is a good
solution though.
<br>
</blockquote>
We have a different position on the legalities. We believe it is OK to
produce a theme that has icons under multiple licences, as long as the
licences file clearly identifies which icon is under which licences. In
other words, we believe the icons are individual pieces of work.<br>
<br>
So, we will start with Tangerine including existing icons from Tango
and GIT, carefully identified, and also welcome contributions from the
community under (your) direction to fill that out.<br>
<br>
The best community icons, if they meet the standards for Human, will go
into Human as well as Tangerine.<br>
<blockquote cite="mid44170244.1000306@home.se" type="cite">It would be
nice to have some more info on why some icons in human or gnome was
chosen instead of the tango ones, so that we either can fix this
upstream or fix tango in dapper to use some better metaphors/styles.
<br>
</blockquote>
Hard to describe taste issues, I'm not an expert and don't have too
much time for it. Have just gone through an iterative process with the
Human theme to get to something I and some others really like, and are
now trying to expand that theme to cover the core parts of the desktop.<br>
<br>
In due course I would like to document the style guidelines.<br>
<br>
I think they look OK when mixed with Tango, except that the Tango
palette is rather blue.<br>
<br>
Mark<br>
</body>
</html>