[jira] [Closed] (INFRA-6342) Seeking infra review of process for importing an existing confluence space export zip into CWIKI: SOLR-4884

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

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

Gavin closed INFRA-6342.
------------------------

    Resolution: Fixed
      Assignee:     (was: Gavin)

https://cwiki.apache.org/confluence/display/solr/Apache+Solr+Reference+Guide 
                
> Seeking infra review of process for importing an existing confluence space export zip into CWIKI: SOLR-4884
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: INFRA-6342
>                 URL: https://issues.apache.org/jira/browse/INFRA-6342
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Confluence
>            Reporter: Hoss Man
>
> LucidWorks has donated a sizable amount of Solr documentation to the ASF in the form of a confluence space export.  The parent issue tracking the full discussion about how the Lucene/Solr project intends to use these docs (and containing the ZIP export as an attachment) is SOLR-4618.
> I have broken out a sub-issue SOLR-4884 focused solely on the necessary steps to import the content into CWIKI to replace the (currently empty) "SOLR" space.  As far as I can tell, I already have all the necessary confluence-admin permissions to handle this import myself, but I wanted to give infra an opportunity to review/object before I proceed.
> (Note: there has been some discussion in the comments of SOLR-4618/SOLR-4884 about whether additional confluence plugins may be needed/useful for these docs -- my first priority is getting the content imported so we can review it and assess -- I will not consider adding any plugins w/o filing explicit INFRA Jiras first)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira