09:00:55 < henne> Welcome to the openSUSE Status Meeting! 09:01:02 < henne> This meeting is meant to discuss the latest developments in and around openSUSE. 09:01:10 < henne> The topics for this meeting are: 09:01:10 < henne> 1. Status Distribution 09:01:10 < henne> 2. Status Communication 09:01:10 < henne> 3. Status Buildservice 09:01:10 < henne> 4. Status Events 09:01:13 < henne> 5. Questions & Answers wiki 09:01:15 < henne> 6. Questions & Answers channel

Status Distribution

09:01:27 < henne> first topic. Status Distribution 09:01:31 < henne> AJaeger lets go :) 09:01:38 < AJaeger> Thanks henne! 09:01:45 < AJaeger> We have this week our internal Alpha5plus and try to get factory stable again. There was quite some
breakage with the bootloader and I hope we have those fixed by now. 09:02:02 < AJaeger> The switch to GCC 4.2 caused also some problems for updates - we might need some further fixes for that. 09:02:38 < AJaeger> That's what I can tell right now. Expect some of the hackweek projects to show up in the distribution soon. 09:02:51 < AJaeger> Any questions, comments etc? 09:03:53 < henne> no questions? 09:04:10 < AJaeger> There's time at the end again for questions... 09:04:10 < henne> hm okay

Status Communication

09:04:25 < henne> so the second topic: Status Communication 09:04:27 < henne> notlocalhorst? 09:04:30 < notlocalhorst> mom 09:04:42 < notlocalhorst> - Hackweek is over, many nice projects, for the winners look on http://idea.opensuse.org/ 09:04:43 < notlocalhorst> - we are working on a news portal, news.o.o. The conent will not be Novell/SUSEgenerated,
the users can submit stories. It will run on wordpress, no eta but it will come soon. 09:04:43 < notlocalhorst> - download.o.o: Frank is nearly ready, should be online very soon 09:04:43 < notlocalhorst> - zh_tw wiki is online, waiting for the maintainer to announce it 09:04:43 < notlocalhorst> - fi wiki is ready and will be synced out very soon 09:04:44 < notlocalhorst> - ro wiki is still on my todo list, probably i will finish it after my vacation 09:05:11 < notlocalhorst> questions? 09:06:49 < henne> hmmmmm 09:06:55 < henne> is anyone awake? 09:07:01 * AJaeger is awake. 09:07:03 < markgray> hello all 09:07:03 < wolfiR> yes ;-) 09:07:05 < dl9pf> piep ... 09:07:15 * timrs isn't 09:07:42 < henne> okay so no questions there either 09:07:52 < henne> next topic: Status Buildservice 09:08:01 < notlocalhorst> ah mom .. new version of guiding principles is online, right now :-) 09:08:13 < henne> bauersman/adrianS? 09:08:26 < adrianS> notlocalhorst: announced on -project ml ? 09:08:28 * apokryphos had to get some nachos 8)

Status Buildservice

