reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-4) Create a REEF website on Apache infrastructure
Date Tue, 14 Oct 2014 15:13:33 GMT

    [ https://issues.apache.org/jira/browse/REEF-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171053#comment-14171053
] 

Markus Weimer commented on REEF-4:
----------------------------------

Also, we should make sure that the new site adheres to the branding guidelines for an incubator
project laid out [here|http://incubator.apache.org/guides/branding.html]

> Create a REEF website on Apache infrastructure
> ----------------------------------------------
>
>                 Key: REEF-4
>                 URL: https://issues.apache.org/jira/browse/REEF-4
>             Project: REEF
>          Issue Type: Task
>          Components: Website
>            Reporter: Markus Weimer
>
> REEF has a web presence at http://www.reef-project.org That presence is built using WordPress
and run on a Linux VM hosted on Microsoft Azure. 
> As per [this guide|http://incubator.apache.org/guides/sites.html] we shall have a website
on Apache Infrastructure. The guide also assumes that the website is static (e.g. not require
PHP and MySQL like WordPress does). 
> Hence, we have two options:
>   # Figure out how to move WordPress onto Apache servers.
>   # Drop WordPress and make a static website as per the instructions.
> The actual choice shall be left to the person doing the work, but I would favor the second
option, as it lowers the long-term cost of maintaining the site: REEF would not be on the
hook for installing security updates on the stack that runs WordPress.



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

Mime
View raw message