systemml-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shirish Tatikonda <>
Subject Re: Project Website
Date Sat, 07 Nov 2015 22:44:58 GMT
I agree with Mike on keeping overview separate from full documentation.
However, in the systemml page, we should include all the basic information,
such as project technical overview, downloads, quick start guide,
contribution guidelines, link to issues, etc.

I think that hosting the "overview" website (basic info on the project,
link to the GitHub code repo, binary releases, snapshots of docs for the
releases, etc.) in a separate Git repo should be fine since it's not tied
to the core codebase.  For our "docs" (guides, language references, API
Javadocs, etc.), I vote that we keep them in their current location within
the SystemML Git code repo.  When we cut a release, we can just compile a
snapshot of the docs for that release and publish to the "overview"
website.  For the current, bleeding-edge version, we can just continue our
current practice of automatically deploying a subtree of the "docs" folder
from the master branch to the "gh-pages" branch and let GitHub render it
(as is the case for  This should be
beneficial in that it keeps the docs, which are intrinsically tied to the
current version of the codebase, collocated with the code.  Also, since the
"docs" folder is just a Jekyll project with Markdown, images, etc., we
won't have any compiled artifacts (HTML, etc.) in the repo.

- Mike

On Sat, Nov 7, 2015 at 9:54 AM, Luciano Resende <>

> Some follow-ups below:
> On Sat, Nov 7, 2015 at 10:15 AM, Luciano Resende <>
> wrote:
> > I have started to put together a strawman for the SystemML website using
> > Jekyll to generate the static version of the site. If you want to take a
> > look at the alpha version, please check the link below:
> >
> >
> >
> > My goal is to have some basic info available and publish the first
> > version, and continue to work as a team to make it better.
> >
> > Some decisions we need to make :
> > - Where should the source for the website go
> >    -- own repository versus
> >    -- collocated with the systemml source code main repo
> >
> >
> Based on previous discussion [1] and some best practices from other
> projects, I am planning to create a git repository for the SystemML
> website, and use svnpubsub to publish the website.
> The git repository could have been just a folder in the SystemML
> repository, but I was thinking that it won't match release cycles, etc and
> always have to be updated after the fact of a release, so a separate repo
> seemed better for me. Please let me know what are your thoughts.
> > - How are we going to integrate the project artifacts, such as docs,
> > javadocs, etc which needs to be versioned and accessible by version
> >    -- at the time of the release, we publish a snapshot to the website ?
> >    -- and how we publish all changes to the "current" documentation ? do
> > we actually need this ?
> >
> >
> >
> Based on the comment above, with svnpubsub, we would be able to store
> extra and versioned projects artifacts in svn, and link them from the
> website code.
> >
> > Anyway, please provide your feedback, and unless I get some very bad
> > feedback, hopefully we will get this published by monday.
> >
> [1]
> --
> Luciano Resende

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message