Speaker: jpr (12:02:13) ChanServ has changed the topic to: Meeting in Progress - Introduction (jpr) <jpr> welcome to the opensuse gnome team meeting! <hobbsc> indeed <jpr> some of use are freshly excited by guadec events <jpr> (and some are possibly still drunk) <jpr> (but not me) <jpr> today's meeting really marks the beginning of the push towards 11.1 <jpr> i have alpha 0 installed in a vm ahead of alpha 1 next week :-)

Speaker: suseROCKs (12:03:50) ChanServ has changed the topic to: Meeting in Progress - Feature review (suseRocks) <jpr> suseROCKs: ... <suseROCKs> yes jpr <jpr> suseROCKs: your topic :-) <suseROCKs> ummm.... it is?  :-) I haven't got a clue. Damn my mind is blank... <jpr> ok + jpr steps in <jpr> so <jpr> feature wise for 11.1 + chen_ (n=chen@117.192.232.5) has joined #opensuse-gnome <jpr> the ideas page is technically closed <jpr> though it is a wiki <jpr> :-) <jpr> openfate is finally on track as well <jpr> (fate being a feature tracking tool used internally at novell) <jpr> to help record some of this <hobbsc> that explains the tons of "fate" emails i get <suseROCKs> hey that's vuntz's topic. I knew I shouldn't have been in trouble.  :-) <jpr> we've got a lot more ideas from more people than in 11.0 <jpr> which is great <jpr> we need to start doing some filtering and prioritizing and ownership <suseROCKs> how do we use/access fate? is there a wiki on this? <jpr> i've stated my belief in past meetings that a top priority should be consolidating the 11.0 features <jpr> specifically pulseaudio, packagekit, compiz config,mulitscreen + FunkyPenguin has quit (Read error: 104 (Connection reset by peer)) <jpr> i think there is general agreement on that <hobbsc> +1 <lejo> +1 <jpr> there are also a number of low hanging fruit items there <suseROCKs> +1 as well, it at least makes it easier to determine who does what. <jpr> like "package foo" <vuntz> (I'll be a few minutes late -- just got out of a meeting) <jpr> (mw will discuss contributions there later) + FunkyPenguin (n=andrew@forcev.demon.co.uk) has joined #opensuse-gnome <jpr> its also important to note we need not just devs but testers and documenters as well <FunkyPenguin> bugger im late, sorry <jpr> its not clear to me though how to select various features <jpr> straight voting? <jpr> voting as input to developers <suseROCKs> verify to me... documentation is end-user or technical? <jpr> email discussion and one person decides <jpr> end-user documentaion <jpr> wiki pages more specifically probably <jpr> most development last time was kind of directed by me (with some discussion) <suseROCKs> I don't think straight voting would be a fair option. Certain features likely require more time to implement than others. We need devs to speak up what is easy and quick vs. time consuming. then vote accordingly <jpr> i would like it to be less so this time <chen_> I think email discussion would be better <jpr> maybe we should group the features by time? <hobbsc> jpr: i'd be happy to test and/or document <jpr> i kind of like that <lejo> aren't there already a number of features marked internally by novell as being priority? (Which we can already skip) <jpr> "you can have these 7 features or this 1" <jpr> :-) <jpr> lejo: true - hopefully thats exposed <jbrockmeier> jpr: Can I pick the features? I think that would be fair. <jbrockmeier> ;-) <jpr> in openfate <jpr> jbrockmeier: you can at least have a say is you are a gnome user <jpr> lejo: i'd still like to get those tagged in the wiki as well <jpr> so people know <lejo> indeed <suseROCKs> zonker is one of us??? ooooh boy... <jbrockmeier> suseROCKs: I am omni-desktopual <jpr> so is there general agreement that we should group these feature by approx time to implement <suseROCKs> +1 <jpr> and perhaps re-categorize a bit <jpr> ie clean up the page now <jpr> and start an email discussion + chen has quit (Read error: 110 (Connection timed out)) <jpr> including ownership? <chen_> +1 <jpr> grouping by type of task might be nice too <jpr> ie <jpr> packaging + nareshov (n=nareshov@59.96.44.189) has joined #opensuse-gnome <jpr> or patch <jpr> (upstream or downstream) <jpr> or big new feature <jpr> ok, maybe just packaging :-) <suseROCKs> ok what will be the process for notifying testers that the next version of a feature is ready for testing? <jpr> suseROCKs: can we put that on the list for next meeting? i think we need a larger discussion <jpr> because the wiki page kind of failed imho <suseROCKs> ok, I agree + FunkyPenguin goes with the consensus as he missed the start <jpr> openfate would help there as well <jpr> all that process stuff being said <suseROCKs> FunkyPenguin so you agree to do all the tasks we assigned to you in the start? <jpr> are there volunteer(s) <jpr> to categorize or clean up the ideas page + mauropm (n=mauro@nat/novell/x-f3166fcae6035dc1) has joined #opensuse-gnome <jpr> and start the mail thread? marioc mauropm metavoid mhwork|away mmeeks mrdocs mw|brb mw|screen marioc mauropm metavoid mhwork|away mmeeks mrdocs mw|brb mw|screen + suseROCKs isn't volunteering for anything new as he has enough on his plate. Don't even think about it! <FunkyPenguin> im pretty tied up until next week at the earliest :( + jpr eyes lejo <jpr> lejo: your chance to influence pulse development :-) <decriptor> the all seeing eye <hobbsc> ok, i don't follow (sorry, semi-distracted). you need a thread in the mailing list to summarize features that need to be consolidated? <jpr> and we need to tidy the ideas page a bit <hobbsc> link? <jpr> http://en.opensuse.org/GNOME/Ideas/11.1 <hobbsc> http://en.opensuse.org/GNOME/Ideas/11.0 <hobbsc> ah <hobbsc> ok <hobbsc> it seems to look ok <hobbsc> i mean <hobbsc> straight-forward anyway <suseROCKs> or !gnomeideas works too  :-) + jpr notes lejo went quickly slient :-) <jpr> ok, i'll own starting the thread i guess <jpr> but you all must participate in the thread! <jpr> :-) <jpr> AI: JP to start feature thread on opensuse-gnome@ <suseROCKs> will do my best.

