[Libreoffice-qa] FDO Permissions
-- Forwarded message -- From: Joel Madero jmadero@gmail.com Date: Mon, Sep 17, 2012 at 8:56 AM Subject: FDO Permissions To: libreoff...@lists.freedesktop.org Hi All, I know that this is a touchy subject and needs a lot of discussion but, how difficult is it to make it so you need permissions to change priority and severity of a bug? My goal is to at least kind of deal with priorities in the coming months but it's pretty much impossible if a regular user can go in and set a bug as CRITICAL - HIGHEST because of a minor alignment issue -- and this is pretty common. I think we should start discussing if it's time to close off certain things in FDO to regular users and start talking about who gets permissions to do these. My suggestion is upon request a user gets permissions, most users won't take this step just to up the priority of their own bug and it won't be harmful to have 10's or 100's of users with permissions to prioritize/triage/etcIf a user takes the time to say hey, I'd like permissions on FDO, they are probably at least 50/50 likely to prioritize right. Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] [TRIAGE] Weekly Update
Hi All, Weekly update, stats, and more requesting of triagers: Date Number of Unconfirmed Bugs 30 Days Old Average Length of Days Since Opened Average Length of time Since Last Change Median Length of Days Since Opened Median Length of time Since Last Change 4/9/2012 893 100 64 87 52 10/9/2012 845 103 65 86 50 17/9/2012 847 102 62 81 44 As you can see we've seen progress and it's still realistic that we can hit the goal of being caught up by Dec. 31st. This weeks request, can we get 10 people (devsanyone?) to commit to triaging 15 bugs? This would mean 150 done in the week which will help a lot. 15 bugs shouldn't take more than half an hour in most cases. Again here is the spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=1 I recently saw that the spreadsheet looks like garbage if you have a smaller screen, my apologies and I'll try to make this better (my screen is quite a bit bigger so it looks fine on my side). If you could reply to this email (reply all) and just say I'll do 15 that would be great (maybe motivate others to agree to do 15 also). Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Proposal for Hard Hacks
Hi Everyone, Michael came up with an idea for hard hacks that I liked. Here is the proposal: a) each QA staff member gets to nominate one bug to hard hacks at a time b) that member monitors the bug occasionally and once it is fixed they can put another one on the list c) in order to track we could use the QA Contact Field since no one else uses that field vs. whiteboard where anyone and everyone edits. We could use it in one of two ways: - have a dedicated QA member that we assign to (one) and then that basically tells the developers this is a hard hack - each individual member of QA puts their own name in there so then the developers know who put the bug as a hard hack I am also open to the idea of just adding a whiteboard status of HardHack. Today at the conference call they had done all but 1 of them and asked for more, I was unprepared to give more. We should try to keep that list constantly at 5-7 bugs. Probably something that we should discuss next week during our call but we need to get a method down so that developers can tackle these bugs. Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Esc Call Notes
These are just a few of the things that pertained to QA 1. Calc (3.6) crashing 1. bugs discussed, we need to go through the Unconfirmed and verify. The NEW ones are being looked at by the developers 2. HardHacks 1. Previous email sent out, we need to finalize the process 2. Developers have gone through the hard hacks, a continuous list is preferred (max of 5-7 bugs at a time, refilling these as they are taken care of is best 3. See previous email for suggestions 3. Triaging 1. Begged for more help for back log ;), some interested but suggestion of bug hunting session. Time difference could be an issue, can someone else in Europe try to arrange this? If it's over the weekend I may be able to join, otherwise very hard 2. There are 30ish students from Hungary (I believe?) doing development, asked for more EasyHacks to work on, I suggested that maybe they could help triage and maybe find their own EasyHacks (not sure what the result of this was) 4. EasyHacks 1. Like above, need more EasyHacks marked, people are available to deal with them but there aren't enough out there 2. My comment: I'm seeing things marked as EasyHack without the entire list of things that we usually should put for easy hack (particularly bt if possible, and some direction as to where to look in the code) 5. MAB 1. There really shouldn't be any put to 3.7 from what I understood 6. Resolved Status 1. Only mark as Resolved if it's resolved in latest stable, not if it only works in latest master (a comment can be put in if it's working on latest master) 2. WORKSFORME unless you know for sure the bug was assigned and dealt with by a developer, in which case ask them to mark as RESOLVED - FIXED or mark it yourself (again only if you're sure that it wasn't just coincidentally fixed, or just works for you and you're not sure if the particular bug was dealt with) 7. Issues regarding rudeness on FDO 1. Michael dealt with the one case, banning a user is probably more problematic than it's worth. 2. Creating a wiki page (Joel) to kind of address this, something along the lines of What is not useful in reporting a bug I think that was about it, if I missed something, my apologies. Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Reporting Ignorant User on FDO?
I think Michael already sent him a message and he's said he's done it before as well. What got to me a bit was that this actually made his bug move faster which is like promoting these ridiculous antics that he apparently is known to have. Because it was a minor bug to begin with, I was tempted to let it sit there for awhile and make it clear that it was because he was being an a.but, that ultimately hurts our project and probably doesn't do much to help any of us including him. Best thing I could have done was ignore it and move on but it was late and it pissed me off so I commented and spammed everyone about it ;) I do think that most forums and community sites have general rules listed somewhere that a user can be directed to, this is probably a good thing to have just so that if in the future we ban a user, we can direct him/her to the rules and point out which ones were violated. Best Regards, Joel On Thu, Sep 13, 2012 at 9:46 AM, Rainer Bielefeld libreoff...@bielefeldundbuss.de wrote: Joel Madero wrote: IMO we need to add a section to how to file a bug report that is labeled what is not helpful or useful in there I could put Hi, of course you can do that, but there are 2 kinds of users: 1. those who do not need such advise 2. those who do not follow such advise We already have had some discussion concerning U. from time to time. My suspect: c... and f... are at least 20% of his English vocabulary? ;-) I'm not involved and so I can send to him a friendly but assertive E-Mai; and it's annoying but possible to delete a useless f... comment, may be such a warning shot might help a little? Best regards Rainer ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[TRIAGE] 2nd Checker fdo#48942
Can someone else check out this bug and see if you can verify. I was unable to but the user swears they still have a problem with it and has reopened the bug as such. If you could check and comment on it that would be great. https://bugs.freedesktop.org/show_bug.cgi?id=48942 Best Regards, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Reporting Ignorant User on FDO?
Is there a way to report users on FDO. This is in regards to the comment made here by user Urmas https://bugs.freedesktop.org/show_bug.cgi?id=40025 Now stop fucking with bugzilla and other people's bugs. I tend to not care much but this particular user pissed me off and well.I'll hold a grudge. Let me know if there is a procedure and I'll deal with it. Best Regards to everyone, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] Triaging Project Update (10/09/2012)
We all fit in just the same :) At this point we're really in the early stages of getting a team together who is willing and able to commit some time at triaging (and more broadly QA work - but for now just triaging). I am hoping to get all bugs 30 days UNCONFIRMED taken care of by the end of the year. We had some solid progress in the last 4-5 weeks but it's slowed down and that's not good. If you can, please go to this link, https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=1 and assign yourself one of the tabs. Also please add your name to the contact list so we can finally get a real team together that's regularly triaging. In the long run (once we're caught up) we can start looking into assigning new bugs to triage based on the list of contacts. I think 10-15 people are needed if we're going to keep up with the amount of bug reports, right now we have probably that number but only 4-6 are really active. Thanks for offering, this is one of the areas where we really need help. Feel free to add me on gchat and/or email me if you have any questions/concerns/suggestions. Best Regards, Joel On Tue, Sep 11, 2012 at 12:05 PM, Hashem Masoud wraithl...@gmail.comwrote: Dear Joel, I'm willing to help. Where do I fit in within the QA team? You can see my recent activity in FDO bugzilla Libreoffice bugs. On Tue, Sep 11, 2012 at 12:44 AM, Joel Madero jmadero@gmail.comwrote: Weekly update and reminder that we're still looking for people to help out. Progress is ongoing but it's slowed down a bit. Thanks to everyone continuing to help. Here is the link to the spreadsheet again: Regards, -- Hashem Masoud ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Triaging Project Update (10/09/2012)
Weekly update and reminder that we're still looking for people to help out. Progress is ongoing but it's slowed down a bit. Thanks to everyone continuing to help. Here is the link to the spreadsheet again: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=1 Stats, I've updated format, this is how it will look for now on for weekly updates: Date/# 30 Days/Average Days Since Open/Average Days Since Last Change/Median Days Since Open/Median Days Since Last Change 4/9/2012 893 100 64 87 52 10/9/2012 845 103 65 86 50 Formatting is terrible in gmail, tables don't seem to work right. Hope everyone had a great weekend, happy Monday Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [PROPOSED] Changes to General Options FDO#40656
http://opengrok.libreoffice.org/xref/core/cui/source/options/optjava.cxx#93SvxJavaOptionsPage http://opengrok.libreoffice.org/s?refs=SvxJavaOptionsPageproject=core::SvxJavaOptionsPage http://opengrok.libreoffice.org/s?refs=SvxJavaOptionsPageproject=core( On Fri, Sep 7, 2012 at 7:28 AM, Caolán McNamara caol...@redhat.com wrote: On Thu, 2012-08-09 at 14:07 -0700, Joel Madero wrote: Hi All, This is in response to FDO#40656: https://bugs.freedesktop.org/show_bug.cgi?id=40656 In order to accomplish this I need to move some things around. I did the visual changes - didn't do any of the functional changes yet, nor did I ensure that spacing and what not is perfect. Looking for general input before I put the time that is needed into this. Thanks all. Seems sane to me (seeing as I pushed the first patch in this process, I thought I'd better go back and have a look at the final picture). Though maybe (more work) Measurements would be better at the top, the rest of the general options are sort of obscure. C. Shouldn't be a problem at all. As for your other comment about changing name of help, how do I go about doing this? I've never messed with the help stuff before so I'll need a bit of guidance. Also now that Java page has changed to Advanced, does it make sense to have files named optjavacxx,src, etc...? Should I consider changing the names to something more sane since it's not just java? Also the page name is now not really complete (svxJavaOptionsPage). If you give me some guidance I'll move forward on that, until then I'll get at least the first part of the measurements moved. I'm not sure if I'm going to redo the measurements completely (ie. combine each components measurement into one) or just have the option in general control all of them as is (ie. separately). I'll figure that out as I go along. Thanks for pushing that one out, it'll be nice when this change is done :) Best Regards, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Triage Project Update
Hi Nino, That's the beauty of our project, everyone's opinion is respected :) I'll try to avoid adding any work to website team and see what method works best to get these triaged and organized best. As of now, google doc + fdo seems to be doing the trick :) Ultimately might just make a macro to auto sort them once every other week to keep the google doc updated until the project is done (ie. getting all bugs 30 days old triaged so we can try to stick with a goal of triaging withing 30 days for new bugs). Thanks for all the valuable input. Best Regards, Joel On Tue, Sep 4, 2012 at 3:07 PM, Nino Novak nn.l...@kflog.org wrote: Am 04.09.2012 23:05 schrieb Joel Madero: I agree that FDO has some benefits but the limitation is really that each user is needed to query every time, the possibility of overlap is great, and no one is really responsible for an individual bug until the query is made and someone takes the time to look into it. I'm not sure if others would agree but it seems like having a group of 50 or so and being able to just do those at your convenience makes people more likely to help and feel like their is an end in sight for their portion. This is vs. just seeing a never ending list from FDO or even having to teach new users (or even not new users) exactly what to search for every time with FDO. As for me (a rather unexperienced QA Newbie), I've chosen a somewhat different approach: I've first created two custom searches, 1) all recent bugs (reported within the last two days) for curiosity (just to see what people report recently) 2) all UNCONFIRMED bugs from the last 14 days From query 2 I picked a couple of bugs every couple of days to reproduce/confirm/assign/close/whatever seemed appropriate. That's just to show a slightly different approach, which is rather simple and can be handled perfectly within bugzilla itself without any external tool. Ok, the only problem was, that when a person starts reproducing a bug, it can happen, that another triager just starts with the very same bug at the same time. So some kind of lock signal was the only missing thing to prevent duplication of work. However, this situation did not happen a single time during my self-chosen BugReviewWeek ;-) Another advantage: By the above process nobody (virtually) blocks 50 bugs for a longer time period. Bugzilla queries are very adequate at every time, as all works with live data. Similar to how developers assign themselves bugs and then can just go look at their own bugs (My Bugs) it would be nice to have this ability for QA triagers but have it somewhat automated since it's just triaging, not programming. In the long run (once we're through the back log of 650+ that are really old), it would be amazing if we had a team of QA staff that signed up to have bugs auto assigned to them for triaging. We have the libreoffice-bugs@fdo mailing list, which contains (nearly?) every new bug. Could we use it somehow for this purpose? E.g. by replying to a bug or forwarding it to the qa list or some such? (Just thoughts, nothing concrete) What I imagine: QA triagers sign up for components they are willing to triage and their max load New bug is reported, if the bug has a component listed the bug gets auto assigned for triaging purposes according to some rule(s) Personally, I prefer not to sign up for a special component but to pick a recent bug which kind of attracts me spontanously. But there might be other opinions/preferences/arguments/approaches. For now the google docs works, FDO does not as it is now but I'll discuss this further with Bjoern, Petr Rainer to see if we can come up with something more functional than the chaos that is FDO :) Or maybe I'm just not familiar enough with FDO to really feel comfortable myself with it, this is more likely than not true :) :-) I like your initiative. Please don't feel discouraged by my comments, I just wanted to add a slightly different view. If people like your approach, that's great! It does not contradict to mine (IMHO), as it's rather obvious if a bug has been triaged or not. So we can all work together towards our common goal. Regards, Nino ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
How Can I Provide More Info For Developers
Hi All, Came across this bug FDO#45570 and I've already nominated as a most annoying bug but I think that devs might appreciate me getting some kind of a log or something together for the crash. What type of log should I create and how do I go about doing this (basic steps, my knowledge of terminology is still in the first stages :) ). Thanks everyone Best Regards, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: How Can I Provide More Info For Developers
I don't see that helping much, as the developer who takes this one can quickly do this themselves. A working doc only takes 2 seconds to make. Best Regards, Joel On Fri, Sep 7, 2012 at 9:35 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 6:11 PM, Joel Madero jmadero@gmail.com wrote: Hi All, Came across this bug FDO#45570 and I've already nominated as a most annoying bug but I think that devs might appreciate me getting some kind of a log or something together for the crash. What type of log should I create and how do I go about doing this (basic steps, my knowledge of terminology is still in the first stages :) ). Thanks everyone Best Regards, Joel Just some random thoughts here: What happens when you create a 'working document', thats been opened and saved in Msoffice or OpenOffice, and then try to open that saved doc in LibreOffice ? Does the issue still appear ? Also, would it be helpful to attach such a document to the bug report for troubleshooting purposes ? - John Smith. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: How Can I Provide More Info For Developers
Wrong Bug, dammit, my bad. Here is the proper one, attachment is there and functioning, I had 5 open FDO tabs in FF and picked the wrong one. https://bugs.freedesktop.org/show_bug.cgi?id=48569 My apologies Joel On Fri, Sep 7, 2012 at 9:57 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 6:38 PM, Joel Madero jmadero@gmail.com wrote: I don't see that helping much, as the developer who takes this one can quickly do this themselves. A working doc only takes 2 seconds to make. Best Regards, Joel Another random thought then: Is there a way to reproduce the issue that doesnt require the installation of Lotus Domino ? - John Smith. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 10:44 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com wrote: Hi John, You can always make it easier for a developer to solve - and the easier it is, the more likely it is to get solved quickly. Ways to do that are: * getting a stack-trace with full debugging symbols * running valgrind with full debugging symbols and attaching a trace. Sounds good, but I agree with John that better instructions are needed. I'm working on a new triage page and hopefully in there we can get someone to contribute incredibly precise, easy for noobs, instructions for every type of backtrace/debug. Right now they are really written by experts for experts (IMO). I would backtrace much more frequently if I could follow the instructions on how to do it. Every time I feel like I have to go on IRC and ask 100 questions. If this is the case, maybe pre-build binaries with full debugging symbols should be made available for download (more) easily: both for releases and daily master builds ? Also, a 'howto' on how to do this (on linux, with gdb, on windows, with windbg ?) would be nice to have ? I don't think we have enough people packaging to make pre-built binaries for everyone. Plus, these are huge, my install is 22 gigs with all symbols on, not very good for packaging purposes. Best Regards, Joel - John Smith. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] How Can I Provide More Info For Developers
I'll bring this up at our next conference call and see if there is a possible solution. Best Regards, Joel On Fri, Sep 7, 2012 at 12:48 PM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 9:42 PM, Joel Madero jmadero@gmail.com wrote: Sounds good, but I agree with John that better instructions are needed. I'm working on a new triage page and hopefully in there we can get someone to contribute incredibly precise, easy for noobs, instructions for every type of backtrace/debug. Right now they are really written by experts for experts (IMO). I would backtrace much more frequently if I could follow the instructions on how to do it. Every time I feel like I have to go on IRC and ask 100 questions. I don't think we have enough people packaging to make pre-built binaries for everyone. Plus, these are huge, my install is 22 gigs with all symbols on, not very good for packaging purposes. I guess it all depends on who your target audience is. If you really want end-users (libre office users) to provide backtraces, you really need to make the threshold for doing that as low as possible. I dont think it is reasonable to have end-users compile source code for themselves; especially on windows, where it requires msvc or cygwin to do so. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] How Can I Provide More Info For Developers
This isn't for end-users, it's for QA team..and it's our job to do as much as possible to help the developers. I know when I'm doing the development side I appreciate whatever previous info users and QA can provide. It's maximizing the efficiency of our abilitieslimited # of developers means we should be using their time wisely, not running backtraces that someone with 1/10th of their computer programming skills could manage just fine. Best Regards, Joel On Fri, Sep 7, 2012 at 12:56 PM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 9:49 PM, Joel Madero jmadero@gmail.com wrote: I'll bring this up at our next conference call and see if there is a possible solution. Best Regards, Joel May I humbly note that I personally feel that developers should be able to produce their own backtraces, given a solid reproducible test-case in the bug report ? Perhaps effort would be better spend on: 1.) teaching end-users how to provide a reproducible test case in a bug report 2.) teaching devs on how to produce backtraces instead of: 1.) teaching end-users how to install symbol binaries and backtrace them on their platform ? Just my 2$ - John Smith. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-qa] Please Triage These (Bugs from 2011)
There are 12 bugs from 2011 that haven't been triaged. I think they have been kind of ignored because they require certain things (such as Mac or UX input or advanced computer understanding :) ). Could someone(s) please get these done, then at least we're up to 2012 :) If you see one or more that you think you can deal with, please do it and send a reply so we know it's done. Thanks everyone ID▲https://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=bug_id%20DESCquery_based_on= Comphttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=component%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Sev▲https://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=bug_severity%20DESC%2Cpriority%2Cbug_idquery_based_on= Pri▲https://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=priority%20DESC%2Cbug_severity%2Cbug_idquery_based_on= OShttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=op_sys%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Assigneehttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=assigned_to%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Statushttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=bug_status%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Resolutionhttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=resolution%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Summaryhttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=short_desc%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= Changedhttps://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMEDchfieldto=2011-12-31list_id=124162product=LibreOfficequery_format=advancedorder=changeddate%2Cbug_severity%2Cpriority%2Cbug_idquery_based_on= 42673 https://bugs.freedesktop.org/show_bug.cgi?id=42673SpreadshmajlowWind libreoffice-b...@lists.free...unco---With disconnected network printers, Calc hangs opening some files waiting on the Windows print spoolerhttps://bugs.freedesktop.org/show_bug.cgi?id=42673 2011-11-0741987 https://bugs.freedesktop.org/show_bug.cgi?id=41987Libreoff normediummaclibreoffice-b...@lists.free...unco---LibreOffice hangs when Save As... tries to re-mount previously used, but now inaccessible network volumes https://bugs.freedesktop.org/show_bug.cgi?id=41987 2011-10-1942118 https://bugs.freedesktop.org/show_bug.cgi?id=42118BASICnor mediumlinulibreoffice-b...@lists.free...unco---Macro editor lacks the standard window controls -- Linux Unity window manager specifichttps://bugs.freedesktop.org/show_bug.cgi?id=42118 2011-11-1743185 https://bugs.freedesktop.org/show_bug.cgi?id=43185Libreoff normediumwindlibreoffice-b...@lists.free...unco---Font Replacement According Replacement Table (Option) does not Work as Expectedhttps://bugs.freedesktop.org/show_bug.cgi?id=43185 2011-11-2343198 https://bugs.freedesktop.org/show_bug.cgi?id=43198Libreoff normediumlinulibreoffice-b...@lists.free...unco---LibreOffice is opened when WebKitGtk is used with installed LibreOffice Mozilla pluginhttps://bugs.freedesktop.org/show_bug.cgi?id=43198 2011-11-2343255 https://bugs.freedesktop.org/show_bug.cgi?id=43255Drawing normediumwindlibreoffice-b...@lists.free...unco---FILEOPEN: MinGW impossible for particular .SVGshttps://bugs.freedesktop.org/show_bug.cgi?id=43255 2011-11-2643449 https://bugs.freedesktop.org/show_bug.cgi?id=43449Document normediumalllibreoffice-b...@lists.free...unco---WIKIHELP image size should be in pixel, or else trash resizinghttps://bugs.freedesktop.org/show_bug.cgi?id=43449 2011-12-0143450 https://bugs.freedesktop.org/show_bug.cgi?id=43450Document normediumalllibreoffice-b...@lists.free...unco---WIKIHELP table-styled list consistency https://bugs.freedesktop.org/show_bug.cgi?id=434502011-12-01 43471 https://bugs.freedesktop.org/show_bug.cgi?id=43471Libreoffminmedium linulibreoffice-b...@lists.free...unco---unable to import gtk library from libreoffice's embedded python on RHEL6.1https://bugs.freedesktop.org/show_bug.cgi?id=43471 2011-12-0242075 https://bugs.freedesktop.org/show_bug.cgi?id=42075UIenh mediumwindlibreoffice-b...@lists.free...unco---Add a scan-button to the select scanner-dialog https://bugs.freedesktop.org/show_bug.cgi?id=42075 2011-10-2043174 https://bugs.freedesktop.org/show_bug.cgi?id=43174Chartenh
Re: [Libreoffice-qa] Triage Project Update
Hi Nino, That's the beauty of our project, everyone's opinion is respected :) I'll try to avoid adding any work to website team and see what method works best to get these triaged and organized best. As of now, google doc + fdo seems to be doing the trick :) Ultimately might just make a macro to auto sort them once every other week to keep the google doc updated until the project is done (ie. getting all bugs 30 days old triaged so we can try to stick with a goal of triaging withing 30 days for new bugs). Thanks for all the valuable input. Best Regards, Joel On Tue, Sep 4, 2012 at 3:07 PM, Nino Novak nn.l...@kflog.org wrote: Am 04.09.2012 23:05 schrieb Joel Madero: I agree that FDO has some benefits but the limitation is really that each user is needed to query every time, the possibility of overlap is great, and no one is really responsible for an individual bug until the query is made and someone takes the time to look into it. I'm not sure if others would agree but it seems like having a group of 50 or so and being able to just do those at your convenience makes people more likely to help and feel like their is an end in sight for their portion. This is vs. just seeing a never ending list from FDO or even having to teach new users (or even not new users) exactly what to search for every time with FDO. As for me (a rather unexperienced QA Newbie), I've chosen a somewhat different approach: I've first created two custom searches, 1) all recent bugs (reported within the last two days) for curiosity (just to see what people report recently) 2) all UNCONFIRMED bugs from the last 14 days From query 2 I picked a couple of bugs every couple of days to reproduce/confirm/assign/close/whatever seemed appropriate. That's just to show a slightly different approach, which is rather simple and can be handled perfectly within bugzilla itself without any external tool. Ok, the only problem was, that when a person starts reproducing a bug, it can happen, that another triager just starts with the very same bug at the same time. So some kind of lock signal was the only missing thing to prevent duplication of work. However, this situation did not happen a single time during my self-chosen BugReviewWeek ;-) Another advantage: By the above process nobody (virtually) blocks 50 bugs for a longer time period. Bugzilla queries are very adequate at every time, as all works with live data. Similar to how developers assign themselves bugs and then can just go look at their own bugs (My Bugs) it would be nice to have this ability for QA triagers but have it somewhat automated since it's just triaging, not programming. In the long run (once we're through the back log of 650+ that are really old), it would be amazing if we had a team of QA staff that signed up to have bugs auto assigned to them for triaging. We have the libreoffice-bugs@fdo mailing list, which contains (nearly?) every new bug. Could we use it somehow for this purpose? E.g. by replying to a bug or forwarding it to the qa list or some such? (Just thoughts, nothing concrete) What I imagine: QA triagers sign up for components they are willing to triage and their max load New bug is reported, if the bug has a component listed the bug gets auto assigned for triaging purposes according to some rule(s) Personally, I prefer not to sign up for a special component but to pick a recent bug which kind of attracts me spontanously. But there might be other opinions/preferences/arguments/approaches. For now the google docs works, FDO does not as it is now but I'll discuss this further with Bjoern, Petr Rainer to see if we can come up with something more functional than the chaos that is FDO :) Or maybe I'm just not familiar enough with FDO to really feel comfortable myself with it, this is more likely than not true :) :-) I like your initiative. Please don't feel discouraged by my comments, I just wanted to add a slightly different view. If people like your approach, that's great! It does not contradict to mine (IMHO), as it's rather obvious if a bug has been triaged or not. So we can all work together towards our common goal. Regards, Nino ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] How Can I Provide More Info For Developers
Hi All, Came across this bug FDO#45570 and I've already nominated as a most annoying bug but I think that devs might appreciate me getting some kind of a log or something together for the crash. What type of log should I create and how do I go about doing this (basic steps, my knowledge of terminology is still in the first stages :) ). Thanks everyone Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How Can I Provide More Info For Developers
I don't see that helping much, as the developer who takes this one can quickly do this themselves. A working doc only takes 2 seconds to make. Best Regards, Joel On Fri, Sep 7, 2012 at 9:35 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 6:11 PM, Joel Madero jmadero@gmail.com wrote: Hi All, Came across this bug FDO#45570 and I've already nominated as a most annoying bug but I think that devs might appreciate me getting some kind of a log or something together for the crash. What type of log should I create and how do I go about doing this (basic steps, my knowledge of terminology is still in the first stages :) ). Thanks everyone Best Regards, Joel Just some random thoughts here: What happens when you create a 'working document', thats been opened and saved in Msoffice or OpenOffice, and then try to open that saved doc in LibreOffice ? Does the issue still appear ? Also, would it be helpful to attach such a document to the bug report for troubleshooting purposes ? - John Smith. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How Can I Provide More Info For Developers
Wrong Bug, dammit, my bad. Here is the proper one, attachment is there and functioning, I had 5 open FDO tabs in FF and picked the wrong one. https://bugs.freedesktop.org/show_bug.cgi?id=48569 My apologies Joel On Fri, Sep 7, 2012 at 9:57 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 6:38 PM, Joel Madero jmadero@gmail.com wrote: I don't see that helping much, as the developer who takes this one can quickly do this themselves. A working doc only takes 2 seconds to make. Best Regards, Joel Another random thought then: Is there a way to reproduce the issue that doesnt require the installation of Lotus Domino ? - John Smith. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How Can I Provide More Info For Developers
On Fri, Sep 7, 2012 at 10:44 AM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com wrote: Hi John, You can always make it easier for a developer to solve - and the easier it is, the more likely it is to get solved quickly. Ways to do that are: * getting a stack-trace with full debugging symbols * running valgrind with full debugging symbols and attaching a trace. Sounds good, but I agree with John that better instructions are needed. I'm working on a new triage page and hopefully in there we can get someone to contribute incredibly precise, easy for noobs, instructions for every type of backtrace/debug. Right now they are really written by experts for experts (IMO). I would backtrace much more frequently if I could follow the instructions on how to do it. Every time I feel like I have to go on IRC and ask 100 questions. If this is the case, maybe pre-build binaries with full debugging symbols should be made available for download (more) easily: both for releases and daily master builds ? Also, a 'howto' on how to do this (on linux, with gdb, on windows, with windbg ?) would be nice to have ? I don't think we have enough people packaging to make pre-built binaries for everyone. Plus, these are huge, my install is 22 gigs with all symbols on, not very good for packaging purposes. Best Regards, Joel - John Smith. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How Can I Provide More Info For Developers
This isn't for end-users, it's for QA team..and it's our job to do as much as possible to help the developers. I know when I'm doing the development side I appreciate whatever previous info users and QA can provide. It's maximizing the efficiency of our abilitieslimited # of developers means we should be using their time wisely, not running backtraces that someone with 1/10th of their computer programming skills could manage just fine. Best Regards, Joel On Fri, Sep 7, 2012 at 12:56 PM, John Smith lbalba...@gmail.com wrote: On Fri, Sep 7, 2012 at 9:49 PM, Joel Madero jmadero@gmail.com wrote: I'll bring this up at our next conference call and see if there is a possible solution. Best Regards, Joel May I humbly note that I personally feel that developers should be able to produce their own backtraces, given a solid reproducible test-case in the bug report ? Perhaps effort would be better spend on: 1.) teaching end-users how to provide a reproducible test case in a bug report 2.) teaching devs on how to produce backtraces instead of: 1.) teaching end-users how to install symbol binaries and backtrace them on their platform ? Just my 2$ - John Smith. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-ux-advise] [PROPOSED] Changes to General Options FDO#40656
http://opengrok.libreoffice.org/xref/core/cui/source/options/optjava.cxx#93SvxJavaOptionsPage http://opengrok.libreoffice.org/s?refs=SvxJavaOptionsPageproject=core::SvxJavaOptionsPage http://opengrok.libreoffice.org/s?refs=SvxJavaOptionsPageproject=core( On Fri, Sep 7, 2012 at 7:28 AM, Caolán McNamara caol...@redhat.com wrote: On Thu, 2012-08-09 at 14:07 -0700, Joel Madero wrote: Hi All, This is in response to FDO#40656: https://bugs.freedesktop.org/show_bug.cgi?id=40656 In order to accomplish this I need to move some things around. I did the visual changes - didn't do any of the functional changes yet, nor did I ensure that spacing and what not is perfect. Looking for general input before I put the time that is needed into this. Thanks all. Seems sane to me (seeing as I pushed the first patch in this process, I thought I'd better go back and have a look at the final picture). Though maybe (more work) Measurements would be better at the top, the rest of the general options are sort of obscure. C. Shouldn't be a problem at all. As for your other comment about changing name of help, how do I go about doing this? I've never messed with the help stuff before so I'll need a bit of guidance. Also now that Java page has changed to Advanced, does it make sense to have files named optjavacxx,src, etc...? Should I consider changing the names to something more sane since it's not just java? Also the page name is now not really complete (svxJavaOptionsPage). If you give me some guidance I'll move forward on that, until then I'll get at least the first part of the measurements moved. I'm not sure if I'm going to redo the measurements completely (ie. combine each components measurement into one) or just have the option in general control all of them as is (ie. separately). I'll figure that out as I go along. Thanks for pushing that one out, it'll be nice when this change is done :) Best Regards, Joel ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
Re: Triage Project Update
Hi All, I have done a complete update of the google document, this being said, if you named a sheet to your name, it's gone. Noel pointed out that a lot of the bugs on the sheet were already triaged so I just started from scratch. I'm still hoping the web team can help us move this away from google docs and get it automated a bit but for now, it is what it is. Please go back to the link: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=75 Choose a sheet, and continue doing the great work. Here are the #'s as they stand now: *We are down to 893 bugs that are = 30 days in unconfirmed status. If we can get just a few more people to dedicate a bit of time we can be caught up for our back log and hopefully set a goal (I think all bugs should be triaged in 30 days, but if that's not possible most should be 60).* * * Thanks Noel for pointing out that they were really out of date, just shows how much time people are spending getting this project done. I'll update every 1-2 weeks, during which time I will set the sheet as private so it'll boot you out if you're working on it (sorry, no other way really). Lastly, there are certain sections which only have a few bugs, if someone(s) can take these and just get them off the list that would be great. These sections are: Chart Contrib Documentation Extensions Filters Storage Formula Editor Framework Graphics Stack Linguistics Localization Printing PDF Export SDK WWW Some of these only have 1-5 bugs to triage. It'll make my job easier in a couple weeks if these are dealt with -- otherwise I have to filter out and create the sheets and what not. Thanks again everyone, great work Best Regards, Joel On Wed, Aug 29, 2012 at 10:10 PM, Joel Madero jmadero@gmail.com wrote: Math was off for averages ;) still doing a good job everyone. On Aug 29, 2012 9:40 PM, Joel Madero jmadero@gmail.com wrote: Well we're 24 days into the project and there is mostly good news (although some bad news is there as well). So bad news first. Overall we're down only about 200 or so bugs in 24 days. This takes into account the new bugs since 8/5 that have been filed which has been a lot. This is also good news as it means our user base is growing and taking an interest in reporting. On to the good news: Start Date: 8/5/2012 Days Since Start: 24 Bugs Triaged: 568! (way to go everyone, I know a lot of these are in NEEDINFO statusbut it's still means we touched the bug which is the goal, letting our users know we care :) ) Some other good news: Average Length of Time Since Last Action: 66 days (prior to project start # was 89) Median Length of Time Since Last Action: 56 days (prior to project start # was 85) These are all incredibly good. Congrats to everyone working on this project, I think we can meet some reasonable goals by the end of the year and work on starting new projects once this back log is finally taken care of. Best Regards, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Triage Project Update
Basically it would be really nice to be able to group and assign bugs the way that the document does. I think bugs are much more manageable this way and we've seen a relative spike in QA triaging activity since starting the process this way. Not sure if you looked at the document but it's basically manual everything, I download FDO bugs to Calc, group them based on Component, then manually copy and paste into groupings of no more than 50. It would be incredibly nice to have the list updated automatically based on FDO, group the bugs based on component and then group each of those to a max of 50 bugs per group. If each group of 50 could then be assigned to a user it would be easy for members of QA to get involved with this project and get this back log taken care of. I'm not sure if this is possible or incredibly time consuming (if it is, probably not worth it). It would be even better if we, as the QA team could do a custom group and then it could assign us bugs based on that. For instance, I'm a QA member and I want to do 20 bugs that are either Writer, Calc or Presentation, and I want the oldest bugs (in terms of those that have been left UNCONFIRMED for the longest period of time). It could then give me the list and allow me to assign myself to the group, and thus prevent other QA members from getting those bugs in their list when they do a custom search. Sorry I felt like that was a bit of rambling, let me know if you need it clarified, I can hardly understand it myself ;) Best Regards, Joel On Tue, Sep 4, 2012 at 12:34 PM, Nino Novak nn.l...@kflog.org wrote: Hi Joel, Am 04.09.2012 19:18 schrieb Joel Madero: I have done a complete update of the google document, this being said, if you named a sheet to your name, it's gone. Noel pointed out that a lot of the bugs on the sheet were already triaged so I just started from scratch. I'm still hoping the web team can help us move this away from google docs and get it automated a bit but for now, it is what it is. I'm not sure to understand what you want to have automated, could you elaborate just a little bit (or - if you have done so already - point me to the archived mail)? Thanks, Nino ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[PATCH]Changes to Tools -Options Tree
Hi All,
This is the first of multiple patches to address fdo#40656 (moving
measurements to the LibreOffice General tab). In this patch:
1. Changed Java to Advanced
2. Shrunk Java stuff to about half of tab
3. Moved experimental options to Advanced tab below Java section
I didn't do any renaming (not sure what if anything needs renamed), just
did a move and verified that the options work.
Please send me any comments about needed fixes, this is my most
advanced change to date so I can be relatively sure it needs things
changed. Thanks in advance everyone.
Best Regards,
Joel
From d801a8fb3ed92db50073138b5f6a19c354113946 Mon Sep 17 00:00:00 2001
From: Joel Madero jmadero@gmail.com
Date: Tue, 4 Sep 2012 07:03:03 -0700
Subject: [PATCH] Moving experimental section to java, changing section name
First of a few patches to move measurements to the general section in the
LibreOffice main tree. This patch moves experimental section to Java
and then changes the name Java to Advanced. The space which was cleared
by moving experimental section will be used for measurements in the future.
modified: cui/source/options/optgdlg.cxx
modified: cui/source/options/optgdlg.hrc
modified: cui/source/options/optgdlg.hxx
modified: cui/source/options/optgdlg.src
modified: cui/source/options/optjava.cxx
modified: cui/source/options/optjava.hrc
modified: cui/source/options/optjava.hxx
modified: cui/source/options/optjava.src
modified: cui/source/options/treeopt.src
Change-Id: I20073296ce81aace4b041ef5cb27e4313637a58d
---
cui/source/options/optgdlg.cxx | 29 -
cui/source/options/optgdlg.hrc |3 ---
cui/source/options/optgdlg.hxx |4
cui/source/options/optgdlg.src | 18 --
cui/source/options/optjava.cxx | 33 -
cui/source/options/optjava.hrc | 10 ++
cui/source/options/optjava.hxx |4
cui/source/options/optjava.src | 22 --
cui/source/options/treeopt.src |2 +-
9 files changed, 71 insertions(+), 54 deletions(-)
diff --git a/cui/source/options/optgdlg.cxx b/cui/source/options/optgdlg.cxx
index 5f7015b..3ff3b3c 100644
--- a/cui/source/options/optgdlg.cxx
+++ b/cui/source/options/optgdlg.cxx
@@ -212,10 +212,7 @@ OfaMiscTabPage::OfaMiscTabPage(Window* pParent, const SfxItemSet rSet ) :
aTwoFigureFL( this, CUI_RES( FL_TWOFIGURE ) ),
aInterpretFT( this, CUI_RES( FT_INTERPRET ) ),
aYearValueField ( this, CUI_RES( NF_YEARVALUE ) ),
-aToYearFT ( this, CUI_RES( FT_TOYEAR ) ),
-aExperimentalFL ( this, CUI_RES( FL_EXPERIMENTAL ) ),
-aExperimentalCB ( this, CUI_RES( CB_EXPERIMENTAL ) ),
-aMacroRecorderCB( this, CUI_RES( CB_MACRORECORDER ) )
+aToYearFT ( this, CUI_RES( FT_TOYEAR ) )
{
FreeResource();
@@ -245,7 +242,7 @@ OfaMiscTabPage::OfaMiscTabPage(Window* pParent, const SfxItemSet rSet ) :
Window* pWins[] =
{
aPrintDlgFL, aPrintDlgCB, aDocStatusFL, aDocStatusCB, aSaveAlwaysCB,
-aTwoFigureFL, aInterpretFT, aYearValueField, aToYearFT, aExperimentalFL, aExperimentalCB, aMacroRecorderCB
+aTwoFigureFL, aInterpretFT, aYearValueField, aToYearFT
};
Window** pCurrent = pWins;
const sal_Int32 nCount = SAL_N_ELEMENTS( pWins );
@@ -266,7 +263,7 @@ OfaMiscTabPage::OfaMiscTabPage(Window* pParent, const SfxItemSet rSet ) :
Window* pWins[] =
{
aPrintDlgFL, aPrintDlgCB, aDocStatusFL, aDocStatusCB, aSaveAlwaysCB,
-aTwoFigureFL, aInterpretFT, aYearValueField, aToYearFT, aExperimentalFL, aExperimentalCB, aMacroRecorderCB
+aTwoFigureFL, aInterpretFT, aYearValueField, aToYearFT
};
Window** pCurrent = pWins;
const sal_Int32 nCount = SAL_N_ELEMENTS( pWins );
@@ -292,7 +289,7 @@ OfaMiscTabPage::OfaMiscTabPage(Window* pParent, const SfxItemSet rSet ) :
Window* pWins[] =
{
aDocStatusFL, aDocStatusCB, aSaveAlwaysCB, aTwoFigureFL,
-aInterpretFT, aYearValueField, aToYearFT, aExperimentalFL, aExperimentalCB, aMacroRecorderCB
+aInterpretFT, aYearValueField, aToYearFT
};
Window** pCurrent = pWins;
const sal_Int32 nCount = SAL_N_ELEMENTS( pWins );
@@ -403,20 +400,6 @@ sal_Bool OfaMiscTabPage::FillItemSet( SfxItemSet rSet )
bModified = sal_True;
}
-if ( aExperimentalCB.IsChecked() != aExperimentalCB.GetSavedValue() )
-{
-SvtMiscOptions aMiscOpt;
-aMiscOpt.SetExperimentalMode( aExperimentalCB.IsChecked() );
-bModified = sal_True;
-}
-
-if ( aMacroRecorderCB.IsChecked() != aMacroRecorderCB.GetSavedValue() )
-{
-SvtMiscOptions aMiscOpt;
-aMiscOpt.SetMacroRecorderMode( aMacroRecorderCB.IsChecked() );
-bModified = sal_True;
-}
-
const SfxUInt16Item* pUInt16Item
Re: Triage Project Update
I agree that FDO has some benefits but the limitation is really that each user is needed to query every time, the possibility of overlap is great, and no one is really responsible for an individual bug until the query is made and someone takes the time to look into it. I'm not sure if others would agree but it seems like having a group of 50 or so and being able to just do those at your convenience makes people more likely to help and feel like their is an end in sight for their portion. This is vs. just seeing a never ending list from FDO or even having to teach new users (or even not new users) exactly what to search for every time with FDO. Similar to how developers assign themselves bugs and then can just go look at their own bugs (My Bugs) it would be nice to have this ability for QA triagers but have it somewhat automated since it's just triaging, not programming. In the long run (once we're through the back log of 650+ that are really old), it would be amazing if we had a team of QA staff that signed up to have bugs auto assigned to them for triaging. What I imagine: QA triagers sign up for components they are willing to triage and their max load New bug is reported, if the bug has a component listed the bug gets auto assigned for triaging purposes according to some rule(s) For now the google docs works, FDO does not as it is now but I'll discuss this further with Bjoern, Petr Rainer to see if we can come up with something more functional than the chaos that is FDO :) Or maybe I'm just not familiar enough with FDO to really feel comfortable myself with it, this is more likely than not true :) Best Regards, Joel On 09/04/2012 01:53 PM, Nino Novak wrote: Am 04.09.2012 21:52 schrieb Joel Madero: Basically it would be really nice to be able to group and assign bugs the way that the document does. I think bugs are much more manageable this way and we've seen a relative spike in QA triaging activity since starting the process this way. Ok, I see: it makes the process a bit more transparent/obvious. And thus is more pleasant and possibly invites more contributors. Not sure if you looked at the document but it's basically manual everything, I looked at it but could not see what is so special with it... I'll try to compare (please comment if you find this inadequate): I download FDO bugs to Calc, group them based on Component, can be done by a bugzilla query then manually copy and paste into groupings of no more than 50. (is this really that important? for crowdsourcing, it might suffice to do coordination by e-mail) It would be incredibly nice to have the list updated automatically based on FDO, group the bugs based on component and then group each of those to a max of 50 bugs per group. if it's a live query, it's current every time you run it If each group of 50 could then be assigned to a user it would be easy for members of QA to get involved with this project and get this back log taken care of. Ok, I don't know how to build such chunks of 50 bugs using a query - but - is it so important? Couldn't we use e.g. time periods (weeks or months) to group the bugs? Then the number would not be constant but who cares? I'm not sure if this is possible or incredibly time consuming (if it is, probably not worth it). I don't know either but wanted to understand what exactly is needed and if it's possible to find (slightly) different solutions which can be implemented more quickly (or are already existing but not thought of) It would be even better if we, as the QA team could do a custom group and then it could assign us bugs based on that. For instance, I'm a QA member and I want to do 20 bugs that are either Writer, Calc or Presentation, and I want the oldest bugs (in terms of those that have been left UNCONFIRMED for the longest period of time). It could then give me the list and allow me to assign myself to the group, and thus prevent other QA members from getting those bugs in their list when they do a custom search. There is a QA Contact field which has not been used extensively (at least according to my recent search). Could it be used for this purpose? (Rainer? Björn?) Sorry I felt like that was a bit of rambling, let me know if you need it clarified, I can hardly understand it myself ;) So let me be a bit of a devil's advocate, aka clarification helper :-) (I've been working in a project as QA helper years ago for several months, they used excel sheets, so I think I understand the need to master the bugs, and to make the processes transparent and obvious. And thus lower the entry barrier for noobs, too btw.) So my present guess would be: - asking for a web tool is ok but - if there's no better tools ATM, let's stay with google docs for the time coming - but let's also try to use bugzilla itself as much as possible - we have also the wiki, but I do not see much advantage of using it compared to a google spreadsheet
Re: [Libreoffice-qa] Triage Project Update
I agree that FDO has some benefits but the limitation is really that each user is needed to query every time, the possibility of overlap is great, and no one is really responsible for an individual bug until the query is made and someone takes the time to look into it. I'm not sure if others would agree but it seems like having a group of 50 or so and being able to just do those at your convenience makes people more likely to help and feel like their is an end in sight for their portion. This is vs. just seeing a never ending list from FDO or even having to teach new users (or even not new users) exactly what to search for every time with FDO. Similar to how developers assign themselves bugs and then can just go look at their own bugs (My Bugs) it would be nice to have this ability for QA triagers but have it somewhat automated since it's just triaging, not programming. In the long run (once we're through the back log of 650+ that are really old), it would be amazing if we had a team of QA staff that signed up to have bugs auto assigned to them for triaging. What I imagine: QA triagers sign up for components they are willing to triage and their max load New bug is reported, if the bug has a component listed the bug gets auto assigned for triaging purposes according to some rule(s) For now the google docs works, FDO does not as it is now but I'll discuss this further with Bjoern, Petr Rainer to see if we can come up with something more functional than the chaos that is FDO :) Or maybe I'm just not familiar enough with FDO to really feel comfortable myself with it, this is more likely than not true :) Best Regards, Joel On 09/04/2012 01:53 PM, Nino Novak wrote: Am 04.09.2012 21:52 schrieb Joel Madero: Basically it would be really nice to be able to group and assign bugs the way that the document does. I think bugs are much more manageable this way and we've seen a relative spike in QA triaging activity since starting the process this way. Ok, I see: it makes the process a bit more transparent/obvious. And thus is more pleasant and possibly invites more contributors. Not sure if you looked at the document but it's basically manual everything, I looked at it but could not see what is so special with it... I'll try to compare (please comment if you find this inadequate): I download FDO bugs to Calc, group them based on Component, can be done by a bugzilla query then manually copy and paste into groupings of no more than 50. (is this really that important? for crowdsourcing, it might suffice to do coordination by e-mail) It would be incredibly nice to have the list updated automatically based on FDO, group the bugs based on component and then group each of those to a max of 50 bugs per group. if it's a live query, it's current every time you run it If each group of 50 could then be assigned to a user it would be easy for members of QA to get involved with this project and get this back log taken care of. Ok, I don't know how to build such chunks of 50 bugs using a query - but - is it so important? Couldn't we use e.g. time periods (weeks or months) to group the bugs? Then the number would not be constant but who cares? I'm not sure if this is possible or incredibly time consuming (if it is, probably not worth it). I don't know either but wanted to understand what exactly is needed and if it's possible to find (slightly) different solutions which can be implemented more quickly (or are already existing but not thought of) It would be even better if we, as the QA team could do a custom group and then it could assign us bugs based on that. For instance, I'm a QA member and I want to do 20 bugs that are either Writer, Calc or Presentation, and I want the oldest bugs (in terms of those that have been left UNCONFIRMED for the longest period of time). It could then give me the list and allow me to assign myself to the group, and thus prevent other QA members from getting those bugs in their list when they do a custom search. There is a QA Contact field which has not been used extensively (at least according to my recent search). Could it be used for this purpose? (Rainer? Björn?) Sorry I felt like that was a bit of rambling, let me know if you need it clarified, I can hardly understand it myself ;) So let me be a bit of a devil's advocate, aka clarification helper :-) (I've been working in a project as QA helper years ago for several months, they used excel sheets, so I think I understand the need to master the bugs, and to make the processes transparent and obvious. And thus lower the entry barrier for noobs, too btw.) So my present guess would be: - asking for a web tool is ok but - if there's no better tools ATM, let's stay with google docs for the time coming - but let's also try to use bugzilla itself as much as possible - we have also the wiki, but I do not see much advantage of using it compared to a google spreadsheet
CTL Default
Hi All, I received a personal email today from a user saying that for them CTL is enabled by default for 3.6. Did I miss something? Is it enabled by default for some locales? I want to give him the right information, thanks all. Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: CTL Default
Right now is it associated with locale or with language selection (or are these the same, I honestly don't use these features at all)? If it's not associated with language selection maybe we should make it so. Otherwise, maybe putting the option in a more obvious location is a good idea. I can do this just need some guidance on where to place it. I'll reply to the user, I'm not sure why he sent me a personal email about this instead of sending it out to the mailing list or even commenting on fdo. Best Regards, Joel On 09/02/2012 10:57 AM, Rainer Bielefeld wrote: Nathan Wells schrieb: Yes, some locales have CTL enabled as the default. Hi, yes, of course. The question is whether e-mail writer has had activated a Locale where that's not required. Where not, CTL (Complex Text Layout) should be disabled. It offers an additional Dialog for CTL fonts and lot's of other frills users really only need for CTL, so I think it should be disabled for languages where it is not required. Best regards Rainer ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] Proposed HARDHACK
On 08/29/2012 10:38 PM, Rainer Bielefeld wrote: Joel Madero schrieb: We should come up with a better method of tracking vs. each of us making our own list. Hi Joel, yes, indeed! If everyone wants, they can email me and I will keep a combined list that we can discuss during our conference call. You can just email me directly Proposed HARDHACK, I would prefer a more public collection. I will (today) start another thread here where everybody can do a proposal for Bug Numbers, Queries filtering candidates or similar, so that everybody can observe the collection process and do his own thoughts. But it would be really great if you could collect the proposals few days before the next call (then we stop the collection, later proposals will be for the next call) so that we have a common and clear base for discussion and decision. BTW: I still wonder whether it would be possible to have a LibO spreadsheet on a server what can be edited by all interested people (here for the collection of data), see [tdf-discuss] Open document from server Best regards Rainer Hi Rainer, I asked for the website team to look into this for the bug triaging process as well -- google docs is messy..-- as of yet they haven't responded so I'm thinking it's not easy. Google docs IS working for the triaging project it's just not ideal. It's a possibility until we find something better for HARDHACKS. Another less than ideal solution is setting a whiteboard status of PROPOSEDHARDHACK, then we in the QA team can query these out a couple nights before the conference call and write our own thoughts down. I actually think I prefer google docs as we already have too many whiteboard status'. Ultimately, our own spreadsheet on our own server would be ideal. Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Proposed HARDHACK
I just came up with a potential idea! What about making a custom search on FDO and just share it with each other? I use a couple custom searches right now, making them is easy, transparent and shared. Just a thought Best Regards, Joel On Thu, Aug 30, 2012 at 7:05 AM, Joel Madero jmadero@gmail.com wrote: On 08/29/2012 10:38 PM, Rainer Bielefeld wrote: Joel Madero schrieb: We should come up with a better method of tracking vs. each of us making our own list. Hi Joel, yes, indeed! If everyone wants, they can email me and I will keep a combined list that we can discuss during our conference call. You can just email me directly Proposed HARDHACK, I would prefer a more public collection. I will (today) start another thread here where everybody can do a proposal for Bug Numbers, Queries filtering candidates or similar, so that everybody can observe the collection process and do his own thoughts. But it would be really great if you could collect the proposals few days before the next call (then we stop the collection, later proposals will be for the next call) so that we have a common and clear base for discussion and decision. BTW: I still wonder whether it would be possible to have a LibO spreadsheet on a server what can be edited by all interested people (here for the collection of data), see [tdf-discuss] Open document from server Best regards Rainer Hi Rainer, I asked for the website team to look into this for the bug triaging process as well -- google docs is messy..-- as of yet they haven't responded so I'm thinking it's not easy. Google docs IS working for the triaging project it's just not ideal. It's a possibility until we find something better for HARDHACKS. Another less than ideal solution is setting a whiteboard status of PROPOSEDHARDHACK, then we in the QA team can query these out a couple nights before the conference call and write our own thoughts down. I actually think I prefer google docs as we already have too many whiteboard status'. Ultimately, our own spreadsheet on our own server would be ideal. Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Triage Project Update
Well we're 24 days into the project and there is mostly good news (although some bad news is there as well). So bad news first. Overall we're down only about 200 or so bugs in 24 days. This takes into account the new bugs since 8/5 that have been filed which has been a lot. This is also good news as it means our user base is growing and taking an interest in reporting. On to the good news: Start Date: 8/5/2012 Days Since Start: 24 Bugs Triaged: 568! (way to go everyone, I know a lot of these are in NEEDINFO statusbut it's still means we touched the bug which is the goal, letting our users know we care :) ) Some other good news: Average Length of Time Since Last Action: 66 days (prior to project start # was 89) Median Length of Time Since Last Action: 56 days (prior to project start # was 85) These are all incredibly good. Congrats to everyone working on this project, I think we can meet some reasonable goals by the end of the year and work on starting new projects once this back log is finally taken care of. Best Regards, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Triage Project Update
Math was off for averages ;) still doing a good job everyone. On Aug 29, 2012 9:40 PM, Joel Madero jmadero@gmail.com wrote: Well we're 24 days into the project and there is mostly good news (although some bad news is there as well). So bad news first. Overall we're down only about 200 or so bugs in 24 days. This takes into account the new bugs since 8/5 that have been filed which has been a lot. This is also good news as it means our user base is growing and taking an interest in reporting. On to the good news: Start Date: 8/5/2012 Days Since Start: 24 Bugs Triaged: 568! (way to go everyone, I know a lot of these are in NEEDINFO statusbut it's still means we touched the bug which is the goal, letting our users know we care :) ) Some other good news: Average Length of Time Since Last Action: 66 days (prior to project start # was 89) Median Length of Time Since Last Action: 56 days (prior to project start # was 85) These are all incredibly good. Congrats to everyone working on this project, I think we can meet some reasonable goals by the end of the year and work on starting new projects once this back log is finally taken care of. Best Regards, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-qa] Proposed HARDHACK
https://bugs.freedesktop.org/show_bug.cgi?id=47283 We should come up with a better method of tracking vs. each of us making our own list. If everyone wants, they can email me and I will keep a combined list that we can discuss during our conference call. You can just email me directly Proposed HARDHACK, I will update the list and 2-3 days before our meeting I'll get the document up for everyone to see. Sooner or later a voting method would be nice :) Let me know what you all think Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Triage Project Update
Well we're 24 days into the project and there is mostly good news (although some bad news is there as well). So bad news first. Overall we're down only about 200 or so bugs in 24 days. This takes into account the new bugs since 8/5 that have been filed which has been a lot. This is also good news as it means our user base is growing and taking an interest in reporting. On to the good news: Start Date: 8/5/2012 Days Since Start: 24 Bugs Triaged: 568! (way to go everyone, I know a lot of these are in NEEDINFO statusbut it's still means we touched the bug which is the goal, letting our users know we care :) ) Some other good news: Average Length of Time Since Last Action: 66 days (prior to project start # was 89) Median Length of Time Since Last Action: 56 days (prior to project start # was 85) These are all incredibly good. Congrats to everyone working on this project, I think we can meet some reasonable goals by the end of the year and work on starting new projects once this back log is finally taken care of. Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] NEEDINFO Status
After thinking about it I agree. The message should probably be done on closing the bug as INVALID or adding a new status of PLEASETEST (I am not hugely in favor of this, we already have too many status' IMO). But for more experienced triagers there's no harm in letting the user know on marking it as NEEDINFO that the bug will be auto closed after 30 days. No need to make this a big deal, just for those of us who have been working with LibO for awhile we can add the friendly message. We don't want to get too strict or mechanical for many reasons, two that come to mind is pissing off our user base because we sound like robots and also making it more difficult for new members to get involved. We should try to finalize this before our next conference call so we can move on to more important stuff :) Joel P.S. Also, is there an ongoing agenda for the next conference? On Mon, Aug 27, 2012 at 3:58 AM, Petr Mladek pmla...@suse.cz wrote: Rainer Bielefeld píše v So 25. 08. 2012 v 11:30 +0200: Joel Madero schrieb: when we actually put a bug into NEEDINFO status we put a comment that has a small blurb on our procedure. Something like we have put this bug in NEEDINFO status because we need you to provide.we will leave the bug in this status for 6 months I recommend that we agree to a standard sentence like This bug will be closed after 14 days if requested information will not be provided. Additional information concerning the reasons for this proceeding and how you can reopen this Bug you can find at jttp://...Wiki... , to be inserted by copy /paste from Wiki. I appreciate you carefulness and sense for details. Well, I am still not convinced that we need to warn people before. I understand the point but it has some drawbacks: + reporters might get angry that we force them to answer within 30 days and then do not fix bug several months; and we are not able to fix all 5000 bugs within one month + the standard message is yet another thing that bug triagers should memorize; it makes the process more complicated and harder to learn + it is another message that makes the report longer and harder to read I still thing that the best solution would be to tune the closing message. It has to be short, explanatory, friendly, encouraging. I suggest something like: We would like to solve this bug but nobody has provided the requested information during last 30 days. We can't move forward and close this bug for now. Feel free to reopen it together with the needed details. This can be done automatically, so nobody need to memorize it. Best Regards, Petr ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] NEEDINFO Status
On 08/25/2012 02:30 AM, Rainer Bielefeld wrote: Joel Madero schrieb: when we actually put a bug into NEEDINFO status we put a comment that has a small blurb on our procedure. Something like we have put this bug in NEEDINFO status because we need you to provide.we will leave the bug in this status for 6 months Hi, that's to long. Be sure, the info provider will answer within a week or never. So it's common sense that a bug can be closed after 10-14 days if there is no answer and if it can be expected that it will not be possible to reproduce the bug with acceptable costs without denied info. I use Reminderfox and add a reminder (10 days later) for all Bugs I set to NEEDINFO, after 10 days (or later, workload ...) I close those bugs INVALID if there was no reply. But sometimes there is additional discussion, users try to reproduce and so on and such bugs sink into oblivion. For those bugs Florinan' suggested PLEASETEST-reminder (what has not been accepted) might have had the advantage that a query would have been very easy. I recommend that we agree to a standard sentence like This bug will be closed after 14 days if requested information will not be provided. Additional information concerning the reasons for this proceeding and how you can reopen this Bug you can find at jttp://...Wiki... , to be inserted by copy /paste from Wiki. I strongly agree with Joel's suggestion to have a time limit in the Comment related to NEEDINFO status change. Best regards Rainer Personally I think 14 days is a bit short. Someone goes on vacation for a couple weeks and come back to their bug going from UNCONFIRMED - NEEDINFO - INVALID. I'd be more inclined to say 30 days but if 14 ends up being the number, that's fine. I like the PLEASETEST status but I know that Bjoern had some reservations about adding yet another whiteboard status. What would be the policy if we did this, changing to INVALID after 14 (or whatever # we agree on) days and then add the whiteboard status of PLEASETEST so that we can query it out. Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] NEEDINFO Status
Hi All, More input on this morning's conversation. Maybe an idea would be that when we actually put a bug into NEEDINFO status we put a comment that has a small blurb on our procedure. Something like we have put this bug in NEEDINFO status because we need you to provide.we will leave the bug in this status for 6 months at which time we'll close the bug as INVALID. If your bug is closed as INVALID after 6 months and you still experience it, please attach needed information and reopen the bug as UNCONFIRMED. Just a thought. Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] New Triage Page (In Progress)
This is only in the first phase but I'm aiming to make the triage page more complete, easy to read, and have all the information (at least linked) to effectively triage. Here is the link, feel free to comment, check it out every once in awhile as I'm trying to do updates somewhat regularly: https://wiki.documentfoundation.org/BugTriage_InProgress Of course if you want to help go ahead an edit it but I would like it to be organized well and be pretty uniform where possible. Best Regards, hope everyone has a great weekend Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-ux-advise] fdo#47677
can someone(s) look at this one and either close it and tell the user that we won't be doing this or mark it as NEW if you think that it will be implemented. Not sure if this is what we want to do or not. Thanks all Best Regards, Joel ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
Re: Help Locating Base Code
Thanks for letting me know it's Lionel :) I told Rafael yesterday in the chat that just because I enjoy being angry (actually just enjoy a good challenge) I'll probably assign myself another base bug in the coming weeks and spend 20 hours to fix one line ;) now I know who to bug with every minor question (just kidding!). Best Regards, Joel On Wed, Aug 22, 2012 at 12:16 AM, Jan Holesovsky ke...@suse.cz wrote: Hi Joel, On 2012-08-21 at 11:10 -0700, Joel Madero wrote: Thanks to everyone who helped me along the way. The code actually ended up being in formcomponenthandler.cxx, FormComponentPropertyHandler::impl_browseImage_nothrow. Great to hear; I hope I did not mislead you too much - that was the other occurrence of FILEOPEN_LINK_PREVIEW/CHECKBOX_LINK :-) I think we need to start looking for a database expert, someone who enjoys it and is willing to get into the grit of the crappy code. Any takers ? ;) Oh - database expert, that's Lionel :-) But of course, having more database experts would be great! I'll get the patch done tonight after I clear all the other stuff I was testing with, going to attempt gerritt for the first time. Looking forward to the patch! All the best, Kendy ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Help Locating Base Code
Thanks to everyone who helped me along the way. The code actually ended up being in formcomponenthandler.cxx, FormComponentPropertyHandler::impl_browseImage_nothrow. One simple change and it's good. Many thanks to everyone again, Rafael ended up locating the exact location and helping me see what I was missing from my backtrace, talked me through it in IRC which is always appreciated from us new users. I think we need to start looking for a database expert, someone who enjoys it and is willing to get into the grit of the crappy code. Any takers ? ;) I'll get the patch done tonight after I clear all the other stuff I was testing with, going to attempt gerritt for the first time. Best Regards, Joel On Tue, Aug 21, 2012 at 10:45 AM, Lionel Elie Mamane lio...@mamane.luwrote: On Tue, Aug 21, 2012 at 11:58:15AM +0200, Jan Holesovsky wrote: On 2012-08-20 at 09:53 -0700, Joel Madero wrote: I am still having a hard time locating the relevant code for this bug fdo#53001. I did the backtrace with the dialog open and I didn't see anything useful in there. If someone can help direct me to the relevant code OR if someone is willing to take the bug and fix it, I think it's a 20 minute fix but hours upon hours of trying to find the code has left me a bit frustrated. Having read the bug report, it says that it is a 'Link' in the file dialog. The file dialog is located in the fpicker/ subdir, so (...) I intended to get back to helping Joel after fixing my bug-of-the-day, which took longer than anticipated. Kendy, thanks for helping Joel. Joel, if you have any other question/difficulty, feel free to continue this thread. -- Lionel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[PATCH] fdo#53001:REPORT BUILDER UI: Unlink picture action in Image control file dialog without effect
As always, feel free to comment. Incredibly simple fix but took forever to locate the code. Many thanks to everyone who helped locate it. Best Regards, Joel 0001-fdo-53001-Disabled-unlink-graphics-in-image-control-.patch Description: Binary data ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Unconfirmed Bugs Triaging Update #2
Hi All, Progress is still going for the unconfirmed bugs but we still needs people to actively and aggressively help. If you have some time in the coming weeks take a look at the following document: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E If you can do 1 bug a week that helps, once we get these unconfirmed under control we'll be able to assign a small team to keep up with new bugs but getting caught up is challenging and any and all help is appreciated. Here are the new #'s. Start Date: August 5th, 2012 Starting # of Bugs: 1,472 # of Bugs Today: 1,177* Bugs done: 295 New Bugs Since August 5th: 322 Yes this means that we're actually BEHIND the pace of bugs still ;) But, good news is that our goal in QA isn't to have bugs triaged the day they are posted but instead just not have them sitting for months and months. Best regards to everyone, Joel P.S. I'm going to try to actively recruit a few more people from the #libreoffice channel who are probably knowledgeable to help triage but just never have been asked to participate in LO. Also, I'm updating the triaging wiki, if anyone is available to help please email me directly and we'll coordinate something, looking for both feedback on what should be on the wiki (right now it's pretty bad) as well as people to actually help write it. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Help Locating Base Code
I am still having a hard time locating the relevant code for this bug fdo#53001. I did the backtrace with the dialog open and I didn't see anything useful in there. If someone can help direct me to the relevant code OR if someone is willing to take the bug and fix it, I think it's a 20 minute fix but hours upon hours of trying to find the code has left me a bit frustrated. Best Regards, Joel On Thu, Aug 9, 2012 at 10:34 AM, Joel Madero jmadero@gmail.com wrote: Thanks to everyone. I have successfully done my first backtrace :) It was unrelated but I see things that make sense :) now time to try to locate this dialog and the trigger that is affecting image linking. Joel On Wed, Aug 8, 2012 at 11:49 PM, Jan Holesovsky ke...@suse.cz wrote: Hi Joel, Joel Madero píše v St 08. 08. 2012 v 18:35 -0700: Thanks for the advice. Unfortunately every time I run run and get into database I get a segfault in gdb. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffc2d06700 (LWP 4977)] To see where it crashed, do 'bt' in gdb - that will show you backtrace of the crash. If it looks unrelated, do 'thread apply all bt' which will show backtrace of all threads. Not sure why. Also mine looks nothing like Lionel's did when he ran gdb. Mine looks more like this: After issuing 'bt' (Lionel's and look at the backtrace), you should see something similar to Lionel's output :-) All the best, Kendy ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] Bugs prioritization - missing pieces
I will have to address the full thread in a few hours when I can sit down and think a bit about this but a couple points: a) I feel strongly that we should be actively aiming at making the triaging a more important aspect of development and agree with Petr that we should use priority and severity now that our team has grown (a little?) and especially since now it seems like we are more aggressive at triaging - going to sent out an update on UNCONFIRMED in a bit. b) As for the components, after UNCONFIRMED I intend on making this our next project if Rainer is okay with this. This would be going through all the bugs currently marked as just LibreOffice and UNCONFIRMED and setting their components and then setting their priority. c) I will upload the draw file for the flowchart so anyone can edit it and make other examples, I see that Rainer doesn't particularly love parts of it -- maybe he'd be willing to edit it a bit and make a second example? d) The QA wiki, and in particular the triaging/components section really seems bad to me. Rainer, if you have time I'd like to discuss with you (and implement) corrections to the triaging section. I think it's so scattered and disconnected that it makes it incredibly hard to do things right. For instance the flowchart that I added is on this severity page that I can't even find half of the time, I always have to dig around past emails to find out where my own flowchart is because it's not included in the bug triaging page where it belongs. Ultimately I think the whole QA wiki needs redone but we can maybe start with the triaging section. Lastly, I've been out of the loop for about a week struggling with computer issues so it's going to take me a couple days to get back into it (still haven't computer issues, might have to change distros which is always fun...) so my ability to use LibreOffice is still a bit limited with now. As always I am excited with the progress, suggestions, comments and complaints about LibreOffice as I feel like all of them will lead to a better product. I will read the full thread in a couple hours and send a second email out if necessary. Best Regards, Joel On 08/20/2012 05:59 AM, Petr Mladek wrote: Rainer Bielefeld píše v Po 20. 08. 2012 v 13:21 +0200: Petr Mladek schrieb: I think that we really should set severity and priority. Hi Petr, a while ago we decided that we should not invest too much time into this because of numerous abuse of these flags. It was during times when we had 2 or three people doing bug triage. The list of non-triaged bugs was growing. I think that we are in a different position now. We have more very active triagers. They have ambitions to end up with zero non-triaged bugs. They put a lot of energy into reproducing bugs, getting backtraces, ... Though, bugzilla is still a kind of swamp and only the very critical bugs are highlighted for developers. IMHO, it is a shame. I think that full prioritization would be a big win. It would allow to get rid of the schizophrenic MAB, moving bugs between MABs, ... Of course, it makes only sense if we have resources to triage all bugs. I believe that we have now. But indeed, I use Priority for my workflow (without trusting selected prio too much), and so we should extend rare info on https://wiki.documentfoundation.org/BugReport_Details#Severity to get a useful guide. I think Joels chart https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg can be a very good base (although believe it's a little too rich in detail). I think that we should add more examples. Do you miss anything else? I suggest something like Use: * Blocker if it's definitively Critical and additionally * Critical if it's criteria for Major is fulfilled and additionally Hmm, this is reverted logic against the flowchart. I am not sure how to convert it. Note that the flowchart describes also priorities = more complex task. It is still pretty readable and understandable. I am not sure if we could achieve this by itemized list. Well, it is possible that you do not like the system described in the chart. You might want to do the decision another way. Let's discuss it. I can put it into the line, but if someone else is interested, he should start to improve chapter on Bug Report Details. I would prefer to improve the Joel's chart. It is sexy and easier to understand than a long text. Best Regards, Petr ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Unconfirmed Bugs Triaging Update #2
Hi All, Progress is still going for the unconfirmed bugs but we still needs people to actively and aggressively help. If you have some time in the coming weeks take a look at the following document: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E If you can do 1 bug a week that helps, once we get these unconfirmed under control we'll be able to assign a small team to keep up with new bugs but getting caught up is challenging and any and all help is appreciated. Here are the new #'s. Start Date: August 5th, 2012 Starting # of Bugs: 1,472 # of Bugs Today: 1,177* Bugs done: 295 New Bugs Since August 5th: 322 Yes this means that we're actually BEHIND the pace of bugs still ;) But, good news is that our goal in QA isn't to have bugs triaged the day they are posted but instead just not have them sitting for months and months. Best regards to everyone, Joel P.S. I'm going to try to actively recruit a few more people from the #libreoffice channel who are probably knowledgeable to help triage but just never have been asked to participate in LO. Also, I'm updating the triaging wiki, if anyone is available to help please email me directly and we'll coordinate something, looking for both feedback on what should be on the wiki (right now it's pretty bad) as well as people to actually help write it. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Bug Closing Automation - Apology
Hi All, First off, sorry that I'm starting a new thread, I'm not sure how to reply to something from the digest in gmail. A couple days ago there was a very brief discussion about NEEDINFO and that it wasn't very useful to have the NEEDINFO status sit for weeks or months on end if the users weren't responding to our requests for more information. I jumped the gun and asked if there was a way to automate closing these bugs if they were open for some period of time, another user volunteered to do this and went ahead and did it. I take full responsibility for the ill feelings, I should have waited longer for more input and thought about it more clearly before requesting if someone had the ability to automatically close these bugs. It has pissed off quite a few people, I take the blame, please direct your irritation my way and not at Florian or any other member of the QA team. Best wishes to everyone, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-qa] Bug Closing Automation - Apology
Hi All, First off, sorry that I'm starting a new thread, I'm not sure how to reply to something from the digest in gmail. A couple days ago there was a very brief discussion about NEEDINFO and that it wasn't very useful to have the NEEDINFO status sit for weeks or months on end if the users weren't responding to our requests for more information. I jumped the gun and asked if there was a way to automate closing these bugs if they were open for some period of time, another user volunteered to do this and went ahead and did it. I take full responsibility for the ill feelings, I should have waited longer for more input and thought about it more clearly before requesting if someone had the ability to automatically close these bugs. It has pissed off quite a few people, I take the blame, please direct your irritation my way and not at Florian or any other member of the QA team. Best wishes to everyone, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Triaging Update
Hi All, As most of you know we've started a major push to triage the unconfirmed bugs and I am going to give updates periodically for 2 reasons: 1. just so we all know the progress :) 2. to remind people that we always need more individuals helping out at least until we get a grasp on the 12+ month back log. A reminder of where the organization is for the the project: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=1 Start Date: 05/08/2012 # of Unconfirmed Bugs: 1,472 Today's Date: 13/08/2012 # of Unconfirmed Bugs: 1,317* That's 145 bugs triaged in some way or another in about a week! :) Thank you to those helping, for those who have a bit of time please feel free to join, for developers, I hope this helps in some way ;) All the best, Joel *These bugs are the ones that were open at the time of the start of the project, doesn't include ones opened in the last week. I think if we can get through the back log we'll only need a few members to stay active in triaging weekly to keep new bugs under control :) ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-qa] Triaging Update
Hi All, As most of you know we've started a major push to triage the unconfirmed bugs and I am going to give updates periodically for 2 reasons: 1. just so we all know the progress :) 2. to remind people that we always need more individuals helping out at least until we get a grasp on the 12+ month back log. A reminder of where the organization is for the the project: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=1 Start Date: 05/08/2012 # of Unconfirmed Bugs: 1,472 Today's Date: 13/08/2012 # of Unconfirmed Bugs: 1,317* That's 145 bugs triaged in some way or another in about a week! :) Thank you to those helping, for those who have a bit of time please feel free to join, for developers, I hope this helps in some way ;) All the best, Joel *These bugs are the ones that were open at the time of the start of the project, doesn't include ones opened in the last week. I think if we can get through the back log we'll only need a few members to stay active in triaging weekly to keep new bugs under control :) ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Triaging Update
Hey Rainer, Do we have the ability to automatically close bugs + add comments that are 2+ weeks old with NEEDINFO status without any action by the user? This way I, and others, don't have to keep track of NEEDNIFO bugs so closely. If we can do this, maybe do a weekly or monthly purge for these bugs? Thanks for your feedback, I'm glad we're making progress. Joel On Mon, Aug 13, 2012 at 10:03 AM, Rainer Bielefeld libreoff...@bielefeldundbuss.de wrote: Joel Madero schrieb: As most of you know we've started a major push to triage the unconfirmed bugs and I am going to give updates periodically for 2 reasons Hi Joel, sounds great! A small hint from my side: It's useless to change status for bugs like Bug 45124 - PRINTING: Problem with printing while using Figures- Writer hangs https://bugs.freedesktop.org/**show_bug.cgi?id=45124https://bugs.freedesktop.org/show_bug.cgi?id=45124 to NEEDINFO. Experience shows that 99% of them will also not contribute requested info even after a second demand, and so you only waste your time with the friendly demand and other people's time who read your comment and the your next comment when you finally decide to close ... Please close such Bugs RESOLVED-INVALID if infoprovider did not answer within 2 weeks after first demand, of course with a friendly hint Please feel free to reopen this bug if you find out that the problem still exists with the current stable LibreOffice version and if you can contribute requested additional information! Thank you very much for your engagement Best Regards Rainer ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] RESOLVED status question
Thanks Peter. Given the information you and Rainer provided I think the best thing for QA triagers to do is to mark as WORKSFORME in most cases unless they know specifically that the bug was fixed and then maybe CC the person who patched the bug so they see the bug is closed. If this isn't the best method please let me know what is. Best Regards, Joel On Tue, Aug 7, 2012 at 3:29 AM, Petr Mladek pmla...@suse.cz wrote: Joel Madero píše v Čt 02. 08. 2012 v 14:42 -0700: At what point do we put resolved as a status? Is it when it's committed to master branch? If not then is the developer/qa team expected to continue to check a patchs status after it's already committed to master in order to find out if it's committed elsewhere? Thanks in advance, I'm not positive I've been doing it right :-/ A few I marked as RESOLVED because I know they are fixed in master and will soon be seen by other users as resolved as well. I would mark it as RESOLVED when the fix is pushed in all branches where we want it. IMHO, it means that the work is done from the developer side. We always want it in master. Sometimes, we want to backport it into older products which need some developer input as well. Best Regards, Petr ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Triaging Update
Excellent. You mind doing this monthly? We have 1,379 NEEDINFO bugs currently.I feel bad closing so many when a lot of them are as simple as attaching a document. Maybe once we get unconfirmed under control we can move on to NEEDINFO and INVALID to see if there are some in there that we can produce the documentation/attachments so we can reopen them and confirm them. Best Regards, Joel On Mon, Aug 13, 2012 at 11:17 AM, Florian Reisinger reisi...@gmail.comwrote: Hi Joel! __ Florian Reisinger Von meinem iPad gesendet Sent via iPad Am 13.08.2012 um 19:06 schrieb Joel Madero jmadero@gmail.com: Hey Rainer, Do we have the ability to automatically close bugs + add comments that are 2+ weeks old with NEEDINFO status without any action by the user? This way I, and others, don't have to keep track of NEEDNIFO bugs so closely. If we can do this, maybe do a weekly or monthly purge for these bugs? Thanks for your feedback, I'm glad we're making progress. Hi! I will do that tomorrow... Joel On Mon, Aug 13, 2012 at 10:03 AM, Rainer Bielefeld libreoff...@bielefeldundbuss.de wrote: Joel Madero schrieb: As most of you know we've started a major push to triage the unconfirmed bugs and I am going to give updates periodically for 2 reasons Hi Joel, sounds great! A small hint from my side: It's useless to change status for bugs like Bug 45124 - PRINTING: Problem with printing while using Figures- Writer hangs https://bugs.freedesktop.org/**show_bug.cgi?id=45124https://bugs.freedesktop.org/show_bug.cgi?id=45124 to NEEDINFO. Experience shows that 99% of them will also not contribute requested info even after a second demand, and so you only waste your time with the friendly demand and other people's time who read your comment and the your next comment when you finally decide to close ... Please close such Bugs RESOLVED-INVALID if infoprovider did not answer within 2 weeks after first demand, of course with a friendly hint Please feel free to reopen this bug if you find out that the problem still exists with the current stable LibreOffice version and if you can contribute requested additional information! Thank you very much for your engagement Best Regards Rainer ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/ ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Update QA Site Please
Can someone who has permissions (or if someone can give me permissions) to access http://www.libreoffice.org/get-involved/qa-testers/, we need to add the QA IRC channel (#libreoffice-qa) to the site. Thanks all Best Regards, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: Help Locating Base Code
Thanks to everyone. I have successfully done my first backtrace :) It was unrelated but I see things that make sense :) now time to try to locate this dialog and the trigger that is affecting image linking. Joel On Wed, Aug 8, 2012 at 11:49 PM, Jan Holesovsky ke...@suse.cz wrote: Hi Joel, Joel Madero píše v St 08. 08. 2012 v 18:35 -0700: Thanks for the advice. Unfortunately every time I run run and get into database I get a segfault in gdb. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffc2d06700 (LWP 4977)] To see where it crashed, do 'bt' in gdb - that will show you backtrace of the crash. If it looks unrelated, do 'thread apply all bt' which will show backtrace of all threads. Not sure why. Also mine looks nothing like Lionel's did when he ran gdb. Mine looks more like this: After issuing 'bt' (Lionel's and look at the backtrace), you should see something similar to Lionel's output :-) All the best, Kendy ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[PROPOSED] Changes to General Options FDO#40656
Hi All, This is in response to FDO#40656: https://bugs.freedesktop.org/show_bug.cgi?id=40656 In order to accomplish this I need to move some things around. I did the visual changes - didn't do any of the functional changes yet, nor did I ensure that spacing and what not is perfect. Looking for general input before I put the time that is needed into this. Thanks all. Image of Changes: https://wiki.documentfoundation.org/images/1/1a/-PROPOSED-_General_Options_Change.pdf Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Help Locating Base Code
Thanks to both of you. I have tried the gdb method before and honestly, for a new programmer, our directions aren't the best on the wiki. I am yet to successfully make progress but I am going to figure it out this time around since it seems like that's what is needed. Usually I just grep the label for something I am search for and then backtrack from there, seeing where it is used and how and sooner or later I find the code that I'm looking for. In this case Lionel is right, both the ... and the pictures labels are both so generic that they are useless for tracking down the code. Also it seems like these dialogs are a bit complex (seems like they could be simplified but that's probably for another day ;) ). So my next question is two fold... 1. For getting a bit more in depth instructions, is it best to ask here or in IRC? I believe (almost positive) that my Libo is installed with symbols enabled, so I want to try to do the gdb method but need kind of a complete breakdown of what to do (I believe it's only a few steps). 2. If the best place to ask is here, could someone be kind enough to write out the few steps? Again thank you for all of your patience. I feel like I'm starting to get a grasp on the code :) Joel On Wed, Aug 8, 2012 at 6:20 AM, Lionel Elie Mamane lio...@mamane.lu wrote: On Wed, Aug 08, 2012 at 02:01:28PM +0100, Michael Meeks wrote: On Wed, 2012-08-08 at 07:32 +0200, Lionel Elie Mamane wrote: On Tue, Aug 07, 2012 at 06:50:22PM -0700, Joel Madero wrote: I'm trying to locate the code that handles the dialog that appears when you do the following steps in base: To answer this kind of questions, I find it useful to run a build with symbols (debug build) under gdb. Then, when the dialog is open, just press CTRL-C in gdb So - that is one way :-) another way is to grep for the UI strings, which usually come from a .src file; so git --no-pager grep -2 Create Report in Design View In general, you are right, this is a useful technique that needs less tooling, and I didn't think of mentioning it. In this case, however, Joel was looking for a _different_ thing than what you show in the example. He wanted to see what creates the dialog titled Picture when one presses the button labelled As these are quite generic labels, in this case, the gdb technique is faster / more accurate, assuming you already have a build with symbols. -- Lionel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Unconfirmed Bugs
It's only been a couple days since we've started but I wanted to say thanks for those who have taken the time to take a group and start getting the unconfirmed bug count down. Good news is that the # has gone down by almost 50 in less than 2 days. I'm happy with progress and hope that more people will join. Thanks again everyone! Joel On Tue, Aug 7, 2012 at 12:49 AM, Petr Mladek pmla...@suse.cz wrote: Hi Joel, first, thanks a lot for organizing such an event. It is a good start in any case. Joel Madero píše v Po 06. 08. 2012 v 11:15 -0700: Hi All, Well, we attempted to do a triaging event Sunday and ...it didn't work out well. Hardly anyone showed, and I understand, it was the weekend ;) I guess that we might get better audience in winter. You know, the long cold evenings are better for sitting in front of computer than the current shiny days :-) So I'm attempting something new. What I've done is made a google doc (yes I know, boo, lame, whatever), for now, it was the easiest and fastest way to organize. I have organized based on the component and then grouped in approximately 50 or less groupings. If you have the time (even if it takes a couple months to get through them) PLEASE take a group. I am convinced that it reflects poorly on us that we allow bugs to stay unconfirmed with no comment or anything for months and months and months - I would actually say that alone should be a critical bug ;) So, if you could take a grouping please rename the sheet to your name (or IRC name or some other way you call yourself) and just go through them at your leisure, that would be fantastic. If we could get 10-15 people to commit to a group we could halve the unconfims over the next few months which would be nice for the UA team, for the dev team and for our user base. LINK: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=0 Could you please mention it at http://wiki.documentfoundation.org/BugTriage or somewhere around? I think that it might be interesting also for newcomers. Thanks a lot for all your great efforts. Best Regards, Petr ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
New QA IRC Channel
Hi All, An official QA channel was established today at #libreoffice-qa, I'll update the wiki when I get a chance. Feel free to come sit in there, talk in there will be mostly about qa stuff, help with triaging, discussing organization of QA, etc Thanks everyone, see you in the channel Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [PATCH]fdo#52636:VIEWING: unintuitive Heading for 'Enable experimental Features
3rd try is a charm? Thanks for that fix regarding the size of the space
between the options - that was creating a snag for me and I couldn't
figure it out. Again, feel free to comment.
Joel
On 08/06/2012 11:28 AM, Ivan Timofeev wrote:
Hi Joel,
On 02.08.2012 21:57, Joel Madero wrote:
Here is an updated patch.
not that it is essential, but it is good if the commit message is
wrapped so that it does not exceed a reasonable width (say 70-80
characters). (Yes, my e-mail client seems unable to do that, ugh.)
Please enter the commit message for your changes. Lines starting
with '#' will be ignored, and an empty message aborts the commit.
Something wrong with your editor? These lines should start with '#'
and be ignored, why they are in the commit message again?
Text [ en-US ] = Optional features ;
uhm, IMHO optional means not necessary in most cases, but sometimes
might be helpful. So a user would think Ok, let's enable all these,
won't hurt anyway. But this features aren't stable and somewhat
dangerous to enable, and
-Text [ en-US ] = Enable experimental (unstable) features;
+Text [ en-US ] = Enable experimental features;
makes it sound even more safe. Maybe Unstable features as a header
then?
Another nit-picking:
you placed two labels in one row, not good IMHO: consider long
translations. But then the last row could go out of the visible area,
it would be great to check that - play with #define ROW.. constants in
optgdlg.hrc, remove my ugly +6 in ROW14 etc... :)
Thanks!
Ivan
From fea8e91665e2b9e52f004514a796f01c13bf81d0 Mon Sep 17 00:00:00 2001
From: Joel Madero jmadero@gmail.com
Date: Wed, 8 Aug 2012 17:04:09 -0700
Subject: [PATCH] Addition of linear divider and header Optional (unstable)
Features
Put two experimental options (Experimental Macro Recording) below
a linear divider with the header of Optional (Unstable) Features
Had to adjust distance between two options in order for them to fit
properly in the dialog.
Change-Id: I784f99c282d5b70e7e025b1ca05a7c8d73869cef
---
cui/source/options/optgdlg.cxx |7 ---
cui/source/options/optgdlg.hrc |6 --
cui/source/options/optgdlg.hxx |1 +
cui/source/options/optgdlg.src | 14 ++
4 files changed, 19 insertions(+), 9 deletions(-)
diff --git a/cui/source/options/optgdlg.cxx b/cui/source/options/optgdlg.cxx
index 8800e11..4f83368 100644
--- a/cui/source/options/optgdlg.cxx
+++ b/cui/source/options/optgdlg.cxx
@@ -213,6 +213,7 @@ OfaMiscTabPage::OfaMiscTabPage(Window* pParent, const SfxItemSet rSet ) :
aInterpretFT( this, CUI_RES( FT_INTERPRET ) ),
aYearValueField ( this, CUI_RES( NF_YEARVALUE ) ),
aToYearFT ( this, CUI_RES( FT_TOYEAR ) ),
+aExperimentalFL ( this, CUI_RES( FL_EXPERIMENTAL ) ),
aExperimentalCB ( this, CUI_RES( CB_EXPERIMENTAL ) ),
aMacroRecorderCB( this, CUI_RES( CB_MACRORECORDER ) )
{
@@ -244,7 +245,7 @@ OfaMiscTabPage::OfaMiscTabPage(Window* pParent, const SfxItemSet rSet ) :
Window* pWins[] =
{
aPrintDlgFL, aPrintDlgCB, aDocStatusFL, aDocStatusCB, aSaveAlwaysCB,
-aTwoFigureFL, aInterpretFT, aYearValueField, aToYearFT, aExperimentalCB, aMacroRecorderCB
+aTwoFigureFL, aInterpretFT, aYearValueField, aToYearFT, aExperimentalFL, aExperimentalCB, aMacroRecorderCB
};
Window** pCurrent = pWins;
const sal_Int32 nCount = SAL_N_ELEMENTS( pWins );
@@ -265,7 +266,7 @@ OfaMiscTabPage::OfaMiscTabPage(Window* pParent, const SfxItemSet rSet ) :
Window* pWins[] =
{
aPrintDlgFL, aPrintDlgCB, aDocStatusFL, aDocStatusCB, aSaveAlwaysCB,
-aTwoFigureFL, aInterpretFT, aYearValueField, aToYearFT, aExperimentalCB, aMacroRecorderCB
+aTwoFigureFL, aInterpretFT, aYearValueField, aToYearFT, aExperimentalFL, aExperimentalCB, aMacroRecorderCB
};
Window** pCurrent = pWins;
const sal_Int32 nCount = SAL_N_ELEMENTS( pWins );
@@ -291,7 +292,7 @@ OfaMiscTabPage::OfaMiscTabPage(Window* pParent, const SfxItemSet rSet ) :
Window* pWins[] =
{
aDocStatusFL, aDocStatusCB, aSaveAlwaysCB, aTwoFigureFL,
-aInterpretFT, aYearValueField, aToYearFT, aExperimentalCB, aMacroRecorderCB
+aInterpretFT, aYearValueField, aToYearFT, aExperimentalFL, aExperimentalCB, aMacroRecorderCB
};
Window** pCurrent = pWins;
const sal_Int32 nCount = SAL_N_ELEMENTS( pWins );
diff --git a/cui/source/options/optgdlg.hrc b/cui/source/options/optgdlg.hrc
index 9be9051..2bf4343 100644
--- a/cui/source/options/optgdlg.hrc
+++ b/cui/source/options/optgdlg.hrc
@@ -51,6 +51,7 @@
#define ROW13 (ROW12+RSC_CD_FIXEDLINE_HEIGHT+ROWSPACE)
#define ROW14 (ROW13+RSC_CD_CHECKBOX_HEIGHT+ROWSPACE+6)
#define ROW15 (ROW14+RSC_CD_CHECKBOX_HEIGHT+ROWSPACE)
+#define ROW16
Re: Help Locating Base Code
On 08/08/2012 11:34 AM, Jan Holesovsky wrote: gdb ./soffice.bin when I do that all I get is this: joel@joel-Studio-1737:/data/git/libo/install/program$ gdb ./soffice.bin GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/... Reading symbols from /data/git/libo/solver/unxlngx6.pro/installation/opt/program/soffice.bin...done. LibreOffice doesn't actually start at all :-/ Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Help Locating Base Code
On 08/08/2012 06:01 AM, Michael Meeks wrote:
On Wed, 2012-08-08 at 07:32 +0200, Lionel Elie Mamane wrote:
On Tue, Aug 07, 2012 at 06:50:22PM -0700, Joel Madero wrote:
I'm trying to locate the code that handles the dialog that appears when you
do the following steps in base:
To answer this kind of questions, I find it useful to run a build with
symbols (debug build) under gdb. Then, when the dialog is open, just
press CTRL-C in gdb
So - that is one way :-) another way is to grep for the UI strings,
which usually come from a .src file; so
git --no-pager grep -2 Create Report in Design View
dbaccess/source/ui/app/app.src-String RID_STR_NEW_REPORT
dbaccess/source/ui/app/app.src-{
dbaccess/source/ui/app/app.src:Text [ en-US ] = Create Report in Design
View... ;
dbaccess/source/ui/app/app.src-};
dbaccess/source/ui/app/app.src-
Maps the string to the ID, then grep for that RID_STR_...
git --no-pager grep -2 RID_STR_NEW_REPORT
dbaccess/source/ui/app/AppDetailView.cxx-
dbaccess/source/ui/app/AppDetailView.cxx-case E_REPORT:
dbaccess/source/ui/app/AppDetailView.cxx:rList.push_back( TaskEntry(
.uno:DBNewReport, RID_STR_REPORT_HELP_TEXT, RID_STR_NEW_REPORT, true ) );
dbaccess/source/ui/app/AppDetailView.cxx:rList.push_back( TaskEntry(
.uno:DBNewReportAutoPilot, RID_STR_REPORTS_HELP_TEXT_WIZARD,
RID_STR_NEW_REPORT_AUTO ) );
dbaccess/source/ui/app/AppDetailView.cxx-_rData.nTitleId =
RID_STR_REPORTS_CONTAINER;
dbaccess/source/ui/app/AppDetailView.cxx-break;
So somewhere thereabouts :-)
There was (IIRC) an easy-hack to create some web infrastructure that
would help do this lookup (particularly with accelerator keys) for new
developers - that'd be an awesome thing to build of course - a bit of
php (or somesuch) interfacing to a database built by some 'git greps ?'
All the best,
Michael.
Thanks for the advice. Unfortunately every time I run run and get into
database I get a segfault in gdb.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc2d06700 (LWP 4977)]
Not sure why. Also mine looks nothing like Lionel's did when he ran gdb.
Mine looks more like this:
[New Thread 0x7fffb8fff700 (LWP 4966)]
[New Thread 0x7fffb8efe700 (LWP 4967)]
[New Thread 0x7fffb8dfd700 (LWP 4968)]
[New Thread 0x7fffb8cfc700 (LWP 4969)]
[New Thread 0x7fffb8bfb700 (LWP 4970)]
[New Thread 0x7fffb8afa700 (LWP 4971)]
[New Thread 0x7fffb89f9700 (LWP 4972)]
[Thread 0x7fffc2d06700 (LWP 4962) exited]
[New Thread 0x7fffd08a3700 (LWP 4973)]
[New Thread 0x7fffc2d06700 (LWP 4974)]
[New Thread 0x7fff93fff700 (LWP 4975)]
[Thread 0x7fff93fff700 (LWP 4975) exited]
[Thread 0x7fffc2d06700 (LWP 4974) exited]
[New Thread 0x7fffc2d06700 (LWP 4977)]
[New Thread 0x7fffc9667700 (LWP 4978)]
Any help appreciated. Thanks all
Joel
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] Unconfirmed Bugs
It's only been a couple days since we've started but I wanted to say thanks for those who have taken the time to take a group and start getting the unconfirmed bug count down. Good news is that the # has gone down by almost 50 in less than 2 days. I'm happy with progress and hope that more people will join. Thanks again everyone! Joel On Tue, Aug 7, 2012 at 12:49 AM, Petr Mladek pmla...@suse.cz wrote: Hi Joel, first, thanks a lot for organizing such an event. It is a good start in any case. Joel Madero píše v Po 06. 08. 2012 v 11:15 -0700: Hi All, Well, we attempted to do a triaging event Sunday and ...it didn't work out well. Hardly anyone showed, and I understand, it was the weekend ;) I guess that we might get better audience in winter. You know, the long cold evenings are better for sitting in front of computer than the current shiny days :-) So I'm attempting something new. What I've done is made a google doc (yes I know, boo, lame, whatever), for now, it was the easiest and fastest way to organize. I have organized based on the component and then grouped in approximately 50 or less groupings. If you have the time (even if it takes a couple months to get through them) PLEASE take a group. I am convinced that it reflects poorly on us that we allow bugs to stay unconfirmed with no comment or anything for months and months and months - I would actually say that alone should be a critical bug ;) So, if you could take a grouping please rename the sheet to your name (or IRC name or some other way you call yourself) and just go through them at your leisure, that would be fantastic. If we could get 10-15 people to commit to a group we could halve the unconfims over the next few months which would be nice for the UA team, for the dev team and for our user base. LINK: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=0 Could you please mention it at http://wiki.documentfoundation.org/BugTriage or somewhere around? I think that it might be interesting also for newcomers. Thanks a lot for all your great efforts. Best Regards, Petr ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-ux-advise] Unconfirmed Bugs
It's only been a couple days since we've started but I wanted to say thanks for those who have taken the time to take a group and start getting the unconfirmed bug count down. Good news is that the # has gone down by almost 50 in less than 2 days. I'm happy with progress and hope that more people will join. Thanks again everyone! Joel On Tue, Aug 7, 2012 at 12:49 AM, Petr Mladek pmla...@suse.cz wrote: Hi Joel, first, thanks a lot for organizing such an event. It is a good start in any case. Joel Madero píše v Po 06. 08. 2012 v 11:15 -0700: Hi All, Well, we attempted to do a triaging event Sunday and ...it didn't work out well. Hardly anyone showed, and I understand, it was the weekend ;) I guess that we might get better audience in winter. You know, the long cold evenings are better for sitting in front of computer than the current shiny days :-) So I'm attempting something new. What I've done is made a google doc (yes I know, boo, lame, whatever), for now, it was the easiest and fastest way to organize. I have organized based on the component and then grouped in approximately 50 or less groupings. If you have the time (even if it takes a couple months to get through them) PLEASE take a group. I am convinced that it reflects poorly on us that we allow bugs to stay unconfirmed with no comment or anything for months and months and months - I would actually say that alone should be a critical bug ;) So, if you could take a grouping please rename the sheet to your name (or IRC name or some other way you call yourself) and just go through them at your leisure, that would be fantastic. If we could get 10-15 people to commit to a group we could halve the unconfims over the next few months which would be nice for the UA team, for the dev team and for our user base. LINK: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=0 Could you please mention it at http://wiki.documentfoundation.org/BugTriage or somewhere around? I think that it might be interesting also for newcomers. Thanks a lot for all your great efforts. Best Regards, Petr ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
Help Locating Base Code
Hi All, Spent a few hours trying to track this down and I can't figure it out so hoping someone can guide me in the right direction. I'm trying to locate the code that handles the dialog that appears when you do the following steps in base: 1. From Start Center create and save new sample.odb 2. Database-Pane: Reports 3. Tasks-Pane: 'Create Report in Design View ...' Report Designer appears 4. Click into Page footer (Related properties appear at the right) 5. Click 'Graphic' icon in toolbar 6. Draw a 20mm x 20mm with pushed mouse button into footer field Propperties field will change to Image control will appear at the right 7. In 'Image control - General' nearby bottom in line Graphics click '...' button To insert a picture The dialog that appears simply says Picture as the header. If someone can guide me to the relevant code, more specifically I'm trying to see how it's passing on the default of unlinked to that dialog. If you go to Insert - Image the check mark is checked by default. Would be nice to track that down as well so that I can compare the two. Thanks for your guidance and continuing patience with my beginner skills :) Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] Bug triage workflow
I will hopefully get a chance tonight to play around with the wiki a bit. I'll get the odg document up and put it under commons license :) Joel P.S. I think separating the triaging page from priotizing (severity) page isn't the best idea, any opinions from other people? Seems like all triaging should be on the same page, including devs we may want to CC for a particular bug. On Tue, Aug 7, 2012 at 3:40 AM, Petr Mladek pmla...@suse.cz wrote: Hi Joel, Joel Madero píše v Út 31. 07. 2012 v 07:02 -0700: It's terribly located, I'll fix it today. It's on the right page but just not very clear: http://wiki.documentfoundation.org/BugReport_Details#Severity If you scroll down you'll see a link to it but it's small and not very easy to find. Direct link is here: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg BTW: Is also the original .odg document in wiki? It would be cool if you could put it there with a reasonable license. It would help to improve the already nice diagram in the future. Best Regards, Petr ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Unconfirmed Bugs
Hi All, Well, we attempted to do a triaging event Sunday and ...it didn't work out well. Hardly anyone showed, and I understand, it was the weekend ;) So I'm attempting something new. What I've done is made a google doc (yes I know, boo, lame, whatever), for now, it was the easiest and fastest way to organize. I have organized based on the component and then grouped in approximately 50 or less groupings. If you have the time (even if it takes a couple months to get through them) PLEASE take a group. I am convinced that it reflects poorly on us that we allow bugs to stay unconfirmed with no comment or anything for months and months and months - I would actually say that alone should be a critical bug ;) So, if you could take a grouping please rename the sheet to your name (or IRC name or some other way you call yourself) and just go through them at your leisure, that would be fantastic. If we could get 10-15 people to commit to a group we could halve the unconfims over the next few months which would be nice for the UA team, for the dev team and for our user base. I know I sound like I'm preaching.thanks all who participate. LINK: https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E#gid=0 ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [PATCH]fdo#52636:VIEWING: unintuitive Heading for 'Enable experimental Features
I'll take care of these issues. I put 2 in one row because there is a limit as to how many rows can be in the general tab and we've hit that limit :-/ I'm not sure how that is being handled or if we want to increase the # but if I increase the row by one it shoots out an error for me. Let me know how to proceed, I'll deal with the other two issues as soon as possible. Thanks for the comments Joel On Mon, Aug 6, 2012 at 11:28 AM, Ivan Timofeev timofeev@gmail.comwrote: Hi Joel, On 02.08.2012 21:57, Joel Madero wrote: Here is an updated patch. not that it is essential, but it is good if the commit message is wrapped so that it does not exceed a reasonable width (say 70-80 characters). (Yes, my e-mail client seems unable to do that, ugh.) Please enter the commit message for your changes. Lines starting with '#' will be ignored, and an empty message aborts the commit. Something wrong with your editor? These lines should start with '#' and be ignored, why they are in the commit message again? Text [ en-US ] = Optional features ; uhm, IMHO optional means not necessary in most cases, but sometimes might be helpful. So a user would think Ok, let's enable all these, won't hurt anyway. But this features aren't stable and somewhat dangerous to enable, and -Text [ en-US ] = Enable experimental (unstable) features; +Text [ en-US ] = Enable experimental features; makes it sound even more safe. Maybe Unstable features as a header then? Another nit-picking: you placed two labels in one row, not good IMHO: consider long translations. But then the last row could go out of the visible area, it would be great to check that - play with #define ROW.. constants in optgdlg.hrc, remove my ugly +6 in ROW14 etc... :) Thanks! Ivan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Tomorrow's Triaging
Hi All, Tomorrow morning I'll be opening up an IRC room (#libreoffice-qa) at 9am (GMT-7). Starting at 9:30 (GMT-7) we're just going to spend an hour going through unconfirmed bugs and trying to confirm them and prioritize them. I suspect the first 10-15 minutes will be organizational, I've created a couple spreadsheets with lists of bugs for Brennan and Florian who have already confirmed that they can help out. If you can help out feel free to join the room in the morning or shoot me an email and I'll prepare a list of unconfirmed bugs for you. Thanks to everyone, I know I've beenaggressive with bugging people to help us out. Joel On Thu, Aug 2, 2012 at 4:54 PM, Brennan T Vincent brenn...@email.arizona.edu wrote: Hi, this is uman from freenode signing up for sunday triaging session ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-qa] Tomorrow's Triaging
Hi All, Tomorrow morning I'll be opening up an IRC room (#libreoffice-qa) at 9am (GMT-7). Starting at 9:30 (GMT-7) we're just going to spend an hour going through unconfirmed bugs and trying to confirm them and prioritize them. I suspect the first 10-15 minutes will be organizational, I've created a couple spreadsheets with lists of bugs for Brennan and Florian who have already confirmed that they can help out. If you can help out feel free to join the room in the morning or shoot me an email and I'll prepare a list of unconfirmed bugs for you. Thanks to everyone, I know I've beenaggressive with bugging people to help us out. Joel On Thu, Aug 2, 2012 at 4:54 PM, Brennan T Vincent brenn...@email.arizona.edu wrote: Hi, this is uman from freenode signing up for sunday triaging session ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [PATCH]fdo#52636:VIEWING: unintuitive Heading for 'Enable experimental Features
Perfect idea! I'm going to go ahead and work on that. I will take out limited (I have no clue what it means either, I figured someone else must have known when they added it ;)). I have a quick question though. What's the best way to modify a patch? The only way I know how is to go back to dismiss my changes and start from scratch. I'm sure there is a better way that I don't know of. Is it to directly modify the patch file in an editor or is there a way for me to edit the cxx/hxx/etc...files and then add/modify the patch using some git command? Thanks for the input Joel On Thu, Aug 2, 2012 at 12:45 AM, Stefan Knorr heinzless...@gmail.comwrote: Hi Joel, On Wed, 2012-08-01 at 13:53 -0700, Joel Madero wrote: I'll fix both. I'll leave limited since it fits, I actually noticed that right after I sent out the email. What does that limited mean, can I ask? I can't really make that out. I'll be moving a lot of stuff around when I move the measurement unit to the general tree, maybe a good solution is moving the experimental stuff to its own tab. Well, the Java panel is quite empty (or at least its space isn't used very well). Renaming that to Advanced and putting the experiments section there might be viable. Astron. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [PATCH]fdo#52636:VIEWING: unintuitive Heading for 'Enable experimental Features
Here is an updated patch. Also here is a link for everyone to see what we could make Java tab look like: https://lh5.googleusercontent.com/-lzTcvXoWhOw/UBq_VGFqL2I/ACc/TnxVpfV5WL0/s937/Advanced_Options.jpg Notes: 1. Changed name to Advanced 2. Shrunk Java dialog box 3. Added bottom section for experimental features This would clear up enough space in the general tab for me to move the measurement units over. I've cc'ed the ux team since this is now a visual thing also. Please respond to the dev mailing list as I'll be pushing out a few patches corresponding to these changes. Joel On Thu, Aug 2, 2012 at 11:29 AM, Stefan Knorr heinzless...@gmail.comwrote: Hello there, On Thu, 2012-08-02 at 08:14 -0700, Joel Madero wrote: Perfect idea! I'm going to go ahead and work on that. I will take out limited (I have no clue what it means either, I figured someone else must have known when they added it ;)). Well, hopefully, I didn't sound overly assertive here. I have a quick question though. What's the best way to modify a patch? The only way I know how is to go back to dismiss my changes and start from scratch. I'm sure there is a better way that I don't know of. So, I am by no means the git expert here (I still barely understand the basics of it) but ... you probably still have the original patch committed locally, (and if not, you can do $ git am path/to.patch ), so, do all the modifications you want to do, then do the usual $ git add . $ git commit At the end, you can just use $ git rebase -i HEAD~2 to either squash (merge the commits and edit the commit message) or fixup (just merge the commits) (assuming you had only your original commit and the new one = HEAD~2). Also: Note that you should only ever use rebase -i on local commits – modifying the global commit history is evil. (It won't do any harm to everyone else, if you don't have commit access, but still.) Modifying the patch in a text editor can easily go wrong, so that's not recommended. Astron. 0001-fdo-52636-Added-Sectional-Line-and-Header-for-Experi.patch Description: Binary data ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Unconfirmed Bug Flowchart + Triaging this Sunday
First go at doing a flowchart for unconfirmed bugs, looking for feedback and suggestions. This one is quite a bit harder than the prioritizing bugs one was. https://wiki.documentfoundation.org/images/c/c4/Unconfirmed_Bugs_Status_Flowchart_Version_0.1.pdf For anyone who hasn't seen the one for prioritizing bugs: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Lastly, QA is doing an unconfirmed bug triaging event Sunday morning (9:30 am PST - GMT-7) if anyone could help we would really appreciate it. Don't worry if you haven't done it before, devs welcome to help us ;) As of now I believe we have 3 people, aiming for 5-10 so please email me if you're available and can spare an hour or so. Best Wishes, Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-qa] RESOLVED status question
At what point do we put resolved as a status? Is it when it's committed to master branch? If not then is the developer/qa team expected to continue to check a patchs status after it's already committed to master in order to find out if it's committed elsewhere? Thanks in advance, I'm not positive I've been doing it right :-/ A few I marked as RESOLVED because I know they are fixed in master and will soon be seen by other users as resolved as well. Thanks again, Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Responding to Digest Item
I've never successfully figured out how I respond to a particular item in the digest. Do I compose a new message with the subject or is there some other method that I get on that particular messages thread? Thanks Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [PATCH]fdo#52636:VIEWING: unintuitive Heading for 'Enable experimental Features
I'll fix both. I'll leave limited since it fits, I actually noticed that right after I sent out the email. I'll be moving a lot of stuff around when I move the measurement unit to the general tree, maybe a good solution is moving the experimental stuff to its own tab. Joel On Wed, Aug 1, 2012 at 3:48 PM, Stefan Knorr heinzless...@gmail.com wrote: Hi Joel, your idea sounds good [even though I think that if these features aren't ready yet, they shouldn't be so prominent in the options – but that's a fight for another day]. However, please have a look at your patch again, it leaves in the (limited) and also changes the capitalisation to title case which we don't for elements on dialogue boxes (only for menus and toolbars). Astron. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Triaging Event?
I was wondering if anyone is interested in trying to do a triaging extravaganza in the next month or so. The main goal would be to get the unconfirmed bugs in the proper status (New, NeedInfo, Resolved) and set priority. Whiteboard status would be a plus but a secondary triaging event could do this. Currently there are 1,452 unconfirmed bugs, if we could get 5-10 people to commit and get on IRC for a few hours in the next few weeks I think we could get through a lot of them. Triaging Event Date Poll: New Doodle poll: http://doodle.com/**kzmzfr86pwk59ihuhttp://doodle.com/kzmzfr86pwk59ihu Thanks to Florian for setting this up :) Joel P.S. After that particular week I become more open on weekends, the Sunday, September 9th works for me as well. Weekdays 9-11 PST (GMT - 7) is hard for me as I'm at work, after 4PM (11PM GMT) works for me but I know that's difficult for a lot of people in Europe. I'll try to be flexible ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[PATCH]fdo#52636:VIEWING: unintuitive Heading for 'Enable experimental Features
Feel free to comment. Thanks Joel 0001-fdo-52636-Added-Sectional-Line-and-Header-for-Experi.patch Description: Binary data ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] Bug triage workflow
It's terribly located, I'll fix it today. It's on the right page but just not very clear: http://wiki.documentfoundation.org/BugReport_Details#Severity If you scroll down you'll see a link to it but it's small and not very easy to find. Direct link is here: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg The other site that you linked to is for triaging status not priority. I intend on making another one for status but just haven't found the time. Hope that helps. Best Wishes, Joel On Tue, Jul 31, 2012 at 1:20 AM, Jan Holesovsky ke...@suse.cz wrote: Hi Joel, Some time ago you created a nice bug triage workflow diagram. Today I was trying to find it in the wiki, but failed :-( Can you please remind me where it is, and link it from: http://wiki.documentfoundation.org/BugTriage Thank you a lot! All the best, Kendy ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Triaging Event?
Hi QA people :) I was wondering if anyone is interested in trying to do a triaging extravaganza in the next month or so. The main goal would be to get the unconfirmed bugs in the proper status (New, NeedInfo, Resolved) and set priority. Whiteboard status would be a plus but a secondary triaging event could do this. Currently there are 1,452 unconfirmed bugs, if we could get 5-10 people to commit and get on IRC for a few hours in the next few weeks I think we could get through a lot of them. Let me know what you think. Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] Open Issues
Hi All, Do we have an ongoing list of open issues that we keep track of and up to date? If not it might be a good idea to get one going. I think that there are at least 3-4 things in the past couple months that have had serious conversations but a decision was never made to finalize things. The most notable that I remember is the CTL discussion that we had over the course of a couple weeks. Quite a few users are requesting us to make a final decision on that and it's kind of just in limbo. Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Triaging Event?
Triaging Event Date Poll: New Doodle poll: http://doodle.com/**kzmzfr86pwk59ihuhttp://doodle.com/kzmzfr86pwk59ihu Thanks to Florian for setting this up :) Joel P.S. After that particular week I become more open on weekends, the Sunday, September 9th works for me as well. Weekdays 9-11 PST (GMT - 7) is hard for me as I'm at work. Joel On Tue, Jul 31, 2012 at 7:58 AM, Joel Madero jmadero@gmail.com wrote: Hi QA people :) I was wondering if anyone is interested in trying to do a triaging extravaganza in the next month or so. The main goal would be to get the unconfirmed bugs in the proper status (New, NeedInfo, Resolved) and set priority. Whiteboard status would be a plus but a secondary triaging event could do this. Currently there are 1,452 unconfirmed bugs, if we could get 5-10 people to commit and get on IRC for a few hours in the next few weeks I think we could get through a lot of them. Let me know what you think. Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[PATCH] fdo#47164: Start Center: Recent Documents picker can not be reached right third of separate button area
Patch #2, think this one is much cleaner. Feel free to comment, next patch I'll submit through gerrit, late and didn't want to learn about it at midnight ;) Joel 0001-fdo-47164-Increased-size-of-hotspot-box-for-recent-d.patch Description: Binary data ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-ux-advise] FDO#40656: Move measurement settings to LibreOffice tree
I'm starting on this one tonight and looking for advice on placement of Measurement Unit (MU) and Tab stops (TS) within the LibreOffice tree. I have three ideas: 1. Remove experimental from general, instead put the MU and TS there and add another item on the left saying Experimental here we can place the two removed from General. 2. Add a new item to the left called Metrics and add the MU and TS to there. 3. Move Help on its own, this will free up space from the General tab to include MU and TS. There isn't enough room in general to add more without moving something out. I'm open to suggestions. Thanks all Joel ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
Re: Excel Function Meta Bug?
I've started the page. You can find information on the Calc development page (bottom). Thanks for the guidance, hopefully I (and maybe others) can complete the list soon and then decide if/when/how to start getting the most important functions implemented. Thanks again all, Joel On Fri, Jul 13, 2012 at 12:21 PM, Eike Rathke er...@redhat.com wrote: Hi Joel, On Friday, 2012-07-13 09:00:28 -0700, Joel Madero wrote: I closed the bug as INVALID and put a comment on there. I also will move the list to the wiki, not sure where it's preferred to go or if I'm making a new wiki page. Thanks for the feedback Please create a new page, i.e. http://wiki.documentfoundation.org/Development/Calc/Spreadsheet_Functions and link to it from http://wiki.documentfoundation.org/Development/Calc For overview, in http://wiki.documentfoundation.org/Development/Calc/Spreadsheet_Functions also place pointers to the pages that Regina mentioned in this thread, so we'll have it all in one place. Thanks Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Excel Function Meta Bug?
Nice, the updates make it quite a bit more functional. I noticed that most of the really useful functions are already well on their way to being implemented. Those cube functions...I've never even heard of. Otherwise, I think the users list was not very accurate, I think he had 25+ functions, I found a total of 14. Thanks again, Joel On Tue, Jul 17, 2012 at 12:57 PM, Eike Rathke er...@redhat.com wrote: Hi Joel, On Tuesday, 2012-07-17 08:36:22 -0700, Joel Madero wrote: I've started the page. You can find information on the Calc development page (bottom). Thanks for the guidance, hopefully I (and maybe others) can complete the list soon and then decide if/when/how to start getting the most important functions implemented. Thanks for getting this started, I took the freedom and fiddled with it ;-) Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] Excel Function Meta Bug?
I've started the page. You can find information on the Calc development page (bottom). Thanks for the guidance, hopefully I (and maybe others) can complete the list soon and then decide if/when/how to start getting the most important functions implemented. Thanks again all, Joel On Fri, Jul 13, 2012 at 12:21 PM, Eike Rathke er...@redhat.com wrote: Hi Joel, On Friday, 2012-07-13 09:00:28 -0700, Joel Madero wrote: I closed the bug as INVALID and put a comment on there. I also will move the list to the wiki, not sure where it's preferred to go or if I'm making a new wiki page. Thanks for the feedback Please create a new page, i.e. http://wiki.documentfoundation.org/Development/Calc/Spreadsheet_Functions and link to it from http://wiki.documentfoundation.org/Development/Calc For overview, in http://wiki.documentfoundation.org/Development/Calc/Spreadsheet_Functions also place pointers to the pages that Regina mentioned in this thread, so we'll have it all in one place. Thanks Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Excel Function Meta Bug?
Nice, the updates make it quite a bit more functional. I noticed that most of the really useful functions are already well on their way to being implemented. Those cube functions...I've never even heard of. Otherwise, I think the users list was not very accurate, I think he had 25+ functions, I found a total of 14. Thanks again, Joel On Tue, Jul 17, 2012 at 12:57 PM, Eike Rathke er...@redhat.com wrote: Hi Joel, On Tuesday, 2012-07-17 08:36:22 -0700, Joel Madero wrote: I've started the page. You can find information on the Calc development page (bottom). Thanks for the guidance, hopefully I (and maybe others) can complete the list soon and then decide if/when/how to start getting the most important functions implemented. Thanks for getting this started, I took the freedom and fiddled with it ;-) Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: Excel Function Meta Bug?
I closed the bug as INVALID and put a comment on there. I also will move the list to the wiki, not sure where it's preferred to go or if I'm making a new wiki page. Thanks for the feedback Joel On Fri, Jul 13, 2012 at 8:56 AM, Eike Rathke er...@redhat.com wrote: Hi Joel, On Wednesday, 2012-07-11 15:53:07 -0700, Joel Madero wrote: I'd like to make a meta bug for functions that Excel has but that aren't currently supported or are problematic in Calc. This stems from FDO 47164: https://bugs.freedesktop.org/show_bug.cgi?id=47164 Taking Regina's answer this actually was about https://bugs.freedesktop.org/show_bug.cgi?id=46918 For my takes on this topic see the mail I just sent to you and the QA list. And now we have the situation that cross-posting to multiple lists isn't always a good idea because each list doesn't know how things evolve on the other list, as answers on the QA list apparently did not include the dev list and vice versa. So, I'm including my answer here again: | On Friday, 2012-07-13 07:46:36 -0700, Joel Madero wrote: | | Thanks for responding Eike. Summary is that I was bug triaging and came | across a bug that had a list of functions in excel that are currently not | supported in LO. | | Cross-reading the dev list I found | https://bugs.freedesktop.org/show_bug.cgi?id=46918 | with a nice attachment listing functions. | | 1. Leave excel bugs as is, keep that bug open with the list of functions, | in the comments I'll confirm individual functions as problematic in LO | (harder to track progress, harder for devs to pick up individual functions | out of the list) | | Better close the bug that otherwise would live for months and years and | end up with 300 comments or so that no one would read anyway.. better | add the there attached list (that would be outdated already after the | first function was implemented) to the wiki from which individual bugs | or implementation notes could be linked then. Such implement dozens of | features bugs weren't helpful at any time. | | 2. Leave excel bugs as is, close bug that has so many functions in one, | tell user that we need them as individual bug reports (easier to track | progress this way) | | We really don't need dozens of bugs open one for each function not | implemented. I'd rather prefer to open a bug for a specific function | only once a developer starts to implement it so we can (discuss if | necessary and) refer it in the commit summary when done. Also, if users | open bugs for functions they actually miss in their daily work it helps | us more than doing that ourself in advance for all functions we know. | | 3. Make a meta excel bug just for the functions, then I'll create | individual bugs for each bug listed by the user and make the meta bug | dependent on them (similar to most annoying) | | See above about my take on creating individual bugs, plus I don't see an | advantage in having a meta bug for this unless it would be there to have | a quick listing of its dependents. | | 4. Make a meta excel bug, separate the function bug into individual bug and | make meta bug dependent on ALL excel bugs (not just the functions one from | the original FDO) | | We might also use something like an interoperability whiteboard keyword | or some such to query for instead. | | Well, you may have deduced from my answers that I'm not a friend of meta | bugs, unless they are there to mail a pointer to the dev list like the | most annoying meta bugs. In short, it's ok for me if QA wants to create | a meta bug to track existing things, but opening a bunch of bugs to be | tracked just for the sake of having everything in that we _might_ want | to implement over time of years doesn't make sense to me. | | Michael CC'ed you on it because he said you're currently the go to for | excel compatibility. My argument is that anything to make it easier to be | fully compatible with Excel is a plus if the goal is to convince MS Office | users that we can provide a better product than MS can. | | Specifically when having dozens of bugs open for functions that only | a very minority of users would use anyway it would be counterproductive | pointing potential users to deficiencies they otherwise would even never | have noticed or heard of ;-) Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice-qa] Excel Function Meta Bug?
Thanks for responding Eike. Summary is that I was bug triaging and came across a bug that had a list of functions in excel that are currently not supported in LO. I wanted input from QA and Devs to see what the best approach is. The options I came up with: 1. Leave excel bugs as is, keep that bug open with the list of functions, in the comments I'll confirm individual functions as problematic in LO (harder to track progress, harder for devs to pick up individual functions out of the list) 2. Leave excel bugs as is, close bug that has so many functions in one, tell user that we need them as individual bug reports (easier to track progress this way) 3. Make a meta excel bug just for the functions, then I'll create individual bugs for each bug listed by the user and make the meta bug dependent on them (similar to most annoying) 4. Make a meta excel bug, separate the function bug into individual bug and make meta bug dependent on ALL excel bugs (not just the functions one from the original FDO) Michael CC'ed you on it because he said you're currently the go to for excel compatibility. My argument is that anything to make it easier to be fully compatible with Excel is a plus if the goal is to convince MS Office users that we can provide a better product than MS can. Thanks for the feedback, Joel On Fri, Jul 13, 2012 at 4:42 AM, Eike Rathke er...@redhat.com wrote: Hi, On Thursday, 2012-07-12 16:20:37 +0100, Michael Meeks wrote: On Wed, 2012-07-11 at 23:03 -0700, Joel Madero wrote: I tend to agree and disagree. I think that ultimately it could dampen creativity but we have to consider some of the facts: Heh - well, there is ongoing work to make us more interoperable. Last I looked there were some patches on the dev list in this vein. I would ask the developers in that area eg. Eike whether they want to have to deal with the hassle of managing dozens of bugs in this area; AFAICS that is unlikely to improve their productivity, even if it tracks the current state better :-) But of course if they want that / would find it helpful that's fine. I love being suddenly Cc'ed on threads of a mailing list I'm not subscribed to.. so, what's this about? Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Excel Function Meta Bug?
I closed the bug as INVALID and put a comment on there. I also will move the list to the wiki, not sure where it's preferred to go or if I'm making a new wiki page. Thanks for the feedback Joel On Fri, Jul 13, 2012 at 8:56 AM, Eike Rathke er...@redhat.com wrote: Hi Joel, On Wednesday, 2012-07-11 15:53:07 -0700, Joel Madero wrote: I'd like to make a meta bug for functions that Excel has but that aren't currently supported or are problematic in Calc. This stems from FDO 47164: https://bugs.freedesktop.org/show_bug.cgi?id=47164 Taking Regina's answer this actually was about https://bugs.freedesktop.org/show_bug.cgi?id=46918 For my takes on this topic see the mail I just sent to you and the QA list. And now we have the situation that cross-posting to multiple lists isn't always a good idea because each list doesn't know how things evolve on the other list, as answers on the QA list apparently did not include the dev list and vice versa. So, I'm including my answer here again: | On Friday, 2012-07-13 07:46:36 -0700, Joel Madero wrote: | | Thanks for responding Eike. Summary is that I was bug triaging and came | across a bug that had a list of functions in excel that are currently not | supported in LO. | | Cross-reading the dev list I found | https://bugs.freedesktop.org/show_bug.cgi?id=46918 | with a nice attachment listing functions. | | 1. Leave excel bugs as is, keep that bug open with the list of functions, | in the comments I'll confirm individual functions as problematic in LO | (harder to track progress, harder for devs to pick up individual functions | out of the list) | | Better close the bug that otherwise would live for months and years and | end up with 300 comments or so that no one would read anyway.. better | add the there attached list (that would be outdated already after the | first function was implemented) to the wiki from which individual bugs | or implementation notes could be linked then. Such implement dozens of | features bugs weren't helpful at any time. | | 2. Leave excel bugs as is, close bug that has so many functions in one, | tell user that we need them as individual bug reports (easier to track | progress this way) | | We really don't need dozens of bugs open one for each function not | implemented. I'd rather prefer to open a bug for a specific function | only once a developer starts to implement it so we can (discuss if | necessary and) refer it in the commit summary when done. Also, if users | open bugs for functions they actually miss in their daily work it helps | us more than doing that ourself in advance for all functions we know. | | 3. Make a meta excel bug just for the functions, then I'll create | individual bugs for each bug listed by the user and make the meta bug | dependent on them (similar to most annoying) | | See above about my take on creating individual bugs, plus I don't see an | advantage in having a meta bug for this unless it would be there to have | a quick listing of its dependents. | | 4. Make a meta excel bug, separate the function bug into individual bug and | make meta bug dependent on ALL excel bugs (not just the functions one from | the original FDO) | | We might also use something like an interoperability whiteboard keyword | or some such to query for instead. | | Well, you may have deduced from my answers that I'm not a friend of meta | bugs, unless they are there to mail a pointer to the dev list like the | most annoying meta bugs. In short, it's ok for me if QA wants to create | a meta bug to track existing things, but opening a bunch of bugs to be | tracked just for the sake of having everything in that we _might_ want | to implement over time of years doesn't make sense to me. | | Michael CC'ed you on it because he said you're currently the go to for | excel compatibility. My argument is that anything to make it easier to be | fully compatible with Excel is a plus if the goal is to convince MS Office | users that we can provide a better product than MS can. | | Specifically when having dozens of bugs open for functions that only | a very minority of users would use anyway it would be counterproductive | pointing potential users to deficiencies they otherwise would even never | have noticed or heard of ;-) Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[PATCH] fdo#47164: Start Center: Recent Documents picker can not be reached right third of separate button area
There is some repetition of code in the patch because I had to separate the recent documents hotspot from the recent documents symbol -- before they were both held within a single rectangle which caused problems when trying to increase the size of the hotspot. If there's something better that I can do let me know and I'll get it done ASAP. Thanks all Joel 0001-fdo-47164-Shifts-recent-doc-symbol-shifts-and-expand.patch Description: Binary data ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Excel Function Meta Bug?
Hi All, I'd like to make a meta bug for functions that Excel has but that aren't currently supported or are problematic in Calc. This stems from FDO 47164: https://bugs.freedesktop.org/show_bug.cgi?id=47164 The user has been nice enough to make a list, I can go one by one and verify that Calc isn't supporting, create an individual enhancement request for the function and then link it to the meta bug. Any opinions on this one? Appreciate the feedback. Joel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-qa] Excel Function Meta Bug?
Hi All, I'd like to make a meta bug for functions that Excel has but that aren't currently supported or are problematic in Calc. This stems from FDO 47164: https://bugs.freedesktop.org/show_bug.cgi?id=47164 The user has been nice enough to make a list, I can go one by one and verify that Calc isn't supporting, create an individual enhancement request for the function and then link it to the meta bug. Any opinions on this one? Appreciate the feedback. Joel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-ux-advise] FDO 47164 (increase backing window recent doc hot spot) Advice
Hi All, I've handled FDO 47164 but need input to see if we'll actually implement. Summary: User thinks that recent documents arrow hot spot is too small on our backing window Solution: I moved the horizontal bar to the left a bit and increased the arrow size quite a bit. Here is a before: https://picasaweb.google.com/117397839011853181951/LODevelopment#5764020605655926498 and After: https://picasaweb.google.com/117397839011853181951/LODevelopment#5764020604014127250 I'm not sure if we want to implement this at all, and if so if I went too big. Advice welcome, I'll either close the bug as WONTFIX or submit a patch as soon as we get some feedback. Joel ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
Re: [Libreoffice-ux-advise] FDO 47164 (increase backing window recent doc hot spot) Advice
Made then public. Sorry about that On Jul 11, 2012 2:46 PM, Philipp Riemer ruderphil...@gmail.com wrote: 2012/7/11 Joel Madero jmadero@gmail.com: Hi All, I've handled FDO 47164 but need input to see if we'll actually implement. Summary: User thinks that recent documents arrow hot spot is too small on our backing window Solution: I moved the horizontal bar to the left a bit and increased the arrow size quite a bit. Here is a before: https://picasaweb.google.com/117397839011853181951/LODevelopment#5764020605655926498 and After: https://picasaweb.google.com/117397839011853181951/LODevelopment#5764020604014127250 I'm not sure if we want to implement this at all, and if so if I went too big. Advice welcome, I'll either close the bug as WONTFIX or submit a patch as soon as we get some feedback. Joel Hi Joel, I tried opening the links but Google tells me that the pages do not exist. Is it maybe a private album...? Cheers, Philipp ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
