xwiki-devs January 2006

xwiki-devs@xwiki.org

11 participants
11 discussions

by Hans Gerwitz

How can I turn off the "shortcut" URLs where /bin/Space/Page is interpreted as /bin/view/Space/Page? (Specifically, I'm using mod_redirect to clean up the URL architecture and need to assume that anything prefixed /bin that isn't /bin/view needs to be passed through as an action.) - - - Hans Gerwitz http://phobia.com/

17 years, 11 months

Re: [xwiki-users] Re: [xwiki-dev] bounty on XWiki?

by jeremi joslin

Hi, There is 2 possibilities about the payement: * first, Someone who propose the bounty is in charge of paying it at the end. * second, the one who propose the bounty pay first the prize for the bounty to a paypal account of XWiki. For me the second one is better, but you have to advance the money. And with the second possibility several people can make a donation to a bounty if they are interested in. some samples of rules : * http://www.os2world.com/bounties/rules.php * http://www.morphzone.org/modules/bounty/ * http://www.voip-info.org/wiki/view/Asterisk+bounty * https://wiki.ubuntu.com/BreezyBounties What do you think about this? I prefer the morphzone way to do it with ubuntu rules. Jérémi On 1/29/06, Stéphane Laurière <slauriere(a)mandriva.com> wrote: > Hi Jérémi, > > Introducing bounties for XWiki would be great, I think! > > Stéphane > > jeremi joslin wrote: > > Hi everyone, > > > > What do you think about enabling anyone to suggest bounty on XWiki ? > > > > Example: > > I need a script for listing all the page in the wiki who contain the > > word "hate". I don't know how to do it. I'm ready to pay 50$ for this. > > > > We need to define some rule, but what do you think about this idea? > > > > For example, ubuntu: > > http://www.ubuntulinux.org/community/bounties/ > > > > > > Jérémi > > -- > > Blog: http://www.jeremi.info > > LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724 > > http://www.xwiki.org > > skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com > > > > > > > > ------------------------------------------------------------------------ > > > > > > -- > > You receive this message as a subscriber of the xwiki-dev(a)objectweb.org mailing list. > > To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org > > For general help: mailto:sympa@objectweb.org?subject=help > > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > > > > > > > -- > You receive this message as a subscriber of the xwiki-users(a)objectweb.org mailing list. > To unsubscribe: mailto:xwiki-users-unsubscribe@objectweb.org > For general help: mailto:sympa@objectweb.org?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > > > -- Blog: http://www.jeremi.info LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724 http://www.xwiki.org skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com

19 years

XWiki community

by jeremi joslin

