Re: question about including website source in release

2018-01-18 Thread Matthew Hayes
Got it, thanks Mark and Julian. On Thu, Jan 18, 2018 at 1:12 PM, Julian Hyde wrote: > I agree that standard practice is to not include the site. However, in > Calcite we do include the web site (or rather, the markdown files from > which the site is generated) since the web site is also our docu

Re: question about including website source in release

2018-01-18 Thread Julian Hyde
I agree that standard practice is to not include the site. However, in Calcite we do include the web site (or rather, the markdown files from which the site is generated) since the web site is also our documentation. So, your choice. Our site includes Jekyll template code under MIT license and s

Re: question about including website source in release

2018-01-18 Thread Mark Thomas
On 18/01/18 20:43, Matthew Hayes wrote: > Hi, > > Sorry if this is already answered somewhere but I couldn't find the > information. The source code that generates the Apache DataFu website > content [1] is currently included in the source code release. However the > source code for the website

question about including website source in release

2018-01-18 Thread Matthew Hayes
Hi, Sorry if this is already answered somewhere but I couldn't find the information. The source code that generates the Apache DataFu website content [1] is currently included in the source code release. However the source code for the website is independent from the source code and build files