[
https://issues.apache.org/jira/browse/SOLR-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608084#comment-13608084
]
Cassandra Targett commented on SOLR-4618:
-----------------------------------------
bq. one possibility is to follow the same model that Lucid has been using, and
"clone" the confluence space for each release
I'm pretty sure there's a way to make that happen without needing asfinfra
every time. If we can get the Copy Space plugin installed (it may already be
there), then all it requires is "space admin" rights. System admin rights will
be needed to import what I just uploaded, then with space admin rights, a
subset of users with admin permissions should be able to copy that to make new
spaces for new versions. At Lucid it's more complicated because we have an
internal Confluence and an external Confluence; with only instance to work
with, the Copy Space plugin should be fine and Atlassian says it only needs
space admin privs. Being able to copy spaces is key, so need to figure out the
policy on permissions there.
bq. another possibility would be use the confluence wiki to always represent
the "live" state of things, and use confluences PDF exporting to generate a PDF
copy on each release.
I think opinions will vary about that...we actually have 2 models at Lucid. For
the Solr Ref Guide, the latest version was both online and in PDF, while older
versions were pdf-only. For the LucidWorks Search product, all the versions doc
are online. I can't really tell which is better from a user perspective, but I
can tell you which is easier, which is only having one "live" state at a time.
When you have all the versions online, each one of those versions is a
different space, and spaces are pretty much managed as separate entities, you
end up after a time with a lot of spaces to manage and a good amount of really
duplicated content across them all.
> Integrate LucidWorks' Solr Reference Guide with Solr documentation
> ------------------------------------------------------------------
>
> Key: SOLR-4618
> URL: https://issues.apache.org/jira/browse/SOLR-4618
> Project: Solr
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 4.1
> Reporter: Cassandra Targett
> Attachments: NewSolrStyle.css, SolrRefGuide4.1-ASF.zip
>
>
> LucidWorks would like to donate the "Apache Solr Reference Guide", maintained
> by LucidWorks tech writers, to the Solr community. It was first produced in
> 2009 as a download-only PDF for Solr 1.4, but since 2011 it has been online
> at http://docs.lucidworks.com/display/solr/ and updated for Solr 3.x releases
> and for Solr 4.0 and 4.1.
> I've prepared an XML export from our Confluence installation, which can be
> easily imported into the Apache Confluence installation by someone with
> system admin rights. The doc has not yet been updated for 4.2, so it covers
> Solr 4.1 so far. I'll add some additional technical notes about the export
> itself in a comment.
> Since we use Confluence at LucidWorks, I can also offer assistance getting
> Confluence set up, importing this package into it, or any other help needed
> for the community to start using this.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