Speaker: vuntz (12:23:13) ChanServ has changed the topic to: Meeting in Progress - Policy review (vuntz) <jpr> vuntz: ... <suseROCKs> is he back? <jpr> maybe not

Speaker: suseRocks (12:24:04) ChanServ has changed the topic to: Meeting in Progress - Helping hands (suseRocks) <jpr> suseROCKs: any updates on HH? <suseROCKs> sure... <suseROCKs> tmw we have HH at 14:30 UTC. Topic is Evolution. Lead by abharath and lakhil. They'll bring the team along with them. <suseROCKs> I am trying to figure out who to line up for next week. Either fspot or banshee but having trouble finding time to chase people down during the daytime. <suseROCKs> since I'm in the studio filming for the last two weeks (Am in the studio right now, just sent my actors away so I could meet now) <suseROCKs> Also talks continue on multiple fronts to expand HH to all of openSUSE. <jpr> banshee 1.2 is very close, you might want to wait on it being released (unless you are only focused on 11.0) <suseROCKs> no im not focused on 11.0. it can be on any currently supported version of oenSUSE <suseROCKs> anyone know who sbe is? Could someone ping him to see if he might do fspot next week? <jpr> you might reach him on the irc.gimp.org f-spot channel + chen_ will not be able to make it for helping hands tomorrow :( going out of station <jbrockmeier> suseROCKs: any interest in a Vim HH? <jbrockmeier> if we want to have some non-GNOME ones... <lewin1> suseROCKs: both sde and I are on vacation next week <suseROCKs> jbrockmeier I was going to try to hold that til we get to the next level of HH when we're not -gnome centric anymore. <lewin1> so no f-spot <suseROCKs> ok + lewin1 is now known as lewing <hobbsc> i'll be at hh <jbrockmeier> suseROCKs: OK <hobbsc> jbrockmeier: i'd love to help with a vim HH <jbrockmeier> suseROCKs: I thought that might help it be non-GNOME-centric <hobbsc> if you're volunteering :) <hobbsc> i'm a vim wizard + hobbsc flexes <jbrockmeier> hobbsc: I feel comfortable with Vim, yeah ;-) <suseROCKs> jbrockmeier but seeing as I am an opportunist and use HH to further my own learning experience, I definitely need/want VIM presentation  :-) <hobbsc> well, i fyou guys get a vim HH together, put me down as a presenter too <vuntz> (sorry, back) <suseROCKs> ok lets do vim next week then. <hobbsc> 30 lashes for vuntz <hobbsc> jbrockmeier: you want to work on that one, too? <abharath> suseROCKs: cool sounds good + longhong_ has quit (Remote closed the connection) <jbrockmeier> suseROCKs: when would that be? I'm at OSCON next week. <hobbsc> oh, you lucky dog + suseROCKs wrings jbrockmeier's neck... <hobbsc> you want to maybe put vim off for the following week? <suseROCKs> Fridays at 14:30 UTC. <FunkyPenguin> a good one for GNOME centric HH is nautilus, for non GNOME what about YaST? <suseROCKs> FunkyPenguin can you do an hour long presentation on nautilus? <jpr> nautilus kind of got covered in the first one <mw|brb> /bin/cat :) + mw|brb is now known as mw <FunkyPenguin> ah missed it <FunkyPenguin> ok what about yast? <jbrockmeier> suseROCKs: sorry :-) yeah, we'd better put it off. Sorry :-/ <cyberorg> how about "gconf-editor" <hobbsc> jbrockmeier: what's your following week look like? <suseROCKs> I think I need to cancel next week's and regroup (fortunately, I get the next 4 days off) <hobbsc> that following friday? <jbrockmeier> hobbsc: I should be available. I'll be in Boston, but not flying out until late in the day. <suseROCKs> an indepth gconf editing session would be good. Who can lead that? <jpr> NM might be a good one with tambeti <hobbsc> jbrockmeier: want to collaborate on a vim HH, then? at the very least it'd be cool tog et some sort of intro document done <jpr> given all the new features <FunkyPenguin> no, dont do it! users should not have to hack gconf <cyberorg> fedrico can do one on sabayon <FunkyPenguin> the app should interface with gconf seamlessly <jpr> speaking of cyberorg <vuntz> suseROCKs: what do you call "in depthy gconf editing session"? <jpr> compiz :-) <abharath> jpr: +1 <FunkyPenguin> +1 <federico1> cyberorg: hmm, that would be a good one <hobbsc> +1 <federico1> cyberorg: first I need to see if it still works :) <jbrockmeier> hobbsc: sure <suseROCKs> ok compiz is next week then.  :-) <jpr> that is potentially a real traffic driver <cyberorg> suseROCKs, sabayon next week, compiz, week after? <jpr> useful to know what kind of setup problems people still have too <suseROCKs> federico1 and I looked at sabayon a couple of weeks ago. There were still some problems at that time. <FunkyPenguin> hows about gimp? get jimmac or garrett or even kallepersson <suseROCKs> i'd also like to do a video editing session soon. <kallepersson> haha, -even- me? <cyberorg> yeah gimp would be good + kallepersson reads <suseROCKs> ok question: Who IS available next Friday and WANTS to do a presentation? <mw> maybe monodevelop or similar would be cool <kallepersson> Hm, what's going on? <hobbsc> if i had something to present, i'd be happy to <jpr> oh man + vuntz tries again <jpr> jimmac could do a sweet gimp/inkscape presentation <vuntz> suseROCKs: what do you call "in depthy gconf editing session"? <suseROCKs> vuntz I call it bad typo.  :-) + wfarr (n=wfarr@lawn-128-61-116-8.lawn.gatech.edu) has joined #opensuse-gnome <jpr> he and tigert used to do a "how to make an icon" presentation <jpr> ok <FunkyPenguin> his vidcasts are great, and i barely understand what he's on about :) <vuntz> suseROCKs: ah, well, then I won't step up ;-) <chen_> that would be great!! <jpr> this was supposed to be a quick update <jpr> :-) <cyberorg> suseROCKs, if there is no one till tomorrow evening, ping me, we'll do compiz <suseROCKs> I meant to say an indepth gconf editing session where you talk about all the different things you can tweak in gconf. <jpr> suseROCKs: so, you got some good ideas now and can proceed on scheduling? <kallepersson> you'd probably need jimmac or garret for a good presentation of GIMP <jpr> yes, garret too <suseROCKs> ok cyberorg + wfarr has quit (Remote closed the connection) <kallepersson> are you talking about screencasts or something? <suseROCKs> ok end this topic I'll continue outside the meeting later. <kallepersson> sorry for disturbing the meeting. <jpr> kallepersson: help hands sessions http://en.opensuse.org/GNOME/HowTos/HelpingHandsSchedule <hobbsc> suseROCKs: ping me after the meeting <jpr> hobbsc: quick plug for tutorials? <hobbsc> jpr: ? <jpr> nm then :-)

