[libreoffice-projects] Does wiki want to come out and play?
Hello, I spent the last week with setting up our new wiki. I've copied all articles, users and most configuration settings, and enhanced them, based on the recent MediaWiki version. What is currently missing: - multiple languages - caching (thus it might be slow) - autopromoting/autoconfirming (spam protection) - WYSIWYG editor (there exists none) I've also enhanced spam protection, but that might trigger false alerts. So, what I'd like as feedback from you now is: - bugs and problems - feature and extension requirements - proposals on what to change Please check your favorite page if it renders allright, please check if all the functions work, and if any of the newly-introduced limitations for spam protection interrupt with your productive work and of course, let me know, what functionality you are missing, since now is the best time to include it. One word of warning, I can't emphasize that enough: This wiki is for TESTING PURPOSES only. Users, articles and settings - in other words: ANYTHING - created here WILL be deleted when the testing is over. There are NO backups. Content WILL break. Do NOT use this wiki for anything productive. So, after you've read all those warnings :) here you get the URL for testing: http://wikitest.documentfoundation.org Please direct feedback to webs...@global.libreoffice.org Thanks a lot for your support, and looking forward to migrationg to the new wiki soon, Florian -- Florian Effenberger, Chairman of the Board (Vorstandsvorsitzender) Tel: +49 8341 99660880 | Mobile: +49 151 14424108 The Document Foundation, Zimmerstr. 69, 10117 Berlin, Germany Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts Legal details: http://www.documentfoundation.org/imprint -- Unsubscribe instructions: E-mail to projects+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] Minutes of the ESC call 2012-10-04
Attending: Fridrich, Thorsten, Lionel, David Tardon, Stephan, Markus, Andras, Joel, Radek, Eric, Eike, Cedric, Björn, Astron, Michael S, Norbert, Michael M, Kohei, Kendy * Completed Action Items + simplify / improve the QA / debugging page (Michael M) https://wiki.documentfoundation.org/BugReport#Providing_extra_information_for_the_developers + many thanks to Petr for the pretty wrapper wins. + issues to look into if we can + HH: fdo#44278 picture duplication on save (Cedric) + now back-ported to 3.6 + HH: fdo#47283 - writer undo / change-tracking interaction (Michael S) + HHL fdo#46100 - calc undo / delete sheet crash (Markus) + fdo#54225, fdo#54744 PDF export regressions (Stephan) + fdo#53673 - Labels broken with mailmerge (Winfried Donkers) + https://gerrit.libreoffice.org/#/c/502/ (Bjoern to review) + superseded by patch 629 ibid. + change to contract and OSL_TRACE for oob results in OUString::copy (Michael) + make bytemark windows box do release builds (Fridrich) + complete but takes 24 hours + gerrit add: private//branches (Norbert) * Pending Action Items + Petr to decide release-schedule / overlap gap issue + create a new AmbitiousHacks wiki page, based on GSOC page (Michael M) + [in progress] enable automatic help build / sync. on a cron-job (Kendy) + script written, testing it for deployment + issues to look into if we can + fdo#34548 - review Michael's patch (Thorsten) + fdo#55290 - master doesn't install on windows (dtardon) + fdo#55360 - mac specific text issue (Thorsten) * Release Engineering update (Fridrich) + vacation / quality report (deferred - Petr sadly ill) + 3.6.2 retrospective + released + should we enable on-line updates to 3.6.2 ? + accidentally skipped / discuss next week. + 3.5.7 retrospective + rc2 uploading, needed because of crasher docx regression + more lenient since 3.5.7 being last scheduled release * 3.6.3 rc1 + monday deadline for fixes + branch on tuesday - then three reviews + tinderboxes on -3-6 over weekend + reconsider schedule on monday * UI / design update (Astron) + unchanged + no chat last week * Saxon split-out (DTardon) + xslt export filters (java, saxon based) + new one, baed on libxslt (written by peter) + for possible backward compat, still ship saxon + drop saxon from install + don't know if anybody needs it - put it into extension + where to put the extension ? + package on extensions.libro + source code outside core repos + decision: David to go ahead with this * conference (Thorsten) + in-person ESC meeting 16th October, 17:00 at the venue. + topics for an extended agenda appreciated ... + your pitch for sanity here :-) ** PLEASE REGISTER BEFORE OCTOBER 8TH ** + http://conference.libreoffice.org/@@register-for-the-conference + speakers please just enter "No" for have you paid; that is a valid option. AI: + folks without a hotel - mail thb / sweetshark (for couchsurfing/rooms) * git submodules / rename (Norbert) + code-wise done, features/submodules branch + does it work when you go across the migration? + testings appreciated! + doc writing in progress + once doc is done, when to do that? + each of the four repos - rename files in all submodules - that means, if you have a patch, across the boundaries, you need to manipulate the patch + proposed submodule migration at the conference. * bibisect goodness (Norbert) + experimented on mac, collected every build on mac, 900 builds, resulting repo is 2.1G -> too big + collect only once a day + collecting the windows ones too + 700M - builds are less frequent + an advanced QA / user is able to bibisect it down to 50 commits * sysadmin contract / work ... AI: + ping Tollef (Bjoern) * distro/suse/suse-3.6 branch: input appreciated (Kendy/Michael) + want to get our product work into public git + all patches are upstreamed anyway, but this makes things better for all + since it's the same code - branch should be small size-wise + problem: lots of tags for customer / PTF builds - 20-30 tags per release + is that ok ? concerned about amount of tags ? + normally people don't get the tags (Norbert)
[libreoffice-projects] minutes of the LibreOffice QA call 2012-10-05 (today) 1300UTC
Hi, Here are the minutes of the QA call today. attendance: Thorsten, Joel, Bjoern pending action items: - merge 3.5 and 3.6 in one big bibisect repo (Bjoern) - recheck and tweak bibisect details (Bjoern) - Ping cloph if we can make that switchable to say "Bug" instead of "EasyHack" when explcitly requested (Bjoern) - new Bug Hunting Sessions (Cor) completed action items: - setup hard hack wiki page (Joel) structured manual testing (Yifan/Petr): - no news bug wrangling: - no new hardhacks needed this week - open/closed hardhack overview AI: - add closed hard hacks to wiki (Joel) AI: - blog about it (Bjoern) AI: - lead Joel to get his blog on the planet, once he has one (Bjoern) - triaging project update (Joel) - we should poke native lang team (Thorsten) AI: - poke Sophie about triaging (Bjoern) - bugzilla contract updates -> postponed, call next week community building/communication (Joel/Florian?) - QA Wochenende in Essen - need more people - few newcomer - bibisect for windows very popular - ping Norbert to go forward with it - timebased releases still perceived as a problem - stable is essentially blocked -- it is open for half a year for critical bugs only and hard hacks are the way to communicate those to development without overcommitment (Thorsten/Bjoern) - more testers of master/3.x.0 needed - marketing storm always hits 3.x.0 - has to be stable enough to prevent backslash - needs to be announced at this point in time to allow early adopters bugreporting - auto updater (Windows) - initial troubles should be solved now - activate for which minor? 3.x.2/3.x.3 - maybe offer a update button without popup for early-adopters in addition (pull-model on request, push at .2/.3) (Bjoern) - BSA API - some reservations: - we have no trouble with the number of initial bug reports - too easy bugfiling lowers the quality of reported bugs, creating even more work for bugwranglers - we are in need of bug wranglers, not so much reporter - most of 'too late bugs' are not 'not reported', but 'not visible to dev as a critical bug' - instead, we should create a landing page on the end of the BSA? - invite people to: - confirm bugs - verify fixed bugs (mostly to motivate more people into running master) - maybe even have a menu entry in About for that? Best, Bjoern -- Unsubscribe instructions: E-mail to projects+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
