Re: [Libreoffice-qa] And then there were two...
Hi, On Wed, Jan 28, 2015 at 08:01:34AM -0500, Robinson Tryon wrote: On Wed, Jan 28, 2015 at 7:42 AM, David Tardon dtar...@redhat.com wrote: Of course, these are not the only products we have... From the top of my head, there are: * DLP Oh, definitely! DLP is one of the primary reasons why I wanted to make sure it was the TDF Bugzilla, and not just the LibreOffice Bugzilla :-) - libabw - libcdr - libetonyek - libfreehand - libmspub - libpagemaker - libvisio The libraries are all versioned separately, right? I'm thinking: one product for each library, and a general 'DLP' product as a catch-all for everything else. That sound good? Yes, very good. * other - cppunit - libexttextcat - libgltf And one each for these, I assume? Yes. D. ___ 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] minutes of ESC call ...
* Present: + Stephan, Christian, Michael M, Cedric, Sophie, Thorsten, Eike, Miklos, Andras, Kendy, Fridrich, Bjoern, Caolan, Markus * Completed Action Items: + fix BSA login / XML-RPC issues (Cloph) [ login is fixed, but adding attachments still needs some work, can't use auto-detection of type via XML-RPC perhaps better to use the guided-bug-entry skin, extend that https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOfficeformat=guided ? ] + ask Fridrich, Cedric wrt. GSOC leadership etc. (Kendy) [ both ready to administer it ] + remove the 'EasyHack' piece from anything 2yrs old (Bjoern) [ some of them cleaned up ] * Pending Action Items: + please file an Easy-Hack this week: just a bug with whiteboard: (All) EasyHack DifficultyBeginner SkillCpp TopicCleanup + thanks to: + Stephan, Michael, Lionel, Ashdod, Miklos, + http://bit.ly/1Dd4y8b + review / amend GSOC ideas page (All) + https://wiki.documentfoundation.org/Development/GSoC/Ideas + look into setting up OpenID proxy after 4.4.0 release (Cloph) * GSoC (Cedric) + We need to have new ideas added to the wiki page: https://wiki.documentfoundation.org/Development/Gsoc/Ideas + sooner the better etc. preferably before FOSDEM: today / tomorrow. + February, 9th: Mentoring organizations can begin submitting applications to Google. + we need a good page by then. + admin vs. mentoring GSOC travel. + title: Mentor summit (Thorsten) + precisely 2x slots, and historically those were for admins. + who at the same time did mentoring. + never happened that a non-mentor went (Fridrich) * Release Engineering update (Cloph) + 4.4.0 retrospective + released as final; but overshadowed by website down-time. + currently only a maint-page, that directs to mirror-brain + will be fixed in the next 10mins or so. + why does mirror-brain work ? (Cloph) + extremely slow adding releases to MySQL database to avoid partial download page completeness; disabled. + 4.3.6 RC2 + built for Linux / Mac so far. + holding off until glustre FS heals itself, to avoid new I/O load. + Android iOS Remote + patches in gerrit status ? * Bugzilla migration update (Cloph) + retrospective + went really well. + initially a long-running query blocked others + if we have queries that time-out, poke Cloph to extend. + was a mis-configuration; now fixed. + pretty flawless - just works (Michael) + one issue in redmine (Bjoern) + while you can't file new bugs anymore, you can reply via E-mail + not many people doing that; the inexperienced users. + might be an issue for a few days, will prolly stop in a month. + impressed that the esc bug scripts still work (Michael) + we should now use tdf#12345 for bugs in commits + thanks to moggi for the fix. * Translations problems (Sophie) + big chunk of translations for 4.4, to change our workflow to work on master instead of branches; so we can get visibility into that sooner and smooth the workload out. + 3x points on the dev. side. 1. ensure respect the en_US strings follow rules for sentance capitalization [ https://developer.gnome.org/hig-book/3.2/design-text-labels.html.en we re-use the GNOME HIG here ] saves thrash that hurts translators. 2. don't commit changes eg. appending '...' to menu items please discuss this with l10n before big-impact changes. + UX type thing (Kendy) + proposal from translators; make en_US a separate lang. touch the strings in the repo - as minimally as possible; + don't think this will work long-term; will need to improve what we have in the repo. + proposal is a tech. sol'n for a social problem. + for large-scale changes UX should talk to l10n first. + would be useful to have a l10n person in the UX call. + hopefully as/when everyone works on master, it is easy to see and have a tighter feedback cycle between the two teams. + UX QA calls at the same time (Sophie) AI: + sort out the calls (Kendy / Sophie) 3. changes that affect all languages can be scripted + eg. _ in dialogs; could have been scripted; would like that tested on several languages + scripts should be applied out of pootle. Is there a way to do that ? (Caolan) + hackers see a git repo - which is a copy of what is in pootle + it'd be good to allow
Re: [Libreoffice-qa] that walrus
Hi! Shouldn't it be stable-walrus and not lab-walrus? All went fine with the migration. Best regards. -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-that-walrus-tp4137990p4138131.html Sent from the QA mailing list archive at Nabble.com. ___ 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] that walrus
On Thu, Jan 29, 2015 at 2:16 PM, bfoman bfo.bugm...@spamgourmet.com wrote: Hi! Shouldn't it be stable-walrus and not lab-walrus? All went fine with the migration. :-) People liked the walrus with all the lab equipment, and requested that he stick around, so I left him there for now. (New incarnations very welcome -- ping me for source SVGs and so forth if you'd like to hop in and show off your skills or artistry! I'm getting on a plane soon, so it might take a little while before I can respond!) Best, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org ___ 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] that walrus
Bjoern, *, Wow, I like Antje--a nice tip of the hat to the StarDivision pioneers... So, does Robinson's caricature exhibit any resemblance to the original Antje? -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-that-walrus-tp4137990p4138161.html Sent from the QA mailing list archive at Nabble.com. ___ 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] suggestion for weekly-bug-summary
Hi, On Thu, Jan 29, 2015 at 03:13:18PM -0800, Joel Madero wrote: I agree that it would be good it is possible. I highly recommend we create a new product bugzilla where we can easily track these enhancement requests...else they are likely to get lost in the abyss. Nope. Bugzilla is Infra. Infra is on Redmine. Lets not make exceptions to exceptions. Its already complicated enough. see: https://redmine.documentfoundation.org/issues/1055#note-1 http://nabble.documentfoundation.org/TDF-bugzilla-bug-report-td4137958.html Still, creating enhancement suggestions _if_ they are reasonably ressourced, or the reporter commits him/herself to it is of course great. But that has to happen on Redmine. Best, Bjoern ___ 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] suggestion for weekly-bug-summary
Hi, On Thu, Jan 29, 2015 at 04:14:24PM -0800, Joel Madero wrote: I've never been a fan of this split to begin with. Having a much less visible means of suggesting enhancement requests or bugs pretty much just sucks. Just speaking for myself, I'm very unlikely to report any enhancement requests about bugzilla on redmine... Oh, hate the split too. The split will not go away easily though (I tried. Hard.). Yeah, sucks. Still, the best we can do now is have a clear cut rather than fractured border between the two. So we're only tracking enhancement requests if the reporter can either (1) do it themselves; or (2) they can show that it's reasonably resourced? I can't imagine a similar strategy working for LibreOffice itself - we might as well close 99% of enhancement requests. I don't get why we'd have two different philosophies just because one is infra and the other is something else? So, maybe Im overcautious. ;) As an exaggeration: There is a risk that we end up with 20 people working on making our Bugzilla nice and beautiful and 1 guy working on triaging LibreOffice. Also note that all customization cumulates to create extra pains during updates etc. IMHO we should just keep in mind to keep the fixed costs of running our Bugzilla constant and rather low[1]. Best, Bjoern [1] For example that we ended up with a Redmine/Bugzilla split (which is already a simplification over the mess we had before that) is ultimately a result of bit too much fast-and-loose play with extending, creating and customizing services. ___ 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] suggestion for weekly-bug-summary
On 01/29/2015 04:01 PM, Bjoern Michaelsen wrote: Hi, On Thu, Jan 29, 2015 at 03:13:18PM -0800, Joel Madero wrote: I agree that it would be good it is possible. I highly recommend we create a new product bugzilla where we can easily track these enhancement requests...else they are likely to get lost in the abyss. Nope. Bugzilla is Infra. Infra is on Redmine. Lets not make exceptions to exceptions. Its already complicated enough. I've never been a fan of this split to begin with. Having a much less visible means of suggesting enhancement requests or bugs pretty much just sucks. Just speaking for myself, I'm very unlikely to report any enhancement requests about bugzilla on redmine... see: https://redmine.documentfoundation.org/issues/1055#note-1 http://nabble.documentfoundation.org/TDF-bugzilla-bug-report-td4137958.html Still, creating enhancement suggestions _if_ they are reasonably ressourced, or the reporter commits him/herself to it is of course great. But that has to happen on Redmine. So we're only tracking enhancement requests if the reporter can either (1) do it themselves; or (2) they can show that it's reasonably resourced? I can't imagine a similar strategy working for LibreOffice itself - we might as well close 99% of enhancement requests. I don't get why we'd have two different philosophies just because one is infra and the other is something else? Best, 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] that walrus
On Fri, 30 Jan 2015 00:30:35 +0100, Bjoern Michaelsen bjoern.michael...@canonical.com wrote: Hi, On Thu, Jan 29, 2015 at 05:07:24AM +0100, Tommy wrote: hi there, I'm curious to know the name of that walrus mascot we have in our own bugzilla. so here are a few proposals: ... my proposal is Angus the Walrus ___ 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] suggestion for weekly-bug-summary
Hi Joel, Joel Madero wrote on 30-01-15 00:13: Would that be good possible? I agree that it would be good it is possible. Can I change add a query myself to that page? Cheers, Cor -- Cor Nouws GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134 80A6 - vrijwilliger http://nl.libreoffice.org - volunteer http://www.libreoffice.org - The Document Foundation Membership Committee Member ___ 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/
