19:02:57 #startmeeting 19:02:57 Meeting started Tue Dec 6 19:02:57 2011 UTC. The chair is bmwiedemann. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:02:57 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:03:06 thanks you all :D 19:03:10 #chart anditosan 19:03:15 #chair anditosan 19:03:15 Current chairs: anditosan bmwiedemann 19:03:28 bmwiedemann, you're the man! thanks 19:03:40 ok, then 19:03:53 and whatever you do, please remember to type #endmeeting at the end! :-) 19:04:05 now repeat the topics so it gets in the transcript log 19:04:06 (he's speaking from experience) 19:04:36 no need to repeat the agenda, just start each point with #topic … 19:04:36 topics repeat 19:04:42 1. team get to know 19:04:46 2. Team Organization 19:04:50 3. Abilities Assessment 19:04:54 4. Insterest (design) 19:04:58 . Design Goals (only if there is enough time) 19:05:04 6. Design goals for next release (very on the surface) 19:05:09 7. Long term design goals, or team goals 19:05:14 8. Q and A 19:05:24 ok, then topic one 19:05:40 let me ask you to introduce yourserlf briefly, we would like to get to know everyone that's one the channel, as well as welcome the ones who are joining us. 19:05:55 who can start? 19:05:56 #topic 1. Team Get-To-Know 19:06:01 heheh thanks 19:06:11 alphabetical, you first! 19:06:15 bugbot needs to be opped before #topic works 19:07:14 I'm jdd, mostly interested by making video tutorials, but also early tester. No real "artistic" knowledge 19:08:04 #topic 1. Get to Know 19:08:10 anditosan, Andres Silva, from Chile. Live in the US. Help openSUSE with concept artwork. It's my b-day today, so thanks :D. Next... 19:08:36 I'm Pascal, not good at artwork itself but moderately skilled at inkscape and I'm here just for general support and to keep up with what's going on :) 19:08:39 #info anditosan is 54 today! 19:08:57 congrats :) 19:09:03 Congrats and 19:09:04 #info incorrect, I am 28. suseROCKs gets his age everywhere 19:09:10 (and if you want to know more, I wrote a book about myself for the board elections lol) 19:09:17 lol 19:09:25 bmwiedemann, your turn 19:09:27 :D 19:09:30 anditosan: ye olde bastard, congrats :) 19:09:42 lol, thanks 19:10:03 folks, just shoot, IRC is line by line anyway :) 19:10:10 I am Kostas 19:10:12 I'm 33, software developer at SUSE/Nuremberg, my wife is great at painting (see http://kati.silberwellensee.de/ ) but I am good at making ugly art :) 19:10:19 have a great day anditosan 19:10:22 and I have nothing to do with art 19:10:28 and I am 12 19:10:33 bmwiedemann: true, you have that on your CV? :D 19:10:46 Bryen here... just an observer and to offer any input on marketing-related discussions here 19:10:53 o/ 19:11:03 bear454: ohai 19:11:03 I made and maintain http://openqa.opensuse.org for automated testing, but it is also good to see the current artwork and to generate videos for marketing/press 19:11:12 bmwiedemann: +1 19:11:13 I am Manu, Not a great artist jumps around the corners and sometimes get my hand dirty though I have not done till now 19:11:25 bmwiedemann: +1 19:11:33 * bear454 begs forgiveness for a flaky connection 19:11:38 I'm Richard, 29, aka Ilmehtar aka Sysrich aka the guy who cant pronounce his own IRC nick. I have no idea what I'm doing here (okay that's a lie) - I used to critique/moan about artwork, started using inkscape to draw my ideas in the hope some 'proper artist' would be able to finish them off, and found I kinda enjoy it 19:11:46 e.g. LinuxActionShow had my video in their openSUSE-12.1 review (around minute 35) 19:11:48 I'm on a bus to the airport 19:12:12 bear454, oh man! hold on!!! 19:12:52 who is next? 19:13:04 * bear454 is a developer on SUSE Studio, and an avid digital artist 19:13:06 CarlosRibeiro. :D 19:13:12 great to know some new ones and some old friends, for the new guys for me (I was out of here for my last 5 months), 19:13:16 I worked as professional designer for 6 years when I was 15, and today I'm 34 not more working as graphical designer but 100% focused in openSUSE/SUSE. I helped to creat the Cool folders artwork, also some scale tshits, banners, folders. Also I helped with some artwork for news.o.o at least I hope to be able to contribute with team as much as possible 19:13:51 CarlosRibeiro_: hi carlos :) 19:14:08 also OI contributed with bug reports, some big, small and mediuns events and my blog is here http://softwarelivre.org/usesuse/blog 19:14:16 Hello, I'm subhashish - Subhashish Pradhan from India; have an artistic eye being a somewhat-good painter; just got started in digital artwok by strting with gimp and opensuse-artwork. 19:14:40 yaloki: hello mate, nice to see you man.. You have no idea how much I know about you :D pretty cool 19:14:53 ok, anyone else would like to introduce himself that has not already done so? 19:14:54 subhashish: cool, welcome to the club :) 19:14:57 nice to see you all \0/ 19:15:01 thanks yaloki 19:15:15 subhashish: hint, hint: inkscape ;D 19:15:16 nice team 19:15:19 Is it ok if we move on? 19:15:25 wait 19:15:35 I think there are two people we're essentially missing here today 19:15:40 but whom are important to the artwork team 19:15:56 yaloki, can you mention them quikly? :D 19:16:00 garett and rlihm 19:16:00 it's Robert Lihm (nickname rlihm), who works for SUSE, and is a professional designer (not quite the same as artwork) 19:16:19 true, Garret, for as far as he's still involved in artwork for openSUSE, not sure 19:16:28 and then Marcus Moeller, who did the artwork for 12.1 19:16:30 yaloki: and bruno are missing too 19:16:31 anditosan - I'm here, but don't need to take time for introduce. I love inkscape, can't draw a straight line, am a grey hair 29 ;-) 19:16:45 I believe they mentioned in ML that they could not attend, so we will miss them today but we will make sure they get the notes 19:16:52 yes indeed, bruno (tigerfoot) isn't here either 19:16:56 AlanClark: Are you 29? 19:16:59 yeah 19:17:06 I thought you were around 25 :D 19:17:11 AlanClark, you're older by one year than I am. Congrats :D 19:17:16 anditosan: sure, just to round up on the team :) 19:17:17 In his dreams 19:17:19 maybe he is not good designer producer, but he mention to be part here and contribute with his crazy ideas 19:17:19 ok, good to move one? 19:17:37 all agree to move on? 19:17:42 warlordfff: ;-) 19:17:43 go 19:17:46 anditosan: please go on :) 19:17:47 go 19:17:49 #topic Team Organization 19:18:29 This one might be hard to firgure out in one hour but, who of the attendants is able to take in requests and either put them on git, or actually code the artwork into the distribution? 19:19:09 I can commit to git 19:19:20 as far as the distribution is concerned, it's "just" a matter of packaging 19:19:25 I can but not now for the moment as I have b/w limits 19:19:25 ok 19:19:30 and synchronizing with the release team (e.g. coolo) 19:19:41 yaloki, that is good info 19:19:45 I can definitely help with packaging, and Ilmehtar has some experience with that too, specifically on the artwork iirc 19:19:56 ok, this is the reason for the question 19:19:57 yes, I did quite a bit of the packaging for the 12.1 stuff 19:20:18 can I get commit-permission? 19:20:42 the artwork team generates, in a sense, a lot of interest from art ethusiasts. However, they mey not be acquainted with our methods just yet, yet they have great potential into making significat art contributions to the team 19:20:47 and to the distribution 19:20:50 #info for everyone who wants write access to the git repository, please just send an email to admin@opensuse.org 19:20:54 I'll pick it up from there 19:21:01 meh, I'm not a chair:\ 19:21:16 #chair yaloki 19:21:16 Current chairs: anditosan bmwiedemann yaloki 19:21:21 #info for everyone who wants write access to the git repository, please just send an email to admin@opensuse.org 19:21:21 we would like to be extra welcoming to our new contributors in assisting them make the contributions 19:21:35 one thing I'd like to mention as part of the organizaiton/prioritization concept.... 19:21:36 bmwiedemann: so just bug me on admin@o.o please :) (need to know your github user) 19:21:47 suseROCKs, please go ahead 19:21:50 I think its good to be more organized on distro artwork. We need that, but at the same time... 19:22:01 we should realize that artwork is not just limited to distro stuff 19:22:08 indeed 19:22:15 I probably have write access to git, but not at all confident with it 19:22:17 and that's been something sorely lackinig in the past 19:22:17 right 19:22:21 Well said suseROCKs :) 19:22:31 Are we using a repo on github now, or still the ones on gitorious? 19:22:31 agreed! 19:22:36 bear454: github 19:22:38 bear454: github 19:22:56 if anyone needs help with git, poke me, or Ilmehtar, or tigerfoot (bruno) 19:23:04 subhashish: agreed, I've been pushing hard to remind people of that..the marketing side of things in particularly (and anditosan and I have done a lot of work doing artwork for -marketing along those lines) 19:23:05 * manugupt1 thinks we need a better access place as 2 gigs of downloading becomes out of question if anytime out of sync 19:23:30 manugupt1: yes, but that's a topic of its own, it shouldn't be 2GB in the first place 19:23:37 but that topic is not on the agenda :) 19:23:38 Likely, we would need to sign up for taking, or rather making ourselves responsible, for artwork requests from other teams 19:23:46 especially Marketing 19:23:51 * subhashish passes Ilmehtar's comment to suseROCKs 19:23:52 yaloki: sorry offtopic 19:23:54 I believe as a artwork team, we need to support news.oo, marketing, project, pr, ambasadors 19:24:04 do we have some sort of plan of what would be needed in terms of artwork for marketing then ? 19:24:10 if not, then that's something to think about 19:24:20 (maybe use bugzilla or something similar) 19:24:25 suseROCKs, what do you say if we keep this topic and sign ourselves up for this type of art over ML? 19:24:27 and distro is just a piece of all thinks I believe we need to take care 19:24:38 I think Gnome is Using Bugzila for artwork 19:24:44 okay 19:24:48 CarlosRibeiro_: AGREED 19:24:51 marketing materials - Presentations, CD Sleeves, Posters, Leaflets..am I forgetting anything? 19:24:51 we should here define a place to ask (artwork mailing list?) 19:25:03 well, it's not about tool fetishism, but it's easier to have a list of requests and know whom is working on what 19:25:10 bear454: We are only a few memebes so most important areas should be focussed first 19:25:13 yaloki, probably the best is to have artwork take on reposibilities now and over time split ourselves into teams. 19:25:19 Ilmehtar, that's the general bit, but also artwork for news.o.o and other "as-needed" stuff 19:25:23 photos, screen shots, tutorials, videos... 19:25:32 we don't have any quick-response opportunities 19:25:34 also, here is a question we've had asked before but never really resolved - what do you all think, should our marketing artwork be related to the distribution artwork, or should we consider an approach of 'version neutral' marketing materials? 19:25:50 Vesion Neutral imho 19:25:51 requests sent to ML seem to die 19:25:55 anditosan: well, you will be interacting with a lot of people (who are asking for artwork, or taking care of the packaging, etc...), so some sort of communication tool will be very helpful to track the state of things, what's TODO, etc... 19:26:03 suseROCKs, understood 19:26:11 Ilmehtar: IMO that depends on the work. 19:26:15 yaloki, true that 19:26:16 suseROCKs: define "quick-response opportunities" ? 19:26:25 bear454: +1 19:26:56 version: most version neutral, but any new openSUSE have to get some original artwork 19:27:12 Some materials can be long-lived, and should be neutral 19:27:14 jdd, that's a good thought 19:27:18 I believe we need to create a kind of templates and stardards for both situations 19:27:18 arguably, if the artwork is properly authored (layers, inkscape, ...), then it's really easy to swap out the release, the motto, etc... 19:27:35 yaloki, "I need some graphics for news..o.o" or "I have this poster concept in mind can someone help design it?" Those are things that typically dont' get responded to. What does morelikely get responded to are distro artwork stuff 19:27:40 but obviously things like counter.o.o should reflect release art 19:27:49 suseROCKs: okay, understood, thanks 19:27:54 not a criticism of that, just we don't have an artwork team that is equipped right now to think beyond distro 19:27:56 I personally Iike the idea of both.. version neutral stuff is great, but, lets say for example presentation templates, which rare likely to be talking about a specific openSUSE version, would probably look better looking liek they derive from that version 19:28:21 Ilmehtar, yes 19:28:22 Ilmehtar: a discussion to have, indeed 19:28:32 suseROCKs, could we crash one of the marketing team meetings and assess the artwork needs? 19:28:52 coming to distro I think that shipping of only one distro-branded wallpaper may seem strange.. 19:29:06 anditosan, that isn't that simple. a marketing team meeting wouldn't know of something that's needed 2 months from now. 19:29:13 #info discuss openSUSE release neutrality of artwork: depends on the purpose, and the issue can be alleviated with properly authored artwork (gimp layers, inkscape, ...) 19:29:54 suseROCKs, I see, mostly to understand the "type" of needs they generate and then we could see in our team who is likely to take those requests. 19:30:01 subhashish: we can ship several, of course, but one needs to be the default and what is reflected in e.g. counter.o.o, marketing material, … 19:30:10 subhashish: just for consistency 19:30:16 let artists give free ideas, then pick in them? 19:30:26 anditosan: yes, we're back to some sort of tracking :) 19:30:41 yaloki, good 19:30:48 jdd: on each individual thing, of course, but that "list of things" is what we're discussing 19:31:03 we won't solve anything right now, let's collect ideas and tasks, and go on :) 19:31:11 subhashish: for 12.1 we do have a package of additional 12.1 wallpapers but they're hidden away in a rarely used repository :) 19:31:17 Iissues on github? 19:31:25 ok, let's have these concerns be defined more in detail. I will be sending out an email about it. We can determine the needs of artwork from other teams and then see how we can integrate those into our artwork team 19:31:33 would that be ok for you all? 19:31:37 ok 19:31:38 Seems like a nice integrated way to collect requests 19:31:45 #info we should fix the packaging of distro wallpapers: the additional ones are hidden away in a rarely used repository for 12.1 19:31:53 bear454: indeed 19:32:06 so shouldn't the repository be changed to one of the default ones included in the distro Ilmehtar ? 19:32:08 #info investigate using github's issue ticketing for tracking of artwork tasks 19:32:14 yaloki: If we can have some templated spec files for gnome and kde.. just wondering 19:32:17 yaloki, noted! 19:32:19 :D 19:32:23 manugupt1: possibly 19:32:37 manugupt1: but as said, Ilmehtar and I (and certainly others too) can take care of the packaging 19:32:46 it may seem we can continue this conversation more in detail on ml. Do you agree to move one/ 19:32:48 ? 19:32:54 anditosan: yes please 19:32:55 Ok.. later then 19:33:11 manugupt1: yes, packaging is at the end of the process anyway 19:33:25 our artwork branding packages are really fun, if a little arcane compared to normal pckages :)..lots of scripting so it takes on design and carves it up into all the formats we need in the package 19:33:30 #topic Skipping Anilities Assessment, we know that already. Interest Assessment 19:33:30 manugupt1: can be made really simple once set up, thanks to OBS 19:33:39 can we have a easy step-by-step packing guide with focus on artwork team and needs 19:33:50 CarlosRibeiro_: difficult 19:33:54 in this section, please state what type of design subjects interest you 19:34:01 yaloki: yes.. I was thinking to have the spec file to wiki and something like get your artwork in a repo and mark the artwork repo as a devel project 19:34:05 #info in this section, please state what type of design subjects interest you 19:34:31 manugupt1: maybe. we can think of how to handle that some time later, when we have artwork for the next distro version :) 19:34:42 I like nature and photography, I like real pictures for artwork. Next :D 19:35:16 me, none, but I can help giving details about the technical nature (SVG vs bitmaps, packaging, batch rendering, ...) 19:35:41 (and licensing!) 19:35:46 licensing is a very important topic 19:35:46 yaloki, thank you 19:36:05 anyone else? :D 19:36:23 hey me 19:36:24 I do some photography ... and then there is my wife painting 19:36:28 I suggest someone volunteer to write a good wiki overview of the importance of licensing and how you should license your works 19:36:40 i'm interested in the licence question 19:36:46 suseROCKs, very good idea. Noted! 19:36:54 I have pretty broad tastes and enjoy experimenting - I already have concepts for 12.2 that include photography and lazers.. and vectored circles..as you can see, nothing in common. 19:37:00 CC-BY-SA license should work? 19:37:00 some of us create work and just give to openSUSE not fully realizing it needs more than just to give. 19:37:03 i can do 19:37:04 suseROCKs: which license, not sure that has been debated actually, think we somehow came to CC-BY-SA 19:37:16 s/suseROCKs/Ilmehtar/ 19:37:19 I like to see more design I mean, I'm not so good with photos, pic, but I understand that I good wuth layouts, design and 3D models 19:37:32 I do some photographic work, but I'm more comfortable in Inkscape, and alright working for print media 19:37:34 CarlosRibeiro_: definitely :) 19:37:35 and like yaloki, strong interest in all the technical side, getting these artworks usable and implemented, packaging and licensing, etc etc 19:37:40 yaloki, sure. But what about when we create work that we want to give exclusively to openSUSE and not to the entire world? 19:37:42 * Ilmehtar suddenly thinks he likes being involved in too much 19:37:42 so I think I can contribute helping to transfrm great pieces in wonderfull arts 19:37:47 i like abstract designed artwork but at the same time nature's beauty serve as good artwork; currently comfortable in gimp 19:37:48 suseROCKs: do we 19:38:01 suseROCKs: ok, so we need to have a discussion about the licensing options 19:38:07 yaloki: while I'm not sure we have an official policy, CC-BY-SA has been how I've licensed everything of mine 19:38:08 I can help in Packaging myself but that is at the end of the day 19:38:12 if I'm giving my photography to openSUSE I don't want it to be used elsewhere until openSUSE first uses it. 19:38:19 yaloki, we can. I will note it for our next meeting. 19:38:22 that's my personal artistic feeling about my works 19:38:27 #info we need to have a discussion (ML) about licensing the artwork, and which options we have (e.g. if we want some of the artwork to be usable only for openSUSE) 19:38:39 yaloki, agreed 19:38:45 oh, and then there is the trademark :) 19:38:48 suseROCKs, Yaloki, good points. Thank you 19:38:50 may we discuss the licencing elsewhere 19:38:56 wonder whether we need to clarify anything on that 19:39:09 ok, thanks for your expressing your interests in artwork 19:39:12 may we move on? 19:39:14 just the three last minutes show why 19:39:15 #info do we need clarification on the right to use the openSUSE trademarks ? 19:39:25 yes, also 19:39:28 yaloki, likely :D 19:39:46 let's use the mailing list for this? 19:39:49 may we move on? what do you all say? :D 19:39:52 jdd: sure 19:40:01 yea 19:40:01 I just wanted to keep it as a point in the meeting log 19:40:27 go on 19:40:31 #topic Design Goals. Please state how do you envision openSUSE as a distribution that has good design and artwork. What do you see in it? 19:41:02 that's not a simple topic :-) 19:41:03 it should be pleasing to the eye. unobtrusive... 19:41:09 smooth, polished, and integration (same artwork for different desktop environments, that's something most other distros don't care about at all) 19:41:18 yaloki: to add to your point, it seems the 'correct' artworks for the openSUSE logo are hard to find..they're not on the wiki.. (we have old ones with tm, not correct ones with (c) ) 19:41:37 Ilmehtar: they're in the "official" git repo, under 00assets/ 19:41:42 yaloki: no, they're not 19:41:43 Ilmehtar, I think lawyers said we have to use (TM) 19:41:45 yaloki: those, also, are wrong 19:41:47 the 12.1 artwork is really good 19:41:48 our germans are better than others gremans - by izabel 19:41:49 smooth, polished. Good fonts, good images, should be a catapult for work, not a stepping stone aka, simplified interface. 19:41:51 suseROCKs: the lawyers said we have to use (c) 19:41:53 1 a solid collection of tools: openSUSE should be the distro artists reach for 19:42:06 suseROCKs: rlihm kept on yelling at me when I did 12.1 artwork using TM 19:42:12 use (tm)(c) 19:42:22 and (r) :) 19:42:26 suseROCKs: but we dont have the (c) versions out there publically for anyone to use 19:42:39 2 comunit involvement; revining the aesthetic forstrong appeal 19:42:43 (c) doesn't make sense for artowkr. that's copyright, isn't that for text? 19:42:45 i feel yast lacks branding.. it is too bare 19:43:01 we should also have some contact able to say "yes" use it or "no" don't 19:43:02 suseROCKs: for the logo, geeko+text ..apparently, (c) is correct 19:43:06 subhashish: ugly as hell and causing eye cancer if you ask me ;) 19:43:09 subhashish: That is something rlihm wants to work upon atleast the openSUSE installer 19:43:15 lol 19:43:18 I still have a bugzilla unanswered for month (11.4 :-) 19:43:19 subhashish: You should speak to him 19:43:25 okay 19:43:33 jdd: that's the board, but we need to find a way to have clear policies, to avoid having to ask the board all the time 19:43:34 awesome guys, thank you for that input 19:43:36 i think we better reinvestigate that. I'm almost certain I was in a conversation at some point where the lawyers said (tm) 19:43:43 are we good to move on? 19:43:45 the board do no give answers :-( 19:43:55 no wait anditosan 19:44:00 #info need to clarify whether (tm) or (c) on trademarked artwork 19:44:02 hehe , go ahead friend :D 19:44:10 jdd The board has to be asked a quesiton before it can be given an answer :-) 19:44:15 what about the sonar theme we lost with gnome 3? 19:44:15 go solution is not our :-) 19:44:50 any replacements in line for custom theming with gnome-shell? 19:44:54 suseROCKS: I made a bugzilla for that (as instructed) and also sent a mail: no answer 19:45:00 subhashish: from what I've read here and there, someone has at least been working on porting it to gtk3 19:45:03 may be they didn't receive it :-) 19:45:04 subhashish, I understand there are a couple of people from artwork who contributed with it. It turned out really good. Although if we were to use tit for next release, we will have to reviewe it in light of this meeting's comments. 19:45:19 I believe bear454 is one of them 19:45:30 bear454, did you work on "sonar"? 19:45:52 * yaloki brb 19:45:52 yaloki: http://en.opensuse.org/openSUSE:Artwork_brand says: openSUSE must have a registered trademark symbol (R). 19:46:07 I did a Sonar chrome theme, thats all 19:46:14 thank you 19:46:35 bmwiedemann, yes. Depending on which piece is actually registered. 19:46:36 openSUSE ®©tm 19:46:42 ok, subhashish, let's make a note of that and we can discuss it more in detail with the creators of the theme. 19:46:52 (r) for those that were properly filed and (TM) for those that are not filed but "common law" 19:46:53 also we would need a different theme for windows in kde - the oxygen theme is very paiful to the eye 19:47:02 bmwiedemann: oh yes..my mistake..(r) not (c)..either way, all of our assets on the wiki and in git have TM in them and are therefore wrong, and that's my point :) 19:47:12 Brb. - need to check into my flight 19:47:17 plus openSUSE would have a different identity.. 19:47:24 anditosan, okay 19:47:41 #info bear454 checks into flight to Bermuda triangle 19:47:49 are we good to move on? 19:47:56 yes 19:48:14 anditosan: ok 19:48:22 bear454: very nice place for artwork :-) 19:48:45 #topic jumping into Long Term Goals. Please state the ideal opensuse view from other people about our design. What do you think they would say about opensuse's design overall? 19:49:01 it is openSUSE bugbot 19:49:38 openSUSE is the best integrated project ever 19:50:00 would be nice to keep some consistency over releases. like the green, the polished nice look 19:50:16 with the new release cycle openSUSE must have evolutionary artwork for every main.x release 19:50:27 get changes smooth and progressives 19:50:38 like evolution in 12.2 and 12.3 inspired by 12.1 19:50:52 #chair Ilmehtar 19:50:52 Current chairs: Ilmehtar anditosan bmwiedemann yaloki 19:51:22 I believe integration is really what is cited most often 19:51:30 bmwiedemann: consistancy..I agree, but how do we do that without being boring? 19:51:32 subhashish: actually, 13.1 should be as close to 12.3 as is 12.2 - major number does not mean anything 19:51:53 I think people will say, "there is nothing lacking in opensuse, and it looks sooo good. A pleasure to work with." Green has never looked so good." 19:52:28 I believe this is a good question to be part of a kind of pool/poll . Like some other questions here, I think is a good idea to have a quickly questionary about openSUSE artwork, publish in some blogs, portals 19:52:35 well, "doing the most awesome artwork" is not really a goal, that's an ideal :) 19:52:45 CarlosRibeiro +1 19:52:59 yaloki, exactly, what is your ideal? 19:53:14 nothing too long or complicated, but I think is a good idea to collect some feddback from outside view, maybe others users from others distros, projects... 19:53:34 bmwiedemann, still in the light of numbering scheme i think that would help differentiate the version nos. atleast 19:53:36 anditosan: consistent, unique (identity), smooth, and integrated 19:53:39 #info investigate using connect/ML/other projects to get wider feedback on Long Term Goals 19:53:54 as I understood, humans can distinguish green shades best (which can make good design hard) - but we can use that to our advantage by using a different green for every release (we already did) 19:54:08 and green is our identity :) 19:54:12 anyone else would like to answer the topic question ? 19:54:18 yaloki, +1 19:54:26 we can also have green + other color. Gray was proposed 19:54:29 "Green is good for you" ;) 19:54:32 grey 19:54:38 jdd: sure 19:54:44 jdd, those two have always been my favorite for the distro 19:54:46 the installer is green+grey 19:55:01 well, anything works with grey :) 19:55:02 I think after the 12.1 community vote we really must accept that green is the communities choice, at least for now :) 19:55:06 should we revise our color scheme? 19:55:11 anditosan: no 19:55:12 gray/black/white are not really colors - so they are easy to get in. yellowish was also part of openSUSE artwork (11.2) 19:55:23 anditosan: ;-) see what I said right before you asked that ;) 19:55:32 Ilmehtar, noted! 19:55:38 green, yelow, blue, ... I don't think we need to care about this now. 19:55:38 green is a starting point, but we can evolve (reasonably) 19:55:48 green is an awesome colour 19:55:51 we need to stablish a way to reintroduce our new phase to the world 19:55:54 jdd, +1 19:55:57 yes, green is great 19:56:05 I think we can make green work so well if we put our expertise to it 19:56:11 awesome, thank you all 19:56:20 like SUSE is here, more closed with openSUSE than ever Novell though about 19:56:21 IMHO green is a *must* 19:56:21 let me now move you to our QA section 19:56:26 so many different shades, works so well with many different things..yes its got its flaws but I've really been surprised how flexible green can be 19:56:27 so green is great but we need a definite way to iterate it 19:56:35 true 19:56:46 do we all agree to do QA? 19:56:51 yup 19:56:52 yes 19:56:54 #topic QA 19:57:03 First question - is a mail in from henne 19:57:11 02:55, 24 November 2011 (MST): Can you consider merging your IRC channel into #opensuse-project so we have less channels and everybody gets to see what you are doing? 19:57:13 Ilmehtar will lead this part of the discussion as I need to check in back to work. I know, lame. :D 19:57:25 if we start a good plan, strategy for artwork, we will find the correct color for correct ocasion. 19:57:29 What do we all think? I actually like the idea.. 19:57:36 \me late =( 19:58:11 why merge channels that are anyway temporary? 19:58:59 jdd: what's temporary? 19:59:09 temporary? this channel is permanent, requires ops, draws users, and (IMHO) seperates us 'artworkers' from lots of good feedback we could get if we conducted our business in -project 19:59:12