Hi, We want to change the way the community work. We want to create 2 groups: * One group of developer. A developer is a user who contributes to the project in the form of code or documentation. They take extra steps to participate in a project, are active on the developer mailing list, participate in discussions, provide patches, documentation, suggestions, and criticism. Developers are also known as contributors. (Definition from http://www.apache.org/foundation/how-it-works.html#roles) * One group of committer around XWiki. A committer is a developer that was given write access to the code repository. Not needing to depend on other people for the patches, they are actually making short-term decisions for the project. We also want to change the way to become committer on XWiki. Before becoming committer on XWiki, you have to "earn" the merit to be part of the development community. For those of you who are already committer on XWiki, you will keep this right if you want. You just have to send me a mail OFF LIST before the 9february to stay committer and tell me why you want to stay committer. We will write some rules to lead the project soon. what do you think about that? -- Blog: http://www.jeremi.info LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724 http://www.xwiki.org skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com

19 years

bounty on XWiki?

by jeremi joslin

Hi everyone, What do you think about enabling anyone to suggest bounty on XWiki ? Example: I need a script for listing all the page in the wiki who contain the word "hate". I don't know how to do it. I'm ready to pay 50$ for this. We need to define some rule, but what do you think about this idea? For example, ubuntu: http://www.ubuntulinux.org/community/bounties/ Jérémi -- Blog: http://www.jeremi.info LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724 http://www.xwiki.org skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com

19 years

In the road of XWiki Beta1

by jeremi joslin

Hi all, OK, I've finish to review all XWiki task. (not XWiki applications for the moment.) You can see the Road Map: http://jira.xwiki.org/jira/browse/XWIKI?report=com.atlassian.jira.plugin.sy… Do you agree with this Road Map? We will need your help to fix all bugs and do all tasks to produce a powerful XWIki 1.0. - Jérémi -- Blog: http://www.jeremi.info LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724 http://www.xwiki.org skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com

19 years

Proposal: XWiki Maven2 migration

by Zhong ZHENG

Hi the XWiki Team, I found in the mailing list archives that you are planning to use maven to build xwiki. I am a committer to the apache pluto project, which uses maven2. Thus i got some experience on maven 2. (Mr. Vincent Massol must be a maven master, since he is on the maven team :) I would like to help you migrate to maven. I checked out the xwiki source from subversion, and am trying to re-organize the project layout and create pom.xml files. Currently i am still dealing with the dependencies. I would like to propose to separate the xwiki project into small subprojects, and decouple the APIs from the implementation (such as user api and different implementations, plugin api and different plugin implementations, etc.). That will make the source more clear and more readable. I don't know how to help on this topic. Re-organizing the project layout introduces too many modifications on the project, which may have a lot of impacts on the current development, and it's difficult to generate svndiff and create patches. I would like to know if it is possible to apply for joining the dev team and create a new branch in svn for the maven migration. I am taking a look at the JCR spec currently, since I created a java wiki engine project ( http://people.apache.org/~zheng/elsie/<http://people.apache.org/%7Ezheng/elsie/>) and am thinking of refactoring it using JCR and apache jackrabbit. I found that you are also planning to implement the xwiki repository using JCR. I would like to help and contribute to this subproject too. Best regards. -- ZHENG Zhong - http://heavyz.blogspot.com/ - http://people.apache.org/~zheng/ <http://people.apache.org/%7Ezheng/>

19 years

XWIKI-177 marked "Won't fix"

by Stephen Schaub

I noticed that XWIKI-177, an issue I reported, was recently marked "Won't fix". A comment was made to the effect that the current behavior isn't a bug. This issue affected my design of my "XWiki Aggregate Document PDF Generator" (http://www.xwiki.org/xwiki/bin/view/Dev/AggregateDocs). I wanted to use the xwiki.getDocument() function to retrieve documents for inclusion in the generated PDF, but due to XWiki's current behavior, I had to resort to using HTTP downloads (a much slower and less robust approach). I guess I'm having a hard time understanding why the current behavior described in XWIKI-177 is the intended behavior. It really seems like a bug to me. Stephen

19 years, 1 month

XWiki task organisation

by jeremi joslin

Hi, I will try to do my best to help Ludovic to lead the project because he is very busy. I've started to review Jira tasks to find what we need to fix before the release. 1. I propose to split in Jira the XWiki project in 2 or 3 projects: * XWiki core (which is written in java) and the minimum UI (When you run XWiki with a blank DB) * XWiki plugins (also written in java, for exemple: feed plugin, mail plugin ...) * XWiki applications (in script language like groovy or velocity, for example: blog, photo album, wysiwyg...) the last too can be one because some applications can have a plugin like the feed plugin which have also an application. Like this, we can release the core without all the application and vice versa. Because many of you don't need the applications. 2. For next iterations before the release : - 1.0 B1 - 1.0 B2 - 1.0 RC1 - 1.0 RC2 - 1.0 3. I will do a summary in few days of the work to do before the release and propose you a road map. What do you think about it? I think, we can use the apache voting system (for those who don't know it: http://www.apache.org/foundation/voting.html) Jérémi -- Blog: http://www.jeremi.info LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724 http://www.xwiki.org skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com

19 years, 1 month

RE: [xwiki-dev] Proposal: XWiki Maven2 migration

by Vincent Massol

> -----Original Message----- > From: Ludovic Dubost [mailto:ludovic@xwiki.com] > Sent: mardi 3 janvier 2006 08:59 > To: xwiki-dev(a)objectweb.org > Subject: Re: [xwiki-dev] Proposal: XWiki Maven2 migration > > > Hi Zhong, > > Happy new Year (I'll come up with a longer email a little later). > > You are welcome to help on the migration to maven 2. I know Vincent did > a first try when Maven was still alpha. I'll check with him to see if > there is anything usable from his work. I didn't do much (I'm attaching a pom.xml that I started but it won't help much). My main issue at the time was that ibiblio POMs were almost all wrong. I think the situation has changed now and it should be much more usable. I agree that the build should be split in small modules and the list below sounds good. > Indeed it would be great to create some submodules for each XWiki > module. This of course needs a little discussion to decide what you be a > module and what should be in the core. > > I think a first split would be: > > core > core-doc > core-objects > core-api > core-web I think we should do it nested (check the cargo build for examples): core/ doc/ objects/ api/ web/ > store-rcs > store-hibernate store/ rcs/ hibernate/ > render > render-radeox > render-velocity > render-groovy render/ radeox/ velocity/ groovy/ > user-xwiki > user-ldap > user-exo user/ xwiki/ ldap/ exo/ > plugin > plugin-core > plugin-packaging > plugin-fileupload > plugin-xyz plugin(s)/ core/ packaging/ fileupload/ xyz/ > stats > pdf > xmlrpc (or webservice) > > It might be a little too detailed. It sounds good I think. It doesn't look too detailed at all. > I think in the process of splitting > in modules we might want to use a container system. > We've been discussing OSGi with Mandriva and eXo is using > picocontainer.. It might be a good time to think about it more in details. Cool. However I don't think the module split above would be much impacting by the choice of running inside a container or not. The modules would still be needed. It's just their implementation that would change. > Indeed it will have some impact in the development. I suggest we do this > on a branch. The objective is to get out a new release with the wysiwyg > editor and the new skins, so this should be work for the next release My advice would be NOT to do it on branch. My personal experience (on all projects where I have tried this) is that it doesn't work... You should rather do it on trunk slowly (as I did when I modified the m1 build). The reason is that the branch will never get merged in the trunk (it's just too hard to do). So what I'd do is simply start introducing the modules one by one and ensure that the current build continue to work at all times and add a new m2 build for the new modules. This is what I've done on Cargo too and I currently have two builds sitting next to each other but using a m2-enabled directory structure. Once our m2 build is as good as the m1 build, we'll remove the m1 build. Thanks and happy new year too! -Vincent > Zhong ZHENG a écrit : > > Hi the XWiki Team, > > > > I found in the mailing list archives that you are planning to use > > maven to build xwiki. I am a committer to the apache pluto project, > > which uses maven2. Thus i got some experience on maven 2. (Mr. Vincent > > Massol must be a maven master, since he is on the maven team :) I > > would like to help you migrate to maven. > > > > I checked out the xwiki source from subversion, and am trying to > > re-organize the project layout and create pom.xml files. Currently i > > am still dealing with the dependencies. I would like to propose to > > separate the xwiki project into small subprojects, and decouple the > > APIs from the implementation (such as user api and different > > implementations, plugin api and different plugin implementations, > > etc.). That will make the source more clear and more readable. > > > > I don't know how to help on this topic. Re-organizing the project > > layout introduces too many modifications on the project, which may > > have a lot of impacts on the current development, and it's difficult > > to generate svndiff and create patches. I would like to know if it is > > possible to apply for joining the dev team and create a new branch in > > svn for the maven migration. > > > > I am taking a look at the JCR spec currently, since I created a java > > wiki engine project ( http://people.apache.org/~zheng/elsie/ > > <http://people.apache.org/%7Ezheng/elsie/> ) and am thinking of > > refactoring it using JCR and apache jackrabbit. I found that you are > > also planning to implement the xwiki repository using JCR. I would > > like to help and contribute to this subproject too. > > > > Best regards. > > > > -- > > ZHENG Zhong > > - http://heavyz.blogspot.com/ > > - http://people.apache.org/~zheng/ <http://people.apache.org/%7Ezheng/> > > ------------------------------------------------------------------------ > > > > > > -- > > You receive this message as a subscriber of the xwiki-dev(a)objectweb.org > mailing list. > > To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org > > For general help: mailto:sympa@objectweb.org?subject=help > > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > > > > > -- > Ludovic Dubost > XPertNet: http://www.xpertnet.fr/ > Blog: http://www.ludovic.org/blog/ > XWiki: http://www.xwiki.com > Skype: ldubost AIM: nvludo Yahoo: ludovic >

19 years, 1 month

Vote for Mandriva Club/XWiki for ObjectWeb's best use case Awards

by Ludovic Dubost

ObjectWeb is organizing a "best use case" awards for the ObjectWeb Conference. Mandriva Club usage of XWiki is nominated. Anybody can vote. It's quick and easy ! Go go XWiki community. It's simple. One vote per person (no need to cheat). http://objectwebcon06.objectweb.org/xwiki/bin/Main/Vote The conference is in Paris from January 31st to February 2nd at the same time and place as the "Solution Linux" show (which is the most known Open Source show in France). We will have a presentation of XWiki on February 2nd ! Ludovic -- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic

19 years, 1 month

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs January 2006