09:08:30 < adrianS> bauersman is on vacation 09:08:41 < adrianS> so the build service crew is rather small atm 09:08:43 < notlocalhorst> adrianS: i will do 09:08:57 < adrianS> in short we work on an end-user interface 09:09:07 < adrianS> which will support Benji's yast module 09:09:22 < adrianS> the idea is that one can host pattern files on the build service 09:09:27 < henne> end user interface? you mean the software portal? 09:09:40 < apokryphos> nope, one specifically for the OBS 09:09:40 < adrianS> (patterns contains a list of packages or reference to other patterns) 09:09:46 < adrianS> exactly 09:10:04 < adrianS> the software portal will be a meta search for this on others on top of it 09:10:29 < henne> okay 09:10:38 < adrianS> but we want to have an end-user interface where end-users (read as downloaders) 09:10:50 < adrianS> can also give feedback 09:10:51 < adrianS> via rating, tags and so on 09:10:58 < dl9pf> nice! 09:11:05 < adrianS> but in first step there will be only a search and download interface 09:11:35 < adrianS> the pattern files will be used and together with the other data, the build service has, it can create .ymp files
for Benji's yast module 09:12:02 < adrianS> so, it is REALLY easy to create a solution stack with this 09:12:14 < adrianS> simply upload a pattern file and the users can install with a click on the webinterface 09:12:29 < adrianS> and even get updates for it afterwards, because the repos get added 09:12:53 < adrianS> beside from that the build switches will be available soon (they are already in svn code of the build service) 09:13:17 < adrianS> means you can control the build, the release process or the reuse of packages from now on 09:13:33 < henne> neato 09:13:34 < adrianS> apart from that we work on getting Factory building 09:13:49 < adrianS> it does build already in the build service all packages, but does not boot strap yet 09:13:59 < adrianS> most build problems are solved 09:14:12 < adrianS> outstanding issues are esp. the java packages 09:14:25 < adrianS> we try to compile against gcj java instead of the sun java 09:14:32 < adrianS> because of the policy of the build service 09:14:43 < adrianS> but some packages fails with that 09:14:50 < adrianS> and others requires sun-java explicit 09:15:01 < adrianS> we need to discuss how to proceed here 09:15:17 < adrianS> I think openSUSE will not move away from the OSI license compliance requirement 09:15:31 < adrianS> that means we either need to port the packages or move them away 09:15:48 < adrianS> since this affects also quite important packages like eclipse it is not easy to decide 09:15:56 < adrianS> I think this is it from me 09:16:01 < adrianS> anything to add ? 09:16:03 < adrianS> any questions ? 09:16:22 < markgray> Any word on when sun java is going open source? 09:16:31 < adrianS> well, it is partly already 09:16:41 < adrianS> but it seems not to be enough for all packages 09:17:11 < adrianS> and the java 1.6 package still contains a quite large "binary only compatibility plugin" 09:17:32 < wolfiR> is there a document which describes the "build switches"? 09:17:56 < adrianS> wolfiR: the xsd files in the doc dir of the build service got adapted 09:18:10 < adrianS> for the docu in general, the docu team worked on that 09:18:22 < adrianS> I hope they publish it soon, but I have no update on that yet 09:18:32 * adrianS is currently in glasgow at aKademy :) 09:19:32 < adrianS> henne: okay, I think you can move on 09:19:43 < henne> any questions regarding all that? 09:20:15 < henne> oki doki

Status Events

09:20:28 < henne> next topic: Status Events 09:20:32 < henne> notlocalhorst again 09:20:33 < notlocalhorst> mom 09:20:47 < notlocalhorst> - LWE SF - we will have a obs talk & booth, /me and Seth 09:20:47 < notlocalhorst> - LWE UK - i will contact Novell UK, last year we had a counter on the Novell booth 09:20:47 < notlocalhorst> - LWE NL - i'm in contact with Novell NL, looks good 09:20:47 < notlocalhorst> - openexpo zuerich - http://www.openexpo.ch/ 19-20.09.2007, booth and talk 09:21:03 < notlocalhorst> questions? 09:21:34 < AJaeger> Anybody going to a local fair and needing some DVDs to give away? 09:21:44 < AJaeger> We have some 10.2 ones that we could send... 09:21:47 < apokryphos> do akademy have dvds? ;) 09:22:37 < AJaeger> apokryphos: They were planned but forgotten AFAIK. 09:22:40 < adrianS> aKademy is a hacker event, all are busy hacking ;) 09:22:42 < cb400f> we might like some for software freedom day 09:22:50 < adrianS> no one wants to install a system here ... 09:22:54 < cb400f> not sure when it is this year 09:23:03 < apokryphos> mandriva got really great publicity for shipping with the usb too :P 09:23:03 < cb400f> september some time 09:23:15 < AJaeger> cb400f: Send an email to michl at suse.de and ask for it... 09:23:22 < adrianS> right ... the free 2GB is popular 09:23:23 < cb400f> AJaeger: cool 09:23:27 < adrianS> michl knows already about that 09:23:30 < adrianS> and wants it also ;) 09:23:35 < apokryphos> adrianS: great chance to give people the option to try it out ;) 09:23:45 < adrianS> yes, definitive 09:23:59 < adrianS> and even when they remove the OS it is still printed on it ;) 09:24:00 < notlocalhorst> cb400f: no, send it to marketing@opensuse.org 09:24:09 < cb400f> notlocalhorst: noted 09:24:45 < henne> okay anything else regarding events? 09:25:21 < henne> not? okay

