+1 too
Right now the site content is in https://github.com/apache/arrow-site
Thanks Uwe for volunteering!
On Tue, Jan 3, 2017 at 11:51 PM, Julian Hyde wrote:
> If you decide to take this approach, feel free to copy whatever you
> like from Calcite (not that you need my permission - this is ASL!)
If you decide to take this approach, feel free to copy whatever you
like from Calcite (not that you need my permission - this is ASL!) and
please let me know if can help.
On Tue, Jan 3, 2017 at 3:46 PM, Jason Altekruse wrote:
> +1
>
> Jason Altekruse
> Software Engineer at Dremio
> Apache Arrow C
+1
Jason Altekruse
Software Engineer at Dremio
Apache Arrow Committer
On Tue, Jan 3, 2017 at 2:59 PM, Leif Walsh wrote:
> +1 this sounds pretty sane
> On Fri, Dec 30, 2016 at 06:02 Uwe L. Korn wrote:
>
> > I just had a look over the Apache Calcite approach and I like it very
> > much. Both, fr
+1 this sounds pretty sane
On Fri, Dec 30, 2016 at 06:02 Uwe L. Korn wrote:
> I just had a look over the Apache Calcite approach and I like it very
> much. Both, from a technical and the structural (i.e. keeping the
> website in the main repo). This will enable us to have the format spec
> on Git
I just had a look over the Apache Calcite approach and I like it very
much. Both, from a technical and the structural (i.e. keeping the
website in the main repo). This will enable us to have the format spec
on Github, let users edit the spec and the homepage via PRs and keep
them both linked and in
At Calcite we have a simple approach that Arrow could mimic. We keep our
documentation under the source tree in .md (GitHub markdown) format and we use
Jekyll to generate into the svn repo that backs the Apache web site. Due to the
markdown format it’s easy for committers and non-committers to w
hi folks,
Our lack of organized documentation outside README documents on GitHub
is making it harder for people to pick up and use the project. What's
the easiest way to set up publishing tools that committers can access,
so we can add a /docs page on http://arrow.apache.org/, or links to
the spec
