xwiki-devs April 2012

xwiki-devs@xwiki.org

31 participants
86 discussions

[xwiki-devs] [Proposal] XWiki Days every month?

by Vincent Massol

Hi devs, We've had several special days in the past: * Deprecation day ** 26 April 2012: http://markmail.org/thread/c5oytyvgw6fcimqq * Bug fixing days: ** 11 june 2008: http://xwiki.markmail.org/thread/oyfxis3umqrvutxm ** 18 June 2008: http://xwiki.markmail.org/thread/brfx6gme37vgr3m5 ** 25 Jun 2008: http://markmail.org/message/nrobo3x4ppgssklk ** July 2008: http://xwiki.markmail.org/thread/mn5veblndbtgcsm5 ** 10 Feb 2011: http://xwiki.markmail.org/thread/rierrb2wk72dkpqy and result http://www.xwiki.org/xwiki/bin/view/Blog/BugFixingDayFebruary2011 * DocHour days: ** 5 March 2008: http://xwiki.markmail.org/thread/dyypju5dn23wkwr2 I think it's a good concept and I'd like to propose that we regularly (once every month?) have an XWiki Day. Ideas for such days: * Bug fixing day: Reduce bug count * Doc day: improve xwiki.org * Deprecation day: reduce # of deprecated calls. Around 1700: http://nemo.sonarsource.org/drilldown/violations/XWIKI?&rule=squid%3ACallTo… * Violation day: reduce # of violations. 10274 right now: http://nemo.sonarsource.org/drilldown/violations/XWIKI * Javadoc Day: Add missing javadocs in our code and remove checkstyle excludes * Code Coverage Day: Add as many tests as possible (unit and functional) * Broken Links Day: fix as many broken links as possible on xwiki.org. To find them is easy: we just need to enable the IRC Link Checker botlet and wait on IRC to get them! I propose that whenever a day is over, we send a mail with the Date and Topic for the next day and it has to be about 1 month from the date of the mail. To get this started I volunteer to be responsible for sending Day emails for now, unless someone else is interested to do this. WDYT? Thanks -Vincent

11 years, 11 months

[xwiki-devs] XWiki WebDAV for MSOffice read-write mode

by bouderbala＠nearbee.com

Hello all, I would like to use XWiki WebDAV for editing MSOffice documents online To do this in read-write mode, we must configure XWiki WebDav on ROOT. Instead of opening the document from: http://myserver.test/xwiki/webdav/spaces/test/msoffice/Bonjour.docx we must open it from: http://myserver.test/spaces/test/msoffice/Bonjour.docx This is what I did: - I am running Tomcat 7 / XWiki Enterprise V2.6 - I renamed the ROOT context xwiki - I changed the servlet-mapping like this <servlet-mapping> <servlet-name>webdav</ servlet-name> <url-pattern>/*</ url-pattern> </ servlet-mapping> Now I can't even request the document http://myserver.test/spaces/test/msoffice/Bonjour.docx I have response: HTTP Status 400 - Bad Request Is there any solution XWiki WebDAV to open MSOffice in read-write mode ? Thanks in advance

12 years, 1 month

[xwiki-devs] Pretty Time library

by Vincent Massol

Could be useful: http://ocpsoft.com/prettytime/ Idea of usage: For ex we could use that to show the last modified document dates for dates in the past week (for ex): "Document created 2 days ago" It's in the maven central repo and it's under LGPL -Vincent

12 years, 1 month

[xwiki-devs] [Prooposal] Roadmap for XE 4.1

by Vincent Massol

