- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [Brainstorming] Default Flavors Proposals

by Ecaterina Moraru (Valica)

Hi, I've investigated a bit what use cases could be used inside XWiki for and I've came up with: - Documentation Flavor http://markmail.org/thread/cvfzvwv6dnhkimuy - Groupware Flavor http://markmail.org/thread/mzby6ofaunrsxpun - Public WebSite Flavor http://markmail.org/thread/fgpzoxtdw2jgrrvl - Application Development Flavor http://markmail.org/thread/ion37cj7zb255j3d XWiki can be used for many things and the ones above are just the ones I've investigated recently. This mail acts like a collection of the flavors already proposed and should also gather other proposals/ideas for use cases you find interesting. One thing to have in mind is the flavor's ideas should be generic enough in order to be proposed in the sub-wiki creation process (marginal/very specific flavors should be discussed in another thread and would be of interest if we are gonna implement the Flavor Creator). The features described in the Flavors can have 5 states: - Mandatory: the feature is mandatory for the described flavor and needs to be installed; - Optional: the feature could be of interest for some sub-use cases of the described flavor. A solution to have optional features would be to customize what extensions you install in the creation process (http://incubator.myxwiki.org/xwiki/bin/download/Improvements/Flavours/custo…) or to have Disabled/Enabled states for installed extensions (http://jira.xwiki.org/browse/XWIKI-5704). - Default: the feature is bundled by default in XE. This means is tested and supported. If we are gonna create default Flavors, some features might be present just in the related flavors (like Annotations), and not by default, but right now they are default. - Extension: the feature is available as an extension. If the feature has both 'Default' and 'Extension' it means that some functionality is available by default, while additional functionality is available through extensions (one example is the Export: by default we can export in PDF, HTML, etc. but there are extensions that provide Multipage PDF Export or Export in other formats like Excel, etc.) - Custom: Custom means that the feature will have specific differences from the variant is available now. For example, in a Documentation Flavor we will need some custom templates; or the Macros categories should contain macros specially created for content creation. Each proposal describes the contained features and also provides a summary at the end, example http://incubator.myxwiki.org/xwiki/bin/view/Improvements/DocumentationFlavo… Your feedback is welcomed. Thanks, Caty

12 years, 5 months

1
0
0 0

[xwiki-devs] [Brainstorming] [Flavor] Application Development Flavor

by Ecaterina Moraru (Valica)

Hi, The proposal for Application Development Flavor can be found at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AppDevelopmentFlav… Besides being a wiki, XWiki is also an application development platform. You can build simple applications, extend the platform with custom plugins, or even build complex Web applications. There are 2 use cases related to Application Development: - one targeted to Advanced Developers. I detailed this use case because it's more complex than the other. I've made a selection of applications from our extensions repository that I considered could be of interest for developers in a web environment; - the other is targeted to Simple Users that want to create applications. For this use case, choose just the 'Mandatory' features. A simple user will always use AppWithinMinutes and we need better integration of created application to be the focus part of the sub-wiki. I encourage you to take a look at the features and give your opinion. Thanks, Caty

12 years, 5 months

1
0
0 0

[xwiki-devs] [Brainstorming] [Flavor] Groupware Flavor

by Ecaterina Moraru (Valica)

Hi, The proposal for Groupware Flavor can be found at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/GroupwareFlavor Collaborative software (or groupware) is designed to help people involved in a common task achieve goals. Groupware are focused on the usage of applications and collaboration inside teams. I've tried to make a selection of application we currently have in our extensions repository. An interesting discussion would be to make proposals on applications that we currently don't have implemented, but would be vital in such a flavor. I encourage you to take a look at the features and give your opinion. Thanks, Caty

12 years, 5 months

1
0
0 0

[xwiki-devs] [Brainstorming] [Flavor] Public Website Flavor

by Ecaterina Moraru (Valica)

Hi, The proposal for Public Website Flavor can be found at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/PublicWebsiteFlavor The purpose of a Public Website is to share information about a company/product and it's procedures, features, services, etc. It's the on-line presence of a company for it's targeted audience. I encourage you to take a look at the features and give your opinion. Thanks, Caty

12 years, 5 months

1
0
0 0

[xwiki-devs] [Brainstorming] [Flavor] Documentation Flavor

by Ecaterina Moraru (Valica)

Hi, The proposal for Documentation Flavor can be found at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/DocumentationFlavor A Documentation Wiki is an information repository about a certain topic (product, service, etc.) It needs to provide means for information to be collected, organized, shared, searched and utilized. I've created only the Documentation Flavor and not the Knowledge Base Flavor because I consider the Documentation to be more strict than the other. The main difference between the two is the Workflow (http://incubator.myxwiki.org/xwiki/bin/view/Improvements/DocumentationFlavo…) which involves also custom Rights (http://incubator.myxwiki.org/xwiki/bin/view/Improvements/DocumentationFlavo…) and should provide documentation specific Export formats. Besides these differences, the Knowledge Base and Documentation are very similar: knowledge base encourage content collaboration in all stages, while Documentation only in the content gathering phase, becoming read-only after. I encourage you to take a look at the features and give your opinion. Thanks, Caty

12 years, 5 months

1
0
0 0

[xwiki-devs] [Fun] Creating jira issues for failed tests automatically (bad idea IMO)

by Vincent Massol

http://www.maplesteve.com/2013/03/24/create-jira-issues-from-jenkins That's fun… :) I was wondering if this could help us be more proactive in fixing our tests (especially the flickering ones) or if it wasn't going to help at all and instead cause more troubles. The good part is that it creates new jira only for new tests that fail so it may not be that bad. The bad part is that if we have false positives we'll need to close those jira as won't fix thus leading to extra maintenance (even though we've excluded most if not all real false positives already). I'm actually worried about the case when someone commits an error that affects all tests and suddenly you have 600 tests failing and thus 600 new jiras created :) So while the idea seemed attractive, I think it could cause us more problems than advantages. Too bad because right now almost nobody in our team (except Marius) is fixing flickering functional tests and we need to have stable tests as the norm… (that being said the build is still failing in lots and lots of places as of now :( Even commons and platform are failing…). Thanks -Vincent

12 years, 5 months

2
1
0 0

[xwiki-devs] [PROPOSAL] Allow simple users to choose from a menu of editors instead of forcing WYSIWYG.

by Caleb James DeLisle

Hi, The reasoning for this is because I have seen a number of users running in to problems with the lack of dropdown menu, giving instructions for fixing a problem is harder when they always begin with "edit the page then append ?editor=wiki to the URL". I think showing the menu of editors is not too overwhelming for new users whereas showing them internal documents is. This will also pave the way for more experimental editors such as realtime. WDYT? Caleb

12 years, 5 months

4
3
0 0

[xwiki-devs] [QA] Feedback for 5.0 M2

by Manuel Smeria

Hi, XWiki 5.0M2 is scheduled to be released on Monday according to the Roadmap<http://www.xwiki.org/xwiki/bin/view/Roadmaps/WebHome> . Besides the full list of issues fixed for 5.0M2 and the "Automatic Paste Cleaning in WYSIWYG Editor"<http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki50M2#HAut…> feature, do you want something else tested as well ? Thanks, Manuel

12 years, 5 months

6
6
0 0

[xwiki-devs] XWikiDocument#get/setUser/Creator/ContentAuthorReference() and guest

by Thomas Mortagne

Hi devs, Following http://markmail.org/message/snnlesexie4ox3i5 I would like to modify user related methods in XWikiDocument to behave like the what has been voted for XWikiContext and follow the same logic. As a reminder here it is: not logged in user (guest) reference is null. Plain and simple. The idea would be to do exactly the same thing than XWikiContext meaning that old String APIs continue to deal with "XWikiGuest" and do convertions for retro compatibility especially with existing databases. It will change the behavior of XWikiDocument#getUserReference() from external point of view so it's a breakage but we might actually fix more bugs than we create when thinking about codes like context.setUserRefererence(document.getAuthorReference()) or $context.userReference == $doc.authorReference which I'm sure we can find here and there. 5.0 and new right service is a good occasion for this improvement. WDYT ? Here is my +1 -- Thomas Mortagne

12 years, 5 months

5
7
0 0

[xwiki-devs] [Reminder] BFD#13 today

by Thomas Mortagne

Here is the filter: http://jira.xwiki.org/issues/?filter=12207 It's not because Vincent is not here that we can be lazy ;) -- Thomas Mortagne

12 years, 5 months

4
6
0 0

[xwiki-devs] [GSOC] XWiki is applying for GSoC 2013. Proposals and mentors needed!

by Eduard Moraru

Hello fellow XWiki community members, This year XWiki is planning to participate once more at Google's Summer of Code [1]. The organization registration period has already started today (18th of March) and the deadline is the 29th of March [2] (almost 2 weeks). 1. We need to provide by then a list of proposals and assign mentors for the students that are going to implement them. I would like to ask everybody that wants to participate as a mentor from the XWiki organization to review the proposals [3] list (we currently have 12 proposals) and add as many interesting proposals as possible. The proposals can be either new, or they can be revived from previous year proposals. Just navigate to the previous years, find the proposal you like and know about, go to its proposal page (click it) and press the "Clone to this year" link. Now you can assign yourself as lead for that project, update it's description if needed and wait for the student applications to start pouring :) 2. We also need to submit the actual application [4] of the XWiki organization to participate to the GSoC 2013 project so I would also like to ask you to review it so that we have a better chance of being selected into the program. 3. If you feel that you would like to help on improving XWiki's GSoC guides and application forms, please find tips for students [5] on XWiki's GSoC page, the student application form [6] and the lessons learned [7] from previous years participations. Thanks for your help, Eduard ---------- [1] http://www.google-melange.com/gsoc/homepage/google/gsoc2013 [2] http://www.google-melange.com/gsoc/events/google/gsoc2013 [3] http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/#HProposedProjects28… [4] http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/OrganizationApplicat… [5] http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/WebHome#HSuggestedwa… [6] http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/student+application+… [7] http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/LessonsLearned

12 years, 5 months

3
4
0 0

[xwiki-devs] Where is the Class Editor Wizard?

by markus.u.mueller

