Hi devs,
I’d like to propose some changes to the governance related to paying extensions and extensions.xwiki.org and the Extension Manager.
* Make extensions.xwiki.org an extension repo for free and open source extensions only. This is the case till now but during the last governance change VOTE we had said we could allow non-free versions. After more thinking I believe it’s better that companies who want to have paying apps provide them through their own extension repository. One issue is that these companies will need to have users register and log in and we cannot do that on xwiki.org.
* Allow top sponsoring companies to have their extension repository defined in the default XWiki configuration (in xwiki.properties). I’m proposing that sponsoring companies require 3 active committers to be able to have their stores listed by default in the XWiki config. The same would be done on nexus.xwiki.org which would proxy any maven repo from a top sponsoring company. Note that any company (even one not participating to the development of the XWiki project can provide an extension repository with some instructions for users to add their repo to their config - This point here is only about having some repos by default).
* Allow the top sponsoring company (TSC) an advertising space on the home page of extensions.xwiki.org to advertise extensions it wishes to promote.
Please cast your votes.
Here’s my +1
Thanks
-Vincent
Hello sir/ma'am
This is Shilpi Singh pursuing B.tech in information technology from Indira
Gandhi Delhi Technical University for women
I wish to contribute to mozilla.
I am really keen to get involved in an open source project.
I am proficient in c, c++,php,html,css, java with frameworks, javascript.
Please do reply if i can contribute to something in some open source
project.
Thank you
Shilpi Singh
B.Tech student at Indira Gandhi Delhi Technical University for Women
Hello sir/ma'am
This is Shilpi Singh pursuing B.tech in information technology from Indira
Gandhi Delhi Technical University for women
I wish to contribute to mozilla.
I am really keen to get involved in an open source project.
I am proficient in c, c++,php,html,css, java with frameworks, javascript.
Please do reply if i can contribute to something in some open source
project.
Thank you
Shilpi Singh
B.Tech student at Indira Gandhi Delhi Technical University for Women
Thanks you.
Merry Christmas 2016 and a Happy New
Year. I wish you a good health
2017 the year without bounced mails, better stars war (ie without death star) and more excellent opensource project like xwiki!
Pascal
--------------------------------------------
En date de : Ven 23.12.16, Vincent Massol <vincent(a)massol.net> a écrit :
Objet: [xwiki-users] Merry Christmas 2016
À: "XWiki Developers" <devs(a)xwiki.org>, "XWiki Users" <users(a)xwiki.org>
Date: Vendredi 23 décembre 2016, 18h44
Hi everyone,
Let me wish everyone a Merry Christmas 2016 and a Happy New
Year.
May you continue to use XWiki in 2017!
And let’s make 2017 the year when XWiki takes the world by
storm… :)
Thanks
-Vincent
XWiki developer
Hi everyone,
Let me wish everyone a Merry Christmas 2016 and a Happy New Year.
May you continue to use XWiki in 2017!
And let’s make 2017 the year when XWiki takes the world by storm… :)
Thanks
-Vincent
XWiki developer
Hello developers. I'm here to propose a new template in XWiki to help users
creating container-oriented pages.
= Problem =
UC1: Users don't always understand the Nested Pages concept. They are lost
because they know the concept of Folders and Files and they are used to it,
and then we ask them to switch to something new that breaks their habits.
UC2: Users often need a page that will be the container of some others
(think about the typical "Code" space that we have in all applications) and
they'd like to see quickly all children of that container.
= Proposition =
* Introduce a Folder template the user can chose when she creates a page.
* This folder template displays the children of the page
** It could even be a Dashboard with the children pages on the left, and an
Activity Stream on the right.
== Drawback ==
The workflow of creating a page that is a folder instead of directly create
a folder might be confusing.
== Screenshots ==
Screenshot of my proposition are available there:
http://design.xwiki.org/xwiki/bin/view/Proposal/FolderTemplate#HScreenshots
Please answers your ideas on this mail thread, not on the wiki.
Thanks,
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi devs,
The story
========
1) We introduced some new translations keys in https://github.com/xwiki/xwiki-platform/commit/5c50e2e88bb7cf592c1ecedcf0f3…
That was done in XWIKI-12431 (Adapt the "rename" action for nested documents), i.e. in 7.2M3
2) We modified the keys in https://github.com/xwiki/xwiki-platform/commit/12ec17d1c486935162581d47bbf1…
That was done in XWIKI-13067 ("Rename: Change the label to make it clear that both links and backlinks are updated or have 2 separate options”), i.e. in XWiki 8.0-rc-1, 7.4.3
3) The consequence is that all translations got broken, resulting in problems such as http://jira.xwiki.org/browse/XINFRA-219. However this issue reports the issue only for French but it’s likely that it broke the translations for other languages.
The learnings
===========
1) We must never change the format of existing translation keys. This is the equivalent of breaking an API. Instead we need to go through deprecation of existing keys and introduction of new keys, even though it’s a pain. http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HTransla… would probably benefit from additional explanations too.
2) We would need a tool in the quality profile of our build/CI that would break the build if someone changes the format of a translation.Easiest would be a tool that compares the English translations on master vs the last released version and breaks if there’s a difference in parameter (i.e. {N} syntax).
3) We need to decide if A) we keep the current change done in XWIKI-13067 or B) revert them and revert/adapt the changes already brought to some translations keys (as it was done for FR). For this we need to evaluate the extent of the damage.
Any volunteer for 3)? :)
Thanks
-Vincent
Hi,
This is a idea proposal for an Administration Overview that:
A. Provides generic/global information about the instance like 'version',
'instance id', etc.
B. Provides a summary of usage listing count of major entities (wikis,
users, pages, extensions, etc.)
C. Lists demo content installed in the wiki
D. Provides a way for administrators to subscribe to the XWiki Community
I'm curios which of the above section sounds interesting to you and would
like to see inside the product. Also maybe you have other ideas of what is
missing or could be represented better.
Thanks,
Caty
Hi devs,
We need to debug our udpate_ow2() which is broken ATM.
It does several curl calls but there’s a “-o /dev/null” that prevents seeing errors.
It would be great if the next RM could remove those and report the error, (and even possibly work to fix the problem with the others).
Thanks
-Vincent
Hello,
A new version of the Nested Pages Migrator Application is available. See
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+…
You can install or upgrade with the Extension Manager.
This version brings a new tool that help you to check if the migration is
needed.
Thanks,
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi devs,
I have an XWiki application that has a template provider which allows the
users to create application entries anywhere on the wiki using the Create
Page menu. I would like to control entirely how application entries are
displayed to the user. I can do this partially from my sheet but:
* I can't control the panels. I would like to display panels that are
specific to my application whenever a user is viewing an application entry,
no matter where the application entry is located.
* I can't control the color theme or the icon theme. I would like to use a
custom color theme and icon theme without affecting the other pages from
the wiki.
* I can't control the layout (the skin). I can hide the extra tabs from the
sheet but I can't hide a panel column or control the panel column width.
One solution to fix my problem is to introduce XClass Preferences, same as
we have page and wiki preferences. XClass preferences would have priority
over page and wiki preferences, inheriting from them. We can implement it
using either a naming convention, <ClassName>Preferences, or using some
xobject on the XClass, similar to the ClassSheetBinding xobject.
Do you see any problem with solution? I can think of one: access rights.
Does it make sense to have access rights specific to an XClass? E.g. "only
this group can edit instances of this XClass".
Do you think it is worth implementing? Another solution would be to allow
the sheet to overwrite some of the preferences, but the problem is that the
sheet is executed after the page HTML has started to be written to the
response.
Thanks,
Marius
Hi devs,
Here’s a use case:
* We set up a clone of xwiki.org (in order to upgrade it for example)
* The issue: those other instances of xwiki.org send watchlist mails or the IRC bot on them hijack the #xwiki channel (preventing the real xwiki.org IRC bot to connect)
The proposal:
* Introduce a maintenance configuration parameter in xwiki.properties.
* Have the scheduler obey this mode and not trigger any job when it’s on
* Have the IRC Bot module also obey this mode and not try to connect when it’s on
WDYT?
Thanks
-Vincent