infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-15387) Migrate community.apache.org to Pelican
Date Fri, 27 Oct 2017 14:02:00 GMT

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

Greg Stein edited comment on INFRA-15387 at 10/27/17 2:01 PM:
--------------------------------------------------------------

git vs svn is only personal preference. ... But github.com is a great tool for quick/easy
edits and pull requests, so I would recommend github (which then means gitbox and git).


was (Author: gstein):
git vs svn is only personal preference. ... But github.com is a great tool for quite/easy
edits and pull requests, so I would recommend github (which then means gitbox and git).

> Migrate community.apache.org to Pelican
> ---------------------------------------
>
>                 Key: INFRA-15387
>                 URL: https://issues.apache.org/jira/browse/INFRA-15387
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Website
>            Reporter: Rich Bowen
>            Priority: Minor
>
> I understand that we will eventually be moving (some of?) our web publishing infrastructure
off of the CMS and onto Pelican, or other Jekyl-ish publishing process.
> I'd like to have community.apache.org in the queue to be one of the sites that gets migrated,
once that is available.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message