Dear listers, I am new to XWiki and I am trying to get familiar with it. I started doing the FAQ tutorial (http://platform.xwiki.org/xwiki/bin/view/DevGuide/FAQTutorialManual) but got stuck pretty early. I cannot find the Class Editor Wizard. I use an administrator account but when I search for "XWikiClasses" I do not get any results. Directly going to XWiki.XWikiClasses does also not help, the page does not seem to exist. I use XWiki-enterprise 4.5 (xwiki-enterprise-installer-windows-4.5.exe) on Windows XP. Any hints appreciated, Markus

12 years, 5 months

3
4
0 0

[xwiki-devs] [xwiki-dev] How to add new action in application made with AppWithinMinute

by Arnaud bourree

Hello, How to add new action in application made with AppWithinMinute? I've write entries import. I want to add "Import" action to WebHome page in addition to: Add new entry Edit application Delete application. Regards, Arnaud.

12 years, 5 months

2
3
0 0

[xwiki-devs] Nexus: Promotion Completed.

by Nexus Repository Manager

12 years, 5 months

1
0
0 0

[xwiki-devs] Nexus: Staging Completed.

by Nexus Repository Manager

12 years, 5 months

1
0
0 0

[xwiki-devs] Nexus: Promotion Completed.

by Nexus Repository Manager

12 years, 5 months

1
0
0 0

[xwiki-devs] Nexus: Staging Completed.

by Nexus Repository Manager

12 years, 5 months

1
0
0 0

[xwiki-devs] [Discussion] Set virtual=1 by default and deprecate the virtual mode API

by Eduard Moraru

Hi devs, According to the Roadmap of 5.0 [1][2] we will be deprecating the virtual mode API and moving to a virtual-by-default mode instead. The idea is that the multiwiki environment should be the default and, anyone wanting to use the single-wiki mode (as XE was doing in the past), will simply not create any subwiki. It is just pointless to have 2 products for such a simple fact and it also confuses users that have downloaded and started to use one product and later on realise that they needed the other. Also, when installing the wiki-manager and/or workspace extension(s) (because you might want to create subwikis/workspaces), there will be no need to stop the wiki, enable-virtual mode and restart it; all will be doable in the browser. Therefore, I`m sending this mail to ask your opinion about this topic, in case you might have something to say against it, and also to brainstorm on the required changes and implications on existing code so that the transition is as smooth and invisible as possible. Proposed changes: - Remove "xwiki.virtual" from xwiki.cfg(.vm) -- remove the usage of the "$xwikiCfgVirtual" maven property from xwiki-platform (, xwiki-enteprise and xwiki-manager) - Deprecate boolean com.xpn.xwiki.XWiki.isVirtualMode() (and the api.XWiki version) -- change its code to ((getVirtualWikisDatabaseNames(context).size() == 1) ? true : false) until it is removed by the deprecation process. Possibly needed changes: - Add main wiki default descriptor to xwiki-enterprise-ui (so that getVirtualWikisDatabaseNames includes the main wiki and also to avoid DNS issues (?) caused by how we handle virtual mode) -- or have it generated programmatically at startup if it does not exist (might be safer this way, since people might be using a different UI than xwiki-enterprise-ui) I will start working on this locally and see if I can spot other issues, but please share your thoughts. Thanks, Eduard ---------- [1] http://markmail.org/message/o6adfbscpidnn7zr [2] http://jira.xwiki.org/browse/XWIKI-8822

12 years, 6 months

7
22
0 0

[xwiki-devs] [ANN] XWiki 4.5.2 released

by Vincent Massol

12 years, 6 months

1
0
0 0

[xwiki-devs] Nexus: Promotion Completed.

by Nexus Repository Manager

12 years, 6 months

1
0
0 0

[xwiki-devs] Nexus: Staging Completed.

by Nexus Repository Manager

12 years, 6 months

1
0
0 0

[xwiki-devs] [Reminder] BFD#12 tomorrow the 14th

by Vincent Massol

Filter for tomorrow: http://jira.xwiki.org/issues/?filter=12203 Thanks -Vincent

12 years, 6 months

4
5
0 0

Re: [xwiki-devs] [Contrib] Push XSLT Macro to xwiki-contrib

by Arnaud bourree

Hello, I'd like to push XSLT Macro extension to xwiki-contrib. XSLT Macro extension is already available at http://extensions.xwiki.org/xwiki/bin/view/Extension/XSLT+Macro Extension is actually version 1.0 and I like to push also a new version 1.1 with style-sheet parameters management. My github username is rnoboo Regards, Arnaud.

12 years, 6 months

3
6
0 0

[xwiki-devs] [PROPOSAL] Make "create" right distinct so that running CreateAction on an existing document doesn't fail.

by Caleb James DeLisle

Hi, I would like to fix http://jira.xwiki.org/browse/XWIKI-8892 by making a distinct "create" right. Currently "create" is an alias for "edit" which fails if CreateAction is called on an existing document. CreateAction and the accompanying UI expect to be called on an existing document and for the name of the new document to be passed in a form parameter. I'm proposing adding a create right which aliases to "edit" on the space and wiki level but is not checked on the per-document level. WDYT? Caleb

12 years, 6 months

2
1
0 0

[xwiki-devs] Nexus: Promotion Completed.

by Nexus Repository Manager

12 years, 6 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs