The XWiki development team is pleased to announce the release of XWiki
Enterprise and XWiki Enterprise Manager 2.2.3.
This is a bug fix release for the 2.2 branches.
It fixes mainly one important regression around documents objects and
references handling so if you are using a previous 2.2.x version you
should really upgrade to 2.2.3.
New features:
* XWIKI-4983 - Add Reference Resolver for resolving string
representations of references as a relative reference
* XWIKI-4899 - Add Model API to get default Entity Reference values
Improvements:
* XWIKI-5003 - Add optional parameter support for Reference
Resolvers and Serializers
* XWIKI-5002 - Implement Explicit Reference Resolver and Serializer
* XWIKI-4995 - Introduce duplicate() method in BaseObject and
XWiiDocument to clone a document but with new GUIDs
* XWIKI-4921 - LiveTable improvement to remember filter even in
case of shift-reload or with Internet Explorer
* XWIKI-4606 - Statistics exclusions by user
* XWIKI-5028 - Improve the performance and functionality of the
whatever:hover behavior
* XAADMINISTRATION-114 - Extract successful registration message
to a new page for easier customization and link to it from admin UI
* Updated translations
Important Bugs fixed:
* XWIKI-4996 - Statistics broken in Oracle
* XWIKI-5006 - Wiki Copy doesn't work anymore with relative references
* XWIKI-5007 - BaseElement#setWiki produce nullpointerexception
when called before setName
* XWIKI-4987 - Cannot import as backup pack any longer
* XWIKI-4992 - Counting documents using parametrized HQL query fails
* XWIKI-4946 - Default values for the required macro parameters
should be send to the server by the WYSIWYG
* XWIKI-5016 - Display a message in place of the livetable
infinitely loading in a environment where its JS can't be executed
(example : noJS or in the WYSIWYG)
* XWIKI-5013 - HTML code visible when inserting velocity macro
displaying a property
* XWIKI-5000 - Image links of office imports gets broken when
using an OpenOffice 3.2 back-end
* XWIKI-4994 - Invalid document references for Cloned and Merged
Objects in Documents
* XWIKI-4973 - Live table sort does not work for anything else
than StringProperty fields
* XWIKI-5009 - Saving a xwiki/1.0 document from another wiki can
produce error or wrong backlinks
* XWIKI-4130 - Three closing parenthesis, ))), are evaluated even
though no open equivalence exists
* XWIKI-4988 - After deleting an imported attachment the user is
redirected to the Global Administration
* XWIKI-5023 - Impossible to properly install XE from scratch
* XWIKI-5026 - Wrong codes in ApplicationResources_pt
* XE-620 - A double quote contained in a field listed in the
livetable break the livetable
* XE-623 - Live Table filtering does not work on fields with
"Multiple Select" (but without Relational Storage)
* XE-621 - Live table does not show if some fields value of type
"StringProperty" contain carriage return
* XE-616 - LiveTable impacted by velocity set to null option
* XE-619 - Several bugs and improvements of the LiveTableResults macros
* XE-614 - Errors in UI for deleted documents & attachments
* XAADMINISTRATION-120 - SQL injection via "Forgot username" page
* XAADMINISTRATION-119 - Exception displayed when entering an
invalid email address in the ForgotUsername form
* XATAG-36 - Inconsitent management of tags case
For more information see the Releases notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise223
and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM223
Thanks
-The XWiki dev team
Hi devs,
I've been wanting to make it easy to upgrade XWiki from one version to another for some time (I'm not talking about XAR upgrade here, that's the extension manager). I'm talking about XWiki configuration files.
Here are the use cases I'd like to solve:
UC1: Easy install: no need to explode the XAR to install XWiki. See also the comment about xwiki on http://java.dzone.com/articles/file-system-storage-and
UC2: Easy upgrade: no need to take care about saving the configuration so that it's not overwritten by an upgrade
UC3: Should be possible to have multiple installs on the same machine and running at the same time
UC4: Should be possible to control the location of the configuration files for our automated functional tests (so that we control the configuration used)
The configuration files I'm talking about are:
* xwiki.cfg
* hibernate.cfg.xml
* xwiki.properties
Proposed Solution:
===============
1) Look for a system property (e.g. xwiki.config.dir) defining a directory location and if defined look for the files in it using File IO (I know it's not JEE kosher but it's acceptable IMO). Could be relative or absolute.
2) If not found, look for a JNDI property that gives the location of the config directory
3) If not found, look for config files in [user.home]/.xwiki
4) If not found, emit an error explaining how to configure xwiki
1) solves UC3 and UC4
2) solves UC3
3) solves UC1 and UC2
Note
====
I'm not suggesting any backward compatibility here since it's a new way of configuring XWiki. It means upgraders will need to read the release notes/doc to understand how to configure XWiki.
If really needed, we could devise a backward compat strategy, but I'm not sure we absolutely need that.
WDYT?
Thanks
-Vincent
FYI:
http://bit.ly/9UmUis
The part that is interesting:
"Improved JavaScript support, now all jQuery and Mochikit tests pass, adding to already supported GWT and Sarissa"
Since we're moving to Selenium2 and Selenium2 has a driver for HtmlUnit, we should try and see if using it would be good enough to detect JS problems in various browsers. The advantage of it over real browser drivers is that it runs much faster.
Or we could imagine a scenario where we would use the HtmlUnit driver for standard functional tests and then use the real browser driver once per day to provide additional warranties, thus providing the best of both worlds.
-Vincent
In an interview of Dan Kaminsky last year he says the following:
[[
Kaminsky: DNSSEC is interesting not because it fixes DNS. DNSSEC is interesting because it allows us to start addressing core problems we have on the Internet in a systematic and scalable way. The reality is: Trust is not selling across organizational boundaries. We have lots and lots systems that allow companies to authenticate their own people, manage and monitor their own people and interact with their own people. In a world where companies only deal with themselves, that's great. We don't live in that world and we haven't for many years.
Q: How does DNSSEC help fix that?
Kaminsky: One of the fascinating elements of the Verizon Data Breach Investigations Report is that if there was a hack, 40% of the time it was an implementation flaw, and 60% of the time it was an authentication flaw -- something happened with authentication credentials and everything blew up. At the end day, why do we use passwords? It's the only authentication technology that we have that even remotely works across organizational boundaries, and the only thing that scales today. Our existing ways of doing trust across organizational boundaries don't work. Passwords are failures; certificates that were supposed to replace passwords are not working -- period, end of discussion.
DNS has been doing cross-organizational address management for 25 years; it works great. DNS is the world's largest PKI without the 'K.'All DNSSEC does is add keys. It takes this system that scales wonderfully and has been a success for 25 years, and says our trust problems are cross-organizational, and takes best technology on the Internet for cross-organizational operations and gives it trust. And if we do this right, we'll see every single company with new products and services around the fact that there's one trusted root, and one trusted delegating proven system doing security across organizational boundaries.
]] http://bit.ly/19P188
I came across this from the very interesting Wikipedia article
http://fr.wikipedia.org/wiki/DNSSEC
On 20 Mar 2010, at 19:44, Henry Story wrote:
> Hi,
>
> Here are two issues with X509 that were hindrances for a solution like foaf+ssl to be deployed, but which can and are being fixed:
>
> 1. Client Side Certificate selection
> ------------------------------------
>
> Browsers currently do a very bad job of allowing the user to choose his certificate (Safari being the absolute worse). As a result I posted "Firefox Hackers Needed"
>
> http://bit.ly/cQ5f48
>
> earlier this week. @snej who is working at Google put up a picture of a solution for this in Chrome using a foaf+ssl certificate created by http://webid.myxwiki.org/
>
> http://bit.ly/azCXTU
>
> Vote for it!
>
> 2. Server side certificates
> ---------------------------
>
> One factor that people mention often with foaf+ssl is that the server has to have his own certificate. This means registration with a CA which is costly and tedious and it does not really solve the problems of server authentication as Dan Kaminsky shows ruthlessly in "Black Ops of PKI" http://bit.ly/4Uwb2K .
>
> To summarise his talk, server security is in a double bind:
>
> 1- Dan Kaminsky's DNS poisoning attack which is very well explained by Rick Van Rein's presentation "Cracking Internet: the urgency of DNSSEC" ( http://bit.ly/2darr8 view with FFox > 3.5 as it uses ogg video) means that a DNS easily be hacked in 6 weeks, and a lot of money poured into the wrong people's pockets. So there is a financial incentive to break DNS.
>
> 2. The solution of using https with X.509 public key cryptography's backing cannot work because there is a race to the bottom in the way CA's issue certificates. For enough money it is not that difficult to become God and to pretend you are anyone.
>
> Given the above DNSsec has become urgent enough, that it is being deployed.
>
> - verisign will put .com in July http://bit.ly/dyd54E
> - .org will be available in June http://bit.ly/abEJ28
> - .gov went dnssec in March 2009 http://bit.ly/bH27b0
> - The root will be signed July 2010 http://bit.ly/9YQMDJ
> - a map of dnssec deployment http://www.xelerance.com/dnssec/
>
> So listening to Dan Kaminsky you would think that he is against X509. Well certainly it could be improved a lot, but he is not quite as negative as one may think. X.509 with DNSsec seems to be something he thinks can work.
>
> What he told me after his CCC and HAR talks and what you can see in the last few minutes of the HAR talk "X509 considered Harmful" http://bit.ly/2darr8 is that once DNS is secure one could put the X509 (self signed even) certs into the DNS records. This would bypass the need for CAs. [ I hope I understood him correctly ]. I am not sure what needs to be done to make this possible with the browser vendors, but it would massively improve security on the web.
>
> As a result I have fait that the global situation on the internet will only make foaf+ssl solutions easier and more secure to deploy, enabling a completely distributed social network to emerge, free and without the spying, as Eben Moglen author of the GPL said so well recently http://bit.ly/brQmJz
>
> Henry
>
Hi,
Here are two issues with X509 that were hindrances for a solution like foaf+ssl to be deployed, but which can and are being fixed:
1. Client Side Certificate selection
------------------------------------
Browsers currently do a very bad job of allowing the user to choose his certificate (Safari being the absolute worse). As a result I posted "Firefox Hackers Needed"
http://bit.ly/cQ5f48
earlier this week. @snej who is working at Google put up a picture of a solution for this in Chrome using a foaf+ssl certificate created by http://webid.myxwiki.org/http://bit.ly/azCXTU
Vote for it!
2. Server side certificates
---------------------------
One factor that people mention often with foaf+ssl is that the server has to have his own certificate. This means registration with a CA which is costly and tedious and it does not really solve the problems of server authentication as Dan Kaminsky shows ruthlessly in "Black Ops of PKI" http://bit.ly/4Uwb2K .
To summarise his talk, server security is in a double bind:
1- Dan Kaminsky's DNS poisoning attack which is very well explained by Rick Van Rein's presentation "Cracking Internet: the urgency of DNSSEC" ( http://bit.ly/2darr8 view with FFox > 3.5 as it uses ogg video) means that a DNS easily be hacked in 6 weeks, and a lot of money poured into the wrong people's pockets. So there is a financial incentive to break DNS.
2. The solution of using https with X.509 public key cryptography's backing cannot work because there is a race to the bottom in the way CA's issue certificates. For enough money it is not that difficult to become God and to pretend you are anyone.
Given the above DNSsec has become urgent enough, that it is being deployed.
- verisign will put .com in July http://bit.ly/dyd54E
- .org will be available in June http://bit.ly/abEJ28
- .gov went dnssec in March 2009 http://bit.ly/bH27b0
- The root will be signed July 2010 http://bit.ly/9YQMDJ
- a map of dnssec deployment http://www.xelerance.com/dnssec/
So listening to Dan Kaminsky you would think that he is against X509. Well certainly it could be improved a lot, but he is not quite as negative as one may think. X.509 with DNSsec seems to be something he thinks can work.
What he told me after his CCC and HAR talks and what you can see in the last few minutes of the HAR talk "X509 considered Harmful" http://bit.ly/2darr8 is that once DNS is secure one could put the X509 (self signed even) certs into the DNS records. This would bypass the need for CAs. [ I hope I understood him correctly ]. I am not sure what needs to be done to make this possible with the browser vendors, but it would massively improve security on the web.
As a result I have fait that the global situation on the internet will only make foaf+ssl solutions easier and more secure to deploy, enabling a completely distributed social network to emerge, free and without the spying, as Eben Moglen author of the GPL said so well recently http://bit.ly/brQmJz
Henry
Social Web Architect
http://bblfish.net/
Social Web Architect
http://bblfish.net/
Hi devs,
To fix http://jira.xwiki.org/jira/browse/XE-615 i would like to change
the test associated to backup pack.
You can look at the issue for more detail on the issue but basically
the problem is that on an empty XE guest does not have programming
right which make impossible to import XE xar like it used to. You have
to enable superadmin user with a password in clear in the xwiki.cfg
file.
I propose to change the way importer is working and test only once for
the whole import and for admin right on main wiki which will make
possible to install XE without having to enable superadmin.
I feel it's secure enough but i prefer sending this vote mail to make
sure more people can validate it's ok.
Here is my +1.
--
Thomas Mortagne
Hi all,
I'm writing integration tests for the patch fixing
http://jira.xwiki.org/jira/browse/XABLOG-99. In particular, I want to
test adding, renaming and deleting of blog categories from
Blog/ManageCategories page.
My problem is that the "toolbox" with rename and delete buttons is only
displayed on hover, and selenium complains that it cannot access
invisible elements.
I tried to use RenderedWebElement.hover() as follows:
By locator = By.xpath("//a[contains(@href, \""
+ name + "\")]/ancestor::span[@class='blog-category-level']");
RenderedWebElement category
= (RenderedWebElement) getDriver().findElement(locator);
category.hover();
but the n I get error "Unable to hover over element".
Does anybody knows how to show these delete buttons?
I'm using FF 3.6 on Linux.
Thanks,
Alex
-------- Original Message --------
From: socghop.noreply(a)gmail.com
Subject: Thank you for your application
To: sergiu.dumitriu(a)gmail.com
Hi Sergiu Dumitriu,
Thank you for submitting "XWiki" organization application to Google
Summer of Code 2010. Unfortunately, we were unable to accept your
organization's application at this time. We received many more
applications for the program than we are able to accommodate, and we
would encourage you to reapply for future instances of the program.
Best regards,
Google Open Source Programs
Hi all,
I'm wondering if it's possible to rename the "bin" part of the URL to
something else. For same reason I can't drop the bin from the URL in
Weblogic so I was wondering whether it could be possible to nicely rename
it.
Best Regards
Nicola
--
View this message in context: http://n2.nabble.com/URL-How-to-rename-bin-to-wiki-or-something-else-tp4755…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi Devs,
I am a girl from China. I am a student pursuing my BS degree in The Central
University Of Finance and Economics. My major is Electronic Commerce.
I love Open Source, but in China Open Source is not so popular. Open Source
is powerful and the idea of Open Source can accelerate the development of
the Software indursty. I want to involve into a Open Source program, learn
Open Source method and popularize open source in China.
One of my friend use XWiki as his personal Knowledge repository and dairy. I
try xwiki in myxwiki.org. I think is a powerful platform, in which any
applications can be built on it, only limited by your imagination. I want to
learn xwiki and use the power of xwiki. The best way to do this, I think, is
to involved to xwiki. I follow the mail list and ask question in IRC xwiki
channel. I find the guys in xwiki community are very nice to help others. I
like that. I want to contribute to xwiki, as open source guy do.
I checked the 21 proposal projects, and I think I am interested in Calendar
application proposal. I use google Calendar which is a great product. I have
program skill in java, but I don't have must experience in JaveScript and
ajax. I will try my best to learn xwiki and related knowledge.
I need your help to do this, and I will do my best.
Look forward working with your guys.
Thanks.
Michelle Shi
Hi devs,
I am the student who is interested in xwiki GSoC. I want to build a new
calendar Application for XWiki.
This is my homework about this project ;)
After learning xwiki for a while, I really think it is a great platform, and
supported by a great comunnity.
I can find all kinds of documents in xwiki, such as introduction to xwiki
features, documents for xwiki new developer or contributor, Developer's
Guide, FAQ, and active maillist. I can learn a lot by dive into xwiki.org.
Thanks for you guy document work ;)
This is a list for what I have do and my future plan. Please direct me to
prepare for this project. I need your suggestion.
1. Family with xwiki. I have applied a wiki in myxwiki.org, and I use this
wiki for my weblog and project schedule. I learn some xwiki feature throught
http://platform.xwiki.org/xwiki/bin/view/Main/. I know some base concepts in
xwiki, such as page, space, object, class. I know the xwiki is a platform to
build various kinds application, such as BBS, blog, photo album. I learn how
to export and import xar, how to manage the xwiki right, and how to create
simple class in xwiki.
2. Learn the "Suggested way of working for GSoC students" in this page
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/
3. Learn base xwiki develop knowledge. I learn how to build xwiki from
source code, directed by http://dev.xwiki.org/xwiki/bin/view/Main/. I use
svn, maven, eclipse. And How to debug xwiki in eclipse.
4. Community with xwiki devs. I are following xwiki dev and user list to
know the lastest news in xwiki. I read all the mails in dev list, but I
can't understand some top for now. I will post my questions to this list in
the future. I ask questions in xwiki IRC.
5. I have use the old calendar application, and read the source code. I
think I need check the old calendar plugin java source code again.
6. I have read the requirment for the now calendar application.
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/CalendarApplication2….
I think some details need to be discussed.
7. I will record my process in http://michelle.myxwiki.org, this is my blog
http://michelle.myxwiki.org/xwiki/bin/view/Blog/. I make a project space in
my wiki. You can follow my plan in this page
http://michelle.myxwiki.org/xwiki/bin/view/GSoC/
Todo
1. Learn how to develop application in xwiki. Learn the Tutorials and Guides
in this page http://platform.xwiki.org/xwiki/bin/view/DevGuide/. I think
"Creating a TODO application in XWiki" is a great tutorials.
2. To learn about the whole xwiki, I think I need to check out all the
content in Developer's Guide.
3. Check out the open source calendar program and learn the the source code.
I think the render of calendar need some javescript code. I will learn it.
4. After discuss with <sdumitriu> in IRC, I know some idea of the new
calendar, like "calendar event in its own document And the calendar view
just gathers and displays all the events in the current wiki or space". I
will think about how to realise it in xwiki.
Hi devs,
as part of 2.3M1, we'd like to commit and activate annotations by default in the
xwiki platform.
WDYT?
and as a strategy we could have:
1/ jars in platform and .xar that users can install if they want -- the .xar
would actually provide the interface of the annotations, js css & forms
2/ jars in platform and .xar included in XE by default
I think i'd go for 2/ in M stage. If we can't stabilize it enough for final, we
could get it out, but 2. would be fine for now.
WDYT?
Thanks,
Anca
Hi everyone,
I'd like to move this topic forward. Thus I've now created a draft of the XWiki.org Governance that gathers what I had proposed at
http://markmail.org/message/fxqvprtbb5vyog6g
The Governance page is currently at:
http://dev.xwiki.org/xwiki/bin/view/Drafts/Governance
Please review it and vote. The idea is then to move it to
http://dev.xwiki.org/xwiki/bin/view/Community/Governance in a few days.
As usual, non committers don't have binding votes but are still very much encouraged to give their opinions. Their voice is especially more important on this topic since most committers are from XWiki SAS and thus I feel we need at least a general agreement from the community at large before doing anything.
Thanks a lot
-Vincent
I've realized another proposal for the homepage, it's
here<http://incubator.myxwiki.org/xwiki/bin/view/Mockups/Homepage2>(thanks
to Silvia who uploaded image).
In the uppper part there are the links equivalent to the tab bar proposed by
Silvia in her proposal,
i've added "Get Involved" that's equivalent to "How do I contribute"(link)
but is placed in the upper part
of the homepage. In the centre there is a rounded box where should be placed
the Xwiki logo plus a motto
and an awesome background similarly to www.kde.org at the end of the
homepage for me should be placed
some links with a nice show effect(i think jquery could do this).
Source of inspiration(i'm a "thief" :))
- easy to read <http://informationarchitects.jp/100e2r/>
- example_KDE <http://kde.org/>
- apache_menu <http://www.apache.org/>
Giuseppe.
Hi XWikiers,
The goal of this proposal is to be able to deploy contrib projects on
the xwiki maven repository, allowing distributions to depend on
contrib projects.
Contrib projects deployment must be different from the other xwiki.org
deployments since want to review the artifacts contributors publish
under our banner.
The proposal is to use the nexus staging deployment feature to perform
contrib releases. Strategy:
- Create the http://maven.xwiki.org/contrib/ repository
- When a contributor first want to release his project, create a user
for him allowed to push artifacts in staging on nexus.xwiki.org. This
credentials are meant to be put in ~/.m2/settings.xml to be used by
maven for authentication on nexus.xwiki.org.
- When a contributor performs a release the artifacts are pushed on
the nexus staging repository, an email is sent on
notifications(a)xwiki.org to notify nexus admins that they must
review/publish them.
We could create a new http://svn.xwiki.org/svnroot/xwiki/contrib/pom/
pom project to ease maintainers work, here's a draft:
-------------------------8<-----------------------------
<groupId>org.xwiki.contrib</groupId>
<artifactId>root</artifactId>
<name>XWiki Contrib - Root POM</name>
<packaging>pom</packaging>
<version>1.0-SNAPSHOT</version>
<url>http://contrib.xwiki.org</url>
<issueManagement>
<system>jira</system>
<url>http://jira.xwiki.org/jira/browse/XCONTRIB</url>
</issueManagement>
<scm>
<connection>scm:svn:http://svn.xwiki.org/svnroot/xwiki/contrib/pom/trunk</connection>
<developerConnection>scm:svn:https://svn.xwiki.org/svnroot/xwiki/contrib/pom/trunk</developerConnection>
<url>http://svn.xwiki.org/svnroot/xwiki/contrib/pom/trunk</url>
</scm>
<distributionManagement>
<repository>
<id>xwiki-staging</id>
<name>XWiki Staging Repository</name>
<url>http://nexus.xwiki.org/nexus/service/local/staging/deploy/maven2/</url>
</repository>
</distributionManagement>
------------------------->8-----------------------------
Note: I'm still not sure about this, I think duplicating
distributionManagement in an application and have xwiki-applications
as parent might be more convenient than the contrary (duplicating
build extensions and stuff + have org.xwiki.contrib.root as parent).
WDYT ?
Thanks,
JV.
Hi everyone (devs and users),
While we have a clear governance for write access to our source
repository (http://dev.xwiki.org), we're missing a clear governance
for xwiki.org. The idea is to address mainly the following 2 questions:
1) who "owns" it and thus "controls" (or rather provides direction
for) its content
2) can it be used for business advertising (support, paid packages,
consulting services)
Bit of History about XWiki SAS
========================
- XWiki SAS (http://xwiki.com) is the company founded by Ludovic
Dubost the creator of XWiki (I'm the CTO of XWiki SAS in addition to
being a committer here).
- Most of the active contributors are also employed and paid by XWiki
SAS to develop the XWiki software. Today that's
-- 12.5 committers (developers)
-- 1 open source product manager (see http://markmail.org/thread/ggaaw4u6yyci4oan
for its definition)
-- 1 designer
-- 1 tester/technical writer
- XWiki SAS sells services around the open source software, see http://www.xwiki.com/xwiki/bin/view/Services/
- XWiki SAS truly believes and understands open source, see http://www.xwiki.com/xwiki/bin/view/About/Values
-- I also wrote a blog post on this some time back: http://massol.myxwiki.org/xwiki/bin/view/Blog/XWikiSASAndOpenSource
- XWiki SAS has promised "not to do evil" ;), see its manifesto at http://www.xwiki.com/xwiki/bin/view/About/Manifesto
- XWiki SAS is paying for the servers and maintenance of xwiki.org,
myxwiki.org, the maven repo, the svn repo, the hudson build serversn
the free JUG farm, and more
Issue at hand
===========
XWiki SAS would like to generate more revenue to be able to increase
the development pace of the XWiki software. We'd like to fund even
more the development of XWiki, so that it becomes an even better
product. We've asked you what you'd like to see in the future in XWiki
and you've answered on this survey result:
http://www.xwiki.org/xwiki/bin/view/Blog/Features+Survey+Results
We'd like to implement those features as fast as possible.
For this we need to ensure that users interested in commercial
services find easily the way to http://xwiki.com, even when they
arrive on xwiki.org.
This is true for XWiki SAS's services but also for any company willing
to offer services around the XWiki open source project. There's no
magic. Developers need to be paid when they work full time on some
project. We need a commercial ecosystem around XWiki for it to
progress as quickly as its competitors (the collaboration market). We
need to allow for commercial companies the ability to generate revenue
from their work on the XWiki open source project. However we also want
to continue ensuring that all the XWiki development is done in open
source, under a LGPL license.
Governance Proposal
=================
1) xwiki.org is controlled by the XWiki committers. This means that
important changes brought to it should be discussed/vote on the list,
using the same practices as for code commits
2) xwiki.org stays open in edit mode to all external contributors (and
XWiki committers continue to monitor it to remove spam, etc)
3) we agree to start with 3 zones where companies can advertise their
commercial offers on top of the XWiki open source product:
-- On the download page (for business packages, subscriptions, hosting)
-- On the support page (for services: support, consulting)
-- (still to be defined) Possibly on a "Products" tab in the new
horizontal navigation. The idea would be to do as jboss.org is doing.
Projects are open source and community and Products are commercial
4) the company offerings are listed by their amount of contributions
to the XWiki open source project. The company that contributes most
(XWiki SAS today) gets the best spots (top of the list, bigger space)
5) Companies who want to be listed should provide some proof of their
contributions to the XWiki open source project
6) XWiki SAS gets some acknowledgment for paying for the xwiki.org
server/maintenance of it. Probably somewhere in the footer of the site
or on side panel somewhere
7) xwiki.org should always remain a site for the xwiki open source
community
Conclusion
=========
We want to stress that this proposal is not about XWiki SAS making a
commercial takeover of the xwiki.org site.
It's about recognizing that if the XWiki open source software
progresses quickly today, it's thanks to contributors but also for a
very large proportion to companies paying developers to work on it,
either directly (like XWiki SAS or other companies that have
developers contributing) or indirectly (by paying for example XWiki
SAS or other companies to work on specific features).
It's also about recognizing that XWiki SAS is happy to see other
companies willing to contribute to the progress of the XWiki open
source project and thus to provide a place for these companies to be
visible too.
I hope that all our contributors but also users of the XWiki Open
Source software will find this proposal acceptable and I welcome any
feedback on it.
Thanks
-Vincent Massol
Hat 1: XWiki SAS CTO
Hat 2: XWiki committer
On Wed, Mar 17, 2010 at 7:59 AM, Vincent Massol <vincent(a)massol.net> wrote:
>
> On Mar 17, 2010, at 12:56 AM, Anca Luca wrote:
>
> > Hi Vincent,
> >
> > On 03/15/2010 07:17 PM, Vincent Massol wrote:
> >>
> >> On Mar 15, 2010, at 4:04 PM, Anca Luca wrote:
> >>
> >>> Hi Vincent, all
> >>>
> >>> On 03/15/2010 12:15 PM, Vincent Massol wrote:
> >>>> Hi,
> >>>>
> >>>> We've slipped badly for the 2.3M1 release (my fault for not monitoring
> it closely enough). It was planned on the 8th of March and we're the 15th
> already (one week delay).
> >>>>
> >>>> The other problem is that we don't have what we had imagined would go
> in 2.3M1 (color theme improvement for ex). Right now there are lots of
> changes but nothing really user-noticeable.
> >>>>
> >>>> So I'd suggest the following:
> >>>> * Delay by a few days in order to be able to include:
> >>>> - color theme improvement. Sergiu you need to tell us if that's doable
> and for when.
> >>>> - captcha on comments. Caleb, let us know if that's all done or if
> there's need for more testing/development.
> >>>>
> >>>> Bonus:
> >>>> - Anca, will it be possible to have annotations released for 2.3M1 (ie
> now)? How much more time would you need?
> >>>
> >>> I'll close the vote for XWIKI-4775 asap, and commit it since it's due a
> long
> >>> time now.
> >>> I shouldn't need more than 2 days, but how would we want the
> annotations
> >>> integrated in the platform?
> >>>
> >>> Right now they're built as an extension, with some jars to deploy on
> the server
> >>> and a .xar to install the default annotations application.
> >>
> >> I think we should:
> >> * have platform/xwiki-annotations and release it when we release the
> plaform
> >> * have applications/annotations and include it in the default XE XAR
> >>
> >> The rationale is that annotations is a powerful feature and I believe
> it's good to have it by default for now (it would be too difficult to
> install it separately for now).
> >
> > Why would it be difficult? we can maven magic a zip with a bunch of jars
> anytime
> > and make people unpack it in their WEB-INF/lib & install the xar. I think
> that's
> > reasonable complexity for such an extension.
>
> That's what I call complex. It's too complex for a large majority of our
> users and it would make the annotation feature not used which is a shame. In
> any case I don't see any compelling reason not to bundle it by default in
> the default XE we distribute.
>
+1 again!
Anca, why don't you want your awesome work to be bundled in XE by default?
;-)
Guillaume
> Thanks
> -Vincent
>
> > Thanks,
> > Anca
> >
> >>
> >> When we have the extension manager implemented, we'll be able to trim
> down the size of what the "core" platform and instead have the user be able
> to install extensions when they start their wiki for the first time or when
> they go to the admin page for this. But since we don't have this now I feel
> it's better to have annotations packaged in the platform and in the default
> XAR than not have it.
> >>
> >> Here's my +1 to both (API in the platform and annotation XAR in default
> XE).
> >>
> >> Note: It would be great to have the ability to turn on/off the
> annotations feature for 2.3 final.
> >>
> >> Thanks
> >> -Vincent
> >> _______________________________________________
> >> devs mailing list
> >> devs(a)xwiki.org
> >> http://lists.xwiki.org/mailman/listinfo/devs
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
--
Guillaume Lerouge
Product Manager - XWiki SAS
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
On Mar 16, 2010, at 6:28 PM, mflorea (SVN) wrote:
> Author: mflorea
> Date: 2010-03-16 18:28:54 +0100 (Tue, 16 Mar 2010)
> New Revision: 27661
>
> Modified:
> platform/web/trunk/xwiki-gwt-wysiwyg-server/src/main/java/com/xpn/xwiki/wysiwyg/server/plugin/WysiwygPluginApi.java
> Log:
> XWIKI-5013: HTML code visible when inserting velocity macro displaying a property
>
> Modified: platform/web/trunk/xwiki-gwt-wysiwyg-server/src/main/java/com/xpn/xwiki/wysiwyg/server/plugin/WysiwygPluginApi.java
> ===================================================================
> --- platform/web/trunk/xwiki-gwt-wysiwyg-server/src/main/java/com/xpn/xwiki/wysiwyg/server/plugin/WysiwygPluginApi.java 2010-03-16 15:51:03 UTC (rev 27660)
> +++ platform/web/trunk/xwiki-gwt-wysiwyg-server/src/main/java/com/xpn/xwiki/wysiwyg/server/plugin/WysiwygPluginApi.java 2010-03-16 17:28:54 UTC (rev 27661)
> @@ -35,6 +35,14 @@
> public class WysiwygPluginApi extends Api
> {
> /**
> + * The context property which indicates if the current code was called from a template (only Velocity execution) or
> + * from a wiki page (wiki syntax rendering).
> + *
> + * @see #parseAndRender(String, String)
> + */
> + private static final String IS_IN_RENDERING_ENGINE = "isInRenderingEngine";
> +
> + /**
> * The plugin instance.
> */
> private WysiwygPlugin plugin;
> @@ -98,11 +106,26 @@
> */
> public String parseAndRender(String html, String syntax)
> {
> + // Save the value of the "is in rendering engine" context property.
> + Object isInRenderingEngine = context.get(IS_IN_RENDERING_ENGINE);
> +
> try {
> + // This tells display() methods that we are inside the rendering engine and thus that they can return wiki
> + // syntax and not HTML syntax (which is needed when outside the rendering engine, i.e. when we're inside
> + // templates using only Velocity for example).
> + context.put(IS_IN_RENDERING_ENGINE, true);
> +
> return Utils.getComponent(HTMLConverter.class).parseAndRender(html, syntax);
> } catch (Exception e) {
> // Leave the previous HTML in case of an exception.
> return html;
> + } finally {
> + // Restore the value of the value of the "is in rendering engine" context property.
> + if (isInRenderingEngine != null) {
> + context.put(IS_IN_RENDERING_ENGINE, isInRenderingEngine);
> + } else {
> + context.remove(IS_IN_RENDERING_ENGINE);
> + }
Shouldn't you always put back the value that you saved (even if it's null) ?
Thanks
-Vincent
Hi dev,
I'm working on http://jira.xwiki.org/jira/browse/XWIKI-4606 and i
would like to propose the following:
1) add a property than takes a list of users/groups
I only found xwiki.stats.excludedUsers for now,
xwiki.stats.excludedUsersAndGroups is a bit long an groups are meta
users so it's ok, right ? ;)
For each element of the list we get the document to know if it's a
user of a group and recursively get groups users to produce a list of
all users to filter. That means that StatUtils#getFilteredUsers would
return a list of users without any group that would have been
internally "resolved".
I plan to add this resolve tool in
com.xpn.xwiki.plugin.rightsmanager.RightsManager for now, we can see
latter if we want to add this in public apis (RightsManager*PluginApi
classes).
For now i plan to have:
* xwiki.stats.excludedUsers in xwiki.cfg (follow "xwiki.stats" propery naming)
* statistics_excludedUsers in XWikiPreferencesmyxwiki.org (follow
"statistics" property naming)
2) in all statistics search/get methods we filter theses users
automatically by inserting them in the hql where clauses (all theses
methods are mostly about creating the proper database query to get the
result)
WDYT ?
Thanks
--
Thomas Mortagne
On Mar 16, 2010, at 10:14 AM, Caleb James DeLisle wrote:
> Actually I was trying to be hip and use gedit to write the log so I could use multiple lines.
> Maybe I'll set a newline variable in my .bashrc so I can keep on using the command line...
FWIW I use vi and it works well. I just type "svn commit", then vi opens, I enter my comment and save it and it just works for me.
-Vincent
>
> Marius Dumitru Florea wrote:
>> cjdelisle (SVN) wrote:
>>> Author: cjdelisle
>>> Date: 2010-03-16 09:50:34 +0100 (Tue, 16 Mar 2010)
>>> New Revision: 27643
>>>
>>> Modified:
>>> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/UnknownAction.java
>>
>>> Log:
>>
>> You forgot the log :)
>>
>> Thanks,
>> Marius
>>
>>>
>>> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/UnknownAction.java
>>> ===================================================================
>>> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/UnknownAction.java 2010-03-16 08:34:35 UTC (rev 27642)
>>> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/UnknownAction.java 2010-03-16 08:50:34 UTC (rev 27643)
>>> @@ -40,6 +40,10 @@
>>> * @see XWikiAction#render(com.xpn.xwiki.XWikiContext)
>>> */
>>> public String render(XWikiContext context) throws XWikiException {
>>> - return context.getWiki().Param("xwiki.unknownActionResponse", "exception");
>>> + String defaultAction = context.getWiki().Param("xwiki.unknownActionResponse", "exception");
>>> + // Set the action in the context because code which uses $xcontext.getAction()
>>> + // should get the desired action instead of "unknown"
>>> + context.setAction(defaultAction);
>>> + return defaultAction;
>>> }
>>> }
>>>
>>> _______________________________________________
>>> notifications mailing list
>>> notifications(a)xwiki.org
>>> http://lists.xwiki.org/mailman/listinfo/notifications
>> _______________________________________________
>> notifications mailing list
>> notifications(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/notifications
>>
>
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications