Hi, Thanks Ludovic for the roadmap and the diagrams. AFAIR you mentioned that you were using IntelliJ. Is that your XWiki.com default tool? How many of us like me will be using Eclipse and or Rose and or AspectJ? Or some other suggestion. If we were round-trip engineering then there would be a question to discuss about diagram import/export between tools. I am a committed automatic documentalist. Round-trip seems to me the sensible way to meet the demand for learning materials with guaranteed accuracy and currency. You're current class diagrams are jpegs. We have Graphviz as a built in tool. WDYT?
I'm not sure the XWiki documentation should be copied over to the offline wiki install. I'm more a fan of a link to the online documentation.
Sorry to disagree but I want full documentation for my own experiments on my own offline wiki so I need a downloadable documentation framework.
Now I think we should move the documentation to the xwiki.org web site in a specific area. Using some XWiki classes, we can mark the documentation articles that are specific to XWiki.com.
We can definitively open the default wiki to developer's editing so that people can contribute to it's improvement. We can then have an automated export to XML so that we can release it on ObjectWeb regularly.
Documentation is a weak part of XWiki. We are definitively looking for people that can help in this area.
I have started listing some of the use cases. They appear to start something like: __UC__1. Render XWiki Documents __UC__1. Verify Authorisation and Rights __UC__1. Read Documents __UC__1. Access and Modify Documents, Objects __UC__1. Search Documents and Objects __UC__1. Read User and Rights __UC__1. Read/Write Object/Classes There are plenty turning up nearly every day on Jira but they are technical. IMHO The current (largely implicit) business use case hierarchy doesn't quite seem abstract enough or explicitly and correctly nested. It just seems that way, I have no examples cos I'm talking about a missing level or lack of separation of levels. IMHO The classes seem too large to me and seems to mix model content and model management functions in the same class. Is that unfair? Regards Jim PS As an ex editor I volunteer to correct the english on the XWiki sites if that's any use? If you want to mail me any drafts offline I will happily try and correct those.