Hello XWikiers,
I would need a wiki on myxwiki.org in order to test/demo collaboration with
somebody remote (and a pain to get a public IP for a local instance of
mine).
It would be temporary so it will be deletable after a while (I will let you
know when you can throw it away).
My username is lucaa, the wiki should be called lucaa.myxwiki.org .
Thank you very much,
Anca
Hi,
In previous years the xwiki.org project launched surveys about features we’d like to see implemented in XWiki (see http://www.xwiki.org/xwiki/bin/view/Main/Feedback).
After some discussions with fellow XWikiers we thought it could be interesting to launch a similar survey in 2015, especially with the 8.x cycle approaching. But this time instead of having a long list of features to vote on, we thought it might be more interesting to have a few open questions that the community could answer.
The aim of this short survey is to find out more about how satisfied (or not!) the members of the XWiki community are with the XWiki product.
We'd be happy to learn about:
* what you like / dislike about the product
* the features and improvements you’d like to see in the product in the future and especially for XWiki 8.x
The survey will run till November 13 and the results will be synthesised and made available mid-November through a blog post on the community blog ( http://blog.xwiki.org/xwiki/bin/view/Blog/ )
The survey has 6 questions and should only take a few minutes:
http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiProduct2015
Thanks a lot for your contributions and for helping improve the product,
-Silvia & Vincent
Hi devs,
I’m sorry I’m late on the this email (should have been sent a week ago at least).
I started discussing it a bit on http://markmail.org/message/4xlfdla2f3ds5rhq (regarding dates)
So the proposal is to continue with stabilization as per our cycle plan and especially to continue putting the priority on Nested Pages/Spaces which we need to be as stable as possible for 7.x, so that we can have a 7.4.x LTS.
The priority is to reduce this list of open issues to 0 (or close):
http://jira.xwiki.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=%…
A second priority is to finish the polishing of "Upgrade Tools” (ie DW) as much as possible since it was introduced in 7.x. More generally we need to fix/polish features that have been introduced in this cycle (7.x).
Proposed Dates:
===============
7.4M1: 30 November 2015
7.4M2: 14 December 2015
7.4RC1: 21 December 2015
7.4final: 28 December 2015
Note 1: we need to finish 7.4 by the end of the year to start a new cycle in early Jan
Note 2: we don’t have much margin with the Christmas holidays.
Thanks
-Vincent
Hi devs,
So this proposal appeared in some of my proposals but right now I created a
proper Proposal/Idea mail for it.
It's about having an 'Administer Page' section in the menus, similar to the
'Administer Wiki' and 'Administer Space' functionality.
The 'Administer Page' will be accessible to global admins, page creators
and users with (edit?/admin?) rights for the page.
>From what we currently have implemented it should contain the 'Rights
Editor' (?editor=rights) at page level.
In the future we could make 'Presentation', 'Page Elements' or 'Panel
Wizard' to be more granular and be set at Page level (have different panels
and style for just one page).
Some screenshots at
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/PageAdministration
Thanks,
Caty
Hi,
Currently we don't provide any README files for the repositories found on
https://github.com/xwiki
There are several remarks about this fact:
- README is promoted by GitHub as the way to summarize your project. That
green button "Add a README" won't disappear unless we create a file :)
- All the other major organizations provide READMEs for their repositories,
even if they have dedicated websites (a.k.a the README is not the only way
to document your project).
I think we should provide a README that contains just:
- Summary for the repo
- Links to the xwiki.org wiki about that particular repo
-- the links should be general and easy to maintain
-- they should facilitate access to devs for the most useful pages on
xwiki.org, promoting development and contributions.
I've created these proposals:
- Enterprise https://gist.github.com/evalica/b439c6dc98ca109e1f5b
- Platform https://gist.github.com/evalica/6431b99514d59bb7b66f
- Rendering https://gist.github.com/evalica/79298c6830480eff321d
- Commons https://gist.github.com/evalica/2affcfff5a4a40b418aa
The custom parts for each repository are Summary, Documentation, Download.
The generic parts are Release Notes, Tools, Community.
Let me know what you think.
Thanks,
Caty
P.S. For the LICENSE file we could just provide a link to the xwiki.org
page, see https://gist.github.com/evalica/8d58ec8353a30cad3386
Hi guys,
I think we need to an agreement on how to handle the default Tomcat security which disables the usage of / and \ in URLs (even URL-encoded). See http://www.tomcatexpert.com/blog/2011/11/02/best-practices-securing-apache-…
We have 2 main options:
* Option 1: Tell users to disable this security feature of Tomcat: http://tomcat.apache.org/tomcat-7.0-doc/config/systemprops.html#Security. In this case we just need to review our code to ensure we’re not subject to directory traversal attacks (see https://en.wikipedia.org/wiki/Directory_traversal_attack).
* Option 2: Decide to make it easy for Tomcat users (since it’s probably the typical servlet container used by our users) and to not use / and \ in our URLs.
Option 2 means modifying our code. There are various possibilities:
* A) Replace the “/“ and “\” characters by other characters in URLs and modify our URL Serialization code (implementations of XWikiURLFactory) and our URL parsing code (URL modules).
* B) Use a different encoding. Marius has used Base64 encoding for http://jira.xwiki.org/browse/XWIKI-11528. However this cannot be a generic solution since it leads to large URLs and also makes the URL not legible anymore. So this solution could only be for internal URLs.
* Other?
For A), it could b a character like ‘|' for ‘/' (and thus “||" if you want to have a real ‘|') and ‘~’ for ‘\’ (and “~~” if you want to have a real ‘\’).
So there are 2 questions in this thread:
* Do we want to be Tomcat-friendly?
* If so, what strategy do we apply?
WDYT?
Thanks
-Vincent
Hello there !
I had some issue about WYSIWYG editor, I explain :
I wanted to add a link toward a xWiki page using the "Research" tab
But sometimes I had access to the field and sometimes I didn't.
It seemed pretty random to me, but then i realize it was caused by the
"Allow Realtime Collaboration"
When it was checked, i couldn't access to the research field"
when it was unchecked i could.
So i solve my issue, I though that maybe you guys should be aware of that !
here's two screenshots to show you :
[image: Images intégrées 1]
--
*Vianney Deneux*
Élève ingénieur à Telecom Lille
Engineering Student at Telecom Lille
<http://www.telecom-lille1.eu/>06 28 34 53 84
<http://www.nounou-top.fr/>
Hello devs,
Would someone be kind to validate my extension on nexus, please?
extension id : application-rightsui-simplifier
vesion: 1.0
Thanks,
Paul Pantiru