![](https://seccdn.libravatar.org/avatar/89e2af2dee694c8b533159159c4946da.jpg?s=120&d=mm&r=g)
This is perfect, Martin. Thanks so much! I don't suppose you have a nice shot of yourself at work? I can use a screenshot showing the icons. Rajko has contributed quite a bit about contributing to the Wiki and other written work. Bug reporting is an important one - any comments on that? I think it's something that newbies get a bit confused by. I've noticed on IRC that people will report a bug several times and so create extra work 'triaging' the bugs before they even get addressed. Also, the bug reporting system can be quite frustrating when people don't feel that their bug has been addressed. I'm not sure if this is heading towards the 'technical' side, although it's probably good for users to know that it's worthwhile to do a bug report in the first place. If anyone has any further comments or tips about artwork - even just something brief that you think I should consider - do let me know. I wonder, has there been any occasions where there's been problems with conflict due to work not being accepted, differences of opinion about design issues and so on? If so, how have these been resolved? I notice with the Ubuntu 'meritocracy', there's the design team that makes the decisions and others have to trust their judgment. I'm not sure that all projects run that way and often the 'power structure' seems very loose indeed, so I wonder who makes decisions! Any problems with image licensing? thanks, Helen On Mon, Nov 8, 2010 at 8:19 PM, Martin Schlander <martin.schlander@gmail.com> wrote:
Mandag den 8. november 2010 02:43:57 skrev Helen:
I'm working on an article on getting involved in open source projects, aimed at non-technical people.
I'd be keen to hear your stories about getting involved in doing openSUSE artwork and any other projects that you do.
You can write a little or a lot, it's up to you. Something like how you first got involved, your background and tips on the best way to get started, any mistakes you made and so on.
Here's a brief story of how I got started doing the YaST Oxygen icon theme.
Novell announced they'd no longer maintain the Crystal icon theme for YaST, and said nonsense like "Tango icons will integrate well in KDE4", I could not live with that, so I decided to try and collect an iconset using existing Oxygen icons - initially it was just intended for my own use and as a proof of concept. I thought it worked ok, so I put it on kde-look.org and blogged about it.
To my surprise a lot of things started happening. Martin Lasarsch packaged the icon theme, Marco Michna wrote a yast theme selector module at Novell Hackweek and Stephan Kulow even committed the theme to be included in the actual distro.
Initially I had just used Oxygen icons as they were, so the theme had a lot of duplicates and such, but now that people were actually using it I had to make it a lot better. I have no artistic skills at all - before getting myself into this situation, I think I had only ever launched Inkscape once or twice, but I polished up the theme a bit by modifying and "remixing" existing Oxygen icons.
The YaST Oxygen icon theme has now been the default for KDE users for 3-4 releases - and I haven't heard too many complaints about it, though I think it could be a lot better if done by a proper experienced artist, but at least it beats using Tango icons.
I have stories about many other non-technical contributions btw. if you're interested (translation, opensuse-guide.org, bugreporting, etc.) :-) -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-artwork+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-artwork+help@opensuse.org