16:06:31 #startmeeting 16:06:31 Meeting started Wed Feb 9 16:06:31 2011 UTC. The chair is henne. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:06:31 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:06:34 #meetingtopic Welcome to the openSUSE Project Meeting! 16:06:37 Welcome to the openSUSE Project Meeting! 16:06:40 This meeting is meant to discuss the latest developments in and around openSUSE. 16:06:43 The topics for this meeting are: 16:06:47 * sshaw makes a shocked look 16:06:58 1. Old Action Items 16:06:58 2. Status Reports 16:06:58 3. Questions & Answers 16:07:26 first topic 16:07:36 #topic Old Action Items 16:07:54 #info you can find the action items in bugzilla with this link: http://bit.ly/opensuse_action_items 16:08:30 There are two action items 16:08:37 number 1 is #663985 16:08:54 LinuxTag talks 16:09:17 the deadline passed last week but on FOSDEM we got an extension from one of the LT organizers 16:09:33 i ran around and talked to people about their submissions 16:09:35 * mrdocs waves 16:09:48 i will again run around tomorrow and see what they did about it 16:09:56 * suseROCKs places an anvil on mrdocs's hand to stop his waving 16:10:15 after that we should have some nice contributions to LT 16:10:15 henne, did you notify ambassadors@ about this as well? 16:10:45 suseROCKs: all of them are aware of it 16:11:10 and are we doing a booth there as well? 16:11:11 i have notified -project 16:11:22 about the deadline twice i think 16:11:28 ok 16:11:46 yes I have put in an application for a booth 16:12:00 I need to figure out a way to coordinate how we put out calls for such things. Some people only communicate to marketing/ambassadors and others to only -project. 16:12:01 the Call for Project still runs a bit longer 16:12:21 And there's no guarantee that relevant and good speakers are on either lists. 16:12:33 should we just start cross-posting from now on? 16:12:41 well putting out a call on some list isnt all you have to do 16:12:54 you have to organize a programm. otherwise people will just forget 16:12:56 agreed. I also ping people directly whenever I see someone who is good 16:13:05 agreed on that as well 16:13:08 organizing means poking people constantly... 16:13:22 my point is we don't always realize we have a greater pool of potential folks than what we see up front 16:13:34 and I want to cultivate that 16:13:57 henne, trust me, I know that. Seems like its all I do these days re: SCALE :-) 16:14:11 i think these things belong onto -project 16:14:42 there should be _no one_ active in the project that doesnt read -project 16:14:52 in a way, I do too. But I'm finding that not everyone is on -project. (Which means maybe we need to do a better job of marketing -project) :-) 16:14:59 no marketeer, no ambassador, no developer 16:15:27 agreed. Also something I keep telling people. IF you want to promote the Project, you need to look beyond your l ittle corner. 16:15:55 i can produce lists of addresses not on -project 16:16:02 for every list you can think of 16:16:09 you just can ask :) 16:16:18 that's a repetitive process :-) 16:16:28 henne, how about this? 16:16:54 when people subscribe to a mailing list (maybe not for all mailing lists) In the ack message, it says something to the effect of "By the way, shouldn't you also be on -project?" 16:16:56 sure you would iterate this once in a while... 16:17:22 suseROCKs: no problem. just provide me with the texts 16:17:32 ok 16:17:52 * suseROCKs will need to look at existing acks and see how it is worded now 16:17:58 I guess that's an action item for me then :-D 16:18:04 also are new members auto subscribed ? 16:18:10 #action suseROCKs provide ml-admin@opensuse.org with welcome texts for mailinglists that include suggestion where to subscribe also 16:18:13 might be a good idea so we can spam them :P 16:18:24 mrdocs, I don't think we autosubscribe anyone at this time 16:18:28 GNOME does that. 16:18:36 autosubscribe sounds pretty evil to me 16:18:45 16:19:03 something to consider 16:19:23 also we don't really have a very tecnical process there. this would be another manual task for the member officials 16:19:30 what I get constantly is people saying oh... I didn't know about -project. How am I supposed to know all these many lists to subscribe to? 16:19:35 * mrdocs nods 16:19:41 suseROCKs: from the welcome mail 16:19:49 lets try that :) 16:20:03 welcome mail to new members? or welcome mail to ? 16:20:06 okay next action item 16:20:23 suseROCKs: see your AI 16:20:29 ok that one 16:20:55 the second AI we have open is about the feature list bug #659659 16:20:58 openSUSE bug 659659 in openSUSE.org (Action Items) "Top feature list for 11.4" [Normal,Assigned] https://bugzilla.novell.com/659659 16:21:17 is that under control? 16:21:49 suseROCKs? 16:22:55 * henne sees a tumbleweed rolling around and hears a wolf howling 16:22:55 that's a thread that's been floating on -factory list, and I've been monitoring it to some extent yes 16:23:17 henne, wrong setting... if a tumbleweed is rolling, you'll hear coyotes 16:23:25 eheh 16:23:35 okay so as jos isn't here, again... 16:23:39 next topic 16:23:43 * suseROCKs autosubscribes henne to the Discovery Channel 16:24:00 #topic Status Reports 16:24:15 Teams and individuals send various status reports around. Coolo sends one for the distribution, the OBS team publishes meeting minutes, the boosters their "What are the boosters up to" blogposts, the board has a public meeting and so on and so on. Are there any questions regarding those or do we need to discuss anything in detail? 16:24:59 You might add where those are posted to the welcome mail 16:25:16 so that newbies know the latest happenings with the projects 16:25:19 those? 16:25:20 we probably do need to do a more structured way of getting status reports from all (including the teams I'm on) 16:25:40 as they provide useful feed for stories on news.o.o 16:26:00 those = Coolo, OBS, boosters,... 16:26:02 as usual guys. the idea is great it just needs someone doing it :) 16:26:17 either convincing them to do it structured 16:26:19 or collect them 16:26:19 henne, I wasn't giving an idea 16:26:37 I was saying there's a greater need... now how do we come up with a way that makes everyone easily do it? 16:26:52 because let's face it, reporting is not a favorite task amongst humans 16:27:21 "I'm too busy doing to say what it is I've been doing!" :-) 16:27:51 hmm what if we created a status bot or something? 16:28:17 #status We're working on xyz 16:28:21 #status We're done with xyz 16:28:40 (end of week) We compile it into a report or its viewable in list form for others to look at 16:28:40 like ive said. this is not about ideas HOW to do it 16:28:44 we have tons of those 16:28:59 this is about someone convincing the people that report to do it otherwise 16:29:02 dude, I'm trying to come up with a way that we can do it simply 16:29:11 or about someone collecting the information that is out there 16:29:28 someone collecting = "status bot" :-D 16:29:34 nope 16:30:02 ok 16:30:02 a status bot means that i don't have to switch from blogging about what the boosters to to use a status bot 16:30:14 err that I have to switch* 16:30:21 no that's not what it means 16:30:22 do* 16:30:28 no? 16:30:38 so who would feed the status bot? 16:30:44 about the boosters 16:30:47 it means I don't have to poke everyone on the team to tell me what they've been doing when I can just as easily look up a web page with this week's statuses and summarize it into a blog post 16:31:18 and THAT is exactly what is missing 16:31:30 everyone, as they're working would siimply type #status (message) which is a lot easier than writing a summary or recalling from memory what they did on Monday and its now Friday 16:32:10 suseROCKs: then go out there and make it happen. code up a status bot and concinve people to use it instead of what they use now 16:32:27 what do they use now? :-) 16:33:01 ok let's move on 16:33:04 mails and blogs 16:33:53 okay are there actually any of the status reports that we need to dicuss? 16:34:42 or does anyone want to give a live status report? 16:34:54 * henne does 16:35:20 okay here we go 16:35:21 FOSDEM 16:35:42 as I possibly don't get to a full even report let me do it live 16:36:00 the opensuse project went there last weekend with around 30 people 16:36:13 FOSDEM was packed like _never_ before 16:37:06 often the devrooms had to be close because of overcrowding 16:37:14 re: packed, any speculation as to new/additional demographic? hobbyists? corporate types? etc? 16:37:42 Shouldn't that be asked to FOSDEM? 16:37:43 dev001: FOSDEM is a developer meeting so mostly developers 16:37:52 opensuse mostly participated in the cross-distro devroom 16:38:09 henne: sure. hobbyist devs? corporate devs? 16:38:13 we had a couple of talks and did part of the moderation and all of the video taping 16:38:15 suseROCKs: perhaps ... 16:38:27 dev001: FOSS devs :) 16:38:36 sigh 16:38:36 :-) 16:38:54 dev001: no one track the attendands 16:38:58 with 10,000 people I would say its a cross-pollination of dev types 16:39:04 dev001: and as far as i know there was no survey 16:39:13 so i don't know 16:39:31 unfortunate, but ok. thx. 16:39:47 all of the videos from the cross-desktop room you find on http://opensuse.blip.tv/ 16:40:00 we also had a booth 16:40:10 we handed out around 1.000 promo DVDs 16:40:13 I hear you had beer too :-) 16:40:19 500 T-shirts 16:40:23 the youtube channel for the videos is at: http://tinyurl.com/crossdistro and they are linked from tube.opensuse.org 16:40:25 suseROCKs: we never ;-) 16:40:30 around 1.000 project flyers and stickers 16:40:37 dragotin, near-beer then? :-) 16:40:39 and 20 cases of old toad yes :) 16:40:54 the beer was a superhit 16:41:03 kudos to dragotin for the beer 16:41:05 we ran out on saturday around 4pm 16:41:07 yup :) 16:41:08 old toad? .. I hope that's not a reference to geeko 16:41:22 FOSDEM starts at 1pm 16:41:34 cb400f: it was well done :) 16:41:48 oh BTW, we sold the beer and the t-shirts for 1€ and donated the money to FOSDEM 16:41:53 wish we could do that here in the U.S. but with laws around here, I don't think we could get away with it that easily 16:42:02 what were the talks given by opensuse members and any thing that we should do differently in the future? 16:42:06 cb400f: of course it is. http://en.opensuse.org/openSUSE:Beer 16:42:23 cb400f: http://en.opensuse.org/openSUSE:Beer 16:42:27 ah sorry 16:42:34 AlanClark: i think the talks were well chosen 16:42:41 the talks where 16:42:47 Jos with Amazing openSUSE 16:43:06 |miska| with Downstream packaging collaboration, patch sharing or start a new upstream? 16:43:27 vuntz with Example of cross-distro collaboration: Application Installer 16:43:44 a lot of us participated in a panel discussion about Distribution collaboration manifesto 16:43:49 seems like many of the technical experts that can give great talks are largely in EU. We need to figure out a way to get them elsewhere or get them to educate others elsewhere to give the same talks 16:44:02 duncan talked about ZYpp your distro 16:44:07 suseROCKs: We have will going to india soon :-) 16:44:20 berhard about openqa 16:44:28 and saschape about the OBS 16:44:52 and OBS were topic in the cross-desktop room in at least two talks as well 16:45:01 dragotin, unfortunately for those of us outside of EU... most of the talks are "marketing-based" Not indepth-technical based. We need to change that if we want to grow our dev community here. 16:45:29 * suseROCKs puts that on the agenda list for the marketing hackfest to discuss how to change that 16:45:29 suseROCKs: well thats kind of a chicken egg problem 16:45:39 agreed 16:45:44 but anyway 16:45:48 it was a great event 16:45:55 we just need to start looking at ways to actively resolve that though. 16:46:19 suseROCKs: I see the point, but: Will is certainly a dev and India is not in the EU :-) 16:46:36 dragotin, sure. And I'm glad to see that happening. But we need more! :-) 16:46:56 suseROCKs: Yes, more of everything, as more opneSUSE is more fun 16:47:02 yes sure. but don't forget. we're EU based. it is like it is 16:47:10 somewhere you always will have a majority 16:47:13 but anyway 16:47:16 we're drifting 16:47:21 not really 16:47:34 anything else on status reports? 16:47:37 its on the subject of what you offered at FOSDEM and how can we capitalize and clone it elsewhere 16:48:26 make sure you use good demo screens 16:48:50 suseROCKs: yes sure 16:48:53 mrdocs, I demo-ed me in speedos once. It didn't work out as well as I expected. 16:48:55 was nice to see two large touch screens with KDE and Gnome side by side... really professional and looks cool 16:49:11 *shudder* 16:49:39 * mrdocs needs to bail for a bit and fetch the little one from school 16:49:41 bbiab 16:49:50 mrdocs, don't forget the board meeting today 16:49:57 okay can we continue? :) 16:49:59 nope i wont... 16:50:46 henne, if you insist 16:51:30 suseROCKs: i don't 16:51:39 let's move on 16:51:58 okay 16:52:06 there one tricky thing left 16:52:14 good that AlanClark is awake :) 16:52:22 #topic Question and Answers 16:52:25 he's here That doesn't mean he's awake 16:52:26 * AlanClark wakes up 16:52:32 there is one question on the wiko 16:52:33 wiki 16:53:00 from HeliosReds 16:53:02 About the license and copyright of documents on *.opensuse.org sites: Can anybody clarify which country's copyright law and guidelines we should refer to? 16:53:19 wow what a question 16:53:29 hes also referencing a mail thread on -marketing 16:53:30 http://lists.opensuse.org/archive/opensuse-project/2011-01/msg00433.html 16:53:52 hmm 16:53:58 does anyone understand his question? 16:54:10 Give that to me as an AI. I saw the mail thread, talked some to Novell legal, but don't have an answer yet 16:54:11 I think I do. 16:54:17 oh, its not only me? 16:54:36 we have a new wiki footer that says GFDL 1.2 16:54:38 only me who does not understand 16:54:56 this may particularly be related to whether it is legal or not that OWN-de was moved yesterday 16:56:00 It does tie into what materials can be used where and by whom 16:56:20 but there are two parts to this copyright and license 16:56:48 The confusion I had on the email was the ebb and flow of the materials. 16:56:55 AlanClark, I know legal is busy, but given the sudden move yesterday, can we at least get some answers about the legal side of it? the ethical/moral/whatever side of it, we,, the project, still have to address as well. 16:57:16 suseROCKs: what move? 16:57:26 It wasn't clear to me who and where all the copyrighted material is being initially creted 16:57:45 henne, this one: http://saigkill.wordpress.com/2011/02/04/german-weekly-news-relaunched/http://saigkill.wordpress.com/2011/02/04/german-weekly-news-relaunched/ 16:59:03 suseROCKs: what has that to do with the question? :) 16:59:27 a lot 16:59:52 if proper copywriting is in place, does it make the move of OWN out of openSUSE infrastructure legal or not? 17:00:09 dude... 17:00:41 this is about a newsletter that cites various sources 17:01:06 henne, yes but I believe this is the gist of why Helios is asking the question in the first place 17:01:33 i wouldnt want to speculate about that. he asked a simple question and we should anstwer that 17:02:31 and I'm not trying to speculate. I'm asking that given yesterday's move, can we somehow expedite some answers from Novell legal on the question of copyrights so that if we feel we need to respond to the move, we have more knowledge in our hands 17:03:04 that was my only request here. You asked for more information on the move itself. I'm asking for just more legal information 17:03:28 suseROCKS: That's a different question 17:03:46 completely different 17:04:20 so AlanClark you try to clarify that? 17:04:32 AlanClark: what HeliosReds asks I mean 17:05:16 AlanClark: i guess its mostly about licensing of the news/lizards content 17:05:57 His question is about country of origen for copyright purposes. 17:07:07 When developing content on openSUSE which countries copyright guidelines should be refered to 17:07:19 on openSUSE? 17:07:36 well in his case NOWS 17:08:02 s/NOWS/OWN 17:08:47 which is why as suseROCKS points out, it may tie to saigkill's weekly news 17:08:56 hm. from what I understand from that mail thread 17:09:08 they struggle with citing material from around the web 17:09:37 There's always a trail somewhere :-) 17:10:21 including sources like news/lizards 17:10:26 ok there's not much more we can do on this topic until we get some more information 17:10:26 exactly why I pointed out my confusion earlier - in trying to understand the root of those trails 17:10:38 now if the content on those sites is not clearly licensed 17:10:56 they need to know which laws they need to apply 17:11:08 we can only tell them that for our own sites or? 17:11:36 he specifically asks about *.opensuse.org sites in his questions 17:11:41 question* 17:11:59 it has to be. We can't answer questions for external sites 17:12:13 right. 17:12:48 okay so content from us comes exclusively from the wiki which is licensed GFDL 17:13:00 huh? 17:13:01 and news/lizards which are not licensed at all 17:13:08 no 17:13:18 content from us comes from any x.opensuse.org site 17:14:17 so I guess to further push the question... if I write an article for news.o.o, does copyright belong to me or to openSUSE? 17:14:27 to novell for now 17:14:31 look at the footer 17:15:18 hmm so that's something to possibly think about for the future with the foundation to transfer those copyrights to the Foundation I guess. 17:15:38 why not move news.o.o to gfdl, too? 17:15:41 or to just license news/lizards content 17:16:41 actually henne I think you just answered the question. 17:17:41 out of curiousity, when you apply a new copyright to a site, does it automatically apply to past posts? 17:18:59 okay way more complicated then that 17:19:37 part of the Sascha question / issue is that the materials are in GFDL his newsletter is CC 17:19:58 yeah 17:20:54 licensing a newsletter is just crazy 17:21:11 he should have never opened that box... 17:21:28 why? 17:21:54 because its just a document that cites other sources? 17:21:59 yes 17:22:24 anyway 17:22:35 a copyright is about more than just content... 17:22:44 but again... we need more indepth answers before we can go further 17:22:54 as AlanClark says i somehow answered the question lets wrap this up 17:22:59 we're already 22 minutes over time 17:23:14 or are there any other questions? 17:23:22 any other topic we need to discuss? 17:23:27 nada from me, except just a reminder.... 17:23:53 as later today we will have our first board meeting with newly-elected mrdocs, we will also need to discuss when to have our regular board meetings. 17:24:14 and in conjunction with an older topic on the table here, finding a way to join the -project and -board meetings 17:25:56 * suseROCKs pushes bughunter88 to bughunter89 17:25:57 so don't forget about the board meeting 17:26:03 in 1,5 hours! 17:26:25 see you all later! 17:26:26 Okay that's it then. If you have more, don't hesitate to bring it up on the appropriate mailinglist. 17:26:30 #info The next project meeting will be in two weeks. Same channel but this time at 12:00 UTC. 17:26:34 Thank you all for participating. Good night and good luck! 17:26:38 #endmeeting