Q & A

09:25:37 < henne> then lets go trough the questions from the wiki 09:25:52 < AJaeger> Question was Does Novell plan to LSB certify the openSUSEproducts again?
We do not plan to go through the formalcertification (with final Linux Foundation approval) but will doall the tests and
try to comply with it. Tobias, can you explainthe rest of your question? 09:26:13 < AJaeger> There's a question regarding FAN support, e.g. bug #229214.
The bug is in state NEEDINFO for three months - and that means the developer waits for input. In this case,
let's move it away from the state... 09:26:14 < cb400f> software freedom day is saturday sept. 15.. everybody remember ;-) 09:26:17 < bugbot> openSUSE bug 229214 in openSUSE 10.2 (Kernel) "fan not working" [Critical,Needinfo]
https://bugzilla.novell.com/show_bug.cgi?id=229214 09:26:53 < AJaeger> Then there's a question on bugzilla for projects. 09:27:01 < henne> what about the connection from the BS to bugzilla? 09:27:09 < AJaeger> notlocalhorst: ? 09:27:15 < henne> whos involved in that? 09:27:18 < notlocalhorst> mom 09:27:27 < adrianS> henne: on my list ... we will do the easy approach first 09:27:29 < notlocalhorst> - we discussed today to add a new component to bugzilla - obs projects - (or whatever) to make it possible
to file bugs against obs projects. We should make a special mailinglist - obs bugzilla - for all bugs from this component. 09:27:33 < adrianS> found a component 09:27:42 < adrianS> and add http links to the web interface of the build service 09:27:47 < notlocalhorst> yes 09:27:55 < adrianS> thanks to the same userbase, we can reuse the account name 09:28:05 < adrianS> for reporting directly against project/package owner 09:28:35 < AJaeger> Yep... 09:28:46 * adrianS considers to implement it himself during a long compile ;) 09:28:59 < AJaeger> The question is who to handle the default assignee? What if people report directly via bugzilla? 09:29:01 < cboltz> Is it possible to use the username instead of the mail address in the bugreporting link to prevent spam? 09:29:20 < adrianS> cboltz: afaik yes 09:29:54 < adrianS> cboltz: but it should be anyway only available for logged in users imho ... 09:30:19 < adrianS> but that is up for discussion 09:30:29 < cboltz> Why do you think so? 09:30:34 < cboltz> I would also add a bugreporting link to every package 09:31:07 < adrianS> you need anyway an account in bugzilla, so why confuse not logged in users ? 09:31:17 < adrianS> yes, project and package 09:31:56 < cboltz> They would need to login twice - once for *.opensuse.org and once for *.novell.com 09:32:12 < adrianS> that is true ... 09:32:22 < adrianS> unfortunatly there is no solution for this atm :/ 09:32:27 < cboltz> (BTW: package as in "the RPMs available for download - for example in the Packager: field) 09:32:34 < adrianS> a bugzilla.opensuse.org alias seems not to be possible atm 09:33:01 < cboltz> (BTW2: Just tested to assign a bug to "cboltz" and got "did not match anything". Probably needs some
tuning/work...) 09:33:45 < henne> next topic? 09:33:53 < apokryphos> I don't think the novell bugzilla supports assigning bugs to non-novell employees, or was that fixed? 09:34:01 < adrianS> it should 09:34:21 < wolfiR> it does AFAIK 09:34:28 < AJaeger> check https://bugzilla.novell.com/show_bug.cgi?id=229213 - assigned to Pascal ;-) 09:34:31 < bugbot> openSUSE bug 229213 in openSUSE.org (Action Items) "[AI] clarify bugzilla usage for packages in
build service" [Normal,New] 09:34:32 < wolfiR> I got one assigned already 09:34:45 < apokryphos> ah ok, great 09:36:38 < henne> okay next topic 09:36:49 < henne> questions out of the channel 09:36:52 < henne> anyone? 09:37:28 < henne> no general questions? 09:37:43 < cboltz> Can we have a public user lookup in the buildservice? 09:37:47 < cboltz> (see https://bugzilla.novell.com/show_bug.cgi?id=198516, novellonly) 09:37:58 < adrianS> what is a public user lookup ` 09:37:59 < adrianS> ? 09:38:09 < adrianS> you get already the email addresses 09:38:34 * adrianS looks in the bugreport 09:38:44 < AJaeger> I think the bugzilla team has it on their queue of items to do... 09:38:45 < cboltz> The bugzilla user lookup returns *nothing* when searching 09:38:47 < cboltz> except you are a Novell employee 09:38:53 < adrianS> bloody university proxy rejects connecting :/ 09:41:42 * cboltz will paste parts of the bugreport to adrianS 09:43:58 < henne> done? 09:44:31 < cboltz> yes ;-) 09:44:57 < henne> so any other questions? 09:45:10 < notlocalhorst> aprove my vacation! 09:45:34 < henne> stfu 09:45:46 < henne> no questions? 09:46:06 < adrianS> sunshine in Glasgow :) 09:46:12 < henne> So that was it. If you have more, dont hesitate to bring it up on the appropriate mailinglist. 09:46:13 < adrianS> not good for hacking moral ... 09:46:16 < henne> Thank you all for participating. Good night and good luck! 09:46:31 < henne> the next meeting will take place at 07.07.18 09:46:45 < henne> same time, same channel 09:46:50 < henne> !topicdiff 09:47:01 < wolfiR> in 11 years? 09:47:07 < SUSEhelp> henne: Too many changes! 09:47:09 * henne kicks SUSEhelp 09:47:09 < SUSEhelp> henne: Old topic: openSUSE project talk (not support) | Next Meeting 4th July
http://en.opensuse.org/Meetings/Current | Also visit #opensuse-factory and #opensuse-buildservice 09:47:12 < SUSEhelp> henne: Current topic: Welcome to the openSUSE Status Meeting! 09:47:20 < superniemand> wolfiR, learn international formating 09:47:33 < superniemand> ;-) 09:47:33 < wolfiR> superniemand: international formatting is using -, isn't it? 09:48:07 < henne> alrighty 09:48:10 < aka_druid_> AJaeger: ping 09:48:13 < henne> off to fix zsnes

