Hi,
I've created a page on incubator with a collection of issues, problems and
ideas that could improve the way the normal user interacts with XWiki.
Initially the study was part of the "XWiki in 5 minutes" investigation
process, but now it covers all kind of usability issues, grouped by
category.
I know the list is not complete (and maybe never will) and the bad thing
about the list is that is manually generated (I've listed some keyword we
could use in JIRA in order to organize them), but it provides lots of ideas
and directions we could take for our next roadmaps.
Feel free to comment on the collection and please add more ideas and
suggestions you have in order to make XWiki easier and more fun, productive
to use.
Thanks,
Caty
Note: this was a test email. Trying to understand why we don't receive HTML emails anymore.
You may receive a few more while I'm testing.
Thanks
-Vincent
On Oct 19, 2011, at 12:18 PM, notifications(a)xwiki.org wrote:
>
> Hello Developers,
>
> This message is sent by XWiki. Here are the documents in your watchlist that have been modified since the last notification:
>
> + XWiki.org
> |
> | + XWiki
> | |
> | | + XWikiNotifications (XWiki.XWikiNotifications): http://www.xwiki.org/xwiki/bin/view/XWiki/XWikiNotifications
> | | |
> | | | - On 2011/10/19 12:17, the document has been modified by Vincent Massol
> | |
> | | + XWiki Preferences (XWiki.XWikiPreferences): http://www.xwiki.org/xwiki/bin/view/XWiki/XWikiPreferences
> | | |
> | | | - On 2011/10/19 12:05, the document has been modified by Vincent Massol
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications
Hi devs,
The proposal is to use artifactid as directory names.
Note that this is what I did for commons and rendering when I did the move to top level project. You can check how it looks like here:
http://svn.xwiki.org/svnroot/xwiki/commons/http://svn.xwiki.org/svnroot/xwiki/rendering/
I suggest we keep one strategy only for consistency.
Some discussion here too:
http://www.sonatype.com/people/2011/01/maven-tip-project-directories-and-ar…
I know there are some cons (see my comment in the link above) but overall I find it simple to implement and with autocompletion not such a big issue.
WDYT?
If you don't like this then please propose an alternative solution and remember that we'll need to refactor commons and rendering in this case too.
Thanks
-Vincent
Hi devs,
There are a few topics that are not supposed to be public or that would be better be not public.
One such topic is when we want to VOTE someone as a committer. It's very uncomfortable to do this in the open for the following reasons:
* committers are tempted to VOTE +1 since voting negatively is seen publicly, including by the person being voted on
* it's very undelicate to have this in the open especially if the person is voted down since that'll affect that person's morale and future participation in the project
So I'd like to propose creating a committers(a)xwiki.org list with the following characteristics:
* private, visible only to committers
I also propose it to use it for voting committers.
WDYT?
Thanks
-Vincent
Hi devs,
I'd like to propose to improve the Component Override mechanism (currently based on component-overrides.txt, see http://extensions.xwiki.org/xwiki/bin/view/Extension/Component+Module#HOver…). We have a limitation right now in that we can only have one level of override. The issue is that we need more levels even right now since we have component impls in xwiki-commons or xwiki-rendering that are overridden in xwiki-platform (thus using component-overrides.txt). This means that users cannot provide their own implementations.
Thus I'd like to propose the following:
* Deprecate the component-overrides.txt file
* Add an optional priority level number that you can specify in the components.txt
* I propose the following format in components.txt: <priority level>:<full package path to implementation as it is now>. Ex: 1000:org.xwiki.rendering.internal.macro.DefaultMacroManager
* Use a default priority of 1000 when not specified (same as for our Macro)
* Guarantee in the documentation that all components that the XWiki project provides never have priorities under, say, 100. This is so that users who want to override know that if they use a priority under 100 their impls will always win.
* Use a priority of 500 in platform when overriding components found in commons or rendering.
Here's my +1
Thanks
-Vincent
I would like to take this time to welcome you to our hiring process
and give you a brief synopsis of the position's benefits and requirements.
If you are taking a career break, are on a maternity leave,
recently retired or simply looking for some part-time job, this position is for you.
Occupation: Flexible schedule 1 to 3 hours per day. We can guarantee a minimum 20 hrs/week occupation
Salary: Starting salary is 3000 EUR per month plus commission.
Region: European Union.
Please note that there are no startup fees or deposits to start working for us.
To request an application form, schedule your interview and receive more information about this position
please reply to Travis(a)it-jobsearch.com with your personal identification number for this position IDNO: 4799
I would like to take this time to welcome you to our hiring process
and give you a brief synopsis of the position's benefits and requirements.
If you are taking a career break, are on a maternity leave,
recently retired or simply looking for some part-time job, this position is for you.
Occupation: Flexible schedule 1 to 3 hours per day. We can guarantee a minimum 20 hrs/week occupation
Salary: Starting salary is 3000 EUR per month plus commission.
Region: European Union.
Please note that there are no startup fees or deposits to start working for us.
To request an application form, schedule your interview and receive more information about this position
please reply to Alexander(a)it-jobsearch.com with your personal identification number for this position IDNO: 1470
I would like to take this time to welcome you to our hiring process
and give you a brief synopsis of the position's benefits and requirements.
If you are taking a career break, are on a maternity leave,
recently retired or simply looking for some part-time job, this position is for you.
Occupation: Flexible schedule 1 to 3 hours per day. We can guarantee a minimum 20 hrs/week occupation
Salary: Starting salary is 3000 EUR per month plus commission.
Region: European Union.
Please note that there are no startup fees or deposits to start working for us.
To request an application form, schedule your interview and receive more information about this position
please reply to Brandon(a)it-jobsearch.com with your personal identification number for this position IDNO: 7473
I would like to take this time to welcome you to our hiring process
and give you a brief synopsis of the position's benefits and requirements.
If you are taking a career break, are on a maternity leave,
recently retired or simply looking for some part-time job, this position is for you.
Occupation: Flexible schedule 1 to 3 hours per day. We can guarantee a minimum 20 hrs/week occupation
Salary: Starting salary is 3000 EUR per month plus commission.
Region: European Union.
Please note that there are no startup fees or deposits to start working for us.
To request an application form, schedule your interview and receive more information about this position
please reply to Young(a)it-jobsearch.com with your personal identification number for this position IDNO: 0230
I would like to take this time to welcome you to our hiring process
and give you a brief synopsis of the position's benefits and requirements.
If you are taking a career break, are on a maternity leave,
recently retired or simply looking for some part-time job, this position is for you.
Occupation: Flexible schedule 1 to 3 hours per day. We can guarantee a minimum 20 hrs/week occupation
Salary: Starting salary is 3000 EUR per month plus commission.
Region: European Union.
Please note that there are no startup fees or deposits to start working for us.
To request an application form, schedule your interview and receive more information about this position
please reply to Normand(a)it-jobsearch.com with your personal identification number for this position IDNO: 8595