[
https://issues.apache.org/jira/browse/SOLR-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608020#comment-13608020
]
Hoss Man commented on SOLR-4618:
--------------------------------
bq. I also think we want to lock down these docs. I think this is important
enough stuff that we should have committers based on documentation merit. It's
really just as important as the code. Users should still be able to comment to
make suggestions or ask for clarifications or whatever, but I'm not happy with
how much misinformation has creeped into our current wiki
Cassandra is more of a confluence expert them me, but confluence definitely has
the ability for user ACLs and letting all users post comments on a page while a
specific subset of users can edit -- from whatever i remember the ASF
confluence setup should definitely support this for allowing committer only
edit access, because it's neccessary if you want to bundle any confluence
edited content as part of a release (the fact tha we aren't doing this in moin
moin is why we can't legally bundle up the wiki and ship it as docs in the
release)
bq. * separate page for minor errata about previous releases (since they would
just be PDFs if we go with that strategy).
isn't that just CHANGES.txt?
bq. * separate page for trunk-only changes.
...
bq. After we release 4.5 or 4.9 or whatever is the last minor one, we work on
integrating the trunk changes before 5.0 and clear that page for 6.0
I'm okay with that ... but i'm suprised you're suggesting it -- you're usually
the biggest proponent of keeping trunk in a state that it could, in theory, be
released as X.0 on a moments notice -- this type of a approach would mean a
decent amount of doc work needed to make a bunch of doc changes related to
trunk specific features/improvements just before an X.0 release.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
