[
https://issues.apache.org/jira/browse/SOLR-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-4618:
------------------------------
Assignee: Hoss Man
I'll take the lead on trying to move forward with importing and setting up a
process for maintaining things.
{panel:title=Notes hoss made based on poking arround today}
* https://cwiki.apache.org/INFRA/cwiki.html
* PMC members can be in the confluence admin group
** i already am a confluence admin
** we can define our own groups/users
** we can specify fine grained control over actions users can take (ie: only
committers of a certain group can edit pages, any user can comment, etc...)
* we can add new spaces as needed, but there is some non trivial overhead
associated with adding spaces, not to mention the risk of forking, so sticking
with a single space tracking the "stable" branch and exporting as PDF on
release seems like the simplest path forward
* there is a process for setting up edit notifications to go to the commit list
** it involves creating a user using hte commits@lucene mailing address, and
setting that user up to "watch" pages.
* apache policy is that projects can't link directly to confluence wiki pages,
instead an autoexport plugin is used...
** autoexport plugin details
***
https://marketplace.atlassian.com/plugins/com.atlassian.confluence.extra.autoexport
*** https://ecosystem.atlassian.net/browse/AUTOEXP
** solr space export compared to raw solr space...
*** https://cwiki.apache.org/SOLR/
*** https://cwiki.apache.org/confluence/display/SOLR/Index
* note that the autoexport plugin doesn't display comments by default
** it however does support per-space customizable (velocity) templates for the
autoexported pages
** the atlassian docs on developing templates is like a kafka novel, but even
when i did find stuff, it was hard to tell what was applicable since the
autoexport plugin does it's own velocity template rendering, and the supported
context/functions might not be be the same as in normal confluence templates
*** a velocity expert might be able to help figure this out better
** i took a stab are trying to borrow the "#renderComments()" logic i found in
other confluence page templates in the autoexport template, but it didn't work
9shocker)
** worst case scenario, if we can't access the default logic/template for
rendering comments, we can evidently re-invent our own wheel using the java
methods in our customized template...
***
https://docs.atlassian.com/atlassian-confluence/latest/com/atlassian/confluence/pages/Page.html
***
https://docs.atlassian.com/atlassian-confluence/latest/com/atlassian/confluence/pages/Comment.html
*** {code}
<div class="test">
<h3>Hoss'ss test</h3>
<p>trying to access comments in the auto-export template</p>
#set ($comments = $page.comments)
<ul>
#foreach ($comment in $comments)
<li class="smalltext"><b>$comment</b> - $comment.displayTitle
($comment.creatorName)<br/>
<p>$comment.bodyAsString</p> <!-- doesn't seem to work ... shocker -->
</li>
#end
</ul>
</div>
{code}
*** i clearly have no idea what i'm doing here, and it probably isn't a good
idea to try and build this out and maintain it manually if there really is no
way to use the native comment rendering inside our autoexport template, but i
figured i'd show what i had.
* even if we could make hte autoexport pages displya comments in a sane way,
the autoexport is only triggered by page edits, not comments - so we would need
to cron the autoexport
** not sure how to do that
** not sure infra would go for it.
{panel}
My instinct is telling me that we should punt on the issue of allowing page
comments, and instead i'll move forward with focusing on:
* get the content loaded and looking for plugin errors like Cassandra mentioned
might happen
* verifying that autoexports seem to work if/when edits are made
** so far so good, but i don't know how well the autoexport plugin is going to
handle a wiki space this big
* test out the PDF export
* document/automate doing a PDF export so it's easy to do whenever we release
* lock down edits & setup confluence permissions for other committers/PMC
members
* test & setup edit notifications -> commits@lucene
> 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
> Assignee: Hoss Man
> 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]
