Thanks Pierre,
This is an idea to discuss indeed. You mean a repo outside of the ASF repo or a
different branch than trunk or website?
Jacques
Le 20/08/2016 à 08:27, Pierre Smits a écrit :
IMO, we should not have this kind of documentation in the standard
repository, as it creates bloatware in the application. Better would be to
have it it in seperate repository.
Best regards
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
On Sat, Aug 20, 2016 at 7:29 AM, [email protected] <[email protected]>
wrote:
Hi,
Not so long ago Jacopo suggested that we use our versionning system (ie
currently Subversion) to maintain the documentation. Or at least the most
important or entry points of the documentation which will still stay on our
wiki (ie Confluence)
I think that by creating MarkDown files (or other types but we already
started with README.ME for Gradle) and implementing
https://issues.apache.org/jira/browse/OFBIZ-7723 "Use Pandoc to integrate
our README.MD from repo to Confluence" we could not only easily share the
burden of maintaining documentation but also have an easier and more
reliable way for it (believe me Confluence has still its quirks when
updating big pages)
So we would create .MD files and locally relies to transform them in .HTML
files still in the svn repo, and then they should be automatically
integrated and updated in Confluence by its HTML connector plugin
These files would be in the trunk branch or the website one.
Opinions?