Post-Meeting: Handling feature requests and package wishlist

[the following two lines were moved down to meet the context] 09:46:27 < cboltz> Any news on providing some FATE accounts? (Bug 223290) 09:46:29 < bugbot> openSUSE bug 223290 in openSUSE.org (Action Items) "[AI] better wishlist handling using FATE" [Normal,Needinfo]
https://bugzilla.novell.com/show_bug.cgi?id=223290

09:48:13 < apokryphos> cboltz: we spoke about this a little last week and the general thoughts were about having another place to track
the relevant goals etc 09:48:19 < aka_druid_> over already? 09:48:35 < apokryphos> since relaying info about FATE to others isn't ideal 09:48:59 < cboltz> That brings us back to bugzilla with 09:49:25 < cboltz> a) severity "Enhancement" 09:49:27 < cboltz> b) a new product "openSUSE package wishlist" with several components 09:49:58 < cboltz> b) was already there in the good old times of SUSE Linux <= 10.0 ;-) 09:50:14 < apokryphos> I think we decided to use bugzilla for wishlist items 09:50:23 < apokryphos> but we still need a place for goal-tracking 09:50:42 < apokryphos> using idea.o.o was brought up but generally (IIRC) rejected because it'll become a dump 09:51:25 < cboltz> What's wrong with bugzilla for goal-tracking? 09:52:23 * cboltz thinks an enhancement can also be titled a bug ("application foo can't sing") ;-) 09:52:37 < AJaeger> I don't want another openSUSE package wishlist. With the build service, this should be handled differently... 09:53:00 < AJaeger> We need to find a way that a package goes first in the build service - and we can then move it to FACTORY... 09:53:06 < aka_druid_> AJaeger: daemon said you owe use a name or email adress. Do you have it? 09:53:44 < AJaeger> aka_druid_: regarding suse-irc.org? 09:53:49 < aka_druid_> yes 09:53:58 < AJaeger> I gave it to daemon already, let the two of them talk together. 09:54:08 < aka_druid_> ah, good 09:54:17 < aka_druid_> AJaeger: I wonder why it was routed tru you 09:54:22 < aka_druid_> if we are the admins 09:54:23 < AJaeger> But I agree that ridiculing others is not the right thing. 09:54:31 < AJaeger> aka_druid_: That guy didn't know - but know me. 09:54:50 < AJaeger> It was fun doing this in november - but that's a long time ago... 09:55:10 < benJIman> adrianS: Can't you put the svn openjdk in build service and build java stuff against that? 09:55:44 < cboltz> AJaeger: Basically I agree that a package should start its carreer in the buildservice, but this isn't the problem. 09:55:47 < cboltz> The problem is that there will always be people that request a package, but don't have packaging skills. Those people
will still need some type of wishlist. 09:56:07 < AJaeger> We could put that as category under the "openSUSE BuildService Projects" bugzilla. 09:56:17 < cboltz> And you know that handling the wishlists in the wiki is a nightmare... 09:56:18 < benJIman> adrianS: Even development snapshot is going to be considerably better than gcj 09:56:38 < AJaeger> cboltz: I just want to avoid that all gets routed to me ;-) 09:57:11 < kl_eisbaer> cboltz: perhaps we should "drop" the wishlist and/or enhance it: make a "package list" containing already
available packages (and their specfile-description) and wishes? 09:57:15 < benJIman> apokryphos: it doesn't allow searching for non-novell employees though. 09:57:17 < cboltz> Understandable - so create a default (dummy) assignee like wishlist@opensuse.org ;-) 09:57:29 < benJIman> If you know their ichain account's email address you can assign it to them. 09:57:32 < AJaeger> cboltz: Yeah... 09:57:33 < aka_druid_> cboltz: why the wiki page isnt enought? 09:57:50 < cboltz> Editing the large tables is a PITA :-(( 09:58:00 < aka_druid_> bah 09:58:28 < apokryphos> AJaeger: do you know if anything's happening with that? (what benJIman said) 09:59:07 < AJaeger> apokryphos: Searching for non-novell employees? Yes, that seems to be worked on. See cboltz comments before... 09:59:13 < cboltz> And some type of tracking and easily searchable and filterable status notices (like fixed aka done) would really help 09:59:48 < cboltz> I don't know the workload of the bugzilla team, but I would print the "seems" more bold than the "worked on" :-/ 10:00:20 < apokryphos> yes, handling wishlist on the wiki isn't fair to wishers too 10:00:44 < apokryphos> pure chance if they get feedback on their wishlist item etc 10:00:50 < aka_druid_> apokryphos: put some sort of a form then 10:01:06 < apokryphos> some wishes have been there for years etc 10:01:36 < apokryphos> AJaeger: cool, I'll try it out 10:01:50 < aka_druid_> apokryphos: so? It doesnt mean it should be packaged 10:01:52 < aka_druid_> maybe nobody care 10:02:10 < aka_druid_> unlike that idiot alexey taht think he should be giving orders to people 10:02:48 < apokryphos> aka_druid_: it doesn't for sure; but someone should get feedback on a wish they filed 10:03:00 < aka_druid_> why they should get feedback? 10:03:15 < aka_druid_> the lsit is there, if its really interesting for it to be packaged, it will be 10:03:17 < apokryphos> same reason you should get feedback about a bug report? 10:03:27 < aka_druid_> if not, there is no need to send an email saying "sorry, you failed" 10:03:53 < aka_druid_> no, I dont think so, I think its wasting energy with something that makes no diff at all 10:04:08 < apokryphos> so we shouldn't answer all bug reports? 10:04:25 < aka_druid_> we shouldnt send amsil saying "sorry, your suggestion wsnt good enough bla bla bla" 10:04:29 < aka_druid_> mails* 10:04:49 < apokryphos> course not; should be able to mark as rejected etc 10:04:51 < benJIman> It actually saves time or people will re-file or it will clutter up the wishlist. 10:06:18 < aka_druid_> the way it is today seems reasonable, that list... maybe make it easy to put a pkg in the list 10:06:33 < aka_druid_> making in bugzilla will bug the developers, will ahve people asking and eing annoying and reopening bugs 10:06:42 < aka_druid_> I see no reason for the stress, the way it is now is fine 10:07:12 < apokryphos> wishes are important to tend to 10:07:27 < aka_druid_> why? 10:07:35 < apokryphos> because they can improve the distribution 10:07:40 < aka_druid_> if we were to solve that we would ahve 50 php applications in suse right now 10:07:45 < aka_druid_> becasue half the wishlist are php stuff 10:07:54 < aka_druid_> which shouldnt be packaged anyway 10:07:54 < apokryphos> listening to user suggestions is important; that doesn't mean you have to agree with everything said 10:08:09 < aka_druid_> right, let the list there, we hear, and its all great 10:08:20 < cboltz> aka_druid_: either you like to castigate yourself by editing large wiki tables and searching for comments/status or
you never edited a wishlist in the wiki ;-) 10:08:22 < aka_druid_> but now you want people to listen to a no in bugzilla, gets frustrated and pissed 10:08:39 < aka_druid_> cboltz: those kind of people editing the list would never be able to sue bugzilla 10:08:42 < apokryphos> I don't think the wiki is read; it's also another misuse of the wiki 10:08:48 < aka_druid_> its easier for them to edit or fill a form than to go to bugzilla 10:09:06 < aka_druid_> and honestly I dont want to see them in bugzilla. The current sitaution shows taht lost of people shouldnt
have bugzilla accuonts 10:09:25 < aka_druid_> apokryphos: tell people to read it them. If thats the problem... 10:09:34 < aka_druid_> I know packman people and yaloki reads it eventually 10:09:38 < aka_druid_> I read 10:09:42 < cboltz> aka_druid_: editing the wishlist table is a nightmare. Really. 10:09:50 < aka_druid_> cboltz: make a form then 10:09:57 < aka_druid_> thats no reason to push it in bugzilla 10:10:12 < aka_druid_> you are doing like the engineers do: solving the wrong problem 10:10:35 < aka_druid_> apokryphos: if its a misuse of the wiki, its a missuse of bugzilla either 10:10:40 < cboltz> Then tell me how to add status handling to the wiki (like "packaged for 10.3" or "won't be packaged" or "already there"). 10:11:00 < aka_druid_> that doesnt need to exist 10:11:21 < cboltz> nevertheless bugzilla would be the better tool here. 10:11:30 < aka_druid_> maybe when 10.3 is released make a list of whats new in apps for it 10:11:40 < cboltz> I don't claim it's perfect, but it is better. 10:12:04 < aka_druid_> recently packaged page in BS, for example... same way there is now in packman 10:13:42 < cboltz> Bugzilla can provide this list using the search feature: component "package wishlist", status "FIXED", last modified "-30d" ;-)) 10:14:15 < aka_druid_> nobody knows how to use bugzilla, leat alone search and filter 10:14:30 < aka_druid_> people dont like to use bugzilla 10:14:40 < cboltz> You can always provide a link containing the search parameters already 10:14:47 < cboltz> as in "click here to see new packages" 10:14:56 < aka_druid_> or you can provide an email that people send pkg requests, or a form 10:15:11 < aka_druid_> and then somebody checks if its really interesting and thats it, its done 10:15:20 < AJaeger> /me waves goodbye - sorry have to leave... 10:15:40 < cboltz> Well, define "somebody". 10:15:59 < aka_druid_> somebody from suse of course 10:16:10 < cboltz> (And: who knows if somebody else wouldn't be willing to package it?) 10:16:27 < aka_druid_> anyway, the list in the site is much more useful, it could be put in factory or BS or packman 10:16:31 < aka_druid_> everybody can see it 10:16:40 < cboltz> What if someone from the community would package it - but doesn't know it was requested? 10:16:42 < aka_druid_> its there, all you need is a url in your browser 10:17:04 < aka_druid_> cboltz: how bugzilla solves those issues you raised? 10:17:06 < aka_druid_> it doesnt 10:17:13 < cboltz> It does. 10:17:21 < aka_druid_> you need to have people accessing bugzilla actively, doing searches 10:17:25 < aka_druid_> no, it doesnt 10:17:46 < cboltz> Take an example: The list of open Action Items: 10:17:47 < adrianS> benJIman: as far as I am told there is too much missing to be open sourced 10:17:51 < aka_druid_> its much easier for people to read a page in browser or an email with a list of apps then going to bugzilla,
log, do searches 10:18:03 < benJIman> adrianS: Everything in their svn is GPLed. 10:18:18 < adrianS> right, but not everthing what was in former binary only java 10:18:22 < cboltz> Just click this link: http://tinyurl.com/39grvk 10:18:33 < adrianS> but you are right, we should at least try it to see the status 10:18:37 < benJIman> adrianS: Probably enough though, what fails to work with it? 10:18:40 < cboltz> You don't want to tell me that people can't click a link?! 10:18:54 < adrianS> benJIman: look in the openSUSE:Factory project ;) 10:19:03 < benJIman> Afaik it's only things likc colour profiling etc 10:19:07 < aka_druid_> cboltz: they wont click the link adn track stuff in there 10:19:10 < benJIman> adrianS: You mean the broken eclipse? 10:19:15 < adrianS> for example 10:19:34 < aka_druid_> cboltz: and AI are not package requests 10:20:10 < cboltz> aka_druid_: Then they also won't click the link from the Wishlist to one of the Wishlist subpages (like Wishlist Base) also. 10:20:11 < aka_druid_> benJIman: speaking of which, your java6-plugin isnt broken? 10:20:30 < benJIman> aka_druid_: I use konqueror. 10:20:32 < aka_druid_> cboltz: its a webpage, sure they will 10:20:39 < benJIman> adrianS: It's a lot more complete than classpath/gcj anyway. 10:20:40 < cboltz> And: I can't show a link for package requests because they aren't in bugzilla currently. That's a non-argument.
The technical part is the same. 10:20:45 < aka_druid_> benJIman: shouldnt it use the same plugin dir? 10:20:46 < cboltz> So they will also click the link that leads to bugzilla. 10:20:52 < benJIman> aka_druid_: konqueror doesn't require a plugin. 10:20:57 < benJIman> It uses java directly. 10:20:58 < aka_druid_> ah k 10:21:51 * cboltz goes to have evening meal 10:21:58 < aka_druid_> cboltz: you are forcing people to waste time goin tru those bugs and saying no to 99% of them 10:22:01 < adrianS> benJIman: when I get kesselborn to provide open source 1.6 packages for factory, I can configure the OBS to use it ... 10:22:38 < benJIman> adrianS: Ok, you could also try the svn 1.7 if there's problems with 1.6 without the non-free stuff. 10:22:46 < cboltz> aka_druid_: I'm afraid we could do this discussion for hours. 10:22:53 < aka_druid_> cboltz: Im afraid 10:23:10 < cboltz> I have a better suggestion: I'll write to opensuse-factory and ask people for feedback 10:23:17 < cboltz> if they prefer the wiki or bugzilla for the wishlists. 10:23:18 < cboltz> OK? 10:23:25 < adrianS> benJIman: I have no clue about java .... that needs to be done from someone with some more knowledge ... 10:23:33 < aka_druid_> cboltz: I cant prevent you from doing it 10:23:33 < benJIman> GCJ compiled java stuff is just slow, and classpath is very incomplete/full of bugs. 10:23:43 < cboltz> ;-) 10:24:05 < benJIman> adrianS: Trouble is java people have no clue about packaging generally, except yaloki, who's on holiday for 2 or 3 weeks. 10:24:25 < adrianS> benJIman: the problem is that kesselborn gets a new job soon, I have no idea who will take over the job ... 10:24:41 < benJIman> Is that Daniel? 10:24:45 < adrianS> yes 10:25:17 < adrianS> its a pity, because he worked closely with the jpackage people 10:26:17 < benJIman> I think problem is java stuff doesn't really need to be packaged because it runs anywhere, so people havn't generally bothered. 10:26:47 < benJIman> But the core platform needs to be there, and preferablly core things like eclipse,maven,ant,javacc, etc