26 Aug
2016
26 Aug
'16
2:03 p.m.
Hello VIncent,
So for me the important part is for you to develop
your solution in a separate module in xwiki-contrib as a demonstator and possibly start
using it on some contrib project to validate it. The alternative is to work on XFF and
finish it.
Well. That brings the question back: how many are using it?
Obviously, I see almost no-one.
As long as:
- it is not complete
- it is not used by developers big time
... it will not be considered useful.
So... requesting to "go away" is very close to what you're asking, I feel.
In the contrary, I believe that changing the XAR plugin in a fully
conservative way is the way to go if one wants incremental progress.
Can it be that you did not notice, it is fully backwards compatible?
Personally I’m not a big fan at all of modifying the
existing XAR plugin for various reasons:
* We don’t know yet what solution we’ll choose in the future. At this point in time I
even have a preference for XFF. So it wouldn’t be fair and nice to modify the existing XAR
plugin with your solution and then have to remove the code if we don’ want it in the
future.
But obviously the time has not been invested about it.
All issues are closed for XFF.
* It will be much simpler for you to develop your own
project in xwiki-contrib since you’ll have commit access (which you won’t have in
xwiki-commons).
That's a moot criterion.
My code is really not a big change and also not very high risk.
Paul