Hi Roman, Roman Friesen wrote:
Hello,
I have just created the jira task "XWIKI-4375": http://jira.xwiki.org/jira/browse/XWIKI-4375
<description> As you probably know the Ubuntu team has starter the project "One Hundred Paper Cuts": https://launchpad.net/hundredpapercuts
They define a paper cut as (https://wiki.ubuntu.com/PaperCut): * a bug, or an unintended problem occurring within an existing piece of software, * the presence of which makes a computer more difficult or less pleasant to use, * that is easy to fix, * that the average user would encounter during his/her first day of using
XWiki is a great software but it contains also a lot of "paper cuts". Such little but annoying bugs or usability issues would be a great entry point for new xwiki developers, because they are easy to fix. But also experienced xwiki commiters could relax fixing this paper cuts after their hard work ;)
The proposal would be to start a similar task/project for identifying paper cuts in xwiki. Related jira issues could be just linked to this jira task." </description>
I have already linked one paper cut to this jira task - XWIKI-3335. Any feedback would be very appreciated.
Your initiative is good, but IMO the easiest way to promote an issue is to vote for it. Right now XWIKI-3335 has no votes (and nobody watching it, besides me who created it). Regarding XWIKI-3335, it's not hard to fix indeed but it can slow down the editing (navigating with the arrow keys precisely) because the editor will have to make a non trivial test each time you press the left/right arrow key (what's the current caret position? what's the previous/next _visible_ node relative to the current caret position? Is that node a macro container?). I can fix it but I need your vote. Thanks, Marius
Best regards, Roman
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users