18:02:09 #startmeeting openSUSE project meeting 18:02:09 Meeting started Wed Sep 21 18:02:09 2011 UTC. The chair is mrdocs. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:09 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:02:11 dragotin: Yes, meeting! 18:02:15 * suseROCKs wonders if that's going to make dragotin run now 18:02:15 even better 18:02:30 #chairs prusnak suseROCKs AlanClark mrdocs 18:02:45 I assume henne is on FTO? 18:02:51 #chair prusnak suseROCKs AlanClark mrdocs 18:02:51 Current chairs: AlanClark mrdocs prusnak suseROCKs 18:02:51 he is 18:02:53 suseROCKs: Yes, he is 18:03:19 #chair henne 18:03:19 Current chairs: AlanClark henne mrdocs prusnak suseROCKs 18:03:23 just in case 18:03:35 shall we begin ? 18:03:37 Have we heard from Rupert? 18:03:47 not recently 18:04:01 ok, on with the agenda 18:04:08 I run to another computer, see you soon 18:04:10 #topic Old Action Items 18:04:23 #info http://bit.ly/opensuse_action_items 18:05:12 I don't think there's anything discussable in that list right now 18:05:24 they're almost all stagnated for various reasons 18:05:26 * mrdocs nods 18:06:04 hmm that should be a new status item for bugzilla "Status = Stagnated" :-) 18:06:07 #info http://bit.ly/opensuse_board_ais 18:06:12 suseROCKs: Stuck 18:06:38 thought Stuck meant Breakfast :-) 18:06:41 bug 670594 18:06:41 openSUSE bug 670594 in openSUSE.org (Board) "Write an announcement about the new process of creating the foundation." [Critical,Assigned] https://bugzilla.novell.com/670594 18:06:58 https://bugzilla.novell.com/show_bug.cgi?id=670590 18:07:01 openSUSE bug 670590 in openSUSE.org (Board) "user search for bugzilla" [Normal,New] 18:07:04 all items here is also stagnated/stuck 18:07:09 * mrdocs nods 18:07:16 * mrdocs moves on 18:07:32 #topic Status Reports 18:07:47 wstephenson: vuntz anything from Desktop Teams ? 18:08:14 mrdocs: usual package updates 18:08:22 re 18:08:33 dragotin: ? 18:08:43 yes 18:09:05 thought you had something to report, other than beer consumption at OSC :) 18:09:08 he's just saying he's back in case we didn't miss him, but fact is, we ALWAYS miss dragotin! 18:09:17 * mrdocs nods 18:09:22 wait... there was beer??? 18:09:31 sorry, didn't want to confuse 18:09:38 dragotin: NP 18:09:46 next any other status reports ? 18:09:58 Beta of 12.1 has been delayed by up to two weeks 18:10:02 yes 18:10:10 good thing methinks 18:10:30 another status update.... Marketing team had its hackfest this past Thurs and Friday 18:10:48 a lot of tasks got assigned and we'll see some good results in time for 12.1 release day I'm sure 18:10:50 * manugupt1 will say what he did at the fest 18:10:58 go for it, manugupt1 18:11:06 manugupt1: we are all ears 18:11:09 Well we plan to work on openqa 18:11:27 awesome 18:11:28 We have release announcements ready and me and Jos wants to make it the next big software at openSUSE 18:11:42 Something like openSUSE Project = openSUSE + OBS + OpenQA 18:11:47 We have 5 articles ready 18:11:56 Bernhard is making a 1.0 release soon 18:12:02 great stuff ! :) 18:12:18 By 11th october it should be on news / media 18:12:28 and then a series of howtos if the media agrees 18:12:29 #info openqa will make a 1.0 release by 11 Oct 18:12:44 That is what the plan is 18:12:46 * dragotin doesn't really like the equation 18:13:00 dragotin, what would you suggest? 18:13:08 Anyone can chip in here http://ietherpad.com/openqa 18:13:21 Ok.. We just thought and would like 18:13:31 openSUSE is still more than openSUSE + OBS + OpenQA 18:13:54 for example community :-) 18:14:00 dragotin: But its not public yet.. something we need to work on I agree 18:14:08 ok 18:14:10 dragotin: We are the biggest community no one can beat that :) 18:14:19 The whole world agrees 18:14:20 I agree with dragotin. There's more to the project. 18:14:20 dragotin, well you're right about that. During the "Message BoF' at the conference, people wanted the distro to be distinctively named. "openSUSE" should be generic, while Distro should be something like "openSUSE Distro" or something like that 18:14:30 + good beer :) 18:14:52 and I will be publishing my BoF report tomorrow on the Message BoF 18:14:57 suseROCKs: good point to have openSUSE set free 18:15:24 anything else for this ? 18:15:29 any other reports ? 18:15:34 how about a conference report? 18:15:41 overall stats and such? 18:15:41 we can name it coolOpensuse :) 18:15:48 coolo: :D 18:15:50 suseROCKs: One has already been published during the hackfest 18:15:51 coolo: lol 18:15:57 but more are welcome :) 18:16:08 manugupt1, yes but I'm saying a status report that is entered into the record here 18:16:20 Oh.. sorry.. 18:16:24 dragotin: of course written with the stereo sign where the O is 18:16:33 osc11 huge success, what more can be said? 18:16:47 * mrdocs was really sad to miss it 18:17:03 Did we raise some decent funds from beer and t-shirt sales? 18:17:04 * AlanClark wonders what happened to the left over beer? 18:17:16 AlanClark: prolly none left ;) 18:17:19 AlanClark: its in the office 18:17:19 Awesome beer and pizzas and lots of cheese 18:17:28 i guess we now know why we haven't seen henne since the conference ended :) 18:17:31 by the way, henne never brewed that root beer for me ;-) 18:17:34 AlanClark: the next event is on october 22nd 18:17:50 dragotin: where ? 18:17:51 for me was great cause I'll step into wiki team to help henne 18:17:52 What s on Oct 22nd? 18:18:11 An event called "Lange Nacht der Wissenschaften" 18:18:21 its a Nuremberg local event 18:18:22 izabelvalverde: awesome... big necessary job :) 18:18:31 of tech companies, universities and such 18:18:36 dragotin, are you just saying that to try to get me to twist my tongue? 18:18:52 we have a room there at the university in Nbg. 18:19:01 suseROCKs: now I am, sorry, kids → bed and such 18:19:03 and will see more than 1000 people there probabbly 18:19:10 mrdocs besides a great team ;-) 18:19:22 yaloki: o/ 18:19:31 dragotin; glad to see it go to good use 18:19:39 Speaking of events... openSUSE Community will be making its first official appearance at Brainshare in 3 weeks from now as special guests of SUSE. W00T! 18:19:51 yup 18:20:03 big important place for visibilty 18:20:07 next 18:20:14 any other remaining reports ? 18:20:16 and also comment on this it would be great for a few people I know and have mentioned there http://sysbytes.wordpress.com/2011/09/19/opensuse-india/ :) 18:21:26 manugupt1: make sure those are on planet and in news where appropriate 18:21:29 ok mrdocs I guess that's all the status updates 18:21:37 * mrdocs moves on 18:21:40 mrdocs: yes.. 18:21:59 #topic 2012 elections 18:22:15 Do we really have to talk politics ? 18:22:18 :) 18:22:29 who wants to start on that one.. anyone from current commitee 18:22:31 ? 18:22:34 only when it involves your extreme leftist views, bear454 :-) 18:22:39 we have a commitee yet ? 18:22:41 mrdocs, I'll take this one 18:22:52 suseROCKs: go go go 18:22:56 mrdocs: There's no current committee - just the one from the last election;) 18:23:02 no we don't have a committee yet, but AlanClark and I have already begun drafting the request for volunteers 18:23:34 it requires the board to review the text and modify where appropriate and then I'll post it ASAP where relevant 18:23:35 http://ietherpad.com/board-elections 18:23:37 suseROCKs: what else needs doing ? 18:23:39 I can step into committee if it needed 18:23:58 need to mention that we discussed the elections at the osc general meeting. 18:24:05 * suseROCKs adds izabelvalverde to the committee list of volunteers 18:24:36 Thanks izabelvalverde! 18:24:40 izabelvalverde: kudos 18:24:44 * mrdocs wonders if oy would also help 18:25:06 we had 2 people volunteer at the general meeting 18:25:17 wstephenson: would you be interested in being in the election committee again? if I'm not mistaken, you were part of it last time 18:25:19 AlanClark: how many do we need in total 18:25:32 Deadline of 7th October is too long IMO. Let's get this out and have it closed before the next project meeting 18:25:35 237, mrdocs 18:25:48 yaloki: I think it was digitltom 18:26:01 AJaeger, that's fine too. We litterally made this draft an hour ago and its just a brain dump as of now 18:26:11 drago: oh.. but wstephenson was in in the time before then, I'm pretty sure he was 18:26:11 AJaeger, I agree 18:26:14 :) 18:26:58 ok, so once we have the committee we need a time frame 18:27:04 Last year it was digitltom, Sascha Manns, Stathis Iosifidis, Satoru Matsumoto 18:27:05 exactly 18:27:09 I already announced I'm running 18:27:37 yaloki: You need to announce it properly once the election committee has declared how to do it ;) 18:27:42 AJaeger: yep 18:27:44 yaloki, the time frame is primarily designed by the committee itself 18:27:52 correct 18:27:53 so the sooner we get the committee formed, the sooner the time frame evolves 18:27:57 yaloki: But it means you should not join the election committee... 18:28:03 AJaeger: I know, I won't :) 18:28:17 mrdocs: yes, I would help 18:28:18 not to speak for digitom, in talking to him he said he would help. He's not available to lead, but will help with the technical stuff 18:28:28 kudos to oy too! 18:28:40 ok so we have two volunteers now 18:28:48 do we want to set a cap for number of volunteers? 18:28:52 oy: yes... i think you have done a lot and certainly are trustworthy 18:28:56 wasn't it 5 people ? 18:28:58 or 3 ? 18:29:16 4 last year 18:29:25 let's cap it at 5 18:29:29 I wonder whether 3 would be sufficient, actually 18:29:33 suseROCKs who's 2? 18:29:35 "The election is run by an Election Committee that consists of at least three openSUSE members. The Election Committee is appointed for each election by the board. " 18:29:40 izabelvalverde, you and Oy 18:29:43 * AJaeger cites the rules 18:29:50 and, as AlanClark said, probably digitltom too 18:30:03 ok so 18:30:04 so we might have 3 already 18:30:16 oy: weren't you on one of those committees in the past ? 18:30:25 well digitltom never really considred himself an active member of the past teams, just a tech assistant iirc 18:30:29 yaloki: No, he was not. 18:30:31 would be good to know from someone who has been there whether 3 is enough 18:30:38 suseROCKs: He was active. 18:30:43 hmmm okay 18:30:45 ok 18:30:51 #info izabelvalverde oy and 2 others have volunteered to work on Election Commitee 18:30:56 yaloki: You need two active and committed people ;) 18:30:59 any action items ? 18:31:03 * yaloki is being too practical right now :> 18:31:08 so does this mean we don't have to do an announcement after all? :-) 18:31:18 So, should we just make the three the commitee and not do a call for volunteers? 18:31:24 yeah, we annouce the appointments 18:31:28 AJaeger: +1 18:31:29 let's do the announcement 18:31:35 no i we still ask 18:31:39 suseROCKs: please do, but sent it ASAP 18:31:41 * nmarques loves democracy 18:31:48 so if someone wants to, can raise their hand 18:31:59 prusnak, ok but we need to make sure the text is agreeable. 18:32:11 Also AJaeger proposes a different deadline date for volunteers. What is the new date proposed? 18:32:23 mrdocs: Then make a short timeline - next project meeting is on the 5th, so make the deadline the 4th. 18:32:35 AJaeger: yeah true, that's probably better indeed 18:32:36 ok I'll modify it then 18:32:49 * suseROCKs modifies and will send out after the meeting 18:33:05 #action item - AlanClark suseROCKs to make announcement calling for Election Commitee volunteers 18:33:12 if there4s any other textual polishings, please speak now or forever hold your peace :-) 18:33:13 of those who volunteered today, are any of you williing to lead the committee? 18:33:28 I'm not :-D 18:33:36 #action deadline 4 Oct 18:33:44 the text looks ok to me 18:33:46 AlanClark: what's involved in "leading the committee" ? 18:33:47 next ? 18:33:57 mrdocs, I think your action item needed a little more decriptiveness :-) 18:34:02 AlanClark: wiki link ? 18:34:15 suseROCKs: yup 18:34:21 bear454: keeping the commmittee on track 18:34:33 bear454: The leading is informal, there's no leader but you need to keep everything on track. 18:34:45 reporting to the board in a timely fashion 18:34:46 bear454: http://en.opensuse.org/openSUSE:Board_election 18:35:03 that sounds like something I'd be *horrible* at :/ 18:35:12 mrdocs: The election committee does not report to the board - it works on its own once setup. 18:35:20 * mrdocs nods 18:35:39 and tom is there with his experience for the technical side of things 18:35:43 (voting, counting) 18:35:44 But you don't want to kick it awake every two weeks ;) 18:36:11 next ? 18:36:17 anything else to add 18:36:18 ? 18:36:19 AJaeger, it doesn't report per se, but it should give regular status updates to let us know things are on track 18:36:41 and that can be done during Project meeting's Status Updates topic section 18:37:10 Yes, it should inform the community what the status is. 18:37:55 ok I think that's all for this topic... /me yields the floor back to meeting chair 18:38:12 bear454: by the way, you'd make a great lead. 18:38:37 #topic permission@ requests 18:38:41 First 18:38:50 Request for Bronze sponsorship of openSUSE from Heinlein Support 18:38:57 GAH 18:39:05 * bear454 volunteers to lead the election committee 18:39:06 comments ? 18:39:13 I'll take the lead on this one 18:39:25 #info bear454 to lead the election committee 18:39:43 Board members, you should have seen the permission request on this. 18:39:53 yup 18:39:58 i see no issues there 18:40:09 si 18:40:22 suseROCKs: there are ? 18:40:29 no 18:40:33 +1 from me 18:40:37 si to AlanClark saying we should have read it :-P 18:40:41 What I would ask from the board is to approve the proposal to add them as a Bronze Sponsor with AJ and I to work the details 18:40:54 AlanClark: great 18:40:57 Bronze Sponsor for what? 18:41:02 openSUSE 18:41:04 well hang on AlanClark .... 18:41:06 drago: Bronze Sponsor for the project 18:41:20 what will they donate? 18:41:25 I welcome sponsors, just like all others. But one thing we've always raised the question of in the past and never quite figured out how to answer is... "What does sponsor mean?" 18:41:33 drago: Those are the details to work out ;) 18:41:51 drago: Hosting is one option - as the two of us discussed at osc11 18:41:52 so we should approve before the details? 18:42:01 I see, thanks 18:42:02 suseROCKs: in this case its money, hardware or services rendered 18:42:24 suseROCKs: I suggest you let AlanClark and myself continue investigating. 18:42:41 AJaeger, that's what I would prefer as well, 18:42:51 I suggest that the two of us report back before we make a final "signature" under everything, we'd like to have a "go ahead and work out details" 18:42:53 unless you are asking us to approve the investigation itself? 18:43:04 yes AJaeger +1 to that 18:43:07 And your guidance on what to look for 18:43:17 ok I move we ok it as AlanClark suggested then a final ok after the details are understood 18:43:36 +1 (official vote) 18:43:37 a second ? 18:43:47 prusnak: ? 18:43:55 don't go parliamentarian on us mrdocs :-) 18:44:05 i am okay with investigation 18:44:11 suseROCKs: trying to move things along :) 18:44:19 i don't think we need to vote on investigating 18:44:53 no but its fun to use the keystroke combo once in a while to create the + sign :-) 18:45:16 next item? 18:45:32 #info AlanClark AJaeger to further discuss and report final details for Heinlein Support 18:45:43 Open Source Press ? 18:46:01 This is another request that came in from @permission 18:46:03 I'll say a couple things there 18:46:34 I have had a good experience with them in discussing a book contract 18:47:14 very pro open source, good people to work with 18:47:16 eg 18:47:31 very responsive and reasonable 18:47:49 i need to re-read their request, but i did not see anything which bites 18:47:50 but 18:48:15 that's all very good and I have no doubt of their professionalism. However they are requesting an exclusive contract to distribute boxed 12.1 DVDs and that's a problem in my book. 18:48:17 There is one think we should discuss for sure - exclusivity. 18:48:29 requesting to ship a box.. no issues there, but not exclusively 18:48:30 and 18:48:44 why not exclusively? 18:48:49 its not clear to me if it is meant in German or English or other languages 18:49:05 they are talking about a *openSUSE* box, right 18:49:07 ? 18:49:12 mrdocs: German for sure, the others I don't know 18:49:19 drago, For one thing, we have already given approvals to others in smaller groups to distribute openSUSE in their regions. We can't shut them down 18:49:19 AJaeger: exactly 18:49:33 so exclusivity would not harm any derivates 18:49:44 suseROCKs: whom? 18:50:02 we'd have to look back our records for whom, but there's someone in England if I'm not mistaken 18:50:04 exclusivity would be better than nothing here in Brazil 18:50:10 may I ask one simple question ? 18:50:18 just plain curiosity 18:50:27 nmarques: just ask :) 18:50:28 when one asks for exclusivity he has to give something back 18:50:29 suseROCKs: SatManUK, you're right 18:50:40 what are they offering for 'exclusivity' ? 18:50:50 what does openSUSE gets from it ? 18:50:51 nmarques: doing it in the first place, I guess 18:50:56 nmarques, at this time they are offering nothing except asking for exclusivity. That's the other issue I have 18:51:09 so the answer seems to be quite easy :) 18:51:16 I lay back now 18:51:18 I think the exclusivity is only about the "box" - and I would not make it any broader. 18:51:30 but we hve had problems with "exclusive" distributors in the past. and I don't see why we want to get locked into something that only one distributor gets to do 18:51:47 plus in their email request they ask for advertisement space on the .de version of openSUSE website. 18:51:55 suseROCKs: nobody will make the investment if it is not exclusive 18:52:03 That tells me they don't necessarily have a plan to reach out to other markets. 18:52:04 From the request: " 18:52:06 We may use openSUSE trademarks, logos, and artwork for the software 18:52:06 suseROCKs: Besides SUSE in the past, there was never an exclusive distributor 18:52:07 and how many official opensuse boxes do you want to have? 18:52:07 box openSUSE 12.1. We may use these exclusively, ie. other companies 18:52:09 like open-slx GmbH are not allowed to use trademarks and logos for 18:52:10 version 12.1. 18:52:31 AJaeger, open-slx claimed to have a contract (though maybe not necessarily "exclusive") 18:52:32 just another question 18:52:40 suseROCKs: Not exclusive! 18:52:41 in which case, exclusivitity takes this to a higher level than in the past 18:52:48 how much is worth the german market for openSUSE in value and volume ? :) 18:52:57 that would point how much 'exclusivity' is worth 18:52:57 when in the past exclusively? 18:53:01 nmarques: good question 18:53:11 mrdocs: ;) 18:53:39 I doubt they will sell more than 10000 boxes. 18:53:39 now so we obviously cannot accept their proposal as is 18:53:47 10.000 boxes ? :) 18:54:03 that's quite a lot 18:54:03 if so great!!! 18:54:04 I don't know. I just see repeat problems of the past if we have to do a contract. 18:54:08 how do we move forward ? 18:54:14 my advice ? 18:54:17 depends on how they market it, right? 18:54:18 nmarques: That's a few - we had 200000 in the past. 18:54:21 nmarques: be careful with your thousandths separator... in US 10.000 == 10. 18:54:33 take no action until you have all the data 18:54:39 bear454: I meant 10k ;) 18:54:50 we're talking maybe on big numbers 18:54:56 with zero return for openSUSE 18:54:58 ;) 18:55:04 and we still have to make free advertisment ? 18:55:09 sounds like a very good deal 18:55:11 for them 18:55:12 :) 18:55:15 nmarques: It's small numbers with the margins they have. 18:55:23 nmarques: there is an implicit turnaround though 18:55:27 nmarques: more users 18:55:29 nmarques: you could have applied as well :-) 18:55:36 return for opensuse is that there ARE actually some boxes 18:55:40 yaloki: more users? sounds like a falacy to me 18:55:41 right 18:55:48 and nobody said that there is zero return for opensuse 18:55:50 mrdocs, I'll take the action item to reply to their request; explaining that we are not inclined to offer exclusive, etc... 18:55:51 yaloki: who buys boxes ? legacy users or new users ? :) 18:55:54 nmarques: well, if they don't do it, there is no boxed openSUSE at all 18:56:06 yaloki: yeah, I'm not against 18:56:07 nmarques: in countries with bad internet connections, it's still very much an option 18:56:11 (and that includes germany) 18:56:12 yaloki: just take something out of it 18:56:16 yaloki: for example 18:56:20 yaloki: unfortunately true :-( 18:56:23 AlanClark: let's work on this together as I have had contact with Markus as well 18:56:29 yaloki: they should do the advertisement for openSUSE, not the other way around 18:56:30 nmarques: I see your point, but as AJaeger said, the margin is very low 18:56:43 yaloki: the problem isn't the margin 18:56:51 yaloki: we can't take money from them can we ? :) 18:56:54 One info: We should really reply to them today, they are time constrainted to hit the christmas season. 18:57:00 yaloki: so the $US or €'s are not worth 18:57:07 nmarques: probably difficult, indeed 18:57:10 yaloki: but we can take other things, like advertisement and promotion 18:57:16 sure 18:57:17 mrdocs, +1 in working together. I'll draft an email and send it to the board for review 18:57:17 but more users and someone doing what we can't 18:57:18 yaloki: we shouldn't advertise for them 18:57:24 they should be advisertising for us ;) 18:57:33 nmarques: we advertise anyway 18:57:34 ok let's let AlanClark and mrdocs proceed to reach out to them to work out more detailed data and then we can make a more informed choice 18:57:41 #action AlanClark and mrdocs reply to their request of OSP , but to decline the "exclusive" part 18:57:46 but I'm not voting for any exclusivity at this time 18:58:00 suseROCKs: no it definitely needs more definition 18:58:02 more interesting is if they will provide install support for example 18:58:04 I only suggest one thing 18:58:05 the exclusivity bit is really the tricky part, everything else, well, why would we be opposed to it 18:58:05 suseROCKs: I'm against exclusivity - and if we do it, limit it in time and region! 18:58:15 dont hand over exclusivity for periods longer than a year or a cycle 18:58:21 so if something goes really out of hand 18:58:33 we have a natural contractual bail out ;) 18:58:33 AJaeger: *definitely* time-limited and requiring re-negotiation for example 18:58:39 we know what happened in the past 18:58:46 But you can say: We will inform you before we give somebody else the same rights. 18:58:46 nmarques: agreed 18:58:47 AJaeger: +1 18:58:48 nmarques yaloki even more, specific targets 18:58:51 AJaeger, limited may be thecompormise option 18:59:00 next 18:59:09 HaiSoft 18:59:21 * mrdocs does not recall seeing that one 18:59:34 bootable usb key thingie 18:59:54 heh - seems we're hyping :-) 19:00:00 distributing bootable openSUSE USB keys? 19:00:00 And this is not a box - but openSUSE sold in a shop and thus competition to what OSB offers. 19:00:18 * yaloki thinks "OHaiSoft" would be funnier 19:00:20 This one just came in from @permission, not all may have seen it yet 19:00:35 AlanClark: no i just searched, can you forward ? 19:00:36 * suseROCKs goes to look for it 19:00:59 19:38 CEST 19:01:07 subj: openSUSE logo for bootable USB Key 19:01:09 today ? 19:01:17 yes 19:01:17 mrdocs: today, 90 minutes ago 19:01:20 got it 19:01:21 yes it just came in today. 19:01:21 AJaeger: so it goes back to OSB again, and limiting what that exclusivity means, but that's something that needs to be taken care of anyway, to avoid making it impossible for communities to distribute DVDs and such 19:01:22 "I am contacting you because I would like to print the openSUSE logo on a 19:01:22 USB Key. This key will be sold with the latest Live version of openSUSE at 19:01:22 a reasonable price, across Europe. 19:01:22 " 19:01:26 buried :S 19:02:22 that one I can easily _+1 on. Doesn't request any burdens upon us and accepts his own role and burdens for the distribution of the keys 19:02:46 nmarques: I would have expected you to speak up and ask to get something back for the project ;) 19:03:07 I'm +1 on this one 19:03:13 +1 here as well 19:03:23 Haisoft wants to make money with it - anything we won't to have go back t othe project? 19:03:29 and we do get these types of requests from time to time, which is why agreeing to an exclusivity contract is not exactly a good thing 19:03:58 AJaeger: maybe some usb keys for free? ;-) 19:04:11 AJaeger, well here's what we came up with a few months ago. Since we haven't really gotten a foundation in place, we decided that any requests that have money-making potential will be granted a one-year limited permissions 19:04:12 I have an additional question on these topics: Currently we have links to open-SLX for the openSUSE 11.4 box. Would we link to Haisoft? 19:04:20 suseROCKs: Ah, ok. 19:04:24 suseROCKs: otoh it could be a bit weird to have *two* resellers propose openSUSE 12.1 boxes on the shelf :) 19:04:25 that way we can revisit the issue in the future in accordance with the business plans of openSUSE Project 19:04:47 yaloki, I don't think its that weird 19:04:55 yaloki: Yeah, one DVD, one USB key. 19:05:08 AJaeger: that's alright I think, but having 2 boxed sets.. heh 19:05:14 well yeah, maybe it isn't weird 19:05:19 USB cheaper to ship! 19:05:20 the more the merrier :) 19:05:31 well haisoft is only proposing live images, not installers 19:05:33 true, true :) 19:05:36 so 19:05:40 yaloki, a store owner/store product buyer isn't likely to buy the same product to stock their shelves from two different vendors 19:05:58 +1 Prusnak 19:05:59 +1 for me as well, if limited to one year as we have done with prior requests 19:06:14 ok who replies ? 19:06:24 I can do it 19:06:33 jfyi there is one no vote from someone from the legal dept 19:06:35 I suggest another topic: How do we promote these boxes/products from our pages? How prominently do we want this - and this includes also derivates like the open-SLX 19:06:36 suseROCKS - I'll do it 19:06:38 how do we deal with this? 19:06:51 are we overriding this? 19:06:51 ok AlanClark 19:06:52 suseROCKS - I need to include novell legal on 19:07:10 prusnak: there are only two options: promote all or promote neither 19:07:27 prusnak, let AlanClark slap around the legal department until they fear him and give him anything he wants under the sun :-) 19:07:36 AJaeger: sry I missed something... get back what ? 19:07:46 AlanClark: It's Scott Corfield - isn't he marketing? 19:07:46 #action AlanClark to contact legal and follow-up with HaiSoft, board votes OK with permission 19:07:49 AJaeger: was answering mails :/ 19:08:02 Scott is marketing not legal 19:08:04 nmarques: No problem - read the above discussion on haisoft. 19:08:06 AJaeger: about the USB sticks ? 19:08:13 AJaeger: yeah, I would ask something 19:08:24 AJaeger: a % of sticks for our own marketing and events 19:08:27 AJaeger: yes good point about our promotion activites 19:08:35 AJaeger: so we can distribute a few to our users/enthusiasts 19:09:00 AlanClark: ^^ can you add this to your reply ? 19:09:04 AJaeger: I can contact a few companies in Shen Zen or whatever it's called to check for the normal prices of USB sticks (manufacturing costs) 19:09:29 AJaeger: I do have a few contacts, but I would say that the production cost of a 2/4GB stick is bellow 1€ 19:09:43 AJaeger: so asking them a few hundreds would be sane enough :) 19:09:50 mrdocs: I'll add the request to the email 19:09:58 nmarques: plus in some countries there is a media tax + duties 19:10:06 AlanClark: thanks :) 19:10:09 mrdocs: export laws 19:10:13 anything else on this ? 19:10:25 I think we can move on 19:10:35 mrdocs: either way production costs are low 19:10:40 #topic where can we improve ? 19:10:48 #info http://en.opensuse.org/openSUSE:What_to_improve_osc11_session 19:10:58 mrdocs: asking like 500 sticks for our own marketing peeps wouldn't sound unresonable to me 19:11:16 mrdocs: plus the promotion we can give and visibility 19:11:17 nmarques: i agree if they are making 10k 19:11:33 mrdocs: that's my suggestion :) 19:11:40 mrdocs: but it's really up to you guys :) 19:11:50 mrdocs: and yeah, I'm the mercenary kind :) 19:11:58 nmarques: let's see what AlanClark comes up with 19:12:03 nmarques: good suggestion 19:12:28 prusnak: yeah, give the tools to our most efforted ambassadors 19:12:36 nmarques: exactly 19:12:38 prusnak: they will make good usage of them :) 19:12:41 I need to step away for a couple minutes 19:12:49 ok me too 19:13:00 does that mean we have intermission? :-) 19:13:22 #topci 5 min intermission 19:13:25 gr 19:13:31 a first! W00T! 19:13:33 #topic 5 min intermission 19:13:42 lol 19:13:54 back @21:18 CET 19:14:02 pee pause break 19:14:14 that was intense! 19:15:19 * yaloki watches the queue to the bathrooms 19:15:50 hmmrmrmm 19:15:52 don't forget washing your hands! 19:15:55 :) 19:17:52 * suseROCKs is back with dripping hands 19:18:12 * mrdocs hopes people also return with favortie $beverage 19:18:24 we're back 19:18:29 * yaloki DCCs a round 19:18:33 #topic where can we improve ? 19:18:39 #info http://en.opensuse.org/openSUSE:What_to_improve_osc11_session 19:18:47 Who wants to start ? 19:18:58 ok so I was at that BoF led by robjo 19:19:12 I suggest we table this till next meeting robjo isn't able to attend today 19:19:18 yeah 19:19:27 and though he's not here, I'd like to commend RobJo for fulfilling our request to do the BoF 19:19:27 unless suseROCKS wants to report 19:19:30 but it is s meaty subject 19:19:45 I'd like to let robjo handle it. He deserves it 19:20:01 yeah that wiki page is well done 19:20:09 +1 19:20:14 +1 19:20:29 robjo is not here today 19:20:48 He suggested before the meeting to postpone until next meeting 19:21:04 #action postpone discussion until robjo can attend 19:21:23 #topic Q&A 19:21:55 Jedibeeftrix asks: Any update on Jos's request for assistance with Bretzn and how this will affect opensuse 12.1? 19:22:12 gah 19:22:13 HAH nice jos! 19:22:28 i can answer 19:22:32 good 19:22:56 next week we have a hackweek in SUSE offices and AFAIK Frank is coming to NUE office to work on integrating Bretzn into 12.1 19:22:57 make an action item for Jos to send prusnak a bag of waffles for stepping in for him :-) 19:23:13 * mrdocs grins 19:23:19 prusnak is right, Frank will be here 19:23:30 ahh that leads to another question 19:23:33 prusnak: good news.. anything else we need to know or do ? 19:23:37 otherwise i don't know about anyone from the community who'd stepped up for this 19:23:46 still that does not mean that he/we can do it alone 19:24:11 drago: what help is needed ? 19:24:16 exactly, so if there are any volunteers, you know whom to contact 19:24:24 mrdocs: coding currently I guess 19:24:31 y'know this is actually an old question that was addressed in previous meeting at some point, just never removed from the wiki. 19:24:34 .oO(usually happens that way, with stuff developed behind the scenes...) 19:24:49 And we don't really have a way of directly answering that question except for expecting people to read our logs 19:25:13 let's add this answer to the wiki page after the question 19:25:33 yaloki: you mean bretzn? 19:25:35 well in this case it seems Jos needs to bang the drum for community participation 19:25:56 well that kind of leads to my next question, mrdocs, which I'm going to address to drago 19:25:59 drago: amongst a few other cases, yes :) 19:26:45 drago, The hackweek itself isn't widely publicized. I planned to write an article but some are telling me this is only for internal SUSE folks and not a broad hackweek for everyone. Can you explain the participatory goals of hackweek? 19:26:51 yaloki: there has been a very public sprint at the beginning of the year, you remember? 19:27:14 drago: nope, so that might be just me 19:27:28 actually I thought it was end of last y ear? 19:27:34 yaloki: it could always be opener of course 19:27:40 suseROCKs: Hackweek is indeed a SUSE internal event - and this year we're a bit late with organizing it. 19:27:53 hackweek: Well, yes, the communication sucks 19:28:13 but AFAIK its of course not "only for SUSE folks" 19:28:13 drago: what I find puzzling is that, typically, the *concept* isn't discussed a lot :\ 19:28:22 well its never too late to communicate, but as one person said to me earlier today, no real need to publicize because externally people can hack anytime they want. I'm not sure I agree with that perception 19:28:23 It's internal but some participants invite others to work with them. 19:28:27 well, effectively, it kind of is 19:28:27 who tells that? 19:28:47 AJaeger: true 19:29:14 so should we or should we not publicize it? 19:29:22 Why should it be internal? I mean, every Geeko can say "I do a hackweek" and hack with us 19:29:34 of course, please publicize 19:29:35 drago, That's my feeling as well. 19:29:47 drago: but why would that be hackweek, everyone else is doing it during their spare time, just as usual 19:29:51 drago: Indeed - but you don't want to have to mentor everybody on how to e.g. work the build service. 19:29:57 we have many things to publicize not sure if SUSE should be the main need right now 19:30:27 but we've publicizzed hackweeks in the past 19:30:33 hackweek since its 3rd edition is not what it used to be (1st and 2nd one) 19:30:35 guys, if somebody does NOT want to mentor - granted. He/she can simply say that. 19:30:51 izabelvalverde: good point and moreover, many of the devs blog about their stuff, during and after it 19:31:01 prusnak: what's different ? 19:31:02 But I do not see a reason why we shouldnt beat the drum just because of that 19:31:35 mrdocs, but simultaneously, having an actual hackweek may inspire someone who does have skills do do their own hacking but has been procrastinating up to now. That's where publicizing does a good thing 19:31:37 mrdocs: well, if it were not for this meeting you would not learn about it 19:31:39 we need good marketing and hackweek is a good thing 19:31:44 so lets talk about that 19:31:50 while back then nat was writing about it literally everywhere 19:31:54 plus since hackweek is about anything under the FOSS sun, it enhances our image that openSUSE is more than just a distro. Its a project that fosters all of FOSS 19:32:10 but we faild to find a replacement for him once he started to work on studio 19:32:10 I think we should write something - with two intends: One the one hand to invite to hack together, on the other to tell that many people are hacking on projects out of their comfort space. So, they might hang around in other channels with other problems than usual. 19:32:37 "invite to hack together" … 19:32:50 or invite to just hack, period? 19:33:02 well 19:33:10 there is definitely a need for information about it 19:33:13 "invite to hack together" 19:33:17 but fwiw i think having an internal hackweek is fine 19:33:26 because, inevitably, some people will hackweek on things other people have already been doing in the community 19:33:28 we just have to decide if it is a public event or now 19:33:31 and which they don't know about 19:33:35 so hackweek can do harm as well 19:33:43 because if it is we should sponsor some people to come to the offices 19:33:49 prusnak: It will be a public event - because people speak about it like we do here ;) 19:33:54 yaloki: please... 19:34:08 prusnak, I don't think we have to get to the point of sponsoring travel, especially since it starts this Monday 19:34:20 prusnak: of course it is public 19:34:29 drago: "please" what? just saying, needs to be some interaction 19:34:50 drago: really? i learned about it 2 days ago 19:34:53 drago: the potential is there, so, information is needed 19:34:55 yaloki: interaction is *always* needed, right? 19:34:58 yaloki: How does that harm the project off topic though 19:35:26 doing FOSS can never harm, right? 19:35:27 manugupt1: because other people have been doing something during their spare time and then, suddenly, bang, someone else is doing the same without re-using what has been done 19:35:34 evne if efforts are doubled 19:35:40 oh hell no 19:35:42 thats one of the mechanisms of FOSS 19:35:51 not if you want to be a community 19:36:05 I am not saying we should strive for 19:36:06 surely 19:36:07 yaloki: Unless entangled in ego issues.. it should not harm imo yes duplication sucks 19:36:20 But sometime stuff happens 19:36:28 it's a little more complex than that though 19:36:36 yaloki: where do you see a problem? 19:36:41 yaloki, does have a point, and he is speaking from personal experience on this matter as he got "banged" 19:36:41 yaloki: speak out bluntly 19:37:03 suseROCKs: but it's not even that what I have in mind 19:37:10 well 19:37:12 pretty simple 19:37:22 hackweek, high visiblity, lots of blogging 19:37:30 people with connections, more visiblity and presence in the project 19:37:35 but the thing is here, is what yaloki seems to be saying (from my interpretation) is that there needs to be a more orderly fashion of some sort and I don't know if that can be done in such a short time period before Monday 19:37:38 they do something other people have been doing already 19:37:56 those other people not necessarily having the presence and visibility in the project 19:38:06 just imagine how you'd feel 19:38:14 so, I'm just saying, that _could_ happen 19:38:16 yaloki, yup I totally can relate to that feeling 19:38:21 but how do you avoid that? 19:38:26 and hence we _need_ to spread some information about hackweek to the community 19:38:38 * drago experienced that recently with his Owncloud sync client 19:38:56 so that, even if those doing hackweek don't care, those who could get their stuff overwritten and stampeded have a chance of keeping an eye and say "hey! hey! wait!" 19:38:57 its a depressing feeling, for sure 19:39:11 that's all I'm saying 19:39:20 yaloki: good points 19:39:22 so 19:39:27 I'm obviously having a few specific cases in mind, but that's not the issue, and nothing I'd discuss here anyway ^^ 19:39:27 yaloki, I get it now answer is... how do we address it? 19:39:34 where do we go from here ? 19:39:39 we could avoid that using openFATE for example more consequentely 19:39:46 drago: good point 19:40:01 and maybe just send a line or two about that potential situation to those who will participate in hackweek 19:40:02 But would it be one entry or a lot of different open fate entries 19:40:03 and if people do not speak about there projects, they're pimped. True 19:40:29 drago: seems to me that needs to be addressed inside - that is getting devs to pay attention to openfate 19:40:38 surely publicity will make people want to share their ideas for hackweek 19:40:42 "pimped" Now that's a cool word coming out of Drago! :-) 19:40:46 duplication and forking is not an issue, it's a lot more about the psychological impact and not having the same "weapons" in terms of time, contact to key people on the project, and visibility 19:40:58 suseROCKs: from the Bugzilla sources ! 19:41:07 suseROCKs: really. 19:41:14 hehe 19:41:19 drago: maybe everyone who writes a blogpost about his hackweek project can get one Old Toad :) 19:41:26 eheh 19:41:31 we have to motivate SUSE folks I guess 19:41:49 So do we have a solution here? 19:41:50 and to get more people looking at openfate for ideas 19:41:56 mrdocs: +1 19:42:16 * drago likes to avoid using alcohol as motivation ;-) 19:42:17 because i am sure that out of 200 people having hackweek next week we won't hear a word from 168 of them 19:42:39 prusnak: true unfortunately 19:42:44 agreed 19:42:46 s/Old Toad/big lollypop/ 19:42:49 prusnak: too bad.. then it begs the question about changing that 19:43:16 ok guys... time out for a second so I can say something... 19:43:19 mrdocs: the only solution is to make a sooo coool openSUSE project so that everybody cares about 19:43:21 what can the community do to get this in the open and more interactive with the outside wolrd ? 19:43:38 I see 2 things... 1) We are trying to hash out the ideal solution here and 2) We need to publicize this very soon 19:43:39 suseROCKs: go 19:44:01 its late at night for many of you, and the complexiity of this discussion tells me that I'm not going to be the ideal person to write up the first draft of the article 19:44:13 1. we cannot fix now 2. needs action 19:44:16 prusnak: try to find out who is in charge of this HW 19:44:25 drago: Your boss;) 19:44:28 prusnak: and tell him about the issue 19:44:30 I'll be glad to work on the second draft and polish it up for the morning. But wwho can volunteer to write 1st draft tonight? 19:44:33 AJaeger: I doubt 19:44:53 drago: That's what I heard yesterday on the hallways - and it seemed a recent appointment 19:45:13 that's the problem, i guess, no one knows who's in charge 19:45:22 ok, lost... 19:45:33 before it was clear that it is nat or jw 19:46:12 I fear you guys might have rushed into this hackweek but I think we're past the point of resolving that and we should just bite it and figure out the best way to go from here for an awesome start on Monday 19:46:50 prusnak: jw is involved - ask him and roland. 19:47:00 well I hope your hackweek will better that the one last week! 19:47:00 prusnak: yes, please contact jw 19:47:01 Can we move on to my question? 19:47:09 I suggested a few minutes ago to discuss: How do we promote these boxes/products from our pages? How prominently do we want this - and this includes also derivates like the open-SLX 19:47:09 prusnak: he will understand the issue 19:47:26 AJaeger: yup you are next :) 19:47:28 so 19:47:33 mrdocs: Thanks 19:47:33 action item ? 19:47:41 AJaeger: i did not forget :) 19:47:44 who wants to write up the first draft ASAP? 19:47:54 suseROCKs: i can if given some details 19:48:19 #action mrdocs to try and start a first draft tonight 19:48:27 well I'm kinda hoping to shorten the gap here by having the person with the most details do the brain dump into the first draft 19:48:39 suseROCKs: yes.. i see 19:48:50 mrdocs, it needs to be published like tomorrow morning to make this owrthwhile 19:48:55 *worthwhile 19:48:58 by Friday 19:49:10 Friday's always a bad day for publication. low readership 19:49:19 * mrdocs nods 19:49:21 but 19:49:25 suseROCKs: jw, prusnak, myself can review it tomorrow and publish in the afternoon 19:49:37 good 19:49:41 works for me! :-) 19:49:43 i need to step away 19:49:51 bbi 2 19:50:11 suseROCKs: so please add the action item, then its AJ's turn 19:50:13 hmm I think we're actually kind of done with the meeting now, aren't we? 19:50:21 oh yeah AJ .... 19:50:30 Likely done 19:50:50 #action mrdocs to write first draft of hackweek announcement, aj, prusnak and jw will review and publish it by end of day Thursday 19:50:57 ok AJaeger you have the floor 19:50:59 I suggested a few minutes ago to discuss: How do we promote these boxes/products from our pages? How prominently do we want this - and this includes also derivates like the open-SLX 19:51:04 http://software.opensuse.org/114/en right now contains a link "Buy openSUSE" which links to http://en.opensuse.org/Buy_openSUSE. 19:51:19 So, how do we want to do this? What are the guidelines to add external links here? 19:51:42 opensourcepress asked to be included - and open-SLX as derivative are interested as well. 19:51:54 The Haisoft USB stick is another think to add somehow. 19:51:56 AJaeger, my initial thought is to just have a page with the logos of various distributors and people can click to the one they like. But I wonder if distibutors are going to appreciate being all on the same page 19:52:12 hehe - hard thing 19:52:15 but yes we should definitely promote those who distribute us 19:52:34 guys sry for trolling but in the end if possible I have a request to the board 19:52:38 other projects do not do that btw 19:52:44 just let me know if there's time 19:52:53 drago, Just means we're better than the rest :-) 19:52:56 drago: Other projects don't have a box ;) 19:52:58 nmarques: mail is prolly better, as not every board member is here right now 19:53:03 after all, other projects don't even have their own beer! 19:53:04 KDE does not promote openSUSE :-) 19:53:22 I know that does not really match 19:53:30 but still, we don't _have_ to do it 19:53:56 drago: Right, we don't have to. But we did in the past. 19:53:57 drago, but here's the thing. We are not a large community like others. So engaging in a partnership of marketing helps to further our reach where other projects have larger teams to do the work 19:54:20 But exactly since we don't have to, we should be clear on what we want to promote and what *not* 19:54:28 AJaeger: right 19:54:34 AJaeger: exactly 19:54:49 and that has never been clearly discussed, let alone defined 19:55:00 AJaeger, I think any product that is portraying openSUSE under the goodwill clause should simply get a listing on a page. One page listing all of these 19:55:08 the easiest and most equal solution is to not do it at all 19:55:20 I think it should be limited to those which " redistribute without modifications" according to the trademark guidelines 19:55:24 suseROCKs: good compromise 19:55:36 AlanClark: +1 19:55:53 AlanClark: So, no derivatives like open-SLX? 19:55:54 as we then know what is in the tin 19:56:07 the problem is that we basically promote everything 19:56:16 ie. openSUSE Edu, Medical etc. 19:56:30 we're not really promoting Balsam 19:56:40 so why do we discuss the "real" openSUSE clones? 19:56:41 openSUSE Edu and Medical are part of openSUSE - aren't they? 19:56:45 its really difficult 19:56:58 AJaeger; still pondering that one. I like the idea of basing the decisionon the trademark guidelines, so that we have a known basis of judgement 19:57:04 drago, those are community-grown projects. I'd be likely to promote them but in a different way, not in a products page 19:57:11 drago: let's be clear, community driven is different 19:57:22 we 19:57:50 ok, so lets promote Balsam - they consider themselves community as well I am sure 19:57:52 let's limit this to commercially driven derivatives 19:57:56 drago: Yes, it's not easy - and I don't expect an answer tonight. We can table that for the next meeting and thus give everybody of us the chance to come up with a great idea - or realize it's too complex. 19:58:16 AJaeger: its complex, but we need a solution 19:58:25 .oO(and there's a difference between considering yourself and actually being...) 19:58:28 and I agree on postponing 19:58:28 +1 AJaeger. let's put this on the agenda for next time 19:58:34 I'll go with AJaeger's suggestion and table it for now.... 19:58:37 yaloki: sure, but who decides? 19:58:44 AJaeger: no its not impossible, just needs some thought and reasonably good guidlines 19:58:44 drago: I know, I know 19:58:50 yaloki: you see my point? 19:58:51 it is complicated, indeed 19:58:57 drago: yes, absolutely 19:59:16 * drago actually saw that coming.... 19:59:17 drago: not the first time we discuss/brainstorm about it, really not easy 19:59:31 yaloki: right 19:59:47 I suggest we make a list of all the possible products (community derivatives, etc.) and then we can have a broader overview of where the examples lie 20:00:12 suseROCKs: yes, we also need to think about stuff from susetudio 20:00:29 so 20:00:30 mrdocs; ugh 20:00:32 suseROCKs: well, all possible products? You thought of openSUSE beer two years ago? 20:00:47 AlanClark: yes :S 20:00:49 suseROCKs: No chance to foresee all products 20:00:55 drago, no that's not what I mean. 20:01:14 suseROCKs: ah, sorry 20:01:23 drago, what I mean is we're all throwing in little examples here and htere, but if we can itemize the existing examples, we can then easily divide them into categories and then be able to make a more prudent determination 20:01:38 suseROCKs: exactly 20:01:49 its a helluva lot easier to look at a list of examples than a "oh by the way this one too" :-) 20:01:58 suseROCKs: good, but than we discuss all over again and again 20:02:10 so where do we go from here ? 20:02:12 actually guys, there is one easy answer, that many won't like, but it is an answer. Only post those that sponsor the project. 20:02:16 but we probably can not avoid that anyway 20:02:37 AlanClark: yes, definitely a possibilty 20:02:40 AlanClark, and that opens up the age old question that's been brought up before... "What is our definition of Sponsor"? :-) 20:02:42 AlanClark: thats good 20:03:02 * drago drops off now 20:03:04 suseROCKs: We do have "official" sponsors 20:03:06 good night everybody 20:03:09 drago: Good night! 20:03:15 drago: thanks for joining :) 20:03:16 drago: night 20:03:19 drago night ;-) 20:04:07 suseROCKs: sponsors = money, services in kind, goods in kind 20:04:28 which can include beer, guns and lawyers :) 20:04:28 mrdocs, AJaeger but this question has been raised a number of times in board meetings over the past year and no one has ever come up with an answer 20:05:03 suseROCKs: well apart from my list above what would you add to that ? 20:05:07 suseROCKs: Sorry, I don't remember these - might have skipped all of those ;-( 20:05:37 I don't remember that being an issue either 20:05:51 hey 20:05:56 good afternoon 20:06:02 it was raised during our discussions with open-slx and they kept banding around that they were the major sponsor of openSUSE 20:06:11 and I kept asking... what's their definition and our definition of sponsorship 20:06:12 HAHAHAHAHHahhahHAHAHAHHA 20:06:15 oops, sorry :) 20:06:23 what's our expectations vs. the sponsor's expectations, etc. 20:06:30 yaloki, exactly! :-) 20:06:36 ah stepped into that one 20:07:27 I want to join the election comitie 20:07:33 kudos to warlordfff ! 20:07:37 do I still have time? 20:07:41 warlordfff: Great! 20:07:53 I forgot to write that down yesterday 20:08:32 gah sorry irc died on my 20:08:53 but as AJaeger said, we should still have a public call 20:09:01 to give everybody a chance to be part of that committee 20:09:06 and not just those who were on IRC today 20:09:15 ok 20:09:18 can someone pastebin the recent chat ? 20:09:25 and we will send out that email announcement shortly 20:09:26 one question about something else 20:09:34 I think we've spent enough time on the this topic today, I'd recommend that we put it on the agenda for next meeting, so that we can think through some proposals 20:09:35 mrdocs: sign me up for the guns... if anyone is handing over G36C's, I could use one :) 20:09:39 if I have the time? 20:09:40 mrdocs: and save 4000€'s :) 20:09:58 AlanClark: +1 20:10:01 nmarques: i was thinking of the warren zevon song :) 20:10:20 guys 20:10:25 mind if I say something :) 20:10:37 nmarques: sure 20:10:38 you guys need a plan for some sort of 'franchising' the brand 20:10:46 something very well thought of 20:10:56 that would solve the problems with sponsorships and friends 20:11:00 ;) 20:11:11 it shouldn't be a 'per case' thingie 20:11:17 nmarques: i know exactly of what you are speaking 20:11:29 nmarques: There are guidelines on what bronce, silver and gold sponsorship means. 20:11:30 nmarques: is that something you could take on ? 20:11:59 mrdocs: that is something I can help with ;) (help i nthe role of follower, not as in the role of leader) 20:12:19 mrdocs: I have theoretical expertise to do it, but no real life experience on doing it 20:12:24 mrdocs: but it's a start :) 20:12:48 http://en.opensuse.org/images/2/2f/Sponsoring-concept-opensuse.pdf should be the sponsor brochure 20:13:00 AJaeger: thanks 20:13:48 mmh, that one misses bronze sponsorship 20:14:18 can we end the meeting? 20:14:24 AJaeger: that needs to be pretty and attractive 20:14:26 yes 20:15:04 #action postpone discussion for sponsor levels for next meeting 20:15:08 +1 to meeting end 20:15:15 anyone else have anything ? 20:15:24 1,2,3... 20:15:27 * yaloki haz stomach bug, wanna share 20:15:29 ;) 20:15:29 3,2, 1 20:15:31 #endmeeting