Hi devs, Roadmap time again for 4.1. Here's a proposal below. If you're a committer/contributor and wish to propose doing something for 4.1 please reply to this thread to have a complete roadmap. For committers who have their names next to tasks below, please confirm you're ok to do that for 4.1. Dates ====== * Started since 16th of April * 4.1M1: 7th of May * 4.1M2: 28th of May * 4.1RC1: 11th of June * 4.1Final: 18th of June Release manager: Caleb, with help from Sergiu/Vincent Content ======= XWiki SAS has had an internal meeting to discuss what it would like to work on and here's the result as a proposal: Top level tasks: * Extension Manager (XEM compatibility, XAR merge UI, full XAR upgrade) - Thomas and Marius ** The goal is to be able to "upgrade a wiki farm in 5 minutes" for 4.1 final * Hidding Technical Content - Jean-Vincent * Important JIRA issues - Sergiu and anyone having some time, see below for the priority list Investigations: * Home Page Changes Proposals - Caty Misc: * GSOC mentoring - All mentors First priority JIRAs (no order): * Add the ability to auto-generate application entry names XWIKI-7374 * Properly display live table columns based on User-type class fields XWIKI-7372 * Be able to rename a space from the UI XWIKI-6722 Second priority JIRAs (no order): * Add Required and Hint meta properties for class fields XWiki-7373 * Generate and register a document bundle for the application XWIKI-7371 * Add document title and document content to the field palette (class editor) XWIKI--7369 * Use suggest input (custom display) for User and Group field types (class editor) XWIKI-7368 * Rename Application (through rename space) XWIKI-6722 * OpenOffice Issues on Windows (bug) XWIKI-7510 * Cannot filter using "/" on a Date column in the livetable XWIKI-5889 * Auto-create Space.WebHome when creating a page in an underfined space XWIKI-5399 * New XWiki Syntax Guide XE-880 * Occasionally the livetable fails to load on index pages XE-844 * tag suggest feature does not work if Main.WebHome is not saved with programming rights XE-539 * Fix XWiki Installer on Windows 7 XE-1051 * XWIKI-6073 Change stylesheet and javascript extension filename when a modification is done on those Unassigned Third priority (no order): * Add more/all configuration parameters in the wiki administration XWIKI-7066 * XWIKI-7510 XWiki is not able to automatically start OpenOffice daemon on Windows Server Unassigned * XWIKI-7509 XWiki automatically connect to an external openoffice daemon Unassigned * XWIKI-7058 Page creation date should be the date of the installation Unassigned * XWIKI-6951 When using filesystem attachments with attachment versioning disabled, deleted attachments are duplicated on the hard disk. CalebJamesDeLisle * XWIKI-6917 Deleted attachments duplication in recycle bin while File Storage is on CalebJamesDeLisle * XWIKI-6892 Log-in automatically on registration Unassigned * XWIKI-6569 Problems displaying the correct attachment version when using a proxy Unassigned * XWIKI-6363 Performance of blog category panel is still not enough Unassigned * XWIKI-6207 Auto-suggest doesn't work for global users Unassigned * XWIKI-5949 Better handling of different timezones for date properties Jean-Vincent Drean * XWIKI-5930 Activity Stream doesn't show Image Profile change Unassigned * XE-1031 Better placement of the documentation link Unassigned * XE-748 Add option to 'show more entries' on displaying the Activity Stream Unassigned WDYT? Thanks -Vincent

12 years, 3 months

[xwiki-devs] context.language having wild values?

by Paul Libbrecht

Hello developers, We had some (rare) users that had a very bad issue because we told their browser to load the lang_xx.js of their language. And their language was... wild! See: http://jira.xwiki.org/browse/CURRIKI-5694 for a sample of the things that got submitted to us. Sure, we'll now protect against these bizarre languages, still, there might be other things broken. Is there some guarantee on the set of possible languages provided by $context.language? I was expect the possible values of ISO-623-1 but that was clearly not sufficient! paul

12 years, 3 months

[xwiki-devs] [proposal] New way to make sure temp files are deleted.

by Caleb James DeLisle

Hi, In order to fix XWIKI-7748 and XWIKI-7749, we need a plan for deleting temporary file. XWikiAttachmentContent uses File.deleteOnExit(), but in Sun's implementation, deleteOnExit() only deletes on a *clean* exit, in a crash it can't delete the files but it doesn't tag them so they can be deleted in the next run either. Since temp files are usually pseudo-randomly named, they are impossible to find and delete later. I propose that we create a subdirectory, `java.io.tmpdir`/xwiki/ which will be removed on application exit. If the jvm crashes, the files will be removed next time around. Then alter ApplicationContext.getTemporaryDirectory() to yield this directory. WDYT? Caleb