Speaker: vuntz (12:38:06) ChanServ has changed the topic to: Meeting in Progress - Policy review (vuntz) <jpr> vuntz: ... <kallepersson> thx. <vuntz> policy review <vuntz> so, first, the big issue: + linash (n=john@146.87.52.50) has joined #openSUSE-GNOME <vuntz> it's quite painful to maintain our list of policy changes <suseROCKs> somebody save a log of that HH topic pls. I'm on a frickin windows IRC client right now and don't know its logging settings. <vuntz> actually, it's not really maintained... <vuntz> it'd probably be nice to have a way to say "this is a policy change" directly in spec files <federico1> vuntz: in the specfile section for patches, could we drop a comment that says "if you change defaults from upstream, go to en.opensuse.org/blahblah and document it as a policy change" <vuntz> I can imagine a kind of comment like the tags we use for the patches <jpr> aren't a good chunk of these self-documenting in the -branding packages because they are gconf keys? <vuntz> federico1: if you rely on people editing the wiki, it'll fail at some point. I think it's easier if it's inline in the spec <vuntz> jpr: yeah, the changes from the branding packages (at least the gconf2-branding one) should be easier <jpr> so its more about urls and such? <vuntz> the issue is that some policy changes are introduced by patches <vuntz> and some are related to feature changes <kangaroo> cyberorg: something up with your git packages? <kangaroo> when I have cylinder on and I star the cube <kangaroo> only the first face is deformed <jpr> kangaroo: meeting in progress <cyberorg> kangaroo, meeting on now :) <vuntz> so far, the only solutions I can think of are: <kangaroo> whoops; sorry guys <vuntz> a) have someone redo the work every now and then <jpr> vuntz: so are you proposing a PATCH-POLICY tage or something? + jpr waits <vuntz> b) document that people should update the wiki page <vuntz> c) inline stuff in spec files <vuntz> a) will fail <vuntz> b) is easy, but we'll miss a few things <vuntz> c) requires more work <jpr> i was actually kind of partial to a) <jpr> :-) <vuntz> heh <vuntz> well <jpr> well, i think now we are getting it sanitized <jpr> it will be less of a moving target <vuntz> it's easy to do a) if we're only interested in gconf changes <jpr> and we have relatively few items outside of the gconf package <vuntz> ok <vuntz> so let's stay with a) for now <jpr> well, tell me if i'm wrong :-) <vuntz> I didn't have time to update the list, but the one we have from 11.0 should still be relevant so far <jpr> the only thing i can really think of for 11.1 <federico1> vuntz: we can grab a week and ask each package maintainer to document its changes <jpr> is default # of desktops <federico1> vuntz: or to move that documentation from the wiki to the specfiles or to the patches themselves <jpr> other than that, no big proposed changes yet <vuntz> jpr: yeah, this one is the big obvious thing <vuntz> but it implies reworking what we have on the default panel <vuntz> we were talking about removing tomboy <jpr> that is true <vuntz> I'm also a bit worried that with all apps going in the notification area, we don't have that much free space <vuntz> so <vuntz> we can go with 4 workspaces for now (like upstream) and see how it goes <vuntz> federico1: (yeah, moving the doc to the spec file would be great :-)) <vuntz> what do people think about the workspaces? <sreeves> problem with c is that the knowledge is not centralized. no where to do a quick scan of policy decisions that might affect a new package I am making for example <vuntz> note that some other distros ship with 2 workspaces <vuntz> sreeves: it's easy to centralize. I can make something like http://tmp.vuntz.net/opensuse-packages/patch.py <sreeves> ah, true + jpr is slowly being convinced of C <vuntz> heh <jpr> vuntz: so it sounds like a) for now, c) longer term? <hobbsc> not sure how much it means, but i'd like to see tomboy remain. and i use 4 workspaces generally, regardless of what's offered <jpr> a) now so we can have the policy discussion earlier in the cycle <cyberorg> vuntz, we had flood of ubuntu users wanting to know how to activate cube, as they just had two sided desktop <jbrockmeier> vuntz: I always change it to 4 + jpr always makes it 10 <vuntz> jpr: the larger issue is that we're stuck with only one tag per patch right now. Might make sense to have a way to have more than one tag, imho <hobbsc> ha <vuntz> oh <vuntz> also <vuntz> adding back the workspace switcher implies fixing compiz/workspace switcher/libwnck integration <vuntz> because of virtual desktops vs viewport <hobbsc> i don't think compiz should be turned on by default <hobbsc> it's still pretty buggy <jpr> ok <vuntz> hobbsc: that's not the point. If you run compiz, you still want to be able to change the number of workspaces from the workspace switcher instead of having a buggy UI <vuntz> (or maybe I fixed this, don't remember) <vuntz> anyway <hobbsc> right <vuntz> let's go for 4 workspaces <hobbsc> +1 <hobbsc> jpr is just a little overzealous with his 10 :) <jpr> vuntz: does it make sense to do a) for next meeting and start a specific discussion on the mailing list ahead of next irc meeting? <vuntz> it'd be nice to then test the default layout with various resolutions <vuntz> jpr: sure <suseROCKs> +1 + flex_ has quit (Read error: 60 (Operation timed out)) <jpr> vuntz: i agree c) is better longer term, but its going to take longer that one pass at a) right? <vuntz> nod <jpr> vuntz: but maybe people can watch for it during the patch review rodrigo will talk about <vuntz> a) is basically running some commands, checking the output, doing manual export <vuntz> (although this might miss a few things) <jpr> in the mean time, 4 desktops for alpha 1 :-) <vuntz> there was also another thing I was wondering about <vuntz> does it make sense to categorize the changes? <jpr> how so? <vuntz> like "theming", "openSUSE integration", etc. <jpr> quite possibly - i really wanted a record of the rationale for the changes <jpr> because we ended up in these spots where we had no idea <vuntz> ok <jpr> why we ever changed it <jpr> categorization is a partial step there <vuntz> I'll try to group items in the next batch <jpr> doesn't capture the subtley of usability related items though <jpr> great

