On Sun, 2011-01-30 at 16:35 +0100, Bruno Friedmann wrote:
On 01/30/2011 12:35 AM, Jos Poortvliet wrote:
On 2011-01-28 Helen wrote:
That's because it's just about impossible to find a good one in the format I want. I tried looking on GIT and could only find a SVG which downloaded as a pile of code.
GIT is HORRIBLE to find things on - I hate having to click through fifty different folders to find things, and there's hardly any jpgs or pngs, and I have to click before I can see what it looks like. It just makes no sense at all.
Can we have the final artwork put on the WIKI and made easy to find please? One page with a graphical index.
Fully agreed. I know Robert has a lot of stuff on his computer and I think I want to have it in form of a big tar.bz2 and take it with me to the marketing meeting. There we can sort through it and put it all online. ANYTHING we create, for whatever purpose, should go on the wiki! Including sources!
;-)
Or else gather together some and email it to the list so I can have it ready to go on my hard drive.
COPYRIGHTS - dister logo is from here http://susestudio.com/artwork/ and I think is ok to use in this context as far as I can tell (ie, talking about Studio).
My assumption with marketing materials is that they essentially belong to openSUSE. I havent' followed the entirety of the current copyright discussion. Any writing I do for other markets (such as magazine articles) I'll clearly mark with a copyright notice
So it's (cc) or (c)openSUSE as far as I'm concerned. (Jos??)
Public domain as far as I am concerned, as free as possible at least :D CC by SA or so would probably do. We want ppl to USE this material!
cheers
Helen
Dear Helen & Jos ... Sure we should have the sources online, but wiki is just a pain in A (yes a big a)
Tools source control are really cool things. as we can track quickly what change or not, and what was the modification. With svg is more easy, you can just get the patch about it. Mainly asking hostmaster to allow the svg type and not text/plain for svg files.
Sure the web base browsing interface should be adjusted to perhaps offer a preview. but once you have it locally why bothering about the web things.
What would be nice is to have more people able to commit to the git artwork repo, and try to find a way to have one for marketing too.
I'm describing now why we must use it.
In April or May, if the deal ends with Attachmate, lot's of stuff will need to be revised. Without an scm, we would just end in an horrible mess about what to change, who change it, when it was change last time. All that kind of queries can be run on scm, none of them would be available in wiki. Having a kind of gallery, updated automagically, git clone on a website and it's done ...
My main issue with the wiki, is if someone for good or bad reason destroy a page, or change the wiki yet another time we will loose all of what's inside it. Who can actually said, that all of the stuff present in the old-en.o.o was now in en.o.o etc etc ...
you will certainly understand, that's I'm not a big fan about the wiki, but yes I also want all marketing material somewhere online. In a manageable way that would be cool.
Do we need help from a master of Git : certainly. So he can help each of us which are non-dev's to understand how to work with this great tools.
--
Bruno Friedmann
Sorry, But I have to agree with Jos and Helen more than with you on this one. The main goal is to ensure that any artwork we have is readily accessible and usable. Other project marketing teams have lowered the bar on being able to access material, why haven't we yet? I've brought this up in the past and hit a wall and am glad that Jos and Helen are carrying the ball forward on raising this issue. How many times have we been able to go to some other website or project and simply click and save an image that we want to put on, for example, our blog? And in that instant click process, that project gets automatic free promotion from us. Yet, we cannot do the same for our own project. And then we wonder why we aren't doing a better job of promoting openSUSE. There are definitely technical advantages for artists to use GIT for works in progress or revisions. But final artwork needs to be up on the web where anyone can grab it. Sure I can learn GIT, and so can anyone else. But having a GIT master teach everyone is a rather myopic and self-defeating process. Do you expect the GIT Master to be able to teach GIT to someone who just stops by our site for a minute to grab some artwork for an article or a blog post or a poster or... How in heck do you expect that to happen? Keep the bar low. Make things easily "grabbable." It is far easier for a user to download our ISO's than it is to download graphics. Think about that. :-) Bryen -- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-marketing+help@opensuse.org