12 years, 3 months

[xwiki-devs] [VOTE] Improving documentation and automating our Release Notes when doing releases

by Vincent Massol

Hi devs, Sergiu has started a script to fully automate a release (more to come - Sergiu will document what it does soon). The only part not automated are the Release Notes. IMO we can "automate" it by a process which I propose to be: * An issue can only be closed if it's documented on xwiki.org and on the release notes page for the upcoming release. * We collectively enforce this by reopening issues if someone doesn't do the first point, asking him/her to do it This will have some nice effects: * xwiki.org will be more up to date than it is now * it's up to the developer to document what they do (I don't think it's good to push this to someone else) which is good since they have the most knowledge (side note: it doesn't mean we don't need a technical writer to improve on the documentation done by developers but it would be about style and not about content) * the release notes will be ready for the release, as we progress and the burden of writing the release notes will not fall on the shoulders of the Release Manager (there's no reason it should) * the whole release process will almost be a joy to do * with a fully automated release process it means we'll be able to perform a lot more bugfix releases which is good for our users Here's my +1 Thanks -Vincent

12 years, 3 months

[xwiki-devs] [GSoc] Advanced Email Integration

by Vincent Massol

Hi everyone/Jerem, I've seen that we've added the following GSOC project: http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/AdvancedEmailIntegra… This looks quite similar to what Jerem is working on. Jerem, maybe you could tell us a bit more about your project and how it's similar/different than this GSOC. Jerem, any timeframe for a first version of your project to be visible? Is this something you're developing for yourself or do you plan to give it to the community or even to the XWiki project? I'd like to clarify this to know how to best organize this project to not duplicate efforts too much and instead to combine synergies. Thanks -Vincent

12 years, 3 months

[xwiki-devs] Some difficulties with unit testing ...

by jerem

Hello, Seems I did not understand everything about how to write unit tests ... Here's my problem : I want to test a class MA, a component, that has the following code (excerpt) : My test class MATest contains : Here I'm looking up the Execution in order to set expectations on it for the initialize to pass. Problem is that I'm still getting this at test execution : It seems that my initialize() method is called at lookup(), so how could I set-up the expectations before they're actually exercised ? : Thanks for help, Jeremie -- View this message in context: http://xwiki.475771.n2.nabble.com/Some-difficulties-with-unit-testing-tp749… Sent from the XWiki- Dev mailing list archive at Nabble.com.

12 years, 4 months

[xwiki-devs] An appeal for insight into the development of XWiki

by Martin Schönberger

Dear developers of XWiki! I am a student of Software Engineering at the Vienna University of Technology and currently writing my master thesis on project management and the development methods used in open source projects. In my research I analyzed open source development and compared it with elements found in various proprietary approaches, both agile and well-defined. But to provide balanced and up-to-date results my work relies on first- hand information and expert opinion, for which I need your help. XWiki matches my criteria regarding size, activity and available information and I would be glad to include it in my case study. I am looking for an interview partner with good insight into the project structure and a solid overview of all stages of development, ideally a member of the core team with long-term dedication to the project. The interview would take about 20 minutes on Skype (or a similar phone- based tool). If you prefer a written chat, that can be arranged as well. My daily schedule is flexible, so whatever time suits you best should work for me. The subject areas I would like to cover in the interview are XWiki's: * Development flow and release cycles * Social structures, responsibilities and decision making * Code structure and architectural considerations * Special conditions caused by the open source environment I realize your time might be scarce, but if you decide to contribute to this case study your help shall be all the more appreciated. Once finished I will gladly share my results and any new insights gained on the topic with you. Kind regards, Martin Schönberger (maschonber(a)gmail.com)

12 years, 4 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs April 2012