Speaker: jpr (12:57:03) ChanServ has changed the topic to: Meeting in Progress - GUADEC Update (jpr) | http://en.opensuse.org/GNOME/ | Testing needed: http://en.opensuse.org/GNOME/11.0/Testing <jpr> jpr: ... <jpr> so guadec <jpr> those of us who went <jpr> will publish a big report early next week <jpr> to opensuse-gnome@ <jpr> with some cool info <jpr> some quick highlights: <jpr> 1) Istanbul kicks ass <jpr> 2) Its time to package Gnome online desktop for 11.1 <jpr> 3) GNOME 3.0! <jbrockmeier> jpr: might want to put it up on news.o.o as well. :-) <lewing> 2) wasn't that the plan last year? ;) <jpr> federico1, hpj, vuntz others? <jpr> sreeves :-) <jpr> oh <jpr> 4) git vs bazaar <jpr> federico1: anything to say on that? <jpr> any particular topics people want covered in the report? <jpr> tabs in gcalctool? :-) + onestone (n=onestone@f048010142.adsl.alicedsl.de) has joined #opensuse-gnome + hobbsc is mighty jealous <vuntz> hobbsc: you also want tabs? <hobbsc> vuntz: i wanted to go to guadec <hobbsc> but tabs is a good thing <hobbsc> are <hobbsc> s/is/are

