Mmm, I missed so say something about what leads me to write this email, let me
explain.
Sharan shared this tweet
https://twitter.com/opensourceway/status/766000900582158336
I then looked into the article and finally landed there
https://github.com/nayafia/contributing-template/blob/master/CONTRIBUTING-template.md
I thought it could be a good idea to have this adapted in our trunk root folder
I remember Sharan also shared a tweet where it was more question of roadmap. I
can't find it back, but that was also one of the reasons I revivified
https://cwiki.apache.org/confluence/display/OFBADMIN/New+Features+Roadmap+-+Living+Document
Jacques
Le 20/08/2016 à 07:29, [email protected] a écrit :
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?
