[jira] [Assigned] (INFRA-11437) Migrate accumulo site to git

["Daniel Gruno (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Gruno reassigned INFRA-11437:
------------------------------------

    Assignee: Daniel Gruno

> Migrate accumulo site to git
> ----------------------------
>
>                 Key: INFRA-11437
>                 URL: https://issues.apache.org/jira/browse/INFRA-11437
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git, Website
>            Reporter: Christopher Tubbs
>            Assignee: Daniel Gruno
>
> When Accumulo migrated from svn to git, our site was left behind at:
> https://svn.apache.org/repos/asf/accumulo/site
> The committers wish to migrate to a git-based website, as described at:
> https://blogs.apache.org/infra/entry/git_based_websites_available
> This was discussed and decided by lazy-consensus in the thread at: http://mail-archives.apache.org/mod_mbox/accumulo-dev/201603.mbox/%3CCAL5zq9Yo-GB_tKpdv8yfRGQ%3D7-mDyXF4E2TWn14V1SjETHg3gw%40mail.gmail.com%3E
> Based on the recent questions I asked on the infrastructure mailing list, I understand that git-based sites are currently static hosting only (no CMS, staging, or other automatic rendering), which is fine with us because we prefer to use jekyll to build our static site.
> Our site's contents exist in our main git repository:
> https://git-wip-us.apache.org/repos/asf/accumulo
> in the branch called "accumulo.apache.org" and are ready to be published immediately.
> The jekyll source we use to render the contents of this branch are stored in "gh-pages" branch, but I understand that that doesn't matter right now since ASF does not currently provide a service for automatic building of jekyll sites. (noted here in case a future service exists)
> The accumulo svn area at svn.apache.org will no longer be needed for any development or project management, and can be preserved in a read-only mode, although we'll probably want to remove the current contents of trunk/ and update the README pointer to the new location first.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)