Speaker: jpr (13:00:59) ChanServ has changed the topic to: Meeting in Progress - Theme meetings (jpr) <jpr> just a quick note <jpr> giving helping hands exists <federico1> git vs bazaar <suseROCKs> tabs in gcalctool alone would motivate me to upgrade  :-) + stue has quit ("Ex-Chat") <jpr> i think we should finally kill the thought of theme meetings <hobbsc> suseROCKs: or RPN for that matter :) <jpr> any opposed? <hobbsc> due to lack of interest? <jpr> overlap with HH <jpr> and the purpose is less clear <jpr> they were sort of half dev half user meetings <suseROCKs> it does make sense... <hobbsc> +1 then <jpr> ok + jpr kills those

Speaker: mw (13:02:46) ChanServ has changed the topic to: Meeting in Progress - Package submission changes (mw) <jpr> mw: ... <jpr> THIS IS VERY COOL LISTEN UP TO MW! <jpr> assuming he speaks <suseROCKs> whew I thought maybe my hearing aid battery had died... <federico1> oh, this reminds me, do we use autobuild or the new build system now? <hobbsc> suseROCKs: what? <sreeves> mw - stop using the invisi font <vuntz> federico1: we should use the new one <vuntz> federico1: we can still use autobuild, afaik, but by using the new one, we're all community people at the same level. Which is a good thing (tm) imho

Speaker: rodrigo (13:05:18) ChanServ has changed the topic to: Meeting in Progress - Patch tagging day (rodrigo) <jpr> no rodrigo either <federico1> I can talk about the git stuff

Speaker: all

(13:06:01) ChanServ has changed the topic to: Meeting in Progress - Feature update (all) <jpr> sreeves: PackageKit update? <sreeves> couple of annoying bugs - lack of proper restart, some popups - are fixed and submitted <mw> sorry <sreeves> should hit the update channel in a couple days hopefully <jpr> sreeves: and for 11.1? <bugbot> New openSUSE 11.0 (GNOME) bug 410056 filed by jakub.rusinek@gmail.com. <jimmac> re <bugbot> Bug https://bugzilla.novell.com/410056 Minor, P5 - None, NEW, Gilouche theme: not all tooltips are yellow <jpr> mw: will come back around <mw> ok <jpr> sreeves: .... <jimmac> jpr: presentation? how? <sreeves> oh, 11.1 <sreeves> A1 will update to 0.2.3 version <jpr> sreeves: anything interesting in there? <sreeves> working on adding some new features like mime type handling out of rpms <jpr> ok <jpr> federico1: multiscreen update? + chen_ has quit (Read error: 110 (Connection timed out)) + chen_ (n=chen@117.192.226.145) has joined #opensuse-gnome <suseROCKs> hey gotta go all... my actors just came back... later

Speaker: mw (13:10:38) ChanServ has changed the topic to: Meeting in Progress - Package submission changes (mw) <jpr> mw: ... + suseROCKs has quit ("Easy as 3.14159265358979323846...") + flex_ (n=flex@61.14.130.209) has joined #opensuse-gnome <federico1> ok <federico1> multiscreen update: <federico1> nothing is changed so far from how 11.0 shipped <mw> ok <federico1> my next steps are to finish killing resapplet, and moving it to gnome-settings-daemon <mw> so, we're finally positioned to accept submissions from anybody who has a build service account <federico1> and then start looking at how to fix the X drivers that need it <FunkyPenguin> let the carnage begin <mw> FunkyPenguin: yes! <jpr> mw: as it right now? <jpr> ooh <mw> http://en.opensuse.org/Build_Service/Collaboration explains how much of it works <mw> jpr: yes, i'm preparing a glib2 update via the build service :) <mw> while anybody is welcome to submit stuff, i'd ask people to have a glance at http://en.opensuse.org/GNOME/Packaging_policy <mw> the ui for "branching" and "merging" is still rather rough around the edges <mw> i've been thinking about whether some osc plugin action might help to alleviate that, but i don't think we know what all the problem spots are yet <vuntz> mw: so, one stupid question: with autobuild, it's quite fast to build an updated package (to check that everything is fine) and then submit it. It'll be slower to wait for the obs to build a package, and it'll also be slower to build it locally (need to download all the deps, eg). Is there a good way to proceed? <mw> another point: all the new GNOME work can happen in the project GNOME:Factory now. that project has a number of maintainers, but i'd like to add more if anyone's interested <mw> and maybe we G:F maintainers could take turns checking for and submitting/rejecting submissions, say day by day or week by week <mw> vuntz: yes. short answer: "osc build --help". long answer, ask me a little bit later. <mw> vuntz: but downloading deps is still slow and is a pain point for me <federico1> vuntz: I find it actually faster to do local builds for testing <mw> federico1: the problem is when factory is rebuilt, you need to redownload everything from aaa_base and glibc up to whatever it is you're building <vuntz> ok <mw> federico1: so the first build of the day can take upwards of an hour <mw> federico1: even if it's a small package <jpr> and redownload whenever factory gets synced <mw> right <vuntz> mw: should we submit updated package directly to GNOME:Factory (for people who are authorized) or should we branch them and then merge them there (via the collaboration stuff)? + vuntz wonders if people can understand this question that is so badly expressed... <mw> vuntz: i think it's better to branch first <mw> vuntz: although if it's a really trivial change maybe it's ok <vuntz> sounds good <jpr> do we need a tutorial with mw present for this? :-) + kallepersson has quit (Read error: 110 (Connection timed out)) <federico1> hmm <federico1> mw: I'm fixing a gnome-main-menu bug - how do I submit it now? + kallepersson (n=kalleper@c-47fbe455.98-32-64736c10.cust.bredbandsbolaget.se) has joined #opensuse-gnome + kallepersson has quit (Read error: 104 (Connection reset by peer)) + nonsequitir has quit (Read error: 113 (No route to host)) + vuntz raises his hand for another question after federico1's one <mw> federico1: osc branch openSUSE:Factory gnome-main-menu; cd home:federico:branches:GNOME:Factory/gnome-main-menu; hack build; osc submitreq create -m "this is awesome so please accept it" <mw> sorry; i forgot osc commit before osc submitreq <federico1> mw: nice, thanks <FunkyPenguin> that actually makes sense and seems straight forward! <federico1> mw: does this work for 11.0 as well? (if I later need a patchinfo and stuff..) <vuntz> what about updates for 11.0 (and 10.3)? <vuntz> heh <jpr> mw: are you going to mail the list about this? is there a point at which we should definitely not use autobuild? <mw> vuntz: i'm not sure about old distros yet <mw> jpr: yes and good question + vuntz thinks we should avoid using autobuild as much as possible so that all contributors have the same set of tools <mw> vuntz: yes, agreed + jpr is excited <jpr> mw: anything else? <mw> jpr: i think that's it <mw> jpr: there will be plenty of kinks to work out, but i'm excited too <vuntz> looks really promising <jpr> excellent

Speaker: all (13:27:54) ChanServ has changed the topic to: Meeting in Progress - Agenda (all) <jpr> agenda items <jpr> 1) Pattern Review (captain_magnus) <jpr> 2) Policy Review (vuntz) <mw> oh, http://en.opensuse.org/User:Maw/Tips might be helpful for new BS users <jpr> 3) Feature update <jpr> 4) Feature review (jpr) <jpr> there was something for suseROCKS too i thought <jpr> its in the transcript somwhere, past my scrollback <jpr> other items? <hobbsc> jpr: a note on tutorials, i was just offering to help <jpr> ah <jpr> it was decriptor i wanted to ask for a plug <jpr> ok <jpr> other agenda items right now?

Speaker: all (13:30:49) ChanServ has changed the topic to: Meeting in Progress - Q&A <jpr> questions! <vuntz> should we start using factory now? :-) <FunkyPenguin> yes <cyberorg> how is it going to be different from coolsolutions and http://en.opensuse.org/HOWTOs? + vuntz actually did upgrade to factory on his laptop but didn't reboot yes <afonit> just came across http://opensuse-tutorials.com/ does that stuff come from the helping hands sessions? <jpr> vuntz: actually, factory in the vm looks great <FunkyPenguin> vuntz: you remember the issue i had when 11.0 was factory with my display? <jpr> i'm tempted to upgrade <vuntz> FunkyPenguin: yeah? <jpr> decriptor and suseROCKS need to answer afonit and cyberorg's questions :-) <FunkyPenguin> vuntz: it's back in factory again <FunkyPenguin> ive just reinstalled 11.0 so i have a workable display <vuntz> cyberorg: no idea, but I'd guess coolsolutions is not about opensuse? <hobbsc> jpr: what testing or documentation do you need currently? <FunkyPenguin> iirc coolsolutions covers ALL novell products <cyberorg> vuntz, thats ok, most solutions apply to suse ;) <cyberorg> sles and sled ones <vuntz> FunkyPenguin: could be a change in gtk+: it now uses randr1.2 when possible, and it breaks because the server always says it supports randr1.2 while the card might now <jpr> hobbsc: TBD by feature discussion :-) <vuntz> FunkyPenguin: I'd argue that opensuse is not a novell product. It's a novell-sponsored project :-) <FunkyPenguin> yes but it also shows up on their product sheet because they sell the boxed sets <vuntz> right <jbrockmeier> FunkyPenguin: it's complicated <cyberorg> vuntz, and en.o.o/Howtos? <FunkyPenguin> and therefore provide support for it <jbrockmeier> FunkyPenguin: but in general, we don't usually call openSUSE a "novell product" <FunkyPenguin> jbrockmeier: yes true <vuntz> cyberorg: no idea. I think the plan was to write tutorials afterwards and have them listed there <hobbsc> jpr: roger that <vuntz> cyberorg: but you'd have to ask suseROCKS <jpr> ok - looong meeting today to catch up + jpr looks forward to 11.1! <FunkyPenguin> jbrockmeier: maybe novell should be classed as an openSUSE product to balance the issue ;-) <jpr> any last notes? <jbrockmeier> FunkyPenguin: I'll bring that up ;-) + vuntz has to leave <jpr> thanks all!