You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Phillips (JIRA)" <ji...@apache.org> on 2014/04/27 03:45:15 UTC
[jira] [Comment Edited] (JCLOUDS-147) Transfer jclouds API docs
site and generation process to jclouds.apache.org
[ https://issues.apache.org/jira/browse/JCLOUDS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982152#comment-13982152 ]
Andrew Phillips edited comment on JCLOUDS-147 at 4/27/14 1:43 AM:
------------------------------------------------------------------
Another quick fix option: fork or clone the repo(s) under github.com/jclouds or (perhaps wiser and less likely to cause confusion) to create a jclouds-docs GitHub account and clone the repos there?
was (Author: andrewp):
Another quick fix option: fork or clone the repo(s) under github.com/jclouds?
> Transfer jclouds API docs site and generation process to jclouds.apache.org
> ---------------------------------------------------------------------------
>
> Key: JCLOUDS-147
> URL: https://issues.apache.org/jira/browse/JCLOUDS-147
> Project: jclouds
> Issue Type: Task
> Components: docs
> Reporter: Andrew Bayer
> Assignee: Andrew Phillips
>
> We should fold the apidocs into the main jclouds site, and we should fold the apidocs site generation process into the release process (doc'd at https://wiki.apache.org/jclouds/Releasing%20jclouds).
--
This message was sent by Atlassian JIRA
(